Lenovo ThinkPad SL300 - Manual (Page 163)

Chapter 9. Specifying the module-installation order
The ImageUltra Builder program enables you to change the order in which modules are installed. Usually,
there is no need to change the default module installation order unless one or more of the following
conditions exist:
• One or more modules require other modules to be installed first.
• The image is not installing correctly.
• You are installing a partitioning module (other than a Primary NTFS Partition partitioning module).
• Modules are interfering with each other during installation.
The default installation order for modules is automatically controlled by the ImageUltra Builder program.
However, you can override the default module installation order for add-on operating-system modules,
Portable-Sysprep and Hardware-Specific base operating-system modules, partitioning modules, application
modules, and some device-driver modules. The amount of control depends on which boot cycle the module
will be installed.
Note: If you need to control the install sequence for a device-driver module, you must put the device-driver
module in a base map instead of a driver map; otherwise, any settings you make for the install hook or install
slot will be ignored. For more information about configuring a device driver module so it can be included in
base map, see Chapter 12 “Getting help and support” on page 167. I386, Windows Vista, or Windows 7
base operating-system modules always install the Windows operating system first; therefore, you cannot
modify the installation order of these base operating-system modules.
There are three methods of changing the default module-installation order:
• Modifying the install hook: The install hook defines the boot cycle (audit boot or customer first boot)
in which the module is to be installed, or if the module should be installed manually through the use
of a desktop icon after the image has been installed. You can modify the install hook for add-on
operating-system modules, application modules, and some device-driver modules. Install hooks do
not apply to Portable-Sysprep or Hardware-Specific base operating-system modules or to partitioning
modules because, by design, these modules are always installed before the audit boot. Install hooks
also do not apply to modules designated to be installed via a desktop icon. The install-hook setting is
located in the Options tab of the module window.
Note: The Install hook setting in an I386 base operating-system module is not used.
• Modifying the install slot: The install slot defines a priority grouping, 1 through 9999, where modules
assigned to the slot 1 group are installed first, modules assigned to the slot 2 group are installed next, and
so on until modules assigned to the slot 9999 group are assigned last. You can modify the install slot for
add-on operating-system modules, application modules, and some device-driver modules. Install slots
do not apply to Portable-Sysprep or Hardware-Specific base operating-system modules or to partitioning
modules. The install-slot setting is located in the Options tab of the module window.
Notes:
1. The Install slot setting in an I386, Windows Vista, or Windows 7 base operating-system module is
not used.
2. For ImageUltra Builder 5.0, the following limitations apply:
– You can use install slots 1 through 9 for add-on operating-system modules, application modules,
and some device-driver modules regardless of the type of image you are installing.
– Slots 10 through 9999 are valid for use with add-on operating-system modules, application
modules, and some device-driver modules only if those modules are being installed as part of
an Ultra-Portable Image based on an I386, Windows Vista, or Windows 7 base operating-system
© Copyright Lenovo 2008, 2010 149