Lenovo ThinkPad R400 - Manual (Page 172)

Partitioning modules that do not include data are typically language
independent and multiple languages can be selected.
b. In the right pane, put a check mark next to the operating systems for
which this module applies.
15. In the Source tab, do the following:
a. In the Source Directory field, type the complete path to the folder that
contains the image files.
b. In the Silent Install Command area, type the command required to restore
the partition image or prepare the drive.
16. Click the Save icon in the Main window tool bar.
17. Continue with “Building a new module” on page 165.
Note: When you implement one or more partitioning modules in a base map,
make sure you set the order correctly in the Install Order tab of the Map
Settings window. See “Using a partitioning module in a base map” on page
96 for details.
Preparing source files for a device-driver module
Device drivers must use the standard Microsoft Plug-n-Play .INF installation
method, which is usually unattended in nature. The driver itself must be certified
by the Microsoft Windows Hardware Qualification Lab (WHQL) and signed.
Failure to use signed, WHQL-certified device drivers will result in interruptions
during the installation process by Windows-generated information messages,
which require user interaction to bypass.
Adding mini-applications
The use of mini-applications is optional. Mini-applications are useful for creating
special folders, cleaning up registry entries, or performing any other service related
to the device-driver being installed. The content and format of a mini-application is
entirely up to you. You are limited to running one mini-application before the
device driver is installed and one mini-application after the device driver is
installed.
The only requirement related to the preparation of mini-applications is that you
must copy all of the mini-application files into the root folder of your device-driver
source files.
Requirements for preparing device-driver files for modules
The following are the only requirements for preparing the device-driver source
files to be made into a module:
v The device driver must be in a ready-to-install format. It cannot require an
unpacking process.
v The device-driver files must be placed in a dedicated folder on a drive that is
accessible by the ImageUltra Builder console.
v The device-driver folder structure must be maintained.
When the source files meet these requirements, you can set the attributes for the
new device-driver module.
158 ImageUltra Builder Version 4.01: User Guide