beautypg.com

Lenovo ThinkPad Edge 15 User Manual

Page 18

background image

the Lenovo Support Web site at http://www.lenovo.com/support. Navigate to ThinkVantage Technologies
Rescue and Recovery. Select the appropriate version number of the Rescue and Recovery program, and
click the Individual language files for Large Enterprise link.

Main installation package (required)The main installation package is a self-extracting installation

package that extracts the installation source files and launches the installation using Windows Installer.
It contains the installation logic and the Windows application files. The package does not contain any
of the Predesktop Area files.

Example:

– For the Windows XP operating system, the main installation package can be named as

Z696ZISXXXXCC00.EXE.

– For the Windows Vista operating system, the main installation package can be named as

Z695ZISXXXXCC00.EXE.

Note: The XXXX is the build ID. The CC represents the language.

Predesktop Area Base (required)This is the password protected file that contains the entire Predesktop

Area base. This file is required to install the Predesktop Area on all language systems. This file must be
in the same directory where the main installation package is located. The exceptions to this are if the
Predesktop Area is already installed and does not need to be upgraded, or if the property PDA=0 is set
on the command line when you execute the installation and any version of the Predesktop Area does
not exist before.

Example:

– For the Windows XP operating system, the file can be named as z696ZABXXXXCC00.TVT.

– For the Windows Vista operating system, the file can be named as z695ZABXXXXCC00.TVT.

Note: The AB determines the compatibility of the Predesktop Area. The XXXX represents the build
ID. The CC represents the language.

The installation executable contains a file and the pdaversion.txt file. The pdaversion.txt file contains
the minimum version of the Predesktop Area that can work with that version of the Windows operating
system. The installation executable will look for a Predesktop Area file using the following logic:

Old Predesktop Area (the Rescue and Recovery 1.0 or 2.X program) exists or no Predesktop Area

exists:The installer will look for a TVT file with a compatibility code, for example AA or AB, that is equal
to the minimum version compatibility code and a level that is greater than or equal to the minimum
version. All other version fields in the TVT file name must match the minimum version exactly. If a file
meeting these criteria is not found, the installation will be halted.

New (the Rescue and Recovery 3.0 or later program) Predesktop Area exists:The installer will

compare the current Predesktop Area compatibility code with the minimum version compatibility code
and take the following actions based on the results:

The current code is greater than the minimum code.The installer presents a message, saying that

the current environment is not compatible with this version of the Rescue and Recovery program.

The current code is equal to the minimum code.The installer compares the current version level

with the minimum version level. If the current level is greater than or equal to the minimum level, the
installer looks for a TVT file with a compatibility code, for example AA or AB, that is equal to the
minimum version compatibility code and a level that is greater than the current version level. All
other version fields in the TVT file name must match the minimum version exactly. If it does not find
a file, the installation process continues without updating the Predesktop Area. If the current level is
less than the minimum level, the installer will look for a TVT file with a compatibility code, for example
AA or AB, that is equal to the minimum version compatibility code and a level that is greater than or
equal to the minimum version level. All other version fields in the TVT file name must match the
minimum version exactly. If a file meeting these criteria is not found, the installation will be halted.

10

Rescue and Recovery 4.23 Deployment Guide