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. |