[OEMBootFiles]

Answer File = Unattend.txt

The [OEMBootFiles] section contains entries for specifying OEM-supplied boot files. This entry is valid only if you set OemPreinstall to Yes and you place the files listed here in the \$OEM$\Textmode folder of the OEMÆs distribution share point.

This section is required if you use the ComputerType entry in either the [Unattended] or [MassStorageDrivers] sections of Unattend.txt.

Important

• Add driver entries only to the [MassStorageDrivers] and [OEMBootFiles] sections for bootable mass-storage devices. Do not include secondary mass-storage devices. Instead, add the drivers for secondary mass-storage devices to the folder specified by the OemPnPDriversPath entry in your unattended Setup answer file. Including drivers for non-bootable mass-storage devices in the [MassStorageDrivers] or [OEMBootFiles] sections causes an error during Setup.

HAL_file_name

Maps to a hardware abstraction layer (HAL) description in the ComputerType entry of the [Unattended] section of the Unattend.txt file.

SCSI_driver_file_name

Maps to a mass-storage device driver description defined in the [MassStorageDrivers] section of the Unattend.txt file. You can list multiple instances of SCSI_driver_file_name in the [OEMBootFiles] section.

TxtSetup.oem

This file contains descriptions of all the OEM-supplied drivers listed in this section and includes instructions on how to install them. This file must exist if the Unattend.txt file contains an [OEMBootFiles] section.

If your mass-storage device is a Plug and Play device, verify that a Hardware Identification section and a reference to the catalog file for the driver (<Driver>.cat) exist in the Txtsetup.oem file.

If the Hardware Identification section does not exist, you must add [HardwareIds.scsi.yyyyy] to the Txtsetup.oem file and verify that the following information is included:

id = xxxxx, yyyyy

where xxxxx represents the device ID, and yyyyy represents the service associated with the device.

For more information about Txtsetup.oem, see the Microsoft Driver Development Kit (DDK), which you can order from the Microsoft DDK Web site (http://www.microsoft.com/ddk/). You can also read the DDK documentation in the MSDN Library (http://msdn.microsoft.com/library/): Select Windows Development, then Driver Development Kit.