| 
     
      
      
      From: Graeme G. <gr...@ar...> - 2006-04-20 06:29:13
       
   | 
I'm trying to develop some software to talk to a USB device. Previous versions of this device communicated through a serial port, but now the manufacturer has switched to USB. The Device may or may not have had the originally manufacturers USB drivers installed on the users machine. I'd like my software to work in either case, and allow the user the option of installing my software, or the manufacturers software, or both, in any order. So I've installed the LibUSB-win32 filter driver. The sample application (testlibusb.c) compiles and runs OK. Normally it will show 5 busses, and if I plug a USB device in (such as a flash stick), the device will turn up on one of the busses. When I plug the device I'm developing for in, I notice two things. One is that Windows (2K) notices the new hardware, and goes looking for manufactures drivers. I don't have the manufacturers software, because I bought the device without it. Presumably Windows can be made to stop doing this by tweaking the right registry settings, although it's not clear to me whether this will then make it difficult to install the manufacturers drivers later on. The second thing I notice, is that testlibusb.exe doesn't find the device. It's hard to even get to first base if my software can't see it! Can someone point me in the right direction to solve this problem ? Windows can obviously see the device, why can't the LibUSB filter driver see the device as well ? (I'm using version 0.1.10.1) thanks, Graeme Gill.  | 
| 
     
      
      
      From: Graeme G. <gr...@ar...> - 2006-04-21 08:32:21
       
   | 
[ Hello ? Anybody out there ? Is this mailing list still active ? ] Some additional information: inf-wizard.exe does pick the device up (vendor ID 0x0765, Product ID 0xD094) , but then I get the impression from looking at its source, that it doesn't use libusb-win32 to locate devices. libusb on OSX and Linux worked straight out of the box. The OS didn't make a fuss about the new device, and testlibusb found the device without trouble. Any ideas why libusb-win32 is not behaving the same way ? Graeme Gill.  | 
| 
     
      
      
      From: Stephan M. <Ste...@ia...> - 2006-04-21 08:48:13
       
   | 
> [ Hello ? Anybody out there ? Is this mailing list still active ? ] > > Some additional information: > > inf-wizard.exe does pick the device up (vendor ID 0x0765, > Product ID 0xD094) , but then I get the impression from > looking at its source, that it doesn't use libusb-win32 > to locate devices. Does your device show up in the device manager? Is it installed properly (without a yellow exclamation mark or a red cross)? > > libusb on OSX and Linux worked straight out of the box. The > OS didn't make a fuss about the new device, and testlibusb > found the device without trouble. > > Any ideas why libusb-win32 is not behaving the same way ? > > Graeme Gill. > > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel  | 
| 
     
      
      
      From: Graeme G. <gr...@ar...> - 2006-04-21 09:03:12
       
   | 
Stephan Meyer wrote: > Does your device show up in the device manager? Is it installed > properly (without a yellow exclamation mark or a red cross)? Thanks for the response. Yes it shows up in the device manager. It has a yellow exclamation mark. The Device status says "This device is not configured correctly. (Code 1) To reinstall drivers for this device, click Reinstall Driver". Presumably this is because there aren't any device specific USB drivers installed for this device. How can I tell Windows that the libusb-win32 filter driver will handle this device ? [I'm presuming that using the inf-wizard to generate a device .inf file will lead to installing the non-filter libusb-win32 driver for this device, which would likely solve the problem, but seemed like a bad idea if the manufacturers drivers later need to be installed.] Graeme Gill.  | 
| 
     
      
      
      From: Stephan M. <Ste...@ia...> - 2006-04-21 09:34:48
       
   | 
> Yes it shows up in the device manager. It has a yellow exclamation > mark. The Device status says "This device is not configured > correctly. (Code 1) > To reinstall drivers for this device, click Reinstall Driver". > > Presumably this is because there aren't any device specific > USB drivers installed for this device. How can I tell Windows > that the libusb-win32 filter driver will handle this device ? You can't. On Windows every device needs a (device) driver in order to work. You either have to install the manufacturer's device driver or the one provided by libusb-win32. From your application's point of view it should make no difference whether you install libusb as a filter or as a 'normal' driver. You get the same API and the same functionality. The only difference is the way the kernel driver (which is the same binary file in both cases) is installed. > > [I'm presuming that using the inf-wizard to generate a device > .inf file will lead to installing the non-filter libusb-win32 > driver for this device, which would likely solve the problem, > but seemed like a bad idea if the manufacturers drivers later > need to be installed.] > > Graeme Gill. > > > > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel  | 
| 
     
      
      
      From: Graeme G. <gr...@ar...> - 2006-04-21 10:11:07
       
   | 
Stephan Meyer wrote: > > Presumably this is because there aren't any device specific > > USB drivers installed for this device. How can I tell Windows > > that the libusb-win32 filter driver will handle this device ? > > You can't. On Windows every device needs a (device) driver in > order to work. You either have to install the manufacturer's device > driver or the one provided by libusb-win32. OK - no point in attempting the impossible. Pretty brittle and inflexible of MS to do things that way, but that seems to be their style at times. I created the .inf file and installed libusb0.sys, and yes, the device now appears in testlibusb.exe output. Can I hope that if the manufacturers USB driver is installed over the top, that the filter driver will take over for my application ? (Thanks for helping sort my problems out.) Graeme Gill.  | 
| 
     
      
      
      From: Graeme G. <gr...@ar...> - 2006-04-22 01:07:14
       
   | 
On rebooting m machine this morning, I notice I now have more serious problems. USB has stopped working. Presumably this has been caused by installing libiusb0.sys for the device I want to support. What should I do now ? Graeme Gill.  | 
| 
     
      
      
      From: Graeme G. <gr...@ar...> - 2006-04-22 01:51:41
       
   | 
Some other problems I've noticed. After uninstalling libusb (both the filter and non-filter drivers), and re-installing all the USB plug and play drivers, my systems USB was operating correctly again. I then installed the filter driver, and noticed that the "Unplug/Eject" function of Windows stops operating. This means that when I want to remove a USB flash stick, there's no way of telling the system to unmount it. If I do remove the USB stick anyway, then I get a warning panel "Unsafe Removal of Device", telling me I should have clicked on the Unplug/Eject icon in the taskbar, which doesn't exist! (This has been bugging me for months. Now I know. Installing the libusb-win32 filter driver has caused this problem.) So it seems that on my system, both the filter driver, and the filter driver cause problems. The filter driver stops the Unplug/Eject function from working, but works well otherwise, and the non-filter driver kills the whole USB system. Graeme Gill.  | 
| 
     
      
      
      From: Mark B. <mc...@ec...> - 2006-04-22 08:41:13
       
   | 
I've had the same problem with the filter driver causing USB devices to disappear from add/remove programs. There is a bug open on this - 1412538. As for using the filter driver where another driver is already installed... I found that libusb can be used to get the descriptors of such devices, but can not claim an interface if the usual driver has already done so. This was from experimenting with using libusb on a mouse, just to get the hang of things (and I wasn't sure that my hardware was working). To be able to claim an interface from the device, I had to install libusb as the driver for that device, overwriting the manufacturer's driver. Maybe if the manufacturer's driver doesn't connect to the device until some software is started you may be OK using only the filter driver, but just a warning that you may have to install libusb's drivers over the top of the manufacturer's in order to do any more than find the device and get it's descriptors! Personally, I didn't find the filter driver much use, except to run testlibusb and see the descriptors of (most of) the devices connected. Not had any problems with libusb killing anything else. Maybe try again (if cleaning up the mess isn't too hard), and if it still kills everything else there could be a problem with your Windows installation. That's just my (limited) experiences. Hope some it helps. Mark. Graeme Gill wrote: > > Some other problems I've noticed. > > After uninstalling libusb (both the filter and non-filter > drivers), and re-installing all the USB plug and play drivers, > my systems USB was operating correctly again. > > I then installed the filter driver, and noticed that > the "Unplug/Eject" function of Windows stops operating. This > means that when I want to remove a USB flash stick, there's > no way of telling the system to unmount it. If I do > remove the USB stick anyway, then I get a warning > panel "Unsafe Removal of Device", telling me I > should have clicked on the Unplug/Eject icon in the taskbar, > which doesn't exist! > > (This has been bugging me for months. Now I know. > Installing the libusb-win32 filter driver has caused > this problem.) > > So it seems that on my system, both the filter driver, > and the filter driver cause problems. The filter driver > stops the Unplug/Eject function from working, but > works well otherwise, and the non-filter driver > kills the whole USB system. > > Graeme Gill. > > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel  |