Overview:

Prism Deploy, Prism Pack and PictureTaker let you use environment variables and variables that have been defined within a deployment Package (or Self-Installing file). You can install Packages even when people receiving the Package need personalized entries distributed, such as e-mail addresses. It also lets you install one Package to a heterogeneous environment. Prism Deploy, Prism Pack and PictureTaker allow you to insert variables into Packages in place of:

• INI file values
• Shortcut paths
• Registry keys, values, and data
• File names
• Drive letters, folders, and entire paths

Prism Deploy, Prism Pack and PictureTaker recognize some common folders and registry keys and will automatically substitute a variable for the path names or keys when taking a baseline Picture or creating a Package. If the Expert does not automatically substitute a variable for a specific instance of a folder or key, you can include variables in the file properties, or add a variable folder to the deployment Package. An overview of each of these options is given below.

Substituted Variables
When the Expert (similar in Prism Deploy, Prism Pack and PictureTaker) finds the following directories or key names, it will substitute a variable.

For the Windows and System directories it substitutes WINDIR and WINSYSDIR, respectively.

For keys in HKEY_CURRENT_USER\Software\Microsoft\Windows\currentversion\explorer\shell folders, it substitutes the key corresponding to the same name with:

For example, when the Expert finds a reference to a Windows directory, it automatically converts the full path name into the variable WINDIR. This allows you to install the Package on another computer without regard for where the Windows files are located. Let's say you want to install the wallpaper setting "Bubbles." You then:

1. Take a Picture of your workstation.
2. Change your wallpaper setting to Bubbles.
3. Let the Expert find changes.

No matter where your Windows files are located, the resulting Package will include the following lines:

In Registry (Current User) | Control Panel | Desktop:

Wallpaper %WINDIR%\Bubbles.bmp

Prism Deploy, Prism Pack and PictureTaker automatically substitute the variable %WINDIR% for the path to your Windows directory. When you install the Package on another computer, it will expand the variable by putting the correct path to the Windows directory in Registry (Current User) | Control Panel | Desktop.

Where Are Percent Signs Needed?
When adding variables to a Prism or PictureTaker file, you need to enclose them in percent signs in the following areas:

FILE CONTENTS (such as INI files)
REGISTRY VALUE DATA

In all other areas such as folder and file names, registry key names, and registry value names, use the Editor special menu options for creating a variable. You do not need to use the percent sign when using variable folders, variable registry keys, etc.

Add Variables to Package Properties
In the File Properties | Variables dialog box of the Package Editor, you can define a variable that will be resolved when the Package is installed. These variables can indicate differing target paths, registry keys, and so on. Resolve the variable based on a file location, an environment variable, an entry within an INI file, a registry key, or you can prompt the user to enter the variable's value.

Add Variable Folders to Packages
You can also add a variable folder containing an environment variable to a deployment Package. For example, if you want to distribute a Package that updates a DLL in an application directory, but the directory could be different on multiple PCs, set up a variable to search for the application executable file and apply the DLL to the same directory.

Change Existing Folders to Variables in a Package
If you already have a folder that you want to turn into a variable, the simplest thing to do is to edit the paths for the Package. This method is very powerful because Prism Deploy, Prism Pack and PictureTaker automatically change all references to a folder (in INI-Files, the registry, etc.) to the variable you request.

For more information on using variables, including examples, see the relevant chapters in your product User's Guide in the Related Links section below.