|
From: Stephan M. <ste...@we...> - 2007-03-20 10:02:20
|
> Hi there, > > > I have browsed the whole mailing list archive before posting this. > > Before complaining about libUSb, I have to say that I had a first > successful experience with this great library on a DFU class > device both on Windows and Linux, so I thought it would be very > easy to get our new HID project working... > > After reading the LibUsb-Win32 WEB main page and many users messages > I have understood the following: > > - working with an USB HID class device, I don't need the libusb0.sys > driver to get in the way. Moreover, we have choosen the HID class > so that users of our demo application don't have to install any > driver. > > - we only need libUsb0.dll and a filter driver which seems to be > activated by launching a libusbd-nt.exe service we can see running > through the Windows Tasks Manager. > > - we can hide the filter driver launching process by starting it > from our installation program. The service is not part of the latest release any more. The latest version uses a different approach to install the filter. You can install the filter manually by using the 'install-filter.exe' command line tool. Type 'install-filter.exe -h' to see the available options. You can also include the install in your application (see install_filter.c for details). Please note: your users will need admin rights to install the filter! > > Please tell me the above assumptions are wrong because this filter > driver stuff seems to be a tricky part of libUsb. > OK. Here is the problem description: > > usbDevice = device_init(vid, pid); > > deviceHandle = usb_open(usbDevice); > > usb_set_configuration(deviceHandle, CONFIGURATION); // config = 0 Try 'config = 1', it should work then. > > usb_claim_interface(deviceHandle, INTERFACE); // interface = 0 > > I have removed all tests to make things clearer. > device_init, usb_open and usb_set_configuration return codes are OK. > The usb_claim_interface returns the error code -22 > > OS version: Windows 2K 5.00.2195 SP4 > libUsb: 0.1.10.1 > Peripheral Manager: our HID device status is OK > Task Manager: libusbd-nt.exe is running > > I have installed the 0.1.12.0 version to check if it could > fix the problem, but the things go even worse: the filter driver > service starts then stops after a few seconds. This has been tested > on a Windows XP machine with the same behavior: the service starts and > stops. Please do not use the old version any more. It's outdated. Apart from that, I won't recommend to use the filter feature at all and use the device driver instead, because: * it's very likely that the filter won't work on Vista * the device driver will work on Vista * the filter doesn't work properly with some devices (this is a Windows issue) * the filter is a development tool, not intended to be used by "professional" applications * your users have to install a driver anyway, either the filter or the device driver, so they won't see any difference. > > Many thanks for your help and time! > > Georges > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 |
|
From: Spiro T. <an-...@sp...> - 2007-03-20 10:54:43
|
Hello, * On Tue, Mar 20, 2007 at 11:02:10AM +0100 Stephan Meyer wrote: > > OS version: Windows 2K 5.00.2195 SP4 > > libUsb: 0.1.10.1 > > Peripheral Manager: our HID device status is OK > > Task Manager: libusbd-nt.exe is running > > > > I have installed the 0.1.12.0 version to check if it could > > fix the problem, but the things go even worse: the filter driver > > service starts then stops after a few seconds. This has been tested > > on a Windows XP machine with the same behavior: the service starts and > > stops. > > Please do not use the old version any more. It's outdated. This reminds me: What is the state of libusb-win32 for Windows 2000? I found that the latest release does not even install with the DDK (3790.1830) in the Windows 2000 build environment. Does it mean that Windows 2000 is not supported anymore? What about Vista 64 bit? As far as I see, the driver is not signed, thus, it should refuse to install there. (I do not have Vista, so, I cannot check for myself). Do you plan to support 64 bit Windows at all? Regards, Spiro. -- Spiro R. Trikaliotis http://opencbm.sf.net/ http://www.trikaliotis.net/ http://www.viceteam.org/ |
|
From: Stephan M. <ste...@we...> - 2007-03-20 12:15:49
|
> Hello, > > * On Tue, Mar 20, 2007 at 11:02:10AM +0100 Stephan Meyer wrote: > > > > OS version: Windows 2K 5.00.2195 SP4 > > > libUsb: 0.1.10.1 > > > Peripheral Manager: our HID device status is OK > > > Task Manager: libusbd-nt.exe is running > > > > > > I have installed the 0.1.12.0 version to check if it could > > > fix the problem, but the things go even worse: the filter driver > > > service starts then stops after a few seconds. This has been tested > > > on a Windows XP machine with the same behavior: the service starts and > > > stops. > > > > Please do not use the old version any more. It's outdated. > > This reminds me: What is the state of libusb-win32 for Windows 2000? I > found that the latest release does not even install with the DDK > (3790.1830) in the Windows 2000 build environment. Does it mean that > Windows 2000 is not supported anymore? Windows 2000 is fully supported, even Win98SE. I just installed the 0.1.12.1 release (compiled with mingw) on win2k-sp4 (vmplayer install) and it works like a charm. Don't use the DDK's Win2k build environment, use the XP or the Server 2003 build environment even if you want to compile for Win2k. > > What about Vista 64 bit? As far as I see, the driver is not signed, > thus, it should refuse to install there. (I do not have Vista, so, I > cannot check for myself). You are right, Vista-64bit won't let you install unsigned drivers. This means that this platform is currently not supported. To resolve this issue, future versions of libusb-win32 will use Vistas built-in kernel driver winusb.sys. > > Do you plan to support 64 bit Windows at all? XP-64bit and Server-2003-64bit are supported. Use the files libusb0_x64.dll and libusb0_x64.sys on these systems. > > Regards, > Spiro. > > -- > Spiro R. Trikaliotis http://opencbm.sf.net/ > http://www.trikaliotis.net/ http://www.viceteam.org/ > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 |
|
From: Spiro T. <an-...@sp...> - 2007-03-20 17:10:12
|
Hello Stephan, * On Tue, Mar 20, 2007 at 01:15:07PM +0100 Stephan Meyer wrote: > Windows 2000 is fully supported, even Win98SE. I just installed the > 0.1.12.1 release (compiled with mingw) on win2k-sp4 (vmplayer install) > and it works like a charm. Good to know. I am sorry that I did not test it myself, but currently, I do not have a Win 2000 machine myself. I was very surprised because the Win 2000 build environment did not work. > Don't use the DDK's Win2k build environment, use the XP or the > Server 2003 build environment even if you want to compile for Win2k. I have had the opposite experience: Drivers compiled with the XP and 2003 environment did not work with the "lower" versions. > You are right, Vista-64bit won't let you install unsigned drivers. > This means that this platform is currently not supported. > To resolve this issue, future versions of libusb-win32 will use Vistas > built-in kernel driver winusb.sys. Ok, I wanted to propose the UMDF, but obviously, you are already aware of it. As I wrote you in my private mail, I am no specialist in USB. OTOH, I already wanted to start working with UMDF and KMDF myself. Thus, if you need any help in porting the driver, feel free to ask me. If time permits, I will try to help you, if you want. > > Do you plan to support 64 bit Windows at all? > > XP-64bit and Server-2003-64bit are supported. Use the files > libusb0_x64.dll and libusb0_x64.sys on these systems. *grmph* Of course. I already saw these files in the distribution, but I totally forgot them. :( Regards, Spiro. -- Spiro R. Trikaliotis http://opencbm.sf.net/ http://www.trikaliotis.net/ http://www.viceteam.org/ |
|
From: Stephan M. <ste...@we...> - 2007-03-20 18:16:34
|
> > You are right, Vista-64bit won't let you install unsigned drivers. > > This means that this platform is currently not supported. > > To resolve this issue, future versions of libusb-win32 will use Vistas > > built-in kernel driver winusb.sys. > > Ok, I wanted to propose the UMDF, but obviously, you are already aware > of it. > > As I wrote you in my private mail, I am no specialist in USB. OTOH, I > already wanted to start working with UMDF and KMDF myself. > > Thus, if you need any help in porting the driver, feel free to ask me. > If time permits, I will try to help you, if you want. > Thanks, but it won't be necessary to port any kernel driver code since the new DLL will use winusb.sys directly without UMDF, KMDF, or any other useless stuff that Microsoft introduced recently. Stephan _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 |
|
From: Spiro T. <an-...@sp...> - 2007-03-20 19:18:27
|
Hello Stephan, * On Tue, Mar 20, 2007 at 07:16:12PM +0100 Stephan Meyer wrote: > Thanks, but it won't be necessary to port any kernel driver code since > the new DLL will use winusb.sys directly without UMDF, KMDF, or any > other useless stuff that Microsoft introduced recently. Oh, you want to use winusb.sys directly? This sounds very interesting. Anyway, if I can help, just tell me. Regards, Spiro. -- Spiro R. Trikaliotis http://opencbm.sf.net/ http://www.trikaliotis.net/ http://www.viceteam.org/ |
|
From: Bertrik S. <be...@si...> - 2007-03-25 14:21:34
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stephan Meyer wrote: >>> You are right, Vista-64bit won't let you install unsigned drivers. >>> This means that this platform is currently not supported. >>> To resolve this issue, future versions of libusb-win32 will use Vistas >>> built-in kernel driver winusb.sys. >> Ok, I wanted to propose the UMDF, but obviously, you are already aware >> of it. >> >> As I wrote you in my private mail, I am no specialist in USB. OTOH, I >> already wanted to start working with UMDF and KMDF myself. >> >> Thus, if you need any help in porting the driver, feel free to ask me. >> If time permits, I will try to help you, if you want. >> > > Thanks, but it won't be necessary to port any kernel driver code since the > new DLL will use winusb.sys directly without UMDF, KMDF, or any other > useless stuff that Microsoft introduced recently. I won't mind help testing that (no matter how beta). I have some experience debugging USB stuff and I also have a microcontroller board available (LPC2148) that I can program as basically any kind of USB device for testing. (USB 2.0 full-speed only, isochronous currently not supported). Kind regards, Bertrik -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGBoVQETD6mlrWxPURAg6NAJ95RSoteQRnwKGKj1XJcnIQo1/fKACgufDl U/41NwT0ojUjzd/kEwWGzP0= =q1w/ -----END PGP SIGNATURE----- |