This explanation of version 2.5’s new features will help you to better understand them, and better test the Beta too.

Note: we are in need of Beta testers for the auto-updatefeature.

– FAST! Significant speed improvement:

Most importantly when it comes to virtual applications functioning: first launch (“preloading” phase) and general application disk-access performance.
– RAM virtualization mode:
Simply package applications with this mode, and see that they function properly. If they don’t (or if they have issues), check if they work better in Disk mode. This helps identify issues specific to RAM virtualization mode.

– Auto-update:
Perhaps the area where we most need beta testers: in the Package Editor’s Advanced tab, click on “Auto update” link, and enable the auto-update mechanism. Generate your own auto-update environment, and then simulate an update by putting a more recent virtualized application. Check that client applications properly auto update to the latest version.

– App files stored separately from app’s changes:
Using the Package Editor, change the Data storage setting, and play with the “Store user data in a different directory”, to see if:
a. data is properly stored where you’ve configured it.
b. application’s behavior is unaffected by this setting.

– Terminal server friendly:
Those of you who run Terminal servers can test this item by launching Cameyo applications on them, and checking that the applications work properly through terminal session.

– New file isolation mode:
Using the Package Editor’s “Files” tab, you can set directories that the virtual app will not be able to see on the real computer. So for example if you set C_\SomeDir to Strictly Isolated, that means the virtual application will not be able to see any files in that directory, if C:\SomeDir exists on the real system. It will, however, be able to see files in that directory which are part of the package itself.

– License display:
Create (or package, or add) a file C_\License.txt to your package, and it will be displayed when the application first launches.

– Package lockdown:
In the Package Editor’s Advanced tab, there is a new checkbox labeled “Password-protect against editing”, followed by a password box. This protects the package from being edited (i.e. using the Package Editor), unless the person has the password to do it.

– Expiration after X days:
In the Package Editor’s Advanced tab, there is a new expiration method. Rather than expiring just on a specific date (which was the only option in Cameyo 2.0), now you can set a relative number of days, which will set the day counting relatively to the date the virtual application was first launched.

– Branding:
This is a special feature for removing the Cameyo popup. It requires special licensing, but if you are a business / developer and are interested in such paying option, you can contact us.