Your package should work if you use Package Editor to change it from RAM mode to Disk mode.
RAM mode was just introduced in Cameyo 2.5, and we are keeping a list of virtualized applications that work only in Disk mode for troubleshooting to improve RAM mode.
For RAM mode to launch faster, less compression is used on the packages; therefore, the size is larger than Cameyo 2.0 packages. A future version of Cameyo will allow the package builder to choose greater compression, but of course, that will increase the initial launch time.
Without .NET Framework 2.0 or higher installed, only a basic Package Editor is available. With this Package Editor, you can delete files from the package, for example, but you can't change Virtualization mode.
The package created by Cameyo 2.5 is larger because less compression is used to enable faster launches.
Yes, changing Virtualization mode does not affect the package size. I recommended changing from RAM to Disk mode to prevent the error you reported in your original post.
Cameyo 2.5 is optimized for speed, not size. A future version will provide the option to increase compression, which will result in smaller packages. These smaller packages will not be as fast; the user will be able to choose which is more important, size or speed.
We are keeping a list of virtualized applications that work only in Disk mode for troubleshooting to improve RAM mode, so yeah, the aim is for all of those applications to one day work in RAM mode, as well. No ETAs can be given at this time because there are other things that have a higher priority, e.g. virtualized applications that don't work at all.
