5.1

IsolatedMemoryObjects Parameter
The IsolatedMemoryObjects parameter lists the shared memory objects to isolate from other applications or
from system objects.
Applications that use CreateFileMapping and OpenFileMapping Windows functions create shared memory
objects. When you do not isolate memory objects, conflicts can occur between virtual applications and native
applications sharing those objects.
For example, you might have a two versions of an application with one version in the native environment
and one version in the virtual environment. When these application versions use information in the same
memory object, the applications can interfere with each other and fail. You might want to isolate shared
memory objects to ensure that virtual applications and system objects cannot detect each other.
This parameter does not appear in the Package.ini file, but you can add the parameter.
ThinApp sets an initial value that isolates the memory objects that a native version of Internet Explorer uses
in the virtual environment. The value addresses a conflict between the explorer.exe and iexplore.exe
utilities when the utilities map sandbox files.
You can use the IsolatedMemoryObjects parameter to isolate additional named shared memory objects to
ensure that the objects are visible only to other virtual applications using the same sandbox.
The IsolatedMemoryObjects parameter accepts a list of entries that are separated by a semicolon (;).
The following parameters are described in this section:
Example: Isolating a Memory Object
You can modify the IsolatedMemoryObjects parameter to isolate the memory object with the My Shared
Object name and any memory object with outlook in the name.
[BuildOptions]
IsolatedMemoryObjects=*outlook*;My Shared Object
IsolatedSynchronizationObjects Parameter
The IsolatedSynchronizationObjects parameter lists the synchronization objects to isolate from other
applications.
Synchronization objects coordinate actions between applications. The following Windows synchronization
objects might appear in logs for application errors:
n
OpenMutex
n
CreateMutex
n
OpenSemaphore
n
CreateSemaphore
n
OpenEvent
n
CreateEvent
If these objects appear in log files, you might isolate the objects in the virtual environment to avoid a
collision with synchronization objects that native applications create.
You can isolate synchronization objects from applications that do not run in the same virtual namespace. If
two applications share the same sandbox path, the applications have the same namespace for isolated
synchronization objects. If two applications have the same sandbox name, but different sandbox paths, the
applications have separate namespaces.
Chapter 10 Configuring Objects and DLL Files
VMware, Inc. 35