-
trobinso made 3 file-release changes.
2009-11-02 19:10:01 UTC by trobinso
-
trobinso made 3 file-release changes.
2009-11-02 19:09:08 UTC by trobinso
-
trobinso made 2 file-release changes.
2009-11-02 19:08:01 UTC by trobinso
-
trobinso made 3 file-release changes.
2009-11-02 19:07:01 UTC by trobinso
-
trobinso made 1 file-release changes.
2009-11-02 19:06:01 UTC by trobinso
-
Thanks for clarifying. Good luck. If you need supporters to lobby the libusb-win32 team, let us know.
2009-11-02 15:30:45 UTC by pckujawa
-
The disadvantage of the stock libusb-win32 kernel driver is that there is
NO relationship between the usb devices and the windows registry.
2009-10-31 16:55:57 UTC by trobinso
-
I think you have to do more than that. There are some other things to consider, like the device naming scheme (libusb0-0001, libusb-0002, etc), the install filter (if used).
The disadvantage of the stock libusb-win32 kernel driver is that there is to relationship between the usb devices and the windows registry. Libusb-win32 pulls everything directly from the usb device. This makes it...
2009-10-31 16:53:53 UTC by trobinso
-
I just changed the INF file for one device to name the libusb driver files to something else (i.e. libusb0.dll -> MyDevice.dll and libusb0.sys -> MyDevice.sys) and reflected that change by setting UsbGlobals.LIBUSB_SYS = "MyDevice.sys". With only MyDevice plugged in, as well as with a second libusb device using the libusb0 files plugged in, everything seems to work ok.
Do you foresee any...
2009-10-30 16:59:02 UTC by pckujawa
-
I am using 32-bit Windows 7 Ultimate.
You are right; the second device, when placed in a new usb port, was installing different libusb drivers than what was already there (installed by the first device, using LUDN's libusb drivers). I guess the fix lies in changing the libusb driver installation to use the drivers that are present, if any. I would have assumed that this was the default...
2009-10-30 16:08:07 UTC by pckujawa
