You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
(27) |
Dec
(9) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(2) |
Feb
(19) |
Mar
(13) |
Apr
(15) |
May
(11) |
Jun
(17) |
Jul
(31) |
Aug
(45) |
Sep
(10) |
Oct
(40) |
Nov
(39) |
Dec
(45) |
2005 |
Jan
(113) |
Feb
(45) |
Mar
(38) |
Apr
(53) |
May
(11) |
Jun
(42) |
Jul
(56) |
Aug
(50) |
Sep
(32) |
Oct
(32) |
Nov
(47) |
Dec
(22) |
2006 |
Jan
(19) |
Feb
(32) |
Mar
(40) |
Apr
(40) |
May
(41) |
Jun
(44) |
Jul
(37) |
Aug
(51) |
Sep
(30) |
Oct
(30) |
Nov
(51) |
Dec
(20) |
2007 |
Jan
(7) |
Feb
(20) |
Mar
(17) |
Apr
(67) |
May
(13) |
Jun
(73) |
Jul
(16) |
Aug
(58) |
Sep
(29) |
Oct
(5) |
Nov
(74) |
Dec
(9) |
2008 |
Jan
(17) |
Feb
(12) |
Mar
(65) |
Apr
(22) |
May
(40) |
Jun
(32) |
Jul
(11) |
Aug
(8) |
Sep
(3) |
Oct
(41) |
Nov
(34) |
Dec
(12) |
2009 |
Jan
(44) |
Feb
(33) |
Mar
(16) |
Apr
(109) |
May
(11) |
Jun
(22) |
Jul
(21) |
Aug
(37) |
Sep
(5) |
Oct
(23) |
Nov
(7) |
Dec
(7) |
2010 |
Jan
(36) |
Feb
(40) |
Mar
(35) |
Apr
(45) |
May
(42) |
Jun
(104) |
Jul
(135) |
Aug
(50) |
Sep
(65) |
Oct
(110) |
Nov
(129) |
Dec
(75) |
2011 |
Jan
(105) |
Feb
(48) |
Mar
(93) |
Apr
(166) |
May
(169) |
Jun
(188) |
Jul
(106) |
Aug
(33) |
Sep
(85) |
Oct
(46) |
Nov
(102) |
Dec
(105) |
2012 |
Jan
(81) |
Feb
(115) |
Mar
(56) |
Apr
(93) |
May
(56) |
Jun
(77) |
Jul
(88) |
Aug
(52) |
Sep
(72) |
Oct
(16) |
Nov
(70) |
Dec
(70) |
2013 |
Jan
(23) |
Feb
(85) |
Mar
(38) |
Apr
(48) |
May
(40) |
Jun
(49) |
Jul
(33) |
Aug
(28) |
Sep
(66) |
Oct
(28) |
Nov
(28) |
Dec
(16) |
2014 |
Jan
(33) |
Feb
(58) |
Mar
(17) |
Apr
(50) |
May
(16) |
Jun
(24) |
Jul
(19) |
Aug
(32) |
Sep
(10) |
Oct
(10) |
Nov
(4) |
Dec
(10) |
2015 |
Jan
(11) |
Feb
(2) |
Mar
(4) |
Apr
(14) |
May
(1) |
Jun
(6) |
Jul
(16) |
Aug
(29) |
Sep
(6) |
Oct
(26) |
Nov
(10) |
Dec
|
2016 |
Jan
|
Feb
(20) |
Mar
(6) |
Apr
|
May
(3) |
Jun
(3) |
Jul
|
Aug
(16) |
Sep
(6) |
Oct
|
Nov
(15) |
Dec
|
2017 |
Jan
(1) |
Feb
(2) |
Mar
(4) |
Apr
|
May
(1) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
2018 |
Jan
|
Feb
(8) |
Mar
(10) |
Apr
(16) |
May
|
Jun
(15) |
Jul
|
Aug
(3) |
Sep
(19) |
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
(5) |
May
|
Jun
|
Jul
(7) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
(5) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(3) |
Aug
|
Sep
(6) |
Oct
(2) |
Nov
(4) |
Dec
|
2022 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
(5) |
Feb
(1) |
Mar
|
Apr
(3) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
(3) |
Mar
(1) |
Apr
(1) |
May
(11) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Raymond B. <ray...@gm...> - 2024-06-28 19:46:54
|
Hello, I'm looking to write a Windows driver/achieve similar functionality using libusb-win32 for the Apple iPad. I wish to achieve the following with the driver: 1. The driver should be able to send vendor-specific control messages to the device (to expose a CDC NCM interface in a new configuration). 2. The driver should be able to set the device's USB configuration (to this new configuration). 3. The driver should pass through the PTP and Apple USBMUX interfaces to their appropriate (and default) drivers. 4. The driver should configure and present the NCM Data and NCM Control interfaces as a Windows Network Adapter. >From these requirements, I'm thinking that this driver will have a similar role as the Windows Generic Parent Driver. My questions are: 1. Is the "passthrough" of interfaces possible with the libusb-win32 kernel driver? Or will I have to write my own? 2. Windows recently added support for UMDF NetAdapterCx drivers. Would a driver like that be able to communicate with libusb's kernel driver? Or would it have to be bundled within the kernel driver itself? Thanks in advance |
From: Tormod V. <lis...@gm...> - 2024-05-28 20:57:10
|
Use the official Zadig 2.6, it has 1.2.6.0 embedded. Tormod On Tue, May 28, 2024 at 10:07 PM Mayur Purandare <may...@gm...> wrote: > > Hello, > A kind reminder. > Is there any way to rollback to 1.2.6.0 > Thank you. > > BR, > Mayur > > On Thu, 23 May, 2024, 8:24 am Mayur Purandare, <may...@gm...> wrote: >> >> Hello, >> >> I tried to install the driver 1.4.0.0 over the previous version i.e. 1.2.6.0using Zadig tool. However, now I am not able to connect to my hardware. I tried to reinstall the previous version. It gets installed but I still cannot communicate with the hardware. >> Please guide. >> Thank you. >> >> Regards, >> Mayur. >> >> On Fri, 17 May, 2024, 11:40 am Mayur Purandare, <may...@gm...> wrote: >>> >>> Hello xiaofanc, >>> >>> Thank you for your reply. >>> We will try this. >>> Thank you. >>> >>> Regards, >>> Mayur >>> >>> On Fri, 17 May, 2024, 11:11 am Xiaofan Chen, <xia...@gm...> wrote: >>>> >>>> No. That libusbk inf wizard is not part of libusb-win32 project, but rather part of libusbK project. >>>> >>>> You can use the bundled Zadig utility to install libusb-win32 1.4.0 device driver. You can also use libwdi wdi-simple example as a template to write your own driver installer. >>>> https://github.com/pbatard/libwdi/tree/master/examples >>>> >>>> Regards, >>>> Xiaofan >>>> >>>> On Fri, May 17, 2024, 12:53 Mayur Purandare <may...@gm...> wrote: >>>>> >>>>> Hello, >>>>> A kind reminder. Is there any inf wizard utility available to create the 1.4.0.0 driver? >>>>> Kindly let me know. >>>>> >>>>> Thank you >>>>> >>>>> Regards, >>>>> Mayur >>>>> >>>>> >>>>> On Tue, 14 May, 2024, 10:19 am Mayur Purandare, <may...@gm...> wrote: >>>>>> >>>>>> Hello Tormod, >>>>>> >>>>>> Firstly, apologies for posting the wrong link. >>>>>> We had created this driver using the INF Wizard. (The Screenshot is in the attachment.) as mentioned in the first comment of the link below. >>>>>> >>>>>> ==>> https://sourceforge.net/p/libusb-win32/support-requests/65/ >>>>>> (A screenshot of the comment is included) >>>>>> >>>>>> Is there any similar Driver Package creator available for version 1.4.0.0? >>>>>> >>>>>> Also, will it resolve the error we are facing i.e. URB_FUNCTION_ABORT_PIPE or are there any more settings we need to do while invoking this? >>>>>> (We are calling the communication functions in Asynchronous Methods.) >>>>>> >>>>>> Kindly let us know. >>>>>> >>>>>> Thank you. >>>>>> >>>>>> Regards, >>>>>> Mayur >>>>>> >>>>>> >>>>>> >>>>>> On Mon, 13 May 2024 at 13:08, Tormod Volden <lis...@gm...> wrote: >>>>>>> >>>>>>> On Mon, May 13, 2024 at 3:38 AM Mayur Purandare wrote: >>>>>>> >>>>>>> > Thank you very much for your reply regarding the updated version. >>>>>>> > However, is there any installable available for this version as it is there for 1.2.6.0 (link below) >>>>>>> >>>>>>> I believe you can use the zadig_2.8_mod_1400.exe executable to install >>>>>>> the driver. This is zadig 2.8 modified to include libusb0.sys 1.4.0.0. >>>>>>> >>>>>>> > https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download >>>>>>> > >>>>>>> > The install exe available at the above link is also signed so that it can run on Windows 10 and 11. >>>>>>> >>>>>>> Do you use libusb0.sys as a filter driver? >>>>>>> >>>>>>> Tormod >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Libusb-win32-devel mailing list >>>>>>> Lib...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel >>>>> >>>>> _______________________________________________ >>>>> Libusb-win32-devel mailing list >>>>> Lib...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel >>>> >>>> _______________________________________________ >>>> Libusb-win32-devel mailing list >>>> Lib...@li... >>>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
From: Mayur P. <may...@gm...> - 2024-05-28 20:06:50
|
Hello, A kind reminder. Is there any way to rollback to 1.2.6.0 Thank you. BR, Mayur On Thu, 23 May, 2024, 8:24 am Mayur Purandare, <may...@gm...> wrote: > Hello, > > I tried to install the driver 1.4.0.0 over the previous version i.e. > 1.2.6.0using Zadig tool. However, now I am not able to connect to my > hardware. I tried to reinstall the previous version. It gets installed but > I still cannot communicate with the hardware. > Please guide. > Thank you. > > Regards, > Mayur. > > On Fri, 17 May, 2024, 11:40 am Mayur Purandare, < > may...@gm...> wrote: > >> Hello xiaofanc, >> >> Thank you for your reply. >> We will try this. >> Thank you. >> >> Regards, >> Mayur >> >> On Fri, 17 May, 2024, 11:11 am Xiaofan Chen, <xia...@gm...> wrote: >> >>> No. That libusbk inf wizard is not part of libusb-win32 project, but >>> rather part of libusbK project. >>> >>> You can use the bundled Zadig utility to install libusb-win32 1.4.0 >>> device driver. You can also use libwdi wdi-simple example as a template to >>> write your own driver installer. >>> https://github.com/pbatard/libwdi/tree/master/examples >>> >>> Regards, >>> Xiaofan >>> >>> On Fri, May 17, 2024, 12:53 Mayur Purandare <may...@gm...> >>> wrote: >>> >>>> Hello, >>>> A kind reminder. Is there any inf wizard utility available to create >>>> the 1.4.0.0 driver? >>>> Kindly let me know. >>>> >>>> Thank you >>>> >>>> Regards, >>>> Mayur >>>> >>>> >>>> On Tue, 14 May, 2024, 10:19 am Mayur Purandare, < >>>> may...@gm...> wrote: >>>> >>>>> Hello Tormod, >>>>> >>>>> Firstly, apologies for posting the wrong link. >>>>> We had created this driver using the INF Wizard. (The Screenshot is >>>>> in the attachment.) as mentioned in the first comment of the link below. >>>>> >>>>> ==>> https://sourceforge.net/p/libusb-win32/support-requests/65/ >>>>> (A screenshot of the comment is included) >>>>> >>>>> Is there any similar Driver Package creator available for version >>>>> 1.4.0.0? >>>>> >>>>> Also, will it resolve the error we are facing >>>>> i.e. URB_FUNCTION_ABORT_PIPE or are there any more settings we need to do >>>>> while invoking this? >>>>> (We are calling the communication functions in Asynchronous Methods.) >>>>> >>>>> Kindly let us know. >>>>> >>>>> Thank you. >>>>> >>>>> Regards, >>>>> Mayur >>>>> >>>>> >>>>> >>>>> On Mon, 13 May 2024 at 13:08, Tormod Volden <lis...@gm...> >>>>> wrote: >>>>> >>>>>> On Mon, May 13, 2024 at 3:38 AM Mayur Purandare wrote: >>>>>> >>>>>> > Thank you very much for your reply regarding the updated version. >>>>>> > However, is there any installable available for this version as it >>>>>> is there for 1.2.6.0 (link below) >>>>>> >>>>>> I believe you can use the zadig_2.8_mod_1400.exe executable to install >>>>>> the driver. This is zadig 2.8 modified to include libusb0.sys 1.4.0.0. >>>>>> >>>>>> > >>>>>> https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download >>>>>> > >>>>>> > The install exe available at the above link is also signed so that >>>>>> it can run on Windows 10 and 11. >>>>>> >>>>>> Do you use libusb0.sys as a filter driver? >>>>>> >>>>>> Tormod >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Libusb-win32-devel mailing list >>>>>> Lib...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel >>>>>> >>>>> _______________________________________________ >>>> Libusb-win32-devel mailing list >>>> Lib...@li... >>>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel >>>> >>> _______________________________________________ >>> Libusb-win32-devel mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel >>> >> |
From: Mayur P. <may...@gm...> - 2024-05-23 02:54:38
|
Hello, I tried to install the driver 1.4.0.0 over the previous version i.e. 1.2.6.0using Zadig tool. However, now I am not able to connect to my hardware. I tried to reinstall the previous version. It gets installed but I still cannot communicate with the hardware. Please guide. Thank you. Regards, Mayur. On Fri, 17 May, 2024, 11:40 am Mayur Purandare, <may...@gm...> wrote: > Hello xiaofanc, > > Thank you for your reply. > We will try this. > Thank you. > > Regards, > Mayur > > On Fri, 17 May, 2024, 11:11 am Xiaofan Chen, <xia...@gm...> wrote: > >> No. That libusbk inf wizard is not part of libusb-win32 project, but >> rather part of libusbK project. >> >> You can use the bundled Zadig utility to install libusb-win32 1.4.0 >> device driver. You can also use libwdi wdi-simple example as a template to >> write your own driver installer. >> https://github.com/pbatard/libwdi/tree/master/examples >> >> Regards, >> Xiaofan >> >> On Fri, May 17, 2024, 12:53 Mayur Purandare <may...@gm...> >> wrote: >> >>> Hello, >>> A kind reminder. Is there any inf wizard utility available to create the >>> 1.4.0.0 driver? >>> Kindly let me know. >>> >>> Thank you >>> >>> Regards, >>> Mayur >>> >>> >>> On Tue, 14 May, 2024, 10:19 am Mayur Purandare, < >>> may...@gm...> wrote: >>> >>>> Hello Tormod, >>>> >>>> Firstly, apologies for posting the wrong link. >>>> We had created this driver using the INF Wizard. (The Screenshot is in >>>> the attachment.) as mentioned in the first comment of the link below. >>>> >>>> ==>> https://sourceforge.net/p/libusb-win32/support-requests/65/ >>>> (A screenshot of the comment is included) >>>> >>>> Is there any similar Driver Package creator available for version >>>> 1.4.0.0? >>>> >>>> Also, will it resolve the error we are facing >>>> i.e. URB_FUNCTION_ABORT_PIPE or are there any more settings we need to do >>>> while invoking this? >>>> (We are calling the communication functions in Asynchronous Methods.) >>>> >>>> Kindly let us know. >>>> >>>> Thank you. >>>> >>>> Regards, >>>> Mayur >>>> >>>> >>>> >>>> On Mon, 13 May 2024 at 13:08, Tormod Volden <lis...@gm...> >>>> wrote: >>>> >>>>> On Mon, May 13, 2024 at 3:38 AM Mayur Purandare wrote: >>>>> >>>>> > Thank you very much for your reply regarding the updated version. >>>>> > However, is there any installable available for this version as it >>>>> is there for 1.2.6.0 (link below) >>>>> >>>>> I believe you can use the zadig_2.8_mod_1400.exe executable to install >>>>> the driver. This is zadig 2.8 modified to include libusb0.sys 1.4.0.0. >>>>> >>>>> > >>>>> https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download >>>>> > >>>>> > The install exe available at the above link is also signed so that >>>>> it can run on Windows 10 and 11. >>>>> >>>>> Do you use libusb0.sys as a filter driver? >>>>> >>>>> Tormod >>>>> >>>>> >>>>> _______________________________________________ >>>>> Libusb-win32-devel mailing list >>>>> Lib...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel >>>>> >>>> _______________________________________________ >>> Libusb-win32-devel mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel >>> >> _______________________________________________ >> Libusb-win32-devel mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel >> > |
From: Mayur P. <may...@gm...> - 2024-05-17 06:11:12
|
Hello xiaofanc, Thank you for your reply. We will try this. Thank you. Regards, Mayur On Fri, 17 May, 2024, 11:11 am Xiaofan Chen, <xia...@gm...> wrote: > No. That libusbk inf wizard is not part of libusb-win32 project, but > rather part of libusbK project. > > You can use the bundled Zadig utility to install libusb-win32 1.4.0 device > driver. You can also use libwdi wdi-simple example as a template to write > your own driver installer. > https://github.com/pbatard/libwdi/tree/master/examples > > Regards, > Xiaofan > > On Fri, May 17, 2024, 12:53 Mayur Purandare <may...@gm...> > wrote: > >> Hello, >> A kind reminder. Is there any inf wizard utility available to create the >> 1.4.0.0 driver? >> Kindly let me know. >> >> Thank you >> >> Regards, >> Mayur >> >> >> On Tue, 14 May, 2024, 10:19 am Mayur Purandare, < >> may...@gm...> wrote: >> >>> Hello Tormod, >>> >>> Firstly, apologies for posting the wrong link. >>> We had created this driver using the INF Wizard. (The Screenshot is in >>> the attachment.) as mentioned in the first comment of the link below. >>> >>> ==>> https://sourceforge.net/p/libusb-win32/support-requests/65/ >>> (A screenshot of the comment is included) >>> >>> Is there any similar Driver Package creator available for version >>> 1.4.0.0? >>> >>> Also, will it resolve the error we are facing >>> i.e. URB_FUNCTION_ABORT_PIPE or are there any more settings we need to do >>> while invoking this? >>> (We are calling the communication functions in Asynchronous Methods.) >>> >>> Kindly let us know. >>> >>> Thank you. >>> >>> Regards, >>> Mayur >>> >>> >>> >>> On Mon, 13 May 2024 at 13:08, Tormod Volden <lis...@gm...> >>> wrote: >>> >>>> On Mon, May 13, 2024 at 3:38 AM Mayur Purandare wrote: >>>> >>>> > Thank you very much for your reply regarding the updated version. >>>> > However, is there any installable available for this version as it is >>>> there for 1.2.6.0 (link below) >>>> >>>> I believe you can use the zadig_2.8_mod_1400.exe executable to install >>>> the driver. This is zadig 2.8 modified to include libusb0.sys 1.4.0.0. >>>> >>>> > >>>> https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download >>>> > >>>> > The install exe available at the above link is also signed so that it >>>> can run on Windows 10 and 11. >>>> >>>> Do you use libusb0.sys as a filter driver? >>>> >>>> Tormod >>>> >>>> >>>> _______________________________________________ >>>> Libusb-win32-devel mailing list >>>> Lib...@li... >>>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel >>>> >>> _______________________________________________ >> Libusb-win32-devel mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel >> > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > |
From: Xiaofan C. <xia...@gm...> - 2024-05-17 05:41:01
|
No. That libusbk inf wizard is not part of libusb-win32 project, but rather part of libusbK project. You can use the bundled Zadig utility to install libusb-win32 1.4.0 device driver. You can also use libwdi wdi-simple example as a template to write your own driver installer. https://github.com/pbatard/libwdi/tree/master/examples Regards, Xiaofan On Fri, May 17, 2024, 12:53 Mayur Purandare <may...@gm...> wrote: > Hello, > A kind reminder. Is there any inf wizard utility available to create the > 1.4.0.0 driver? > Kindly let me know. > > Thank you > > Regards, > Mayur > > > On Tue, 14 May, 2024, 10:19 am Mayur Purandare, < > may...@gm...> wrote: > >> Hello Tormod, >> >> Firstly, apologies for posting the wrong link. >> We had created this driver using the INF Wizard. (The Screenshot is in >> the attachment.) as mentioned in the first comment of the link below. >> >> ==>> https://sourceforge.net/p/libusb-win32/support-requests/65/ >> (A screenshot of the comment is included) >> >> Is there any similar Driver Package creator available for version 1.4.0.0? >> >> Also, will it resolve the error we are facing >> i.e. URB_FUNCTION_ABORT_PIPE or are there any more settings we need to do >> while invoking this? >> (We are calling the communication functions in Asynchronous Methods.) >> >> Kindly let us know. >> >> Thank you. >> >> Regards, >> Mayur >> >> >> >> On Mon, 13 May 2024 at 13:08, Tormod Volden <lis...@gm...> >> wrote: >> >>> On Mon, May 13, 2024 at 3:38 AM Mayur Purandare wrote: >>> >>> > Thank you very much for your reply regarding the updated version. >>> > However, is there any installable available for this version as it is >>> there for 1.2.6.0 (link below) >>> >>> I believe you can use the zadig_2.8_mod_1400.exe executable to install >>> the driver. This is zadig 2.8 modified to include libusb0.sys 1.4.0.0. >>> >>> > >>> https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download >>> > >>> > The install exe available at the above link is also signed so that it >>> can run on Windows 10 and 11. >>> >>> Do you use libusb0.sys as a filter driver? >>> >>> Tormod >>> >>> >>> _______________________________________________ >>> Libusb-win32-devel mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel >>> >> _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > |
From: Mayur P. <may...@gm...> - 2024-05-17 04:53:13
|
Hello, A kind reminder. Is there any inf wizard utility available to create the 1.4.0.0 driver? Kindly let me know. Thank you Regards, Mayur On Tue, 14 May, 2024, 10:19 am Mayur Purandare, <may...@gm...> wrote: > Hello Tormod, > > Firstly, apologies for posting the wrong link. > We had created this driver using the INF Wizard. (The Screenshot is in > the attachment.) as mentioned in the first comment of the link below. > > ==>> https://sourceforge.net/p/libusb-win32/support-requests/65/ > (A screenshot of the comment is included) > > Is there any similar Driver Package creator available for version 1.4.0.0? > > Also, will it resolve the error we are facing > i.e. URB_FUNCTION_ABORT_PIPE or are there any more settings we need to do > while invoking this? > (We are calling the communication functions in Asynchronous Methods.) > > Kindly let us know. > > Thank you. > > Regards, > Mayur > > > > On Mon, 13 May 2024 at 13:08, Tormod Volden <lis...@gm...> > wrote: > >> On Mon, May 13, 2024 at 3:38 AM Mayur Purandare wrote: >> >> > Thank you very much for your reply regarding the updated version. >> > However, is there any installable available for this version as it is >> there for 1.2.6.0 (link below) >> >> I believe you can use the zadig_2.8_mod_1400.exe executable to install >> the driver. This is zadig 2.8 modified to include libusb0.sys 1.4.0.0. >> >> > >> https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download >> > >> > The install exe available at the above link is also signed so that it >> can run on Windows 10 and 11. >> >> Do you use libusb0.sys as a filter driver? >> >> Tormod >> >> >> _______________________________________________ >> Libusb-win32-devel mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel >> > |
From: Mayur P. <may...@gm...> - 2024-05-14 04:50:16
|
Hello Tormod, Firstly, apologies for posting the wrong link. We had created this driver using the INF Wizard. (The Screenshot is in the attachment.) as mentioned in the first comment of the link below. ==>> https://sourceforge.net/p/libusb-win32/support-requests/65/ (A screenshot of the comment is included) Is there any similar Driver Package creator available for version 1.4.0.0? Also, will it resolve the error we are facing i.e. URB_FUNCTION_ABORT_PIPE or are there any more settings we need to do while invoking this? (We are calling the communication functions in Asynchronous Methods.) Kindly let us know. Thank you. Regards, Mayur On Mon, 13 May 2024 at 13:08, Tormod Volden <lis...@gm...> wrote: > On Mon, May 13, 2024 at 3:38 AM Mayur Purandare wrote: > > > Thank you very much for your reply regarding the updated version. > > However, is there any installable available for this version as it is > there for 1.2.6.0 (link below) > > I believe you can use the zadig_2.8_mod_1400.exe executable to install > the driver. This is zadig 2.8 modified to include libusb0.sys 1.4.0.0. > > > > https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download > > > > The install exe available at the above link is also signed so that it > can run on Windows 10 and 11. > > Do you use libusb0.sys as a filter driver? > > Tormod > > > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > |
From: Tormod V. <lis...@gm...> - 2024-05-13 07:37:37
|
On Mon, May 13, 2024 at 3:38 AM Mayur Purandare wrote: > Thank you very much for your reply regarding the updated version. > However, is there any installable available for this version as it is there for 1.2.6.0 (link below) I believe you can use the zadig_2.8_mod_1400.exe executable to install the driver. This is zadig 2.8 modified to include libusb0.sys 1.4.0.0. > https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download > > The install exe available at the above link is also signed so that it can run on Windows 10 and 11. Do you use libusb0.sys as a filter driver? Tormod |
From: Mayur P. <may...@gm...> - 2024-05-13 01:33:47
|
Hello Tormod, Thank you very much for your reply regarding the updated version. However, is there any installable available for this version as it is there for 1.2.6.0 (link below) https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download The install exe available at the above link is also signed so that it can run on Windows 10 and 11. Thank you. Regards, Mayur On Mon, 13 May 2024 at 02:09, Tormod Volden <lis...@gm...> wrote: > On Fri, May 10, 2024 at 7:47 PM Mayur Purandare wrote: > > We are using LibUSBDotNet 2.2.29 in our application. Along with this, we > are using LibUsb Driver 1.2.6.0. > > > Is there any upgraded driver version available? Where can we get it? > > The latest libusb-win32 release is 1.4.0.0: > https://github.com/mcuee/libusb-win32/releases > > Best regards, > Tormod > > > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > |
From: Tormod V. <lis...@gm...> - 2024-05-12 20:34:44
|
On Fri, May 10, 2024 at 7:47 PM Mayur Purandare wrote: > We are using LibUSBDotNet 2.2.29 in our application. Along with this, we are using LibUsb Driver 1.2.6.0. > Is there any upgraded driver version available? Where can we get it? The latest libusb-win32 release is 1.4.0.0: https://github.com/mcuee/libusb-win32/releases Best regards, Tormod |
From: Mayur P. <may...@gm...> - 2024-05-10 17:44:45
|
Hello, We are using LibUSBDotNet 2.2.29 in our application. Along with this, we are using LibUsb Driver 1.2.6.0. In our application, we communicate with our hardware periodically every 500 ms. We observed that the application gets disconnected from the hardware and with the error URB_FUNCTION_ABORT_PIPE. Is there any setting we are missing while using this driver? Is there any upgraded driver version available? Where can we get it? Please advise. Thank you. BR, Mayur |
From: 许叶洪 <yeh...@te...> - 2024-04-24 03:42:51
|
Hi, The GUI I wrote called libusb-win32 to communicate with Keysight DMM 34464A via USB. During the communication process, I restarted the power supply of the DMM. From the bus sound software, it appears that USB is no longer able to send messages. Opening the GUI again allows for USB communication. After opening the GUI several times, USB cannot send messages again. Why is this |
From: Андрій О. <ost...@gm...> - 2024-03-13 22:12:42
|
Dear libusb team, Let me clarify – I am using unmodified libusb0.sys driver, however I do sign the driver package with my own cert, using my own installer with a custom .inf. I would appreciate if you could confirm that this does not force me to disclose my app source code, provided of course that I clearly state the usage of libusb-win32 with the link to its repository сб, 17 лют. 2024 р. о 16:35 Xiaofan Chen <xia...@gm...> пише: > On Thu, Feb 8, 2024 at 1:30 AM Андрій Остапчук > <ost...@gm...> wrote: > > > > Hello Libusb Team, > > Do you provide a commercial (non-GPL) license for the libusb0.sys > windows driver? > > I would like to use my own installer for the driver and distribute it > with my application without > > being forced to disclose my app code. Unfortunately, I can't use the > newest version of the > > libusbk due to a specific USB device I am connected to. > > Sorry but we do not. > > By integrating libusb-win32 device driver into your driver installer, > you should not be > required to change your driver installer license to be GPL, as long as > you do not > change the driver source code. You can just mention that your device > driver is using > libusb-win32 device driver and provide the web link to libusb-win32 github. > > Reference: similar question. > https://github.com/pbatard/libwdi/issues/279 > > BTW, I am not suggesting you use libwdi though as it is licensed > under LGPL. Rather you can use other installers like Inno Setup. > > -- > Xiaofan > > > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > |
From: Xiaofan C. <xia...@gm...> - 2024-02-17 14:33:59
|
On Thu, Feb 8, 2024 at 1:30 AM Андрій Остапчук <ost...@gm...> wrote: > > Hello Libusb Team, > Do you provide a commercial (non-GPL) license for the libusb0.sys windows driver? > I would like to use my own installer for the driver and distribute it with my application without > being forced to disclose my app code. Unfortunately, I can't use the newest version of the > libusbk due to a specific USB device I am connected to. Sorry but we do not. By integrating libusb-win32 device driver into your driver installer, you should not be required to change your driver installer license to be GPL, as long as you do not change the driver source code. You can just mention that your device driver is using libusb-win32 device driver and provide the web link to libusb-win32 github. Reference: similar question. https://github.com/pbatard/libwdi/issues/279 BTW, I am not suggesting you use libwdi though as it is licensed under LGPL. Rather you can use other installers like Inno Setup. -- Xiaofan |
From: Андрій О. <ost...@gm...> - 2024-02-07 17:29:04
|
Hello Libusb Team, Do you provide a commercial (non-GPL) license for the libusb0.sys windows driver? I would like to use my own installer for the driver and distribute it with my application without being forced to disclose my app code. Unfortunately, I can't use the newest version of the libusbk due to a specific USB device I am connected to. Best regards, Andrii Ostapchuk |
From: Xiaofan C. <xia...@gm...> - 2024-02-01 00:04:42
|
FYI ---------- Forwarded message --------- From: Tormod Volden <lis...@gm...> Date: Thu, Feb 1, 2024 at 7:30 AM Subject: [libusb] Announcing libusb v1.0.27 To: <lib...@li...> We are happy to announce the final release of libusb 1.0.27. ChangeLog with most important changes since 1.0.26: * New libusb_init_context API to replace libusb_init * New libusb_get_max_alt_packet_size API * New libusb_get_platform_descriptor API (BOS) * Allow setting log callback with libusb_set_option/libusb_init_context * New WebAssembly + WebUSB backend using Emscripten * Fix regression in libusb_set_interface_alt_setting * Fix sync transfer completion race and use-after-free * Fix hotplug exit ordering * Linux: NO_DEVICE_DISCOVERY option set per context * macOS: Fix missing device list cleanup locking * macOS: Do not clear device data toggle for newer OS versions * macOS: Fix running binaries on older OS than build host * Windows: Allow claiming multiple associated interfaces * Windows: Ignore non-configured devices instead of waiting * Windows: Improved root hub detection The source code tarball can be downloaded here: https://github.com/libusb/libusb/releases/download/v1.0.27/libusb-1.0.27.tar.bz2 An archive of Windows binaries can be downloaded here: https://github.com/libusb/libusb/releases/download/v1.0.27/libusb-1.0.27.7z Note that the release tarball includes a configure script so unlike a git checkout it is not necessary to bootstrap with autoconf. The 1.0.27 release was made possible by the contributions from all patch submitters (see below git shortlog with 158 commits from 31 contributors, of which 22 new!) plus everyone who contributed with issue reporting, discussions and testing. On behalf of the libusb development community, Tormod -- Addison Crump (1): descriptor: Guard against corrupted descriptor length field Alex Feinman (1): windows: Refactor parsing of MI_XX string taking into account it's 16-based Alexander Mot (1): windows: Define __func__ for vs2015 Aurelien Jarno (1): tests/set_option: Avoid use-after-free in case of test failure Brad Smith (1): threads_posix: Use proper getthrid() for thread ID on OpenBSD Craig Hutchinson (1): Fix `exit` order to match reverse of `init` Dominik Boehi (1): descriptor: Add support for BOS platform descriptor parsing Edgar Fuß (2): netbsd: Add comment about udi_speed values matching libusb enum netbsd: Map NetBSD's udi_bus/udi_addr to libusb's 1-based API Francis Hart (1): Fix setting log level before libusb_init() Ihor Dutchak (2): Fix possible memory leak of configuration descriptor (Darwin/Windows) darwin/windows: Find interface descriptor by bInterfaceNumber Ingvar Stepanyan (15): Add Emscripten backend for WebAssembly + WebUSB support examples/hotplugtest: Match any device by default tests: Mark callbacks as LIBUSB_CALL testlib: Don't count skipped tests as failures CI: Run cross-platform tests on all platforms CI: Enable Address Sanitizer (ASAN) where supported CI: Tell tests that we don't have any devices CI: Pass the extra warnings flags to CXXFLAGS too Add WebUSB testing via node-usb CI: Enable Emscripten build tests/stress_mt: Test open/transfer/close on available devices webusb: Wasm+WebUSB backend fixes and improvements tests/stress_mt: Stop early if any device fails tests/set_option: Allow no devices in test_no_discovery msvc: Add tests/init_context project to MSVC Joshua M. Clulow (2): sunos: Fix error detection in sunos_submit_transfer() sunos: Return error if OS paths hit their limits Lars Kanis (2): core: Don't overwrite the log callback on every global libusb_set_option() core: Allow setting global log callback after first libusb_init() Lonnie Abelbeck (1): configure.ac: Link with -latomic only if no atomic builtins Ludovic Rousseau (6): Doxygen: Add references to LIBUSB_ERROR codes Doxygen: Improve libusb_wrap_sys_device() documentation Add github action build for --enable-debug-log Fix build error with --enable-debug-log Fix build errors of tests with --enable-debug-log Fix github action warnings Mario Kleiner (1): windows: Fix off-by-one error in HID backend for devices without report IDs Martin Ling (4): docs: Clear endpoint halt issued after cancellation only for macOS < 10.5 windows: Add GetPipePolicy to struct winusb_interface windows: Add option for WinUSB RAW_IO endpoint policy Revert "windows: Add option for WinUSB RAW_IO endpoint policy" Nathan Hjelm (17): darwin: add missing locking around cached device list cleanup config: allow configure to continue without pkg-config installed darwin: Do not clear device data toggle on macOS 10.5 or newer Add tags and cscope.out to .gitignore core: Add libusb_init_context() setting options at context creation Update tests and example to use the new libusb_init_context() function libusb_set_options: Adjust semantics of libusb_set_option for log level tests: Add unit test for libusb_set_option Add support for setting the log callback with libusb_set_option/libusb_init_context darwin: fix potential crash at darwin_exit ci: do not hard code test names for CI ci: dump test suite output on test failure ci: ensure testsuite log is dumped on failure darwin: add get_running_version helper darwin: add abstraction for IOUSBInterfaceInterface darwin: add abstraction for IOUSBDeviceInterface darwin: add testing for IOKit version fallbacks Niklas Gürtler (1): Fix #1263 by acquiring the waiters lock while calling transfer callbacks and swapping the order of operations in sync_transfer_cb Orhan aib Kavrakoglu (3): core: Factor out helper get_endpoint_max_packet_size() core: Add helper find_alt_endpoint() core: Add libusb_get_max_alt_packet_size() Pablo Prietz (1): core: Remove leftover usbi_mutex_unlock in libusb_set_interface_alt_setting Petr Pazourek (1): windows: Allow device GUIDs missing terminating characters or separators Rosen Penev (4): windows: Add clock_gettime check windows: Mark libusb_set_option as WINAPIV windows: Fix build with --disable-log windows: Remove __stdcall libusb_set_option from .def file Ryan Metcalfe (3): descriptor: Introduce interface association descriptors (IAD) windows: Allow claiming all interfaces for a WINUSBX composite function xusb: Print info from IAD descriptors Sean McBride (18): Simplify clock_gettime() conditionalization and fallback on macOS examples: Replace most uses of sprintf with safer snprintf core: Fix -Wswitch warnings by including all enum values in switch darwin: Revert seemingly harmless introduction of temporary variable darwin: Avoid error checking regression descriptor: Prevent string descriptor buffer overread io: Fix incorrect alignment in allocation in libusb_alloc_transfer core: Add missing mutex acquisition when manipulating active_contexts_list libusb.h: Rename ZERO_SIZED_ARRAY to LIBUSB_FLEXIBLE_ARRAY io: Change remove_from_flying_list() to not lock flying_transfers_lock itself Fix docs about backend functions that lock itransfer->lock Document backend functions that already lock dev_handle->lock Replace all http://libusb.info/ with https darwin: locationID is 32-bit, not 64-bit Correct some spelling and add codespell config file xcode: Move some options from Xcode project to xcconfig file xcode: Add files from other backends into the Xcode project docs: Prefer use of libusb_init_context() over old libusb_init() Shawn Hoffman (5): msvc: Rework msbuild files windows: Whitespace fix msvc: Implement LIBUSB_DEPRECATED_FOR msvc: Correct usage comments about linking windows: Use sdk-defined GUIDs where possible Simon Chan (1): windows: Recognize Samsung composite device driver SomeAlphabetGuy (1): core: Avoid possible data race in log_v() Sonatique (1): msvc: Add configurations with /MT compilation flag Sylvain (1): git ignore "build" folder Sylvain Fasel (2): windows: Define bus numbers without using HCD windows: No longer wait for device to get an active configuration Tormod Volden (52): windows: Pass on returned isochronous packet status on libusbK core: Remove select case not possibly reached windows: Correct function name in comment core: Avoid mutex lock while printing error and warning windows: Avoid invalid dereference in debug print windows: Silence warnings when building without logging tests: Add multithreaded stress test for Posix platforms CI: Run multithreaded stress test on Linux core: Do not warn about new context as implicit default Fix most -Wpedantic warnings xusb: Add newlines in mass-storage test output Bump LIBUSB_API_VERSION to 0x0100010A windows: Omit -mwin32 GCC option for MSYS/MinGW windows: Only link with --add-stdcall-alias if supported by linker xusb: Improve kernel driver probe messages xusb: Improve Max LUN retrieval stall handling tests/stress_mt: Add Windows threads support tests/stress_mt: Also run with device enumeration Revert "windows: Fix off-by-one error in HID backend for devices without report IDs" core: Avoid crash due to premature va_end core: Fix always-true condition in log callback function setting netbsd/openbsd: Drop parentheses around return values netbsd/openbsd: Remove extraneous parentheses around ioctl call netbsd: Print control transfer request debug values in hex netbsd: Add error number to debug output Add HACKING file with hints on proper commits tests: Remove unused function in init_context.c tests: Fix builds with logging disabled Revert "core: Remove select case not possibly reached" windows: Cover all enumeration passes explicitly in switch statements stress_mt: Return error if device count varies core: Avoid warning with logging disabled windows: Avoid warning with logging disabled windows: Include enumeration details in debug output CI: Simplify Linux job description CI: Add Linux and MSYS build with logging disabled tests/umockdev: Avoid unknown warning option on older gcc .gitignore: Ignore test binaries and logs tests: Use AM_LDFLAGS for -static flag to allow LDFLAGS override libusb 1.0.27-rc1 libusb.h: Avoid UNREFERENCED_PARAMETER macro on GCC/clang tests/stress_mt: Ignore some unavailable devices on Windows tests/stress_mt: Ignore device descriptor mismatch for Windows HID ChangeLog updates Change libusb_init_option to fix libusb_set_option() on big-endian windows: Downgrade get_guid DeviceInterfaceGUID warning to info docs: Add more references in libusb_option section libusb 1.0.27-rc2 configure.ac: Do not build umockdev if --enable-debug-log is used examples/hotplugtest: Tone down message about failed open configure.ac: Bump libtool library version libusb 1.0.27 Xiaofan Chen (2): CI: Add build jobs for MSYS clang32/64 Do not deprecate libusb_set_debug and libusb_init Zeng Guang (1): windows: Add USBD_STATUS_STALL_PID to usbd_status translation xloem (1): linux: Keep the no_device_discovery option per context _______________________________________________ libusb-devel mailing list lib...@li... https://lists.sourceforge.net/lists/listinfo/libusb-devel |
From: Xiaofan C. <xia...@gm...> - 2023-05-19 08:06:41
|
Just FYI that PR 193 has been merged. Best regards, Xiaofan On Sun, Apr 9, 2023 at 10:02 PM Xiaofan Chen <xia...@gm...> wrote: > I am not so sure if there are many libusbdotnet users here. In case you > are interested, you may want to take a look at the PR here.which > is one of the main missing features of the master branch (async > transfer support). > https://github.com/LibUsbDotNet/LibUsbDotNet/pull/193 > > There are other missing features like the Device Notification. > https://github.com/LibUsbDotNet/LibUsbDotNet/issues/32 > > There are also some issues not yet sorted out, for both the master > branch (v3) and v2 branch. > https://github.com/LibUsbDotNet/LibUsbDotNet/issues > > -- > Xiaofan > |
From: Xiaofan C. <xia...@gm...> - 2023-04-14 08:33:39
|
Hi Manish, You need to follow the license. libusbdotnet: LGPL v3 license https://github.com/LibUsbDotNet/LibUsbDotNet/blob/master/LICENSE libusb-win32 driver: GPL v3 license https://github.com/mcuee/libusb-win32/blob/master/libusb/COPYING_GPL.txt libusb-win32 library: LGPL v3 license https://github.com/mcuee/libusb-win32/blob/master/libusb/COPYING_LGPL.txt As long as you did not modify any of the source codes, you should be fine. You can point out the location of the two projects for the source codes or you can bundle the source codes. Best regards, Xiaofan On Fri, Apr 14, 2023 at 4:09 PM Manish Ram <ram...@gm...> wrote: > > Hello Libusb Team, > > Needed information regarding the usage of Libusb in my application. > > We are using the below versions: > > LibUsbDotNet dll version: 2.2.29 > > USB Driver version: 1.2.6.0 > > Could you please let us know if there is any restriction on the distribution of these > libraries along with my application? > > Best Regards, > Manish Ram |
From: Manish R. <ram...@gm...> - 2023-04-14 08:08:35
|
Hello Libusb Team, Needed information regarding the usage of Libusb in my application. We are using the below versions: LibUsbDotNet dll version: 2.2.29 USB Driver version: 1.2.6.0 Could you please let us know if there is any restriction on the distribution of these libraries along with my application? Best Regards, Manish Ram |
From: Xiaofan C. <xia...@gm...> - 2023-04-09 14:03:27
|
I am not so sure if there are many libusbdotnet users here. In case you are interested, you may want to take a look at the PR here.which is one of the main missing features of the master branch (async transfer support). https://github.com/LibUsbDotNet/LibUsbDotNet/pull/193 There are other missing features like the Device Notification. https://github.com/LibUsbDotNet/LibUsbDotNet/issues/32 There are also some issues not yet sorted out, for both the master branch (v3) and v2 branch. https://github.com/LibUsbDotNet/LibUsbDotNet/issues -- Xiaofan |
From: Xiaofan C. <xia...@gm...> - 2023-02-27 13:20:09
|
It is great that Pete has got libwdi/Zadig working under Windows on ARM64. https://github.com/pbatard/libwdi/issues/155#issuecomment-1445231926 This should help you running libusb API based applications on Windows on ARM64, Please take note libusbK.sys will not be modified to support ARM64. However, you may want to try libusbK based application (x86_64) under Windows on ARM64 to see if that works or not. Or you can also try the libusbK Windows ARM64 testing binary (no libusbK.sys( to see if that works or not. https://github.com/mcuee/libusbk/issues/40#issuecomment-1421815330 -- Xiaofan |
From: Xiaofan C. <xia...@gm...> - 2023-01-10 13:04:37
|
Please take note libusb-1.2.7.3 release will be the last version to support Windows 7. https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.7.3/ https://github.com/mcuee/libusb-win32/releases/tag/snapshot_1.2.7.3 The reason is due to the change of Microsoft driver signing policy. https://github.com/mcuee/libusb-win32/issues/26 -- Xiaofan |
From: PriestMarmore <ped...@gm...> - 2023-01-06 01:32:48
|
Damn, I can't believe this, I'm such a fool. I done this at the beginning but I think I've done it on another device that had a yellow triangle showing up. It worked. Thanks!! On Fri, Jan 6, 2023 at 1:11 AM Xiaofan Chen <xia...@gm...> wrote: > You may want to follow the process here. > 1) Right-click the Windows Start button and click Device Manager. > 2) In the tree view, right-click the device and click Uninstall device. > 3) A dialog named Uninstall Device will pop up. If present, check the > box Attempt to remove the driver for this device. Click Uninstall to > continue un-installing this driver. > 4) Unplug your USB device from your computer, and plug it back in for > re-installation. > > Best regards, > Xiaofan > > On Fri, Jan 6, 2023 at 8:51 AM PriestMarmore <ped...@gm...> > wrote: > > > > I have an external HDD that doesn't connect to my desktop when I boot > on Windows but connects to my laptop on windows and both my laptop and > desktop on Ubuntu. I tried to change the partition type, format the disk, > format windows and my BIOS. I can't connect my hdd still. > > When I connect to the PC the desktop acknowledges the disk with a sound > but it doesn't show up anywhere else except on "Device Manager" as > "External USB 3.0" under the category "libusbK Usb Devices". I search > online and this is where I came. I tried to download the program but > nothing although I don't even know if I downloaded the correct version. > > This might be totally off-topic but I went to the Windows forums and > several subreddits and no one knows how to help me out and I'm running out > of ideas (unless it has to do with some "obscure" option on the BIOS) > > > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > |
From: Xiaofan C. <xia...@gm...> - 2023-01-06 01:13:22
|
Or you can follow the more detailed guide here. https://github.com/pbatard/libwdi/wiki/FAQ#Help_Zadig_replaced_the_driver_for_the_wrong_device_How_do_I_restore_it On Fri, Jan 6, 2023 at 9:10 AM Xiaofan Chen <xia...@gm...> wrote: > > You may want to follow the process here. > 1) Right-click the Windows Start button and click Device Manager. > 2) In the tree view, right-click the device and click Uninstall device. > 3) A dialog named Uninstall Device will pop up. If present, check the > box Attempt to remove the driver for this device. Click Uninstall to > continue un-installing this driver. > 4) Unplug your USB device from your computer, and plug it back in for > re-installation. > > Best regards, > Xiaofan > > On Fri, Jan 6, 2023 at 8:51 AM PriestMarmore <ped...@gm...> wrote: > > > > I have an external HDD that doesn't connect to my desktop when I boot on Windows but connects to my laptop on windows and both my laptop and desktop on Ubuntu. I tried to change the partition type, format the disk, format windows and my BIOS. I can't connect my hdd still. > > When I connect to the PC the desktop acknowledges the disk with a sound but it doesn't show up anywhere else except on "Device Manager" as "External USB 3.0" under the category "libusbK Usb Devices". I search online and this is where I came. I tried to download the program but nothing although I don't even know if I downloaded the correct version. > > This might be totally off-topic but I went to the Windows forums and several subreddits and no one knows how to help me out and I'm running out of ideas (unless it has to do with some "obscure" option on the BIOS) |