The OEMSETUP.INF file uses the same format as the Windows 3.0 SETUP.INF file with the exception of a new [Installable.Drivers] section. This section identifies the names and characteristics of each driver on the disk. Each driver entry has the following form:
entry=disk:filename, type(s), description, VxD(s), default_params
Note that the elements that compose a driver entry are separated by commas. Comments are delimited by semicolons; all characters following a semicolon are considered part of the comment string.
Following are the elements that compose a driver entry:
| Element | Description |
| entry | Identifies the driver. This string must be unique. |
| disk | Specifies the disk number for the disk that contains the driver. This entry corresponds to an entry in the [disks] section of SETUP.INF. |
| filename | Specifies the name of the file that contains the driver. |
| type(s) | Specifies the driver type. |
| description | Describes the driver. This string appears in the dialog box displayed by the Drivers Control Panel application. |
| VxD(s) | Identifies any VxDs required by the driver. (For a description of the manner in which multiple VxD names are parsed, see the Microsoft Windows Virtual Device Adaptation Guide.) |
| default_params | Specifies default parameters for the driver. Additional options are appended to the driver entry in the [drivers] section of SYSTEM.INI. |
If you create an OEMSETUP.INF file to distribute with your driver, it must include the [disks] and [Installable.Drivers] sections. For example, the following entries could be used in an OEMSETUP.INF file for a prototype installable driver:
[disks]
; Numeric mappings for disk titles
1 = ., "Sample Distribution Disk 1"
[Installable.Drivers]
; The installable drivers section is unique to the drivers application.
; It is parsed with comma-separated fields.
prototype=1:proto.drv,"ampl,freq","Sample scope driver","1:VXDA.386"The Drivers Control Panel application may need to copy files that support your driver. If any of these files are not VxDs, include a section in the SYSTEM.INI file listing them. Use the entry (that is, prototype) as the name of this new section. For example, if the prototype driver has an additional file called POWERSRC.DLL, include the following section:
[prototype]
; Keyname sections can be created for dependent files. All
; dependent files will be copied directly to the system directory.
1:POWERSRC.DLL