W
Wade_Dawson
Guest
I'm seeing a behavior with a USB composite device that Ive not seen before and wondered if anyone could offer some insight.
We have a USB device with 3 interfaces in its config; AC, AS and MSC. There is an IAD for the the AC+AS, then another for the single MSC interface. The device descriptor C/S/P is 0xEF/02/01 and usbcgp correctly loads on the device and our custom usb midi (multi-client) driver and the inbox msc driver are loaded and work correctly. If the USB device is unplugged / plugged back in, usbcgp.sys no longer loads on the device and our custom driver loads instead rendering the MSC device inaccessible. If we don't install our custom driver, i.e. use the MS inbox Usbaudio2 driver all works as expected across plug / unplug cycles.
The OS is Windows10/1903 x64, but the behavior is consistent on other versions of win10 we tested at least back to 1709.
Thanks for any help you can provide.
Continue reading...
We have a USB device with 3 interfaces in its config; AC, AS and MSC. There is an IAD for the the AC+AS, then another for the single MSC interface. The device descriptor C/S/P is 0xEF/02/01 and usbcgp correctly loads on the device and our custom usb midi (multi-client) driver and the inbox msc driver are loaded and work correctly. If the USB device is unplugged / plugged back in, usbcgp.sys no longer loads on the device and our custom driver loads instead rendering the MSC device inaccessible. If we don't install our custom driver, i.e. use the MS inbox Usbaudio2 driver all works as expected across plug / unplug cycles.
The OS is Windows10/1903 x64, but the behavior is consistent on other versions of win10 we tested at least back to 1709.
Thanks for any help you can provide.
Continue reading...