I have a lower filter driver for usbhub.sys for my usb composite device.It is
working fine in Win 2K and win XP enumerating all three functions
(Audio,video and mass storage )
properly .However in Win Me, the mass storage is not enumerated properly.

I saw that in the registry in Win 2K the CompatibleID created is
USB\Class_08&SubClass_06&Prot_50,USB\Class_08&SubC lass_06,USB\Class_08
while in Win Me it is
USB\CLASS_08&SUBCLASS_06&PROT_80,USB\CLASS_08&SUBC LASS_06,USB\CLASS_08

My device has Protocol Id 50 in it's interface descriptor
If I manually change the id in the registry to 50 in win Me ,the mass
storage driver (usbstor.sys ) is loaded and the it's works fine
any hints on how I could go about debugging this issue are welcome ?

This is a bug in the Windows Me version of USBCCGP.SYS, which is used as
the composite device driver on WinMe. The WinMe version of
USBCCGP creates compatible IDs using decimal values rather than hex values
(i.e. 50h = 80d), which is incorrect. USB storage devices that get
installed based on the compatible ID will not install using the INF shipped
on Windows Me. Vendors typically just ship their own INF for their
composite USB storage device to work around this problem.

Thanks,
Martin Borve [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Martin
Thanks for the info
But I dont understand one thing here.If I do not use my driver, and let
windows act as enumerator exclusively,the drivers are loaded for all
including mass storage interface ....
why does not it (usbccgp.sys) not create a problem then ?


""Martin Borve [MSFT]"" wrote:

With no other third part INFs installed for either the parent device or the
mass storage interface, it should fail.

Thanks,
Martin Borve [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

ofcourse I use my inf to instruct the OS to use usbhub.sys/usbccgp.sys as
the parent driver for my composite device however then also mass storage
interface works properly with usbstor.sys for it being installed
automatically ...

""Martin Borve [MSFT]"" wrote:

If you are using USBHUB as the parent driver, it does not have the problem
that USBCCGP has, so it should work correctly.

Thanks,
Martin Borve [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.