going through the Thinapp documentation and created my first thinapp (firefox). Just a little confused over when to use which isolation mode. For my firefox app, I chose the restricted write access method, but not sure if that was the best option.
Also, do you often just keep a repository of EXE files, or do you normally create MSI packages? Not sure which is my best bet. MSI seems to install the package locally, but since I'm using linked-clones, I don't understand the benefit as those apps will be deleted on refresh?
As always, any help is appreciated
Mike
You should read documentation to get knowledge of isolation modes and how they can affect access to computer resources.
MSI packages are for installation purpose - notebook usage of application. EXE files (or DAT files when package is greater) is for application streaming. It depends what you want to do. I prefer application streaming when I implement linked clones, because as you said, application would get installed all over when clone is refreshed.
Hi, yes I was reading the documentation but still wasnt clear on the matter.
I will continue to read
Isolation modes:
You can change "default" isolation mode in Package.ini and define explicit isolation modes per every registry key or directory.
Thanks again...I think my confusion isnt what each mode does, its about knowing when to use which mode with which application.
You do not use only one isolation mode in a project. Typically you use all three, on different locations of course. The default file system isolation mode (asked during Setup Capture but accessible in the package.ini) is most of the times Merged in production but during debugging and tweaking of a project do I always use Write Copy. This is so I will capture all changes in the Sandbox.
Which locations use which isolation mode depends on how the application behaves and what you want to save in the Sandbox and what not. There is no silver bullet answer to your question.
Some generic rules I use:
* Temp files should not be Sandboxed, use Merged
* User settings, this is 50-50. Sometimes is it easier to store user settings natively but sometimes is it better to Sandbox them.
* Favorites, cookies and so on do I not Sandbox, use Merged
I try always to keep the Sandbox as small as possible.
Thanks pbjork. Does the isolation selected ever determine whether the application works on a particular OS? For instance,I have this application that I captured, it works on 32 bit OS, but on 64 bit, it flashes "preparing to install" a few times and then eventually opens. One it opens the application works fine, but the preparing to install happens every time you open it. The thing is, the installation files have to be available when you open it, otherwise you get an error that it cant find the installation media.
I'm not exactly sure why but I can't seem to fix.
Try to capture the application being installed into a static path instead of in c:\Program Files. For example into c:\ApplicationName. This way can we rule out c:\Program Files (x86) issues. It’s only in the virtual environment the application is located in the root of C: so it should be okay.
I'm smarter than I thought because I did already try that but I was still having the same issue. Very frustrating
The program is called Wavereader , its a shareware program
Sent from my Verizon Wireless BlackBerry
