This section describes keys you can add to the answer file or UDF to add your own files or information to the retail version of Windows NT Workstation.
To specify your own advertising or information during GUI Mode Setup, the following section must exist:
[OEM_Ads]
Banner = text
Logo = file_name{, n]
Bitmap = file_name{, n]
The value of the Banner key is the text string to be displayed as a banner in the upper left of the screen during GUI Mode Setup. The text must contain the substring "Windows NT Workstation" or "Windows NT Server" in order to be displayed. To create a multi-line banner, insert an asterisk (*) where a line break is to appear. If the Banner key is empty or does not contain the "Windows NT Workstation" or "Windows NT Server" substring, the Windows NT retail banner will be displayed.
The value of the Logo key is the filename of a bitmap to be displayed in the upper right corner of the screen during GUI Mode Setup. If your bitmap is referenced in a dynamic link library (DLL), you can specify the name of the DLL followed by the resource ID. The DLL must be in $OEM$\Oemfiles, and the resource ID must be supplied in base-10 format. If only a file name is specified, it must be the name of a .bmp file in $OEM$\Oemfiles that contains the bitmap.
If the Logo key is not specified, or its value is empty, or it specifies a non-existent bitmap, then the Windows NT retail bitmap will be displayed.
The value of the Bitmap key is the name of a bitmap that is to be tiled as a background during end-user setup.
If your bitmap is referenced in a dynamic link library (DLL), you can specify the name of the DLL followed by the resource ID. The DLL must be in $OEM$\Oemfiles, and the resource ID must be supplied in base-10 format. If only a file name is specified, it must be the name of a .bmp file in $OEM$\Oemfiles that contains the bitmap.
If the Bitmap key is not specified, or its value is empty, or it specifies a non-existent bitmap, then the Windows NT retail bitmap will be displayed.
For best results on VGA-based displays this bitmap should be exactly 640 x 480 pixels. On ARC computers (which don't necessarily use VGA mode during setup) other optimal sizes may be possible. If the bitmap is monochrome, it will be tinted blue when displayed (like the retail background bitmap, which is itself monochrome).
To run a custom program concurrently with Setup, add the following line to the [GuiUnattended] section:
DetachedProgram = path\filename
where path and filename describe the location of the custom program. For example:
DetachedProgram = c:\mt32\mtrun.exe
To supply arguments to the custom program, add the following line to the [GuiUnattended] section:
Arguments = path\filename/argument
where path\filename indicates the path to the program and argument indicates the arguments you want to supply. For example:
Arguments = c:\mt32\scriptl.pcd/H
To include files you have added to customize the application, the following line must be present in the [Unattended] section:
OemPreinstall = Yes
A Yes value indicates that Windows NT Setup might need to install some OEM-supplied files located in subdirectories of $OEM$.
The default value is No. The default is used when the OemPreinstall key is missing. The No value implies that Setup will perform a regular unattended installation.
This key can only be specified in the answer file, not in the UDF. The keys described in the following sections are used only if OemPreinstall = Yes.
To install display drivers, include the following section:
[DisplayDrivers]
driver_description = Retail | OEM
.This section is optional. If the [DisplayDrivers] section is empty or absent, Setup will install all the Windows NT retail display drivers during Text Mode Setup. During GUI Mode Setup, any drivers that fail to initialize will be disabled.
The driver_description value identifies the driver to be installed. This value must match one of the strings defined in the right-hand side of the [Display] section of Txtsetup.sif (except for the string "Standard VGA (640x480, 16 colors)" or Txtsetup.oem (for an OEM-supplied driver).
This key can only be specified in the answer file, not in the UDF. This section is valid only if OemPreinstall = Yes.
To install SCSI drivers, include the following section:
[MassStorageDrivers]
driver_description = Retail | OEM
.This section is optional. If the [MassStorageDrivers] section is empty or absent, Setup will attempt to detect and install all known miniport drivers.
The driver_description value identifies the driver to be installed. This value must match one of the strings defined in the [SCSI] section of Txtsetup.sif or Txtsetup.oem (for an OEM-supplied driver).
This key can only be specified in the answer file, not in the UDF. This section is valid only if OemPreinstall = Yes.
To specify keyboard drivers to be installed, include the following section:
[KeyboardDrivers]
driver_description = Retail | OEM
.This section is optional. If the [KeyboardDrivers] section is absent or empty, Setup will detect and install a keyboard driver from the retail Windows NT product.
The driver_description value identifies the driver to be installed. This string must match one of the strings defined in the [Keyboard] section of the Txtsetup.sif or Txtsetup.oem (for an OEM-supplied driver).
This key can only be specified in the answer file, not in the UDF. This section is valid only if OemPreinstall = Yes.
To install pointing device drivers, include the following section
[PointingDeviceDrivers]
driver_description = Retail | OEM
.
.
.This section is optional. If the [PointingDeviceDrivers] section is absent or empty, Setup will detect and install a pointing device driver from the retail Windows NT product.
The driver_description value identifies the driver to be installed. This string must match one of the strings defined in the [Mouse] section of Txtsetup.sif or Txtsetup.oem (for an OEM-supplied driver).
This key can only be specified in the answer file, not in the UDF. This section is valid only if OemPreinstall = Yes.