INF CopyINF Directive

Windows XP and later

[DDInstall]
 
CopyINF=filename1.inf[,filename2.inf]...
 
 

A CopyINF directive causes specified INF files to be copied to the target system.

Comments

This directive is typically used when installing multifunction devices. If the installation of a multifunction device requires multiple INF files (for multiple functions belonging to multiple setup classes), then using this directive insures that Setup will find the INF files when installing the functions. Use the following rules:

• If the functions supplied by a multifunction device are enumerated as children of a parent device (such as an IEEE 1284.4 device), the INF file for the parent device should have a CopyINF directive to copy the INF files for the device's individual functions.
• If all functions supplied by a multifunction device (such as a PCI card) are enumerated as peers of each other, the INF file for each function should have a CopyINF directive to copy the INF files for all peer functions.

If you follow these rules, Setup can install drivers for each function without prompting the user for an installation disk for each function.

Setup copies the specified INF files as part of the default processing for DIF_INSTALLDEVICE (see SetupDiInstallDevice), after the device has been successfully installed.

The locations of INF files specified in the CopyINF directive are relative to the source location of the INF file containing the CopyINF directive.

Setup copies the specified INF files into a system directory path that it will search during device installations.

You must include all INF files on each disk of a multidisk installation.

System support for the CopyINF directive is available in Windows XP and later OS versions. You can also use the directive with Windows 2000 if you install and register the cocpyinf co-installer, which is supplied with this DDK in the /tools directory.

For additional information about copying INF files, see Copying INFs.

Example

[MyMfDevice.NTx86]
CopyINF = Sound.INF