Do the equivalent of installing a driver from a folder, programatically, in Windows XP or higher

I need to have a driver installed in my customers' computers. Unfortunately, the only way to do this right now is having Windows show its "Hardware Update Wizard" when the device is plugged in, and then have the user do the following:

• select "No, not this time",
• select "Install from a specific location (Advanced)",
• check or uncheck app开发者_如何转开发ropriate checkboxes and select the folder that contains the drivers

All of which is slow and unfriendly for a non technically savvy user. For the people who must install the device in many computers, it's a repetitive and annoying process too.

So, I'm trying to write a very simple program that will prompt the user to plug in the device. Then the program will do the same steps above automatically. My questions:

• I wonder if there is a Windows API that looks for drivers in a folder, since that's what the Wizard does.
• I've just discovered the function DriverPackageInstall. Would passing the .inf file as a parameter do what I want? (I'll be writing code to test this in the meanwhile, just give me some time to download the Windows Driver Kit and set up a project...).
• Any other suggestions?

You did not specify which version of Windows.

On Windows 7 there`s pnputil:

c:\>pnputil -?
Microsoft PnP Utility
Usage:
------
pnputil.exe [-f | -i] [ -? | -a | -d | -e ] <INF name>
Examples:
pnputil.exe -a a:\usbcam\USBCAM.INF      -> Add package specified by USBCAM.INF
pnputil.exe -a c:\drivers\*.inf          -> Add all packages in c:\drivers\
pnputil.exe -i -a a:\usbcam\USBCAM.INF   -> Add and install driver package
pnputil.exe -e                           -> Enumerate all 3rd party packages
pnputil.exe -d oem0.inf                  -> Delete package oem0.inf
pnputil.exe -f -d oem0.inf               -> Force delete package oem0.inf
pnputil.exe -?                           -> This usage screen

programmatically, you can use DiInstallDriver

There are several ways and some depend on the type of device you have.

There are several tools for installing driver packages.

1. DpInst is a complete application which can show a wizard and be customized to install a driver package

2. DifXApp builds a msi package which can be used to install drivers

3. DifxApi is the API which DpInst and DifxApp use to install drivers.

4. Directly using the SetupApi functions.

   Here the functions SetupCopyOEMInf and UpdateDriverForPlugAndPlayDevices provide the corresponding entry points for a driver setup. These are contained in the WinSDK.

DpInst/DifxApp/DifxApi are part of the Windows Driver Kit (WDK).

DifX (found in the Windows DDK) is the Microsoft recommended way for installing drivers. DPInst is the standalone tool and DifX API is the programmatic way.

If the driver is signed, you can use DPInst (or DifX API) to preinstall it and then it'll be installed (without any wizards or prompts) as soon as the user inserts the hardware.

If the driver is unsigned (i.e. has no signed .cat file), then:

• on Windows Vista and higher, you can sign it yourself (typically with a certificate you purchase from a CA, though self-signing might be possible)
• on Windows XP, you're doomed (unless you apply some real ugly hacks)