|
From: Pete B. <pe...@ak...> - 2012-01-17 11:50:25
|
Hello Michele, On 2012.01.17 11:00, michele.paolino wrote: > libusb_clear_halt(cur_handle, ENDPOINT_BULK_OUT); is there a reason you issue a clear_halt? As its name indicate this call is intended to be used in case of a transfer problem, so it's a bit unexpected there unless you expect a previous call to fail. Does the same problem occur on the first transfer if you remove the clear_halt? > libusb_set_configuration(cur_handle, 1) http://www.libusb.org/wiki/windows_backend#KnownRestrictions : "WinUSB cannot be used to set a device configuration that is different from the default one. This is a limitation of the Microsoft driver." You should try to avoid using libusb_set_configuration on Windows (at least as long as we only support WinUSB as a driver), unless you are certain to select the default one. > Are there known issues with windows x64? Most of the development and testing of the Windows backend is done on Windows x64 (if anything, it's the 32 bit version that is tested the less), so x64 is not expected to present more problems than non x64. I'll try to investigate this further when I have a chance. Regards, /Pete |