This article was previously published under Q318214
This article has been archived. It is offered "as is" and will no longer be updated.
When you use the system-supplied parent .inf file, Mf.inf (or any other compatible .inf file that does not have override configurations for the children functions), to install a multifunction PC card that fully implements the PCMCIA multifunction standards, you may receive the following error message for the child functions:
There are no compatible drivers for this device.
The result is that none of the drivers is installed.
To work around this problem and to install the multifunction card, use a parent .inf file with override configurations that provide registry entries that define information about the children functions (such as their hardware IDs and I/O resources maps).
For more information, see the following Windows DDK topic on the MSDN Web site:
Microsoft has confirmed that this is a bug in the PCMCIA.sys module.
This behavior occurs as follows:
First, the PnP manager sends IRP_MN_QUERY_ID to the multifunction driver (Mf.sys) to get the hardware and compatible IDs of its children devices.
Mf.sys obtains the IDs from PCMCIA and returns them to the PnP manager.
To locate a driver match, the PnP manager compares the device's hardware and compatible IDs (as generated by PCMCIA) to the hardware and compatible IDs that are listed in the .inf files on the system and then builds a list of compatible drivers for the device. Because of the problems in generating correct IDs, no match is found and the compatible drivers list is empty.
Last, when selecting the best compatible driver from the list, the PNP manager displays the message "There are no compatible drivers for this device".