Lenovo ThinkPad R400 - Manual (Page 98)

this module. If your map contains multiple operating systems and all of the
operating systems will be installed from I386 base operating-system modules, you
can insert the ImageUltra Customizations module under the root entry. If your
map also contains base operating-system modules for Portable-Sysprep Images or
Hardware-Specific Images or imported ImageUltra-developed base
operating-system modules, you must insert the ImageUltra Customizations module
under the menu item used to select the operating system that will use the I386
base operating-system module. Do not attempt to use the ImageUltra
Customizations module with Portable-Sysprep Images or an Ultra-Portable Images
developed from imported ImageUltra-developed base operating-system modules.
UNATTEND.TXT module
The UNATTEND.TXT module contains the UNATTEND.TXT file that defines the
values to be used during an unattended installation. The ImageUltra Builder
program provides two sample UNATTEND.TXT files:
v UNATTEND.W2K: For use with Windows 2000
v UNATTEND.WXP: For use with Windows XP Professional and Windows XP
Home
These sample files require some modification before they can be built as modules.
Information about modifying these files is in Chapter 8, “Preparing source files for
modules,” on page 135.
After these files have been built as UNATTEND.TXT modules, you can insert them
in your map. Because these modules are both operating system unique and
language unique, in most cases you will probably insert the appropriate
UNATTEND.TXT module under the menu item used to select the language of the
operating system. If you are developing images for multiple customers, the
UNATTEND.TXT file typically has customer-unique information such as the
company name and the PID (ProductKey or ProductID) associated with the license.
UNATTEND.XML module
The UNATTEND.XML module contains the UNATTEND.XML file that defines the
values to be used during an unattended installation. The ImageUltra Builder
program provides two sample UNATTEND.XML files:
v UNATTEND.V32: For use with Windows Vista (32 bit)
v UNATTEND.V64: For use with Windows Vista (64 bit)
These sample files require some modification before they can be built as modules.
Information about modifying these files is in Chapter 10, “Using ImageUltra
Builder and Windows Vista,” on page 173
After these files have been built as UNATTEND.XML modules, you can insert
them in your map. Because these modules are both operating system unique and
language unique, in most cases you will probably insert the appropriate
UNATTEND.XML module under the menu item used to select the language of the
operating system. If you are developing images for multiple customers, the
UNATTEND.XML file typically has customer-unique information such as the
company name and the PID (ProductKey or ProductID) associated with the license.
Using a container for I386 base operating-system modules and
related modules
Some developers might find it easier to package the I386 base operating-system
module, the appropriate Primary NTFS Partition partitioning module, the Sysprep
module, the ImageUltra Customizations module, and the appropriate
84 ImageUltra Builder Version 4.01: User Guide