On 2012.06.28 04:19, Jach Fong wrote: > On 27 Jun 2012 15:12:39 Pete Batard wrote: >> >> According to the error returned (LIBUSB_ERROR_NOT_FOUND) that seems to >> be the case. This is the error the Windows backend returns if it was >> unable to cache a config descriptor durin enum. >> >> Jach, if you're running a console application, can you please type the >> following in the command window where you run it: >> >> set LIBUSB_DEBUG=4 >> >> This will enable debug logging, which will indicate how many >> configurations were detected or whether there was an error during the >> caching of the descriptors. > > I run xusb.exe(compiled by BC++ Builder 5.0) under console,
If you're using BC++ Builder, are you using the pre-compiled libusb-1.0.dll, or did you also compile the libusb library? Since we don't provide project files for BC++, I guess you are using the DLL. > libusbx: error [cache_config_descriptors] could not access configuration > descriptor (actu > l) for '\\.\USB#VID_10C4&PID_0001#10807001': [995] 秪俴髯磐旰麼蚚最宒 > 猁ㄛ垀眕眒笢 > 砦 I/O 紱釬﹝ This is ERROR_OPERATION_ABORTED [995], which Microsoft describes as: The I/O operation has been aborted because of either a thread exit or an application request. I don't recall seeing ERROR_OPERATION_ABORTED in that context. We (Graeme) had an issue with ERROR_OPERATION_ABORTED and synchronous transfers back in 2010.03, but it should be fixed, and it had to do with the messaging pipe and overlapped events, which are not used at all to cache configuration descriptors. In this instance, the error is the code we get from a second DeviceIoControl() request, which comes after one that is identical and succeeds, but that doesn't ask for any data. So it looks like this is either a problem with your device, the Windows API or with the compiler. To eliminate the compiler, can you please download the libusbx-1.0.12-win.7z from http://sourceforge.net/projects/libusbx/files/releases/1.0.12/Windows/ and run the xusb.exe you find there in examples/bin32, prerablly with LIBUSB_DEBUG=4. If you get the same error, then we can eliminate BC++ as the possible cause. Also the information I get for VID_10C4&PID_0001 according to [1]), is that it's an HID touch screen kit. Is that correct? Regards, /Pete [1] http://ubuntuforums.org/showthread.php?t=1694716 ------------------------------------------------------------------------------ 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
