Using ImageUltra Builder - IBM Redbooks

partitioning modules in a base map to accomplish various results. When you use a
partitioning module to create additional partitions with data, the module contains all of
the information required to create the additional partition and all of the data to be
placed in the additional partition. These types of partitioning modules are typically
created using an imaging tool, such as Symantec Ghost or Symantec DeployCenter.
See 1.14, “Creating a partitioning module” on page 47.
► Application modules: Each of these modules contains all of the components associated
with a specific application program. Software applications such as Microsoft Office, Adobe
Acrobat and IBM System Migration Assistant would be separate application modules. See
1.10, “Creating an application module from source files” on page 28.
– If you are building an ultra-portable image or a portable-sysprep image, you can use
application modules.
– If you are building a hardware-specific image, you cannot use application modules
when deploying the image. All applications must have been previously contained within
the hardware-specific image when it was created.
► Device driver modules: Each of these modules contains all of the components
associated with a specific device driver. There would be a separate device driver module
for the IBM ThinkPad video driver or a ThinkCentre audio driver for example. 1.11,
“Creating a device driver module from source files” on page 32.
– If you are building an ultra-portable image or a portable-sysprep image, you can use
device-driver modules.
– If you are building a hardware-specific image, you cannot use device-driver modules in
conjunction with that image. All device drivers must be contained within the
hardware-specific image.
During the deployment process, you choose which base map and which driver map to deploy.
This enables you to maintain device-driver modules and driver maps independently of the
operating-system and application content defined by base maps. In addition to modules, the
ImageUltra Builder program enables you to create containers in the repository.
► Container
A container is a special type of module that enables you to group other modules together
under a single identifier. All modules in a container must be of the same type. For
example, you might want to group all of the device drivers used for a specific machine type
into a device-driver container. Or, you might want to group a Windows 2000 base
operating-system module with all of its associated add-on modules into an
operating-system container. The use of containers is optional, but you might find
containers helpful when creating maps because you can simply inserting the container
module into your map instead of inserting each individual module.
► Filters
Filters automate a decision during the installation process. You typically use filters to
obtain hardware-related information from a target computer to determine if a specific
module or set of modules should be installed. The ImageUltra Builder program provides
filters that check the machine type, machine type and model number, hardware platform
(mobile or desktop), and whether or not a computer is an IBM computer. You can also
develop your own filters if needed.
Filters are DOS-based programs that run during the installation process. In most cases
filters query the BIOS of the target computer, but they can query other devices that store
identification information in a ROM or EEPROM module. For example, you might want to
check for the presence of a PCI modem before installing a modem-related application
program or you might want to check for a specific machine type to determine which device
drivers should be installed.
14 ThinkVantage Technologies: Using ImageUltra Builder