4.7.3
Table Of Contents
- ThinApp Package.ini Parameters Reference Guide
- Contents
- About This Guide
- Configuring Package Parameters
- Package.ini File Structure
- Package.ini or ##Attributes.ini Files That Override Package.ini Settings
- Configuring the ThinApp Runtime
- Configuring Isolation
- Configuring File and Protocol Associations
- Configuring Build Output
- Configuring Permissions
- Configuring Objects and DLL Files
- ExternalCOMObjects Parameter
- ExternalDLLs Parameter
- ForcedVirtualLoadPaths Parameter
- IsolatedMemoryObjects Parameter
- IsolatedSynchronizationObjects Parameter
- NotificationDLLs Parameter
- NotificationDLLSignature Parameter
- ObjectTypes Parameter
- SandboxCOMObjects Parameter
- VirtualizeExternalOutOfProcessCOM Parameter
- Configuring File Storage
- Configuring Processes and Services
- Configuring Sizes
- Configuring Logging
- Configuring Versions
- Configuring Locales
- Configuring Individual Applications
- Configuring Dependent Applications Using the Application Utility
- Configuring Application Updates with the Application Sync Utility
- Configuring MSI Files
- Configuring Sandbox Storage and Inventory Names
- Other Configuration Parameters
- Locating the ThinApp Sandbox
- Controlling the Sandbox Location
- Sandbox Structure
- Creating ThinApp Snapshots and Projects from the Command Line
- Index
If you run a GetComputerName or GetComputerNameEx command, the computer returns LOCALHOST. If the
Windows system requires the GetComputerName and GetComputerNameEx commands to operate in a standard
way and return the actual name of the computer where the application runs, do not rename the machine as
LOCALHOST.
VirtualComputerName=LOCALHOST
Example: Including an Environment Variable
In addition to specifying a literal string such as LOCALHOST, you can include an environment variable.
When you specify an environment variable, the value returned is the value of the environment variable. If the
value of the VirtualComputerName parameter is %VCOMPNAME%, and the %VCOMPNAME% environment
variable is set to EnvCompName, the GetComputerName API returns EnvCompName.
VirtualComputerName=%VCOMPNAME%
Wow64 Parameter
The Wow64 parameter simulates a 32-bit environment for 32-bit applications that cannot run on a 64-bit Windows
operating system.
If a 32-bit application tries to handle its own 64-bit registry redirection, you can activate this parameter before
building a project. ThinApp comments out the initial setting to prevent Windows on Windows 64-bit (WOW64)
emulation.
Example: Uncommenting the Wow64 Parameter
The example shows how to uncomment the Wow64 parameter to simulate a 32-bit environment for 32-bit
applications on a 64-bit operating system. For example, a virtualized 32-bit Oracle application might not work
on a 64-bit operating system
[BuildOptions]
Wow64=0
QualityReportingEnabled Parameter
The QualityReportingEnabled parameter specifies whether VMware may collect anonymous data on a package
to improve ThinApp application support. VMware collects application information such as the version and
the number of application failures.
If you agree to anonymous data collection during the capture process, the QualityReportingEnabled parameter
uploads data every ten days.
Example: Turning Off Data Collection
You can modify the QualityReportingEnabled parameter to turn off ThinApp data collection.
[BuildOptions]
QualityReportingEnabled=0
Chapter 4 Configuring the ThinApp Runtime
VMware, Inc. 17