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
(3) |
Nov
(3) |
Dec
|
From: Xiaofan C. <xia...@gm...> - 2016-02-26 04:38:18
|
Just wondering how many users are using the libusbK API (libusbK.dll)? How many are using the libusbK driver (libusbk.sys)? libusbK API is Windows only and it supports libusbk.sys, libusb0.sys and WinUSB. It is quite unique. The only alternative I can think of is probably the original WinUSB API. Travis mentioned before he wanted to add the WinUSB ISO support in libusbK.dll but I am not so sure when that will happen. Of course users can switch to libusb-1.0 API as well. As for libusbk.sys, I think the usage is probably pretty low since WinUSB will be a better alternative. -- Xiaofan On Mon, Aug 10, 2015 at 10:58 PM, Travis <lib...@gm...> wrote: > Greetings, > > LibusbK is already signed with a DigiCert High Assurance EV Root CA. > > At some point, I would like to add the WinUSB ISO support to the libusbK > library and let it become our "primary" driver. There is little > advantage to using libusbK.sys compares to the newer WinUsb.sys with ISO > support. > > That said, nothing is going to stop working. Even if we support WinUSB > ISO, we will not throw libusbK.sys away. I would expect most all users > to WANT to transition to the winusb driver. There are some big > advantage because it is essentially a built-in windows driver for custom > usb devices. You can even add things to you USB descriptor which > identifies it as a "winusb" device and eliminate the need for a driver > installer all-together. > > Regards, > Travis > |
From: Xiaofan C. <xia...@gm...> - 2016-02-26 04:31:02
|
On Sun, Aug 2, 2015 at 12:10 AM, Xiaofan Chen <xia...@gm...> wrote: > On Sun, Aug 2, 2015 at 12:07 AM, Xiaofan Chen <xia...@gm...> wrote: >> So I guess if you are happy with libusb-win32 you can continue to use >> it. If not, better start to switch to libusb. > > BTW, you can use libusb-compat already under Windows. It just lacks > the enhanced Windows only libusb-win32 API. But since it sits on top > of libusb Windows, you can use WinUSB driver. > For users of libusb-win32 filter driver, it may or may not work. If it works that is good. If it does not, we will not support it. If you want to use something like the libusb-win32 filter driver but is more updated, you may want to look at usbdk. https://github.com/daynix/UsbDk usbdk has been integrated in libusb (libusb-1.0 API) git and will be included in the upcoming libusb 1.0.21 release. libusb: https://github.com/libusb/libusb/wiki -- Xiaofan |
From: Xiaofan C. <xia...@gm...> - 2016-02-26 04:26:27
|
Just to rehash this thread. On Sun, Aug 2, 2015 at 12:07 AM, Xiaofan Chen <xia...@gm...> wrote: > Hi all, > > I am not so sure how many people are still using libusb-win32. I will > still be able to spend time on this mailing list to support technical > questions but I do not think any new release will be done. It is quite > mature and I think people can still use it (I have not tested Windows > 10 yet). > > For the libusb-win32 driver portion, other than some legacy device, > I think it is probably better to use WinUSB whenever possible. As > for libusb-win32 library portion (extended libusb-0.1 API), it is probably > better to migrated to libusb-1.0 API (by libusb project). The only missing > function for libusb Windows is currently the isochronous transfer which > I believe will eventually be incorporated. > > So I guess if you are happy with libusb-win32 you can continue to use > it. If not, better start to switch to libusb. > > > > -- > Xiaofan |
From: Xiaofan C. <xia...@gm...> - 2016-02-26 04:25:04
|
On Fri, Feb 26, 2016 at 12:22 PM, Xiaofan Chen <xia...@gm...> wrote: > I think you'd better forget about the libusb-win32 filter driver. It may > or may not work. If it works that is good. If it does not, we will not > support it. Take note there is no libusbk filter driver. The filter driver is the libusb-win32 filter driver. If you want to use something like the libusb-win32 filter driver but is more updated, you may want to look at usbdk. https://github.com/daynix/UsbDk usbdk has been integrated in libusb (libusb-1.0 API) git and will be included in the upcoming libusb 1.0.21 release. -- Xiaofan |
From: Xiaofan C. <xia...@gm...> - 2016-02-26 04:22:18
|
On Fri, Feb 26, 2016 at 11:22 AM, 若水 <shl...@gm...> wrote: >> I have an USB Audio device (win7 x64bit system). It uses system >> internal driver (usbaudio.sys) and works well. >> Now, I need to add some new functions. I tried to install libusbk >> driver and run my new functions program. The new functions work well. But >> there is a problem, after I installed libusbk driver, the device will NOT be >> an USB Audio device. In order to solve the problem, I have to uninstall the >> libusbk driver and install libusbk FILTER driver. At that time, the USB >> Audio device works well. However, the new functions program cannot work. I >> debugged new functions program and found that UsbK_IsoWritePipe failed. The >> error code is 1168 (Element not found). Could you give me some instructions >> to solve the problems? Thanks. >> > I am very sorry. In the last mail, UsbK_IsoWritePipe error code is 87 > (the parameter is incorrect), not 1168. Could you help me to solve the > problem? Thanks. > I think you'd better forget about the libusb-win32 filter driver. It may or may not work. If it works that is good. If it does not, we will not support it. -- Xiaofan |
From: 若水 <shl...@gm...> - 2016-02-26 03:22:55
|
Hello, I am very sorry. In the last mail, *UsbK_IsoWritePipe * error code is 87 (the parameter is incorrect), not 1168. Could you help me to solve the problem? Thanks. Best Regards, Shang Jing 2016-02-26 11:05 GMT+08:00 若水 <shl...@gm...>: > Hello, > I have an USB Audio device (win7 x64bit system). It uses system > internal driver (usbaudio.sys) and works well. > Now, I need to add some new functions. I tried to install libusbk > driver and run my new functions program. The new functions work well. But > there is a problem, after I installed libusbk driver, the device will NOT > be an USB Audio device. In order to solve the problem, I have to uninstall > the libusbk driver and install libusbk FILTER driver. At that time, the USB > Audio device works well. However, the new functions program cannot work. I > debugged new functions program and found that *UsbK_IsoWritePipe* failed. > The error code is 1168 (Element not found). Could you give me some > instructions to solve the problems? Thanks. > > Best Regards, > Shang Jing > |
From: 若水 <shl...@gm...> - 2016-02-26 03:05:11
|
Hello, I have an USB Audio device (win7 x64bit system). It uses system internal driver (usbaudio.sys) and works well. Now, I need to add some new functions. I tried to install libusbk driver and run my new functions program. The new functions work well. But there is a problem, after I installed libusbk driver, the device will NOT be an USB Audio device. In order to solve the problem, I have to uninstall the libusbk driver and install libusbk FILTER driver. At that time, the USB Audio device works well. However, the new functions program cannot work. I debugged new functions program and found that *UsbK_IsoWritePipe* failed. The error code is 1168 (Element not found). Could you give me some instructions to solve the problems? Thanks. Best Regards, Shang Jing |
From: Xiaofan C. <xia...@gm...> - 2015-11-24 02:22:30
|
On Tue, Nov 24, 2015 at 4:35 AM, Karsten Schulz <kah...@fr...> wrote: > we have an Microcontroller on the USB Port, and write/read em succseed with > LibUSB. Now we try to read/write with WinUSB. Why? If you want to use WinUSB, you can try to use libusb Windows (libusb-1.0 Windows) and not libusb-win32. libusb: http://libusb.info/ https://github.com/libusb/libusb/wiki/Windows -- Xiaofan |
From: Xiaofan C. <xia...@gm...> - 2015-11-24 02:18:46
|
On Mon, Nov 23, 2015 at 9:28 PM, Xiaofan Chen <xia...@gm...> wrote: > I just got time to carry out some simple tests under Windows 10 Professional > (upgraded from Windows 7 Ultimate) on a 5 year old PC (only 2GB RAM > with Pentium Dual Core E5500 Intel G41 chipset). > > It seems to me that libusb-win32, libusbK and libusbdotnet all work fine > under Windows 10. > > I use the libusbK inf-wizard GUI and Zadig for the installation of the drivers > (libusb0.sys, libusbK.sys and WinUSB). > > I'd like to get your feedback on Windows 10. It seems to be more stringent > on the digital signature but Zadig and libusbK inf-wizard's self-signing method > seem to work fine. The main worry about Windows 10 is on the driver package signing. Ref: http://libusb.6.n5.nabble.com/libusb-libusb-under-Windows-10-td5715304.html -- Xiaofan |
From: Xiaofan C. <xia...@gm...> - 2015-11-24 02:14:34
|
On Tue, Nov 24, 2015 at 4:04 AM, Tim Hutt <td...@gm...> wrote: > Is there any reason to use anything other than WinUSB on Windows 10? It > supports iso transfers finally and if you're making your own device you can > have it install the WinUSB driver automatically (that actually works on > Windows 7 too). Not many reasons to use libusb0.sys or libusbK.sys. For libusb0.sys and libusbK.sys, they are still needed for people who want to use libusb-win32. The alternative is to use libusb-compat-0.1 under Windows but that is not yet officially supported by libusb project. libusb0.sys is still needed for people who have old HW not compatible with KMDF (WinUSB and libusbK.sys). -- Xiaofan |
From: Graeme G. <gr...@ar...> - 2015-11-23 22:38:40
|
Tim Hutt wrote: > Is there any reason to use anything other than WinUSB on Windows 10? WinUSB doesn't work with all devices, because it does a GET_STATUS automatically. Graeme Gill. |
From: Karsten S. <kah...@fr...> - 2015-11-23 20:38:46
|
Hello togheter, we have an Microcontroller on the USB Port, and write/read em succseed with LibUSB . Now we try to read/write with WinUSB. An Problem is the content of : WINUSB_SETUP_PACKET LibUsb use : usb_control_msg(usb_dev_handle *dev, int requesttype, int request,int value, int index, char *bytes, int size,int timeout) to send/recieve data , in this case WinUSB need to form out an SetupPacket: WINUSB_SETUP_PACKET setup; SetupPacket.RequestType = (1<<5) | 0x80; //try use type from LibUSB SetupPacket.Request = 0; SetupPacket.Value = 0; SetupPacket.Index = 0; SetupPacket.Length = sizeof(UCHAR); WinUsb_ControlTransfer(WinusbHandle, SetupPacket, &bars, sizeof(UCHAR), &cbSent, 0); Command ends Succsesfull! But the part got no data. Hav any one Information to form out the setup packed correctly so we can use alternat WinUSB ? We use it for Digispark Atiny85 Microcontrollerboard with arduino : http://digistump.com/wiki/digispark/tutorials/connecting Thanks much for any Help Karsten from Berlin www.FlexxVision.de |
From: David N. <Dav...@Da...> - 2015-11-23 20:08:17
|
We've always kept libusb0.sys to be code compatible with LibUSB on Linux. David On 11/23/2015 3:04 PM, Tim Hutt wrote: > > Is there any reason to use anything other than WinUSB on Windows 10? > It supports iso transfers finally and if you're making your own device > you can have it install the WinUSB driver automatically (that actually > works on Windows 7 too). > > On 23 Nov 2015 1:29 pm, "Xiaofan Chen" <xia...@gm... > <mailto:xia...@gm...>> wrote: > > I just got time to carry out some simple tests under Windows 10 > Professional > (upgraded from Windows 7 Ultimate) on a 5 year old PC (only 2GB RAM > with Pentium Dual Core E5500 Intel G41 chipset). > > It seems to me that libusb-win32, libusbK and libusbdotnet all > work fine > under Windows 10. > > I use the libusbK inf-wizard GUI and Zadig for the installation of > the drivers > (libusb0.sys, libusbK.sys and WinUSB). > > I'd like to get your feedback on Windows 10. It seems to be more > stringent > on the digital signature but Zadig and libusbK inf-wizard's > self-signing method > seem to work fine. > > -- > Xiaofan > > ------------------------------------------------------------------------------ > Go from Idea to Many App Stores Faster with Intel(R) XDK > Give your users amazing mobile app experiences with Intel(R) XDK. > Use one codebase in this all-in-one HTML5 development environment. > Design, debug & build mobile apps & 2D/3D high-impact games for > multiple OSs. > http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140 > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > <mailto:Lib...@li...> > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > > > > ------------------------------------------------------------------------------ > Go from Idea to Many App Stores Faster with Intel(R) XDK > Give your users amazing mobile app experiences with Intel(R) XDK. > Use one codebase in this all-in-one HTML5 development environment. > Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. > http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140 > > > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
From: Tim H. <td...@gm...> - 2015-11-23 20:04:46
|
Is there any reason to use anything other than WinUSB on Windows 10? It supports iso transfers finally and if you're making your own device you can have it install the WinUSB driver automatically (that actually works on Windows 7 too). On 23 Nov 2015 1:29 pm, "Xiaofan Chen" <xia...@gm...> wrote: > I just got time to carry out some simple tests under Windows 10 > Professional > (upgraded from Windows 7 Ultimate) on a 5 year old PC (only 2GB RAM > with Pentium Dual Core E5500 Intel G41 chipset). > > It seems to me that libusb-win32, libusbK and libusbdotnet all work fine > under Windows 10. > > I use the libusbK inf-wizard GUI and Zadig for the installation of the > drivers > (libusb0.sys, libusbK.sys and WinUSB). > > I'd like to get your feedback on Windows 10. It seems to be more stringent > on the digital signature but Zadig and libusbK inf-wizard's self-signing > method > seem to work fine. > > -- > Xiaofan > > > ------------------------------------------------------------------------------ > Go from Idea to Many App Stores Faster with Intel(R) XDK > Give your users amazing mobile app experiences with Intel(R) XDK. > Use one codebase in this all-in-one HTML5 development environment. > Design, debug & build mobile apps & 2D/3D high-impact games for multiple > OSs. > http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140 > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > |
From: David N. <Dav...@Da...> - 2015-11-23 14:49:21
|
The Windows 8 installation we created using libusbK inf-wizard GUI and libusb0.sys works fine on Windows 10. David On 11/23/2015 8:28 AM, Xiaofan Chen wrote: > I just got time to carry out some simple tests under Windows 10 Professional > (upgraded from Windows 7 Ultimate) on a 5 year old PC (only 2GB RAM > with Pentium Dual Core E5500 Intel G41 chipset). > > It seems to me that libusb-win32, libusbK and libusbdotnet all work fine > under Windows 10. > > I use the libusbK inf-wizard GUI and Zadig for the installation of the drivers > (libusb0.sys, libusbK.sys and WinUSB). > > I'd like to get your feedback on Windows 10. It seems to be more stringent > on the digital signature but Zadig and libusbK inf-wizard's self-signing method > seem to work fine. > |
From: Xiaofan C. <xia...@gm...> - 2015-11-23 13:28:24
|
I just got time to carry out some simple tests under Windows 10 Professional (upgraded from Windows 7 Ultimate) on a 5 year old PC (only 2GB RAM with Pentium Dual Core E5500 Intel G41 chipset). It seems to me that libusb-win32, libusbK and libusbdotnet all work fine under Windows 10. I use the libusbK inf-wizard GUI and Zadig for the installation of the drivers (libusb0.sys, libusbK.sys and WinUSB). I'd like to get your feedback on Windows 10. It seems to be more stringent on the digital signature but Zadig and libusbK inf-wizard's self-signing method seem to work fine. -- Xiaofan |
From: Xiaofan C. <xia...@gm...> - 2015-11-22 14:15:41
|
On Thu, Oct 22, 2015 at 5:32 PM, Xiaofan Chen <xia...@gm...> wrote: > On Thu, Oct 22, 2015 at 1:45 PM, <div...@li...> wrote: >> I don't mean the installer created by info wizard won't work on win 10, I >> mean the info wizard itself doesn't work on win 10. Why the USB driver, >> winUSB, libusbk, and libusb0, versions it detected are all 0.0.0.0? It's >> sure if the wizard itself can't work on win10, doesn't mean the installer it >> generated can't run on win 10. >> > > Right now I do not have Windows 10 to test. If that is the case, please > try Zadig to see if that works. > > Zadig: http://zadig.akeo.ie/ > I just installed Windows 10 Professional (upgraded from Windows 7 Ultimate) and libusbK-inf-wizard works correctly. And the installer it generated also works fine under Windows 10. Are you sure you installed libusbK correctly? Please reinstall. -- Xiaofan |
From: Xiaofan C. <xia...@gm...> - 2015-10-23 11:53:19
|
On Thu, Oct 22, 2015 at 8:18 PM, mabdallah <moh...@av...> wrote: > I'm trying to use libUSb-Win32 with USB-to-TTl serial converter to send raw > data just to test making usb driver on windows. > > bus/device idVendor/idProduct > bus-0/\\.\libusb0-0001--0x067b-0x2303 067B/2303 > - Manufacturer : Prolific Technology Inc. > - Product : USB-Serial Controller This is not really a good device for learning. It is a USB to serial converter and Prolific provides the driver so that you can use serial API to talk to the device. Anyway, you may want to take a look at the example of using the async API. http://sourceforge.net/p/libusb-win32/code/HEAD/tree/trunk/libusb/examples/bulk.c If you want to use the sync API, it is also possible, just write more data in one go and the speed should be faster. -- Xiaofan |
From: mabdallah <moh...@av...> - 2015-10-22 12:18:50
|
I'm trying to use libUSb-Win32 with USB-to-TTl serial converter to send raw data just to test making usb driver on windows, the problem is that data rate monitored on the bus using USBLyzer is 6.6msec per bit ! how can i increase the speed to maximum available speed ? N.B. Data is send correctly with no problem in data itself, the problem is with speed. Here is my code: =========== usb_init(); usb_set_debug(255) ; usb_find_busses(); num = usb_find_devices() ; printf("Devices: %d\n", num) ; busses = usb_get_busses(); for (bus = busses; bus; bus = bus->next) { struct usb_device *dev; for (dev = bus->devices; dev; dev = dev->next) { if ((dev->descriptor.idVendor == 0x067B) && (dev->descriptor.idProduct == 0x2303)) { mydev = usb_open(dev) ; if (mydev == NULL) { printf("Error: usb_open\n") ; } else { printf("Device opened\n") ; mreturn = usb_set_configuration(mydev, 1) ; if (mreturn != 0) { printf("Error: usb_set_configuration\n") ; } else { printf("Config. set\n") ; mreturn = usb_claim_interface(mydev, 0) ; if (mreturn != 0) { printf("Error: usb_claim_interface\n") ; } else { printf("Interface claimed\n") ; mreturn = usb_bulk_write(mydev, 2, data, 1000, 0) ; if (mreturn < 0) { printf("Error: usb_bulk_write\n") ; } else { printf("Data sent\n") ; } usb_release_interface(mydev, 0) ; } } } } } } and here is USB info by testlibusb-win: ========================= bus/device idVendor/idProduct bus-0/\\.\libusb0-0001--0x067b-0x2303 067B/2303 - Manufacturer : Prolific Technology Inc. - Product : USB-Serial Controller bLength: 18 bDescriptorType: 01h bcdUSB: 0110h bDeviceClass: 00h bDeviceSubClass: 00h bDeviceProtocol: 00h bMaxPacketSize0: 40h idVendor: 067Bh idProduct: 2303h bcdDevice: 0300h iManufacturer: 1 iProduct: 2 iSerialNumber: 0 bNumConfigurations: 1 wTotalLength: 39 bNumInterfaces: 1 bConfigurationValue: 1 iConfiguration: 0 bmAttributes: a0h MaxPower: 50 bInterfaceNumber: 0 bAlternateSetting: 0 bNumEndpoints: 3 bInterfaceClass: 255 bInterfaceSubClass: 0 bInterfaceProtocol: 0 iInterface: 0 bEndpointAddress: 81h bmAttributes: 03h wMaxPacketSize: 10 bInterval: 1 bRefresh: 0 bSynchAddress: 0 bEndpointAddress: 02h bmAttributes: 02h wMaxPacketSize: 64 bInterval: 0 bRefresh: 0 bSynchAddress: 0 bEndpointAddress: 83h bmAttributes: 02h wMaxPacketSize: 64 bInterval: 0 bRefresh: 0 bSynchAddress: 0 Thanks -- View this message in context: http://libusb.6.n5.nabble.com/Win7-speed-issue-tp5715261.html Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com. |
From: Xiaofan C. <xia...@gm...> - 2015-10-22 09:32:38
|
On Thu, Oct 22, 2015 at 1:45 PM, <div...@li...> wrote: > I don't mean the installer created by info wizard won't work on win 10, I > mean the info wizard itself doesn't work on win 10. Why the USB driver, > winUSB, libusbk, and libusb0, versions it detected are all 0.0.0.0? It's > sure if the wizard itself can't work on win10, doesn't mean the installer it > generated can't run on win 10. > Right now I do not have Windows 10 to test. If that is the case, please try Zadig to see if that works. Zadig: http://zadig.akeo.ie/ -- Xiaofan |
From: <div...@li...> - 2015-10-22 05:45:36
|
I don't mean the installer created by info wizard won't work on win 10, I mean the info wizard itself doesn't work on win 10. Why the USB driver, winUSB, libusbk, and libusb0, versions it detected are all 0.0.0.0? It's sure if the wizard itself can't work on win10, doesn't mean the installer it generated can't run on win 10. 通过 Android 版 Outlook 发送 On Wed, Oct 21, 2015 at 9:00 PM -0700, "Xiaofan Chen" <xia...@gm...> wrote: On Wed, Oct 21, 2015 at 11:32 PM, diverger <div...@li...> wrote: > Sorry for the long email, I'm not very familiar with my Android email client > yet. > > The info wizard indeed comes from the lib usbk's installer, which I download > from sourceforge. In win7, it works well, but won't on win10. > > I don't know if we mean the same "info wizard", but I mean the one comes > with the libusbk installer, can you give me some suggestions, thanks. > I see. You need to create the installer package and then run installation. (not to install the driver immediately). If that does not work under Windows 10, it is a bit strange. Please try Zadig as well. Zadig: http://zadig.akeo.ie/ -- Xiaofan ------------------------------------------------------------------------------ _______________________________________________ Libusb-win32-devel mailing list Lib...@li... https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
From: Xiaofan C. <xia...@gm...> - 2015-10-22 04:00:36
|
On Wed, Oct 21, 2015 at 11:32 PM, diverger <div...@li...> wrote: > Sorry for the long email, I'm not very familiar with my Android email client > yet. > > The info wizard indeed comes from the lib usbk's installer, which I download > from sourceforge. In win7, it works well, but won't on win10. > > I don't know if we mean the same "info wizard", but I mean the one comes > with the libusbk installer, can you give me some suggestions, thanks. > I see. You need to create the installer package and then run installation. (not to install the driver immediately). If that does not work under Windows 10, it is a bit strange. Please try Zadig as well. Zadig: http://zadig.akeo.ie/ -- Xiaofan |
From: diverger <div...@li...> - 2015-10-21 15:34:47
|
Sorry for the long email, I'm not very familiar with my Android email client yet. The info wizard indeed comes from the lib usbk's installer, which I download from sourceforge. In win7, it works well, but won't on win10. I don't know if we mean the same "info wizard", but I mean the one comes with the libusbk installer, can you give me some suggestions, thanks. 发送自我的三星设备 |
From: Xiaofan C. <xia...@gm...> - 2015-10-21 08:34:03
|
On Tue, Oct 20, 2015 at 4:12 PM, Zaslavsky Evelina <eve...@gm...> wrote: > Hi All, I'm really sorry for disturbing you. I have a problem with my > LibUsbDotNet project and asking for your help. > > In windows 7 the project works correctly, but when I migrate the project to > windows 8 i get the follow error: > No data to read IOTimeOut. > > I already reinstalled the LibUSB0 drivers. I do not know much about libusbdotnet so I am guessing here. 1) Have you tried to increase the timeout? 2) Can you try WinUSB driver instead or libusbK driver instead to see if that helps? -- Xiaofan |
From: Xiaofan C. <xia...@gm...> - 2015-10-21 08:26:49
|
On Tue, Oct 20, 2015 at 7:07 PM, <div...@li...> wrote: > I installed the infowizard on windows 10, and installed wdk7.1, but the > infowizard can't detect it, all driver versions are 0. Does it mean it > cannot work on win 10. Please trim the email next time. Thanks. As for the inf-wizard provided by libusb-win32, it is a known problem that it will not work under Windows 8/8.1/10. You should use Zadig or libusbK driver installer. Zadig: http://zadig.akeo.ie/ libusbK driver installer: http://libusbk.sourceforge.net/UsbK3/usbk_installers.html -- Xiaofan |