Re: [Libusb-win32-devel] driver, not device, installation

[Tyler B. <mrb...@gm...>]

>From what I can tell, that is not, what I need. That targets the driver to
a device, which is what the bug 84 conversation indicates I should not do.
I only want the .sys and .dll in the correct windows directories and
registered to the system. This is complicated by the need for UAC and 32/64
bit divide(a 32 bit app cannot install drivers on a 64-bit machine and and
64-bit app cannot run on a 32-bit machine).
 These are not huge issues, but as libusb has already nicely solved these
concerns for "primary driver" installation, it would be great(and, it
seems, trivial?) if we could reuse the existing code for filter driver
installation.

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.


On Thu, Sep 6, 2018 at 5:51 PM Chris E <sp...@gm...> wrote:

> Sorry, by "the SDK" in my last email, I meant "the libusbK SDK".  Within
> Inf Wizard, you can select an option to use libusb0.
>
> On Fri., 7 Sep. 2018, 2:36 am Tyler Bell, <mrb...@gm...> wrote:
>
>> First, let me apologize for opening this ticket(
>> https://sourceforge.net/p/libusb-win32/bugs/84/) rather than using the
>> mailing list.
>>
>> Second, let me apologize for being dense, but the suggestion "You need to
>> install the base package (libusb installer or libusbk installer) to install
>> libusb0.sys into the system." isn't quite clear to me.
>> The only "base package" installer I can find is for the development kits,
>> which isn't something we should be putting on customer machines. If, on the
>> other hand, you are saying I need to create my own installer, that's
>> probably fair, but also a fair amount of work w/ the 32/64-bit divide that
>> has already been solved in the existing libusb device installers. It's
>> unfortunate that it's not easily reusable.
>>
>> Any advice would be appreciated.
>>
>> Thanks,
>> Tyler
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Libusb-win32-devel mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>