On Fri, May 30, 2014 at 10:17 PM, Steve Soloski <ssoloski@xxxxxxxxxxxxxx> wrote:
> Well, after banging my head against the wall all day yesterday, I've figured
> out what's happening...
>
> In all of my installing/uninstalling of the USB driver - trying both
> libusbK-inf-wizard and zadig - I eneded up with both libusb0.dll and
> libusbK.dll on my system, in addition to the WinUSB that I wanted. Not quite
> sure how they all got installed, but when I deleted both of them (and only
> used the WinUSB driver) then this issue went away. Not sure what was causing
> the issue, but at least it's resolved!
>
Hmm, that is strange. libusbk-inf-wizard and Zadig both install libusb0.dll
and libusbK.dll to be compatible with libusb-win32 and libusbK.
As for libusb Winodws backend, it will work either with libusbK.dll (to
support libusb0.sys, libusbK.sys and WinUSB) or without libusbK.dll
(only works with WinUSB). The code path will be a bit different.
Are you using the latest release version of libusb (1.0.18)?
--
Xiaofan
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
