therau2000 wrote: > > > 2-More intensive testing showed > > > > What testing? > > My own testing; who else's?
Of course, but how did you do it? > > Let's try another approach: Tell us everything you know about the > > device, and show some kind of capture of the non-storage communication. > > Find attached files: > xusb-output.txt > device-sniffer-output.txt Thanks. Although this is not very detailed, it still has some interesting information. > Device commands are op code C5; they are all the same with > different parameter values. Nothing interesting there. I'm not sure if these are visible in the sniffer output? > The sniffer output is from the "competing program" using default OS > driver USBSTOR. It contains BOTH types of communication and the > switch over is quite visible. Where would you say that it happens in the log? Also, do I understand correctly that you snipped part of the log out - from URB 45 up until URB 153, the response to URB 152? Without looking very closely at any of the data being sent, it's clear from the log that the only Driver Name values are USBSTOR and usbhub. This means that you will need to talk to those drivers in order to replicate what the competing program does, rather than trying to use libusb. I still think the storage subsystem has your answer. //Peter ------------------------------------------------------------------------------ WINDOWS 8 is here. Millions of people. Your app in 30 days. Visit The Windows 8 Center at Sourceforge for all your go to resources. http://windows8center.sourceforge.net/ join-generation-app-and-make-money-coding-fast/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
