Lenovo ThinkPad SL300 - Manual (Page 185)

2. Create a setup batch file that does the following:
• Unzips the .ZIP file
• Runs setup using a script file
3. Put all files in a common folder; then, create the module.
Device driver exceptions
You can manipulate device-driver modules for various types of device drivers and applications. The following
conditions explain some of the exceptions pertaining to device drivers.
Condition: The installation order of a device-driver module needs to be modified to resolve a problem.
Solution: Under certain conditions, you can install a device-driver module through a base map to control the
installation order. No modifications are required to the source files or module.
Condition:Pointing to an .INF file that exists in a source file subdirectory.
Solution: Typically, when building a device-driver module, the .INF file is located in the root directory with
other source files used for that device driver. In some cases, a device driver might contain an .INF file in a
subdirectory. The ImageUltra Builder program allows for .INF files in subdirectories.
The process for creating a device-driver module that points to an .INF file subdirectory is similar to creating a
standard device-driver module. However, there is one slight difference when you specify attributes. After you
have your source files prepared, use the New Module Wizard to create a new driver module as you would a
standard device-driver module, but allow for the following exception when you fill in the attributes:
• In the Options tab, complete the Relative location of INF files in the source field with the relative path
to the subdirectory that contains the .INF file. For example, if the source file is X:\SOURCE_FILES\DRIVER_1,
but your .INF file is in X:\SOURCE_FILES\DRIVER_1\WINXP, the relative path is \WINXP.
After specifying attributes for the device-driver module, click the Save icon located in the Main window
toolbar. Then, build the module.
Condition:Preparing a device-driver module that installs using an .INF file, but also has an application
executable packaged with it.
Solution: Some applications are hardware dependent. These applications are sometimes designed to
contain both device-driver and application files. For example, you might have source files that contain a
wireless device driver intended for a wireless network card and a configuration utility intended to work
in conjunction with the network card.
In this case, if you make an INF-only device-driver module from the application source files, the application
might fail to install correctly. Conversely, if you make an application module from the application source
files, the device driver might fail to install correctly.
Although there are several ways to address this exception, the easiest and most successful solution is to
make a device-driver module that is both an INF installable and an executable. This method is optional
and cannot be used for Hardware-Specific Images.
The process for creating this type of device-driver module is similar to creating a standard device-driver
module. However, there are slight differences when you specify the attributes. After you have your source
files prepared, use the New Module Wizard to create a new device-driver module as you would a standard
device-driver module, but allow for the following exceptions when you fill in the attributes:
• In the Options tab, check the INF installable check box.
Chapter 13 . Dealing with exceptions 171