Re: [Libusb-win32-devel] HID device problem

[Xiaofan C. <xia...@gm...>]

On 8/24/06, Adam Kropelin <akr...@ro...> wrote:
> Stephan Meyer wrote:
> > Have you tried to install/update the driver by using the DLL's
> > (undocumented) usb_install_driver_np function?
>
> FWIW, this technique works fairly well for my HID devices. The only
> problem I've noticed is that if I install the driver, then unplug the
> device and plug in a different USB device (but one that still matches my
> vendor/product spec) libusb does not get assigned to it. Instead the
> default MS driver is assigned until I either run usb_install_driver_np
> again or manually "update driver" via the DeviceManager GUI. I'm curious
> why libusb does not get bound to all subsequent devices that match the
> spec.
>

For PICkit 2, it works without a problem. If I unplug and plug
in the same device,  libusb-win32 device driver is still assigned
to the device driver. If I unplug a PICkit 2 and plug in another
PICkit 2, libusb-win32 device driver is still assigned.

PICkit 2 device does not have unique serial number since
it is not common for a user to have 2 PICkit 2 programmer.

Your device might have different serail number assigned to
them and this might be the reason. I am not sure though.

And even better, after I "update" the libusb-win32 device driver
to HID driver, PICKit 2 now appears as a normal HID device:
2 entries under "Human Interface Device" -- "HID-compliant
device" and "USB Human Interface Device". This is great!

I just wonder why Windows only list PICkit 2 as an "HID-compliant
device" last time? That is strange.

Regards,
Xiaofan