Now, with something like save files or settings, such files are created by your virtualized application during normal operation. If you were to use Merged isolation mode, your game would write its saves to whatever computer you are using at the time. DirectoryIsolationMode=WriteCopyįor our example, WriteCopy is useful if you'd like to keep the save files on the USB drive alongside your game. If you don't know what ThinApp version was used to capture your application, run this: Pass this switch to prevent its deletion after the script finishes. This script will create a tmp directory wherever it is located while running. Previously created bak files will not be removed. Passing this switch will disable that behavior. If omitted, it'll attempt some fallbacks, following the logic outlined in build.bat files created on every capture.īy default, this script will backup your existing Registry.rw.tvr to Registry.rw.tvr*, where * is an incrementing number. Must contain vregtool.exe and vftool.exe. Used to populate a CapturedUsingVersion param in a stub Package.ini, which ThinApp's tools require to run. (Default: 5) ThinApp version used to capture the application. Path to your sandbox directory for scanning. Relative paths are resolved against the current working directory. KeepTemp = Don't delete the `tmp` folder (debug)
NoBackup = Don't create Registry.rw.tvr.bak* files ThinAppPath = Path to your ThinApp install directory Version = ThinApp version used to capture the app
SandboxPath = Path to your sandbox directory
0 kommentar(er)
