In case you wondered what happens if you try to run the portable version of an app on a computer that already has that app installed, PAL can handle that just fine. Now take that portable version to another computer (again, it can be just a virtual machine) to test it by running PAL.exe. You may also rename PAL.exe to whatever you want but do not rename PAL.ini.

When you are done editing it, save PAL.ini. If your app doesn't use a directory in the filesystem to store data, then just delete this line completelly. As you can see in the sample INI above, you may use enviroment variables like %appdata% etc. The FilesPath= should point to the place in the filesystem where your app stores files or settings. If your app doesn't use the registry just delete this line completelly. The RegistryPath= line should point to the registry path where you application stores its settings. Edit the Executable= line so that it points to the main executable of your application. If you app uses, for example, two folders in the filesystem to store settings, PAL will not be able to completely handle that app, meaning it will leave traces or not even work.Īfter finding where this app stores its settings, open and edit PAL.ini. This is adequate for most apps I've seen. Currently PAL can only handle one registry path and one filesystem path. Then run and exit it once and start searching as described in the first method for places in the registry or in the filesystem where the installed program might be storing settings. You may rename that directory to App if you want (just like in the sample INI file above).

Then download PAL from here, unzip it somewhere and copy the program's directory from the place it was installed right next to PAL.exe. So just like in the first method, install the program you want to make portable.

Portableapps creator