Re: [Libusb-win32-devel] =?iso-8859-15?q?Trying_to_port_libdjconsole?= =?iso-8859-15?q?=3A_usb=5Fclaim=5Finterface_gives_a_return_code_-22=2C_wh?= =?iso-8859-15?q?at_does_this_mean=3F?=

[Stephan M. <ste...@we...>]

> On 4/9/07, Stephan Meyer <ste...@we...> wrote:
> >
> > This is most likely cause by the fact that you have installed
> > libusb's kernel driver as a filter. This doesn't work properly with
> > some HID devices.
> >
> > Uninstall the filter and install the kernel driver as a normal device
> > driver through an .inf file (use inf-wizard.exe to create one).
> >
> > It should work then.
> 
> The thing is that you need to uninstall the kernel HID driver and
> use the libusb-win32 device driver for this kind of HID device. This
> significantly reduces the usability of libusb-win32 for HID device
> under Windows. Yet many USB device disguise them as HID device
> just to avoid writing a device driver.
> 
> Just wondering if it is possible to use an alternative backend
> (Windows HID apli) and make libusb a wrapper on top of it.
> I understand then it should perhaps be called libhid-win32 then.

This sounds like a great idea! I'll add a native HID backend to the
next version of the DLL. It should be possible to implement most of
libusb's features on top of Windows' hid.dll such as open, close, 
interrupt-read/write and basic control messages. The rest can be 
emulated/simulated. 

> 
> By the way, will the new WinUSB based libusb-win32 solve this
> issue?

No, unfortunetly not. Winusb(.sys) is just a normal device driver like 
libusb0.sys. 

Stephan



_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192