On 05/02/2012 12:18 AM, Pete Batard wrote:
> On 2012.05.01 15:34, Uri Lublin wrote:
>>> Assuming you don't need to change the device's install class,
>> I'm think that assumption is not true with WinUSB based libusb driver.
>> A new install class is created for all WinUSB libusb devices.
>> (Maybe we can make use the same class used for USB devices ?)
> If the device was installed with libwdi, the ClassGUID used will be
> 88bae032-5a81-49f0-bc3d-a4ff138216d6 which is the class that is used by
> Microsoft for WinUSB/WCID devices in Windows 8. Please be mindful that,
> if you ever deal with WinUSB/WCID devices in Windows 8 [1], you will not
> be able to change the ClassGUID, as the driver installation will occur
> automatically, as for HID or Mass Storage devices.
What I meant was that for the ClassGUID values of e.g. USBSTOR and WinUSB
are different:
USBSTOR: 36FC9E60-C465-11CF-8056-444553540000
WinUsb: 88BAE032-5A81-49F0-BC3D-A4FF138216D6
Arnon showed that more registry entries differ too.
Thanks for the explanation,
Uri
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
libusbx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
