Prev: NDIS60 Miniport sharing memory with user mode and WHQL
Next: NDIS 6.0 Using DOT11_OPERATION_MODE_NETWORK_MONITOR in Protocol Driver
From: 0dbell on 9 Jul 2007 12:21
I am trying to understand from reading the DPInst WDK documentation to
which category a virtual device driver would fall: a "device that is
configured in the system" or a "nonpresent device"?

The documentation reads:

"DPInst checks whether the hardware identifiers or compatible
identifiers in the INF file match a device that is configured in the
system or match a nonpresent device."

Since in a virtual device driver there is no hardware involved (i.e.
no "device that is configured in the system"?), it is tempting to
think that DPInst would be dealing with a "nonpresent device", right?

But when I install a virtual device driver (e.g. MSVAD) manually,
using Control Panel's Add Hardware, I am first prompted by a question
"Have you already connected this hardware to your computuer?" - to
which I must answer "Yes, I have already connected the hardware" or
else the driver will not be installed...

So, how is a virtual device driver treated from the standpoint of
DPInst?

Thanks,
Don

From: Sheeshpaul Kamboj on 10 Jul 2007 19:18
I had a similar problem creating a virtual HID device. I used SetupDi to
create a devnode, assigned a hardware ID to devnode, added hardware ID to
INF, and called DriverPackageInstall to load driver on devnode.

>> INFO: No matching devices found in INF
>> "C:\WINDOWS\system32\DRVSTORE\ ... \msvadsim.inf" on the Machine.
>> INFO: No drivers installed.
>> No devices found that match driver(s) contained in
>> 'C:\WINDOWS\system32\DRVSTORE\ ... \msvadsim.inf'.

it says it couldn't find any device that matches the hardware id specified
in INF, so no drivers installed.

 | 
Pages: 1
Prev: NDIS60 Miniport sharing memory with user mode and WHQL
Next: NDIS 6.0 Using DOT11_OPERATION_MODE_NETWORK_MONITOR in Protocol Driver