it is nice that you can set the basedir via an environment variable, but if I want to have different basedirs for different applications I need a way to specify this either in the package or via a command line parameter. This is because you cannot alter environment variables within shortcuts. And starting a batch is not that nice as a command windows flashes at least shortly and disturbs the users.
We have several applications were it is useful to have a VOS for each user. But some applications to not hold user specific data and so a shared VOS would be enough.
We have an MS Access application that we packaged as a whole with the correct MS Access environment. That app is about 500mb. In the VOS about 150mb are placed and I do not want such a big VOS for each user in my domain environment.
We plan to deploy a local VOS on each computer that should be used for such big applications like this.
-- Edited by alienn on Tuesday 24th of September 2013 08:56:13 AM
If you have not changed Data storage, VOS will deploy to %AppData%, so each local computer will have its own sandbox when launched from the network. If you would like to change VOS location permanently, you can use Package Editor to change Data storage. If you would like to change VOS location for a session--starting with Cameyo 2.5.1108 Beta--you can use the parameter -Properties:BaseDirName=, e.g. Access.cameyo.exe -Properties:BaseDirName=%Personal%\VOS\%AppID%
If more than one user is using the package without a separate User login and you want to have different sandboxes for each, it is recommended to change AppID so that registry writes will be separate, e.g. Access.cameyo.exe -Properties:AppID=AccessUser2 and this will also change the folder name under VOS; thus, it is unnecessary to change BaseDirName too unless you want the sandbox to go to a completely different location, in which case you might run Access.cameyo.exe -Properties:AppID=AccessUser2,,BaseDirname=C:\User2\VOS\%AppID%
O.k. I did not know that I can predefine the VOS location in the package. But it is nice that you now specify the basedir on the commandline. Very convenient.
Is there a way to use environment variables like %SYSTEMDRIVE% in the predefined VOS location?
Or more generally speaking: Does it make sense to import the system environment variables (like %SYSTEMDRIVE%, %COMSPEC%) on Cameyo startup so that they can used in different areas (like VOS location, custom events)?
Okay, at some point, an example will be added to FAQ. In the meantime, there is mention of it here.
Version 2.5 is optimized for speed instead of size. In the future, there will be an option to choose size-oriented compression, but keep in mind, the greater the compression, the slower the reading speed.