I read the .PDF manual but still some (basic) things don't seem really clear to me.
1)
Cameyo uses a "VOS" directory for (temporary) processing needs of the portable application. Can't this VOS directory be targeted into the EXE file itself? What I mean is the exe file will grow whenever data is added (for example the itunes library which grows).
If choose for an app to leave the "VOS" folder (not delete it on app exit) What happens when I run another app which uses the same "VOS" folder?
2) When you edit an portable application (exe), the first tab you see is "general"-tab, within this tab you can set the "Isolation" mode. It contains 3 options: Data Mode , Isolated , Full access.
Am I right when I say:
Data mode: means for example, WORD could save a .docx file in MyDocuments on the HOST machine (the machine which runs the cameyo portable app)
Isolated: means a portable made file manager like total commander for example can't delete a file within the c:\windows directory
Full acces: Total commander can do just about anything even within c:\windows
3)
The "files" tab where you can see %Program Files% , %AppData% etc... Does this refer to the INTERNAL .exe file? Or to the EXTERNAL "VOS" directory.
In the top right you can see the folder isolation , it has 2 options: Isolated and full access. Where does this refer to? The accessibility of the INTERNAL structure (%Program Files% , %AppData% etc... ) or the accessibility of the "VOS" file system?
The manual states: "For the virtual application, these will be combined with the other directories & files on the target machine." What does this mean?
4) Are there any restrictions on 64-bit applications? I know the Ghostcapturing is restricted to 32-bit. But are there any other restrictions when it comes to 64-bit apps?.
- No, you cannot point the sandbox into the EXE itself.
- Each app uses its own subdirectory under the VOS directory. Word will use VOS\Word, Mozilla will use VOS\Mozilla.
2) All is right.
3)
- It refers to both the internal structure of the Cameyo app and to the equivalent VOS subdir. You don't need to worry so much about the VOS structure, as it is used internally to "cache" and "redirect" the EXE's structure on the disk. So the VOS and what you call the "internal EXE" are in fact the same thing (one is a reflection of the other).
- I'm not sure what you mean.
- It means: the virtual application will see the combined result of the app's files PLUS the files on the real machine (if those directories exist on the real machine too).
