driver, not device, installation
Tyler Bell <[email protected]> Thu, 6 Sep 2018 11:35:17 -0500
| Newsgroups | gmane.comp.lib.libusb.devel.windows |
|---|---|
| Message-ID | <CAGBb3We0NWWrDsp68c_LAKk9e6w9gUBwDZ+iWXfkXyju5G+ccg@mail.gmail.com> |
--===============0105380046235911355== Content-Type: multipart/alternative; boundary="0000000000009f61cd0575367aa9" --0000000000009f61cd0575367aa9 Content-Type: text/plain; charset="UTF-8" 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 --0000000000009f61cd0575367aa9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>First, let me apologize for opening this ticket(<a hr= ef=3D"https://sourceforge.net/p/libusb-win32/bugs/84/">https://sourceforge.= net/p/libusb-win32/bugs/84/</a>) rather than using the mailing list.</div><= div><br></div><div>Second, let me apologize for being dense, but the sugges= tion "You need to install the base package (libusb installer or libusb= k installer) to install libusb0.sys into the system." isn't quite = clear to me.</div><div>The only "base package" installer I can fi= nd is for the development kits, which isn't something we should be putt= ing on customer machines. If, on the other hand, you are saying I need to c= reate 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 exis= ting libusb device installers. It's unfortunate that it's not easil= y reusable.</div><div><br></div><div>Any advice would be appreciated.</div>= <div><br></div><div>Thanks,</div><div>Tyler</div></div> --0000000000009f61cd0575367aa9-- --===============0105380046235911355== 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 --===============0105380046235911355== 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 --===============0105380046235911355==--