Customize Package Settings

The capture process includes initial settings for the primary data container, MSI packages, and executable package compression.

Procedure

1. In the Package Settings window, select the primary data container from the list that is based on your executable file entry points.

   • If the size of the primary container is smaller than 200MB, Omnissa ThinApp creates a .exe file as the primary container. For a small application such as Firefox, any .exe file can serve as the main data container.
   • If the size of the primary container is larger than 200MB, ThinApp creates a separate .dat file as the primary container because Windows XP and Windows 2000 cannot show shortcut icons for large .exe files. Generating separate small .exe files together with the .dat file fixes the problem.
   • If the size of the primary container is between 200MB and 1.5GB, ThinApp creates the default .dat file unless you select a .exe file to override the default .dat file.

2. (Optional) If you select a .exe file to override the default .dat file when the size of the primary container is between 200MB and 1.5GB, ignore the generated warning.

   Selecting a .exe file enables all applications to work properly but might prevent the proper display of icons.

3. (Optional) If you cannot select a primary data container, type a primary data container name to generate a .dat file.

   If you plan to use the Application Sync utility to update a captured application, ThinApp uses the primary data container name during the process. You must use the same name across multiple versions of the application. You might not be able to select the same primary data container name from the list. For example, Microsoft Office 2003 and Microsoft Office 2007 do not have common entry point names.

4. (Optional) Select the Generate MSI package check box and change the MSI filename.

5. (Optional) To create a smaller executable package for locations such as a USB device, select the Compress virtual package check box.

6. Click Save.