Re: [libusb] libusb_claim_interface -LIBUSB_ERROR_ACCESS

[Maxime B. <bla...@gm...>]

Wow thanks for the fast help!

libwdi's looks like a very nice project, exactly what I needed with the
InnoSetup example.
I also tried 1.2.6 instead of my old 1.2.4 (provided by Windows Update for
some reason..) and had the same problem claiming interfaces.
So I will use WinUSB like you suggested.

One thing that cause problem though.. I tested using WinUSB and some other
software can't recognize the stick after that (Ant Agent).  Is there an
alternative option, like using a previous verison of libusb? I would like
to be able to use libusb0 drivers since most of my users have this driver
already installed and I don't want to mess with their system/cause problem
to other software.

#define GARMIN_USB2_VID   0x0fcf

#define GARMIN_USB2_PID   0x1008

#define GARMIN_OEM_PID    0x1009



Thanks again for the help!

Maxime


On Mon, Feb 9, 2015 at 7:58 PM, Xiaofan Chen <xia...@gm...> wrote:

> On Tue, Feb 10, 2015 at 7:37 AM, Maxime Blais <bla...@gm...>
> wrote:
> > Quick update:
> >
> > I replaced the current driver of the device with WinUSB (v6.1.7600.16385)
> > and was able to claim interface now.
>
> Glad to know that. Currently libusb Windows backend is not working
> well with libusb0.sys (libusb-win32 device driver). BTW, your
> version of libusb0.sys is also old, the latest version is 1.2.6.0.
> But that does not matter much since you'd better use WinUSB
> for libusb Windows backend,
>
> > Is there a way to replace/use another driver on runtime?
> > I don't think my users will be able to use Zadig software to change their
> > drivers, so i'm looking for a solution to deploy the driver with my
> software
> > if possible
>
> Yes. You can write a driver installer to replace the existing driver.
> I think you can start with libwdi's wdi-simple driver example. libwdi
> is developed by Pete, the main developer of libusb Windows
> backend as well.
> URL: https://github.com/pbatard/libwdi/tree/master/examples
>
>
>
>
> --
> Xiaofan
>