Re: driver, not device, installation
Tyler Bell <[email protected]> Fri, 7 Sep 2018 09:37:43 -0500
| Newsgroups | gmane.comp.lib.libusb.devel.windows |
|---|---|
| Message-ID | <CAGBb3WcWQzMztGETYvbWS5qHN5FL2x9MiTKZs1wPQfuWyb_M7w@mail.gmail.com> |
--===============1068867399196115306== Content-Type: multipart/alternative; boundary="000000000000080e51057548f44e" --000000000000080e51057548f44e Content-Type: text/plain; charset="UTF-8" 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 <[email protected]> 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, <[email protected]> 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 >> [email protected] >> 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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > --000000000000080e51057548f44e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">From what I can tell,=C2=A0that is not, what I need. That = targets the driver to a device, which is what the bug 84 conversation indic= ates 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 f= or 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).<div>=C2=A0Thes= e are not huge issues, but as libusb has already nicely solved these concer= ns for "primary driver" installation, it would be great(and, it s= eems, trivial?) if we could reuse the existing code for filter driver insta= llation.<div><br><div>Backing up a bit, I have to interface with a device t= hat has a driver from the manufacturer(FTDI USB-serial cables). The OEM dri= ver is limited(but also required) so I've augmented it w/ libusb. The b= est 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 fo= r 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 doe= sn'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.</div><= /div></div><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"= ltr">On Thu, Sep 6, 2018 at 5:51 PM Chris E <<a href=3D"mailto:sposchy@g= mail.com">[email protected]</a>> wrote:<br></div><blockquote class=3D"gm= ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le= ft:1ex">Sorry, by "the SDK" in my last email, I meant "the l= ibusbK SDK".=C2=A0 Within Inf Wizard, you can select an option to use = libusb0.<br><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Fri., 7 Sep.= 2018, 2:36 am Tyler Bell, <<a href=3D"mailto:[email protected]" targe= t=3D"_blank">[email protected]</a>> wrote:<br></div><blockquote class= =3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd= ing-left:1ex"><div dir=3D"ltr"><div>First, let me apologize for opening thi= s ticket(<a href=3D"https://sourceforge.net/p/libusb-win32/bugs/84/" target= =3D"_blank">https://sourceforge.net/p/libusb-win32/bugs/84/</a>) rather tha= n using the mailing list.</div><div><br></div><div>Second, let me apologize= for being dense, but the suggestion "You need to install the base pac= kage (libusb installer or libusbk installer) to install libusb0.sys into th= e system." isn't quite clear to me.</div><div>The only "base = package" installer I can find is for the development kits, which isn&#= 39;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=C2=A0that has= already been solved in the existing libusb device installers. It's unf= ortunate that it's not easily reusable.</div><div><br></div><div>Any ad= vice would be appreciated.</div><div><br></div><div>Thanks,</div><div>Tyler= </div></div> ---------------------------------------------------------------------------= ---<br> Check out the vibrant tech community on one of the world's most<br> engaging tech sites, Slashdot.org! <a href=3D"http://sdm.link/slashdot" rel= =3D"noreferrer" target=3D"_blank">http://sdm.link/slashdot</a>_____________= __________________________________<br> Libusb-win32-devel mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blan= k">[email protected]</a><br> <a href=3D"https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel"= rel=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/l= istinfo/libusb-win32-devel</a><br> </blockquote></div> ---------------------------------------------------------------------------= ---<br> Check out the vibrant tech community on one of the world's most<br> engaging tech sites, Slashdot.org! <a href=3D"http://sdm.link/slashdot" rel= =3D"noreferrer" target=3D"_blank">http://sdm.link/slashdot</a>_____________= __________________________________<br> Libusb-win32-devel mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blan= k">[email protected]</a><br> <a href=3D"https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel"= rel=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/l= istinfo/libusb-win32-devel</a><br> </blockquote></div> --000000000000080e51057548f44e-- --===============1068867399196115306== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot --===============1068867399196115306== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Libusb-win32-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel --===============1068867399196115306==--