On Thu, Sep 6, 2012 at 9:56 PM, Xiaofan Chen <xiaof...@gmail.com> wrote: > On Thu, Sep 6, 2012 at 6:26 AM, Pete Batard <p...@akeo.ie> wrote: >> OK, IMO, the best way to address that last issue we have with libusb0 as >> composite device is by modifying the libusb0 inf file to create a Device >> Interface GUID during installation. >> >> In this case, this is really a one liner change in libwdi: >> --- "a/D:\\libwdi\\libwdi\\libusb0.inf.in" >> +++ "b/D:\\libwdi\\libwdi\\libusb0.inf.in" >> [libusb_add_reg_hw] >> HKR,,SurpriseRemovalOK,0x00010001,1 >> +HKR,,DeviceInterfaceGUIDs,0x00010000,%DeviceGUID% > > Yes this indeed solved the problem with libusb0.sys > with regard to composite device.
Since you have not released the update Zadig yet. I manually edited the inf file generated by libusbK's inf-wizard2 (MSVC based) and installed the driver. I have not tested the filter cases since it will rely on an updated Zadig or the libusb-win32 install-filter.exe. -- Xiaofan ------------------------------------------------------------------------------ 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 libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
