![]() ![]() Microsoft ships drivers for many common devices. The software that is required to support a particular device depends on the features of the device and the bus or port to which it connects. Long file names are allowed, except for boot-start drivers. Typically, a driver is a dynamic-link library (DLL) with the. The driver service is the part of the package that provides the I/O interface for a device. ![]() For more information on driver services, see Choosing a Driver Model. In most cases, a driver package will contain one or more driver services that should be part of the device stack for the device the driver package is installed on. The INF file must reference the catalog file with a CatalogFile directive in the INF Version section of the INF. For more information, see WHQL release signatures.įor information about how to sign drivers, see Signing Drivers for Public Release and Signing Drivers during Development and Test. WHQL returns the package with a catalog file (. To ensure that the catalog file is not altered, it must be digitally signed with a digital signature that would be trusted by the systems that should use this driver package.Ī vendor obtains release digital signatures by submitting its driver package to the Windows Hardware Quality Lab (WHQL) for testing and signing. Windows uses these hashes to verify that the package was not altered after it was published. Catalog fileĪ driver catalog file contains a cryptographic hash of each file in the driver package. Most of the WDK sample drivers include INF files in the same directory as the sample driver.įor more information about INF files, see Creating an INF File, the documentation for InfVerif, the device-specific documentation in the WDK, and the INF files that are supplied with sample drivers for devices similar to yours. Depending on the localities involved, an international INF file might have to be a Unicode (UTF-16) file instead of ASCII.Ī good way to create an INF file for your driver is to modify one of the samples that the WDK provides. If your device will be sold in the international market, you should create an international INF file. For more information, see Creating INF Files for Multiple Platforms and Operating Systems. Starting with Windows 2000, you can use a single INF file for installation on all versions of the Windows operating system. The InfVerif 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. Entries in the Models section refer to INF DDInstall sections that contain model-specific details. ![]() In general, per-manufacturer information is located in an INF Models section. Summary of INF Sections describes the information that is required in each type of INF. The exact contents and format of the INF file depend on the device setup class that the INF declares itself as being in. It is an ASCII or Unicode (UTF-16 only) 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 driver package on a device. An INF file is not an installation script. For more information, see Sample Device Installation Files INF fileĮvery driver package must include an INF file, which the device installation components read when installing the device. The WDK includes various sample driver packages. Typically, a driver package contains the following components:Ī brief description of each component of a driver package follows. A driver package includes all the software components that you must supply to ensure that your device is supported with Windows. ![]()
0 Comments
Leave a Reply. |