Thought it may be of interest to others who want to do something similar. I had an issue today, I wanted to install adobe reader into a sandbox so it didn't install files across my system, but I also wanted to maintain a fresh install of reader so didn't want it writing inside the sandbox after the install. Usually I choose one or the other, which always put me off installing browsers directly into a sandbox, but I've since found a solution.
Possibly common knowledge but I've not seen it mentioned before; A workaround is to create 2 sandboxes, the first one is the master install (eg AdobeReaderMaster) and will always contain the unchanging master install. The second will run the software (eg AdobeReader), it will contain any changes made during use, and can be deleted to revert back to the fresh installed/configured state. The second box reads the program files directly from the master sandbox (so is small in size) and all changes made during use will be isolated from the master install.
So far I've successfully used this with Adobe Reader, YTD (YouTube downloader), Opera and Open Office (surprised this one worked)
If anyone is interested I can add more details on the setup. There was a little tweaking needed to get PDF files to automatically open in the correct sandbox.
Hope this gives people some interesting ideas on custom setups. I will be setting up all compatible software this way from now on
Linking sandboxes
Who is online
Users browsing this forum: No registered users and 0 guests