I found UVC device would be a multi-interface USB device.
For example, interface 0 is for video control interface and interface 1 is
for video stream interface.
As I konw, multi-interface device will display composite device first, and
then find driver for each interface.
However, it seems that XP SP2 only query driver for interface 0 of UVC
device after display composite device.
It doesn't query driver for interface 1 of UVC device.

If I plug in UVC device on WinME, it will query driver for interface 0 and 1
of UVC device after display composite device.
If I plug in UVC device onWin2000, it doesn't display composite device.
Why doesn't Win2000 find composite device first for UVC device?

I think the behavior difference is a serious problem for developing UVC
driver on these OS.
For example, do I need to write different driver for each interface of UVC
device on WinME?
Do I need to handle multi-interface in one driver on Win2000?

Best Regards
Jack Huang

Re: composite device behavior of UVC device on Win98/ME/2000/XP? by chris

chris
Sat Jun 02 12:48:11 CDT 2007

On May 31, 11:12 pm, "huangjj" <huan...@hotmail.com> wrote:

> If I plug in UVC device on WinME, it will query driver for interface 0 and 1
> of UVC device after display composite device.
> If I plug in UVC device onWin2000, it doesn't display composite device.
> Why doesn't Win2000 find composite device first for UVC device?

Remember, the criteria for getting the generic parent loaded are:

1) Class, Subclass, Protocol all zero

2) NumConfigurations == 1

3) NumInterfaces > 1

Does your device match this? This may have been different on WinME (I
have no idea).