On 2012.06.18 16:31, Johannes Stezenbach wrote: > Doesn't Windows (WinUSB to be precise) return an error code > indicating the device was unplugged for the submitted transfers? > If Windows only returns "unlugged" status for one transfer > and forgets the other ones, can't you just fix this up in the > libusb Windows backend?
If my memory serves me correctly, I believe I tested it, and found that only the general error code was being returned. This is easy to test in debug mode, as the error code returned by WinUSB will be displayed. Regards, /Pete ------------------------------------------------------------------------------ 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
