>> So this seems like a bug in libusbx that it doesn't seem to honor the >> synchronous API expectations in this case, as evidenced by the concatenating >> of the >> buffers from multiple calls. Or am I missing something? > > Can you try using the libusb-win32 or libusbK driver instead of WinUSB? > Besides this being an issue with libusbx, there's a possibility this > could come from the WinUSB DLL or driver, so confirming that the same > issue occurs when using another of the 3 drivers we support on Windows > could give us some more insight. > > Zadig should allow you to replace the WinUSB driver with another one. > > Regards, > > /Pete
I actually started with libusb-win32 before I knew about libusbx and it had the same behavior, which is why I started looking for alternatives. ~QSE ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
