Package.ini File Structure; Parameters That Apply To Package.ini Or ##Attributes.ini Files; Configuring The Thinapp Runtime; Netrelaunch - VMware THINAPP 4.6 Manual

ThinApp User's Guide

Package.ini File Structure

The structure of the Package.ini file includes sections that apply to all applications or individual applications.
Most parameters must appear under a specific section heading. The Package.ini file contains the following
headings:

[BuildOptions]

[<application>.exe]

[FileList]

[Compression]

[Isolation]
The [BuildOptions] section of the Package.ini file applies to all applications. Individual applications
inherit these parameters unless the entries specific to applications override these settings. For example, the
[Adobe Reader 8.exe] section of the Package.ini file for an Adobe Reader application might have settings
that override the larger [BuildOptions] parameters. The application‐specific parameters show the
application entry points that you create during the build process.
The [FileList], [Compression], and [Isolation] parameters act as [BuildOptions] parameters, but are
grouped separately for backward compatibility reasons. You can add the [FileList] heading manually to
the file when you add the ExcludePattern parameter.
Parameters that do not apply to the standard sections can reside under any heading. Parameters do not have
to appear in alphabetical order.

Parameters That Apply to Package.ini or ##Attributes.ini Files

You can apply certain parameters to the Package.ini file or the ##Attributes.ini file, depending on the
requirements, to override the Package.ini settings at the directory level.
You can use the DirectoryIsolationMode, CompressionType, and ExcludePattern parameters in an
##Attributes.ini file. The ##Attributes.ini file exists in the folder macros of the project folder.
For more information about the ##Attributes.ini file, see "Modifying Settings in the ##Attributes.ini File"
on page 24.

Configuring the ThinApp Runtime

You can modify ThinApp parameters for runtime configuration tasks that affect application startup
performance and virtual computer names.

NetRelaunch

The NetRelaunch parameter determines whether to restart an application from the local disk when you run
the application from a network share or removable disk, to address the slow startup of applications.
ThinApp sets an initial value of the NetRelaunch parameter that detects whether an application runs from a
network drive or a removable disk, and uses a stub executable file on the local hard disk to restart the application.
This process addresses performance problems that Symantec AntiVirus generates when it tries to do a complete
scan of executable files that open from a network share or removable disk, and on executable files that make the
initial network connections. The scan can affect start times for large executable files.
Because a large number of desktops have Symantec AntiVirus, ThinApp enables applications to open from a
network share without incurring lengthy scan times. When the application runs from a network share or
removable disk, ThinApp creates a stub executable file in the directory that the CachePath parameter sets on
the local disk and restarts the application from this stub executable file. The stub executable file can load the
runtime from the large package and read the rest of the application from its original location on the network.
Symantec AntiVirus perceives that the application is local and does not scan the larger executable file on the
network share or removable disk.
66 VMware, Inc.