Device information (INF) files are text files that provide information used by the Plug-and-Play mechanism on Windows 7 / Vista / Server 2008 / Server 2003 / XP / 2000 / Me / 98 to install software that supports a given hardware device. INF files are required for hardware that identifies itself, such as USB and PCI. An INF file includes all necessary information about a device and the files to be installed. When hardware manufacturers introduce new products, they must create INF files to explicitly define the resources and files required for each class of device.
In some cases, the INF file for your specific device is supplied by the operating system. In other cases, you will need to create an INF file for your device. WinDriver's DriverWizard can generate a specific INF file for your device. The INF file is used to notify the operating system that WinDriver now handles the selected device.
For USB devices, you will not be able to access the device with WinDriver (either from DriverWizard or from the code) without first registering the device to work with windrvr6.sys. This is done by installing an INF file for the device. DriverWizard will offer to automatically generate the INF file for your device.
You can use DriverWizard to generate the INF file on the development machine – as explained in section 5.2 of the manual – and then install the INF file on any machine to which you distribute the driver, as explained in the following sections.
![]() | |
You must have administrative privileges in order to install an INF file. |
You can use the wdreg utility with the
install
command to automatically install the INF file:
wdreg -inf <path to the INF file> install
(For more information, refer to
section 10.2.2 of the manual.)
On the development PC, you can have the INF file automatically installed when selecting to generate the INF file with DriverWizard, by checking the 5.2).
option in the DriverWizard's INF generation window (refer to sectionIt is also possible to install the INF file manually, using either of the following methods:
In all the manual installation methods above you will need to point Windows to
the location of the relevant INF file during the installation.
We recommend using the wdreg utility to
install the INF file automatically, instead of installing it manually.
![]() | |
If the installation fails with an
ERROR_FILE_NOT_FOUND error, inspect the Windows registry to
see if the RunOnce key exists in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion .
This registry key is required by Windows Plug-and-Play in order to properly install
drivers using INF files. If the RunOnce key is missing, create
it; then try installing the INF file again.
|
![]() | |
You must have administrative privileges in order to replace a driver. |
Install your INF file:
You can use the wdreg utility with the
install
command to automatically install the INF file:
wdreg -inf <path to INF file> install
(For more information, refer to
section 10.2.2 of the manual.)
On the development PC, you can have the INF file automatically installed when selecting to generate the INF file with DriverWizard, by checking the 5.2).
option in the DriverWizard's INF generation window (refer to sectionIt is also possible to install the INF file manually, using either of the following methods:
In the manual installation methods above you will need to point Windows to the location of the relevant INF file during the installation. If the installation wizard offers to install an INF file other than the one you have generated, select
and choose your specific INF file from the list.We recommend using the wdreg utility to install the INF file automatically, instead of installing it manually.
![]() | |
If the installation fails with an
ERROR_FILE_NOT_FOUND error, inspect the Windows registry to
see if the RunOnce key exists in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion .
This registry key is required by Windows Plug-and-Play in order to properly install
drivers using INF files. If the RunOnce key is missing, create
it; then try installing the INF file again.
|