- May 26, 2001
- 984
- 0
- 0
I bought this wonderful USB Bridge Cable with Plug and Play connectivity, right? After all, that's what USB's about... Well I plug the cable in, and Windows asks for the software. I put in the disc, and everything installs fine. Windows recognizes the driver, and everything's wonderful. So I go to my next computer, and plug the other end of the cable into the USB port. I boot up the computer, and Windows 98SE recognizes a USB device, and takes matters into it's own hands. It recognizes the device only as "Unknown Device" and proceeds to install the "Unknown Device" driver from the Windows\INF directory. It never prompts me to locate software for it.
Well, no big deal, right? Just go into device manager and install the driver. Well, I click on the "Update Driver" button, and search the directory with the Bridge Cable driver in it, Windows goes right over it and says the the "Unknown Device" driver is the best one, and it will continue using it.
Anyways, to make the story shorter, I tried removing it, and plugging it back in when it booted onto the desktop, but it does the same thing, installs the "Unknown Device" driver. So I tried unplugging the other end of the Bridge Cable; no help. Now I'm rather mad at it, I've spent a couple hours trying different configurations, unplugging and plugging it back in, downloading USB and chipset updates, and even removing all USB devices from the device manager, and having windows reinstall them all.
Nothing worked.
So finally, I get the idea, "Why don't I just reverse the cable, and try that..." Well, I do that and my second computer recognizes the bridge cable, and installs the correct software. So I plug the cable into my first computer, and that one, the one that installed fine, doesn't recognize the cable, and installs the Unknown Device driver.
To summarize all this, one end of the cable is recognized by windows, but the other end is only recognized as "Unknown Device", and it automatically installs default drivers, which I can't seem to overwrite, because the .INF file won't show up in hardware detection, or manual install.
My question is, Is there any way that I can Force windows to install a Driver for a device?
Otherwise, my only other solution is that the cable must be faulty.
Well, no big deal, right? Just go into device manager and install the driver. Well, I click on the "Update Driver" button, and search the directory with the Bridge Cable driver in it, Windows goes right over it and says the the "Unknown Device" driver is the best one, and it will continue using it.
Anyways, to make the story shorter, I tried removing it, and plugging it back in when it booted onto the desktop, but it does the same thing, installs the "Unknown Device" driver. So I tried unplugging the other end of the Bridge Cable; no help. Now I'm rather mad at it, I've spent a couple hours trying different configurations, unplugging and plugging it back in, downloading USB and chipset updates, and even removing all USB devices from the device manager, and having windows reinstall them all.
Nothing worked.
So finally, I get the idea, "Why don't I just reverse the cable, and try that..." Well, I do that and my second computer recognizes the bridge cable, and installs the correct software. So I plug the cable into my first computer, and that one, the one that installed fine, doesn't recognize the cable, and installs the Unknown Device driver.
To summarize all this, one end of the cable is recognized by windows, but the other end is only recognized as "Unknown Device", and it automatically installs default drivers, which I can't seem to overwrite, because the .INF file won't show up in hardware detection, or manual install.
My question is, Is there any way that I can Force windows to install a Driver for a device?
Otherwise, my only other solution is that the cable must be faulty.
