Alternate API for UpdateDriverForPlugAndPlayDevices().

NTDEV
1

Hi All,

I am looking for an alternative API using which i can update any Driver for
a device without having to embed the Vendor ID and Device ID in the inf
file…where i want to make my inf file very generic without having to be
bothered about the VID’s & DID’s for all the devices in the market.

Any kind of suggestion/guidance will be of great help.

Thanks,
-Kash.

2

I probably don’t understand your intention. If you have set of devices
with known VID and PID, your INF can contain all of them. Just list all
possibilities. What’s the problem?

PnP needs to know which INF to use for plugged in device. It makes the
decision according VID and PID (I assume USB device, Dear “Usb
Protocol”).

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com http:</http:>]

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Usb Protocol
Sent: Friday, May 23, 2008 2:46 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Alternate API for
UpdateDriverForPlugAndPlayDevices().

Hi All,

I am looking for an alternative API using which i can update any
Driver for a device without having to embed the Vendor ID and Device ID
in the inf file…where i want to make my inf file very generic without
having to be bothered about the VID’s & DID’s for all the devices in the
market.

Any kind of suggestion/guidance will be of great help.

Thanks,
-Kash.
— NTDEV is sponsored by OSR For our schedule of WDF, WDM,
debugging and other seminars visit: http://www.osr.com/seminars To
unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

3

Usb Protocol wrote:

I am looking for an alternative API using which i can update any
Driver for a device without having to embed the Vendor ID and Device
ID in the inf file…where i want to make my inf file very generic
without having to be bothered about the VID’s & DID’s for all the
devices in the market.

Nope, this is not what you want. Besides, Windows won’t do this.

You’re doing one of those USB redirector products, right? Filter
drivers are your key. On the side with the hardware, you need to
intercept the PnP reports that advertise the presence of a new device,
and just make sure it doesn’t get to PnP, or at least change it to
something that your own driver will claim. That’s how you’re going to
intercept all devices. You don’t need to have an INF for an arbitrary
VID and PID, because you can’t let PnP know about it.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

4

Usb Protocol" wrote in message news:xxxxx@ntdev…
>Hi All,
>
>I am looking for an alternative API using which i can update any Driver for
>a device without having to embed the Vendor ID and Device ID in the inf
> >file…where i want to make my inf file very generic without having to be
>bothered about the VID’s & DID’s for all the devices in the market.
>
>Any kind of suggestion/guidance will be of great help.
>

Look what Vmware does to redirect and attach USB devices to virtual
machines. This maybe is what you want.

–PA