Re: driver, not device, installation

Xiaofan Chen <[email protected]> Tue, 18 Sep 2018 09:37:08 +0800
Newsgroups gmane.comp.lib.libusb.devel.windows
Message-ID <CAGjSPUCBBYvC-_NwkuyZRObSfi0ezaHBZcrvgvU2WWSEEQtFJw@mail.gmail.com>
On Thu, Sep 13, 2018 at 2:01 AM Tyler Bell <[email protected]> wrote:
>
>> > Backing up a bit, I have to interface with a device that has a driver from the manufacturer(FTDI
>> > USB-serial cables). The OEM driver is limited(but also required) so I've augmented it w/ libusb.
>> > The best way to manage this on a client's machine that I can find is to use libusb as a filter driver.
>> > However, to install libusb as a filter driver for a device, libwdi assumes that libusb already exists
>> > on the client machine. This is not a good assumption to make for a client machine. Infwizard doesn't
>> > seem capable of creating an inf for filter driver mode and I'm not sure that, even if it did, it would copy
>> > the DLL&SYS files.
>>
>> If you use FTDI device, better way is to use libftdi-1.0 and it uses
>> libusb-1.0 API, there you
>> have the option of using different libusb-1.0 Windows backend, one of
>> the option is to use
>> usbdk (filter, similar to libusb-win32 filter but works better in new
>> Windows versions).
>
>
> I would love to use libftdi, but I am stuck w/ the stock driver from FTDI. That is why I'm trying to
> use libusb as a filter driver; I need to add a bit of functionality to one tool, but there are a
> handful of other tools that use the same FTDI device and those are built w/ the FTDI driver.

As answered below, you can use usbdk as a filter and use libftid, and
at the same time
keep the FTDI vendor driver as it is.

>> For usbdk, it is the same, you need to the 32bit/64bit installer first
>> (as admin) and then you
>> can use the command line to install/uninstall the filter.
>> https://github.com/daynix/UsbDk
>> https://github.com/daynix/UsbDk/releases
>>
>> You may need to use libusb-1.0.21 build with usbdk for now and not
>> libusb-1.0.22 due to
>> the following change. libftdi has not been updated to incorporate the change.
>> https://github.com/libusb/libusb/issues/443
>>
>> Leagacy libftdi-0.1 uses libusb-0.1 API and you can use libusb-win32
>> filter with it but libftdi-0.1
>> is no longer maintained.
>>




-- 
Xiaofan