FAQ

Top  Previous  Next

What is the recommended way for packaging software?

The easiest way to package software is by using our Online Packager directly from the cloud. It is ideal because the packaging environment is clean and optimized for application capturing. However not all software can be captured this way. So the second best method is to use a clean virtual machine (preferably XP SP3 32-bit), and use Cameyo's packager on it ("Capture an installation").

Cameyo is probably the product that provides most different methods for packaging virtual applications:

Online Packager: usually the quickest way if your installation can be installed this way, and assuming it doesn't depend on pre-requisite components.
VM packaging (Cameyo's local packager): if you have a clean virtual machine environment, that is usually the most recommended way.
XML / command-line-based packaging: if you need to build packages automatically (i.e. via scripts).
GhostCapture: the least recommended way, this method is about running the application's installer inside Cameyo's sandbox, and then wrapping the result into a virtual package. This method is useful because it can quickly be used on your own machine, however it is the least recommended way as it will often fail and / or produce less portable packages due to the unclean capture environment.

 

I do not see the files saved by Cameyo virtual applications.

Cameyo packages run with certain isolation configuration. By default (Data mode), only files saved under the Documents or Desktop folders, or on network / removable drives, will indeed be written there. All other files will be redirected into the application's isolation repository (the VOS directory).

 

My virtual application doesn't work properly. What should I do?

First, try running your app with the "-SafeMode" parameter. See the procedure described here: http://www.cameyo.com/resources/IssueSubmission.pdf

 

Can packages that require .NET framework run on machines that do not have the .NET framework?

Packages requiring the .NET framework must have at least some version of the .NET framework on target systems in order to work.

 

A virtual application does not work well. What should I do?

First, make sure you have the latest Cameyo version. If so, submit your application name on the forum, under the topic "Virtual applications not working well".

 

I've built my package, but I forgot to make some configuration changes to my software. How can I change settings and apply them to the package?

You can always go back to the packaging machine where the installer was capture, make some changes to your software, and redo a post-snapshot using the -EndCapture command (Cameyo 2.6.1182 and higher only).

 

How to specify path names in a package in a generic way?

Using path variables. Cameyo has its own path variables. For example, %System% expands to something like C:\Windows\System32 (or D:\ or wherever Windows is installed on the target machine). You can also use Windows standard system variables by using double-percent sign: %%LOGONSERVER%%. For more examples, see the Path variables section.

 

How is Cameyo different from other products?

The main differentiators of Cameyo are:

"Agent-less" virtualization, meaning virtual applications can run on machines that don't have any Cameyo agent pre-installed.
Very simple to learn and use, yet very powerful if you need "under the hood" functionality.
Provides many packaging methods.
Automation and customization: almost anything can be done in Cameyo via command-line or scripts.
Self-contained: you can customize and edit your packages without having to maintain heavy "project files / directories".
We like to think of our active community as a strong point as well.

 

How to set up a Firewall exception rule for virtual applications?

Some firewalls, including the Windows Firewall, require to switch your virtual package to work in Disk mode. You can then see which executable causes the alert (within the VOS\... path) and add its full path as an exception. Beware: the Windows Firewall's group policy editor does not work well with paths containing percent signs (%). So for example if your executable is beneath ...\VOS\PROG\%Program Files%, the rule may not work. In this case it is best to install your virtual app in a custom path (so that it appears in the virtual package as C:\MyApp rather than C:\Program Files\MyApp). This will translate to a physical path such as: ...\VOS\PROG\C_ hence avoiding the percent (%) sign.

 

 

COMMERCIAL / LICENSING QUESTIONS

 

Is Cameyo open-source?

Only specific parts of Cameyo are open-source: the Package Editor and the SDK headers. But Cameyo is not open-source.

 

Is Cameyo free?

Cameyo's licensing is counted per number of end-users using the virtual apps that you create. It's free for less than 50. Above that number see our pricing page.

 

What is the difference between the Enterprise edition and the Developer edition?

The difference is mostly in terms of licensing and pricing model. An Enterprise license is for a specific number of end-users, without limitation as to the number of virtual applications. A Developer license is for a specific number of products (typically one), for a very large amounts of end-users.

 

I'm not a company or don't have 50 machines. How can I obtain the extended, licensed version?

The extended version can only be purchased by developers or companies with 50 computers or more. If this isn't the case for you, then the only way you can obtain the professional version of Cameyo is by contributing. There are many ways you can contribute: being an active tester, helping other users on the forum on a regular basis, translating to a new language, writing descriptions for our virtual app library, developing useful add-ons, or other ideas you may have for contributing to the whole Cameyo community.