This may be a stupid question, but how can one create a truly self-contained portable executable using ThinApp?
Each time I try to create a ThinApp version of a game (Fallout 1-2, if you must ask), it creates a single .EXE. When you open said EXE it generates a mess of files: Registry.tvr.backup, Registry.rw.tvr.lck, Registry.rw.tvr, and a directory called "%ProgramFilesDir%".
Am I missing something? How do I make a portable version of an app that doesn't need to generate these files outside of itself when opened?
Thanks in advance! Love the site!
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
for onething we don't use thinapp, most copies of Thinstall/thinapp are illegal and should not be used
your friendly neighbourhood ex-Moderator and developer Zach Thibeau
I will look into the other alternatives people suggest on this site.
Thanks for the help.
As said, we don't use ThinApp here.
But I can say that these files are necessary to store the modifications done when running the application (ie: Configuration files, etc), which is completely normal.
Think of a ThinApp application like a game disc, and these files like a gamesave. Without these, you'll fall back at the original state/beginning of the game everytime you launch it.