On Mon, Oct 1, 2012 at 8:23 AM, Pete Batard wrote:
> On 2012.10.01 00:57, Xiaofan Chen wrote:
>> One minor issue, libusb0.dll is not used for libusbK.dll, libusbk.dll
>> directly talked to libusb0.sys, just like it directly talks to libusbk.sys.
>
> Ok. I was wondering about that as well. Another
On Mon, Oct 1, 2012 at 8:23 AM, Pete Batard wrote:
> On 2012.10.01 00:57, Xiaofan Chen wrote:
>> libusbK's inf-wizard (MFC based) does bundle libusbk.dll and libusb0.dll
>> for both libusb0.sys and libusbk.sys since libusbk.dll and libusb0.dll
>> work with both libusb0.sys and libusbk.sys. libusbk
On 2012.10.01 00:57, Xiaofan Chen wrote:
> One minor issue, libusb0.dll is not used for libusbK.dll, libusbk.dll
> directly talked to libusb0.sys, just like it directly talks to libusbk.sys.
Ok. I was wondering about that as well. Another good job from Travis
then (but then leaving me even more p
On Mon, Oct 1, 2012 at 5:24 AM, Pete Batard wrote:
>>Of course, a nice graphical
>> presentation of the Windows driver layering would be very welcome :)
>
> 1. With libusbK.dll available
>
>libusbx
> |
> V
>libusbK.dll
> |
> ++---
Hi Tormod,
The first thing I want to mention, before discussion your issue (which
is something that should have appeared in the ChangeLog, but that I
completely forgot to add), is that support for the libusb-win32 and
libusbK drivers in libusbx is still very EXPERIMENTAL at this stage, and
wil
Hi,
I wanted to use libusb-win32 as driver for libusb-1.0 so I used Zadig
to change the driver for the device from WinUSB to libusb-win32.
However doing just this would fail. For instance xusb was not able to
read the description strings. The logs were saying something like:
libusbx: debug [libus
