The followings are some observations from my experiments on using the latest Cameyo v2.5.1139. I hope it will be useful to the developer as well as fellow users.
* Virtualization: RAM mode
When starting multiple programs from the same package set on RAM mode, programs will crash.
* Isolation mode
Modifying isolation mode will cause "Files" and "Registry" section to change (might be intended). Also, this option sometimes will switch values automatically, especially after changing "Files" and "Registry" section.
* Data storage
When enviroment variable CAMEYO_BASEDIRNAME is set, the virtual package will extract directly under it, without the AppID subdirectory. e.g. if CAMEYO_BASEDIRNAME=T:\Temp, then a virtual package with AppID=ABC will extract directly under "T:\Temp\", not "T:\Temp\ABC\".
* Remove traces upon app exit
"Leave no registry traces" does not seem to work on Windows XP SP3. (Works well on Windows 7.) The keys under "HKCU\Software\VOS\%AppID%\Registry\" are all still there after exiting.
Great application virtualization software! Please keep up the good work!
1. Virtualization: RAM mode Can you upload a package that exhibits the behavior you describe to a file-hosting site and post the link? If it's not something that can be shared publicly, please send me a private message.
2. Isolation mode Please describe what you are seeing in more detail.
3. Data storage Using %AppID%, e.g. T:\Temp\%AppID%, will result in T:\Temp\ABC
4. Remove traces upon app exit Is the package's sandbox still present, or are you seeing the sandbox being deleted without the registry key? If the sandbox is still present, run package with -ProcessList parameter to see if all parts of the package have exited, e.g. appname.cameyo.exe -ProcessList
