- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As an addition to the above correct answers:
If you take into account that ThinApp does provide 2 major solutions to application deployment:
- Distribution as a single file container
- Sandboxing 'all' changes the application makes at runtime
The main reason for problems is the sandboxing. You want to prevent your system to be 'corrupted' due to an application running (like changing registry entries or altering system files), but if you type a word document you want to be able to have this file in your 'my documents'.
The default folders you see are there to provide a basic usable platform. For all folders you don't see in the project folder (all the %...%-folders), the setting you specify during the post-capture snapshot are applied. Same for folders that don't have a attributes.ini in it, like %drive_C% often has as only a sub-folder is added.
You do NEED some of the folders to be available. For example, if you delete %SystemSystem%/Spool, you will not be able to print...! Similar having %Personal% as writecopy will have your documents end up in the sandbox instead of on your system. You will have to understand the workings of isolationmodes to be able to determine what the effect will be for deleting or even altering the default settings.
In general my experience is that the defaults are quite OK. Some things I have a different opinion about are for example the temporary internet files and normal temp files. This as it is easier to clean the system of these unwanted files and there are numerous tools doing this already, but none do this for sandboxes. Similar i want our users to share the favorites, cookies and so on with their local system, except when providing a secured browser as the users otherwise complain 'where are my' or 'why can't i'...
Kind regards,
Michael Baars - Comprehensive ICT Solutions
Please mark the question answered if so and reward points if it helped you...