Supplying an INF File

Every driver package must include an INF file, which the device installation components read when installing the device. An INF file is not an installation script. It is an ASCII or Unicode text file that provides device and driver information, including the driver files, registry entries, device IDs, catalog files, and version information that is required to install the device or driver. The INF is used not only when the device or driver is first installed, but also when the user requests a driver update through Device Manager.

The exact contents and format of the INF file depend on the device setup classes. Summary of INF Sections describes the information that is required in each type of INF. In general, per-manufacturer information is located in an INF Models section. Entries in the Models section refer to INF DDInstall sections that contain model-specific details.

The ChkINF tool, which is provided in the \tools directory of the Microsoft Windows Driver Kit (WDK), checks the syntax and structure of all cross-class INF sections and directives, together with the class-specific extensions for all setup classes except for Printers.

Starting with Windows 2000, you can use a single INF file for installation on all versions of the Windows operating system. For more information, see Creating INF Files for Multiple Platforms and Operating Systems. If your device will be sold in the international market, you should create an international INF file. Depending on the localities involved, an international INF file might have to be a Unicode file instead of ASCII.

A good way to create an INF file for your driver is to modify one of the samples that the WDK provides. Most of the WDK sample drivers include INF files in the same directory as the sample driver.

For more information about INF files, see Creating an INF File, the documentation for ChkINF, the device-specific documentation in the WDK, and the INF files that are supplied with sample drivers for devices similar to yours.

 

 

Send comments about this topic to Microsoft

Show:
© 2014 Microsoft