On 16 August 2012 12:46, sebastiank wrote:
> The test machine is still running with LIBUSB_DEBUG set to 4. Do you
> know how you will do that?
If you're using the version of libusbx with the latest patches, we
will get the needed inisght about the cause for the error.
> It is unlikely that the e
On Wed, Aug 8, 2012 at 7:41 AM, Pete Batard wrote:
> All,
>
> If you have some interest with regards to libusb-win32 and libusbK
> driver support, you may want to have a look at the new 0K ("zero K")
> branch from the pbatard/libusbx repo on github [1].
>
> I have now pushed a patch that adds libu
On 2012.08.15 23:18, Pete Batard wrote:
> By the looks of it, the error you got on the test environment isn't the
> same as the one you get in prod, though I still wouldn't mind figuring
> out the cause of what happened in test.
The test machine is still running with LIBUSB_DEBUG set to 4. Do you
k
