Please see my comments below:
On 9/17/2013 12:55 AM, Pete Batard wrote:
Hi,
I just tested on Windows 8 x64 and, while I was at it, Windows 8.1 x86
(MSDN RTM version) against the WCID enabled benchmark device and found
no issue when using an USB 2.0 device, be it through an USB 2.0 or and
USB 3.0 HCD (see logs below). In both cases, the version of the WinUSB
driver that was installed was v6.2.9200.16384 which is the same as yours.
These machines had not had another WCID device installed and the only
weird thing I saw is that Windows 8.1 seems to be installing WinUSB as
a filter driver ontop of WUDFRd rather than as a "proper" driver, but
that didn't seem to bother libusbx 1.0.17.
Now, as you just confirmed seems to be an issue with your device
interface configuration, so what I'd like to get some confirmation of is:
- whether any device presenting 2 interfaces and using the
v6.2.9200.16384 driver has an issue (WCID or not)
- whether reverting the driver to the version used by Zadig alleviates
the issue.
On Zadig I have two options "Downgrade WCID driver" or install
"Replace driver". The downgrade option doesn't seem to work as after
downgrade the version 6.2 still installed. If I choose the option
"Replace driver" the device works correctly with libusbx.
As much as I'd like to, I don't think I'll have time to run these kind
of tests myself, especially if WCID + 2 interfaces is a prerequisite
to reproduce the issue, so your cooperation on these tests would be
appreciated.
Sure, just tell me what test you need me to perform.
Also note that there exists limitations with regards to using WinUSB
when accessing interfaces using LIBUSB_RECIPIENT_INTERFACE
See
https://github.com/libusbx/libusbx/wiki/Windows-Backend#wiki-Known_Restrictions
From the linkj I read:
/
//If you use a composite device, and plan to install a libusbx
compatible driver for any of the interfaces, you should ensure that your
driver package adds a Device Interface GUID in the registry, as proper
enumeration of composite devices in libusbx depends on it. This is
typically achieved by adding something like the following in your inf://
//|HKR,,DeviceInterfaceGUIDs,0x00010000,{12345678-1234-1234-1234-123456789ABC}|/
May be this the source of troubles?
Kind regards,
Ramon
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
