• Earn and redeem ZillaCash credit automatically with each order - no fine print, no strings attached, and no hoops to jump through to cash in. Ape hangers on softail deuce.

1. Driver Windows Xp

I decided to give it a go with USB 3 and windows xp. Downloaded the usb 3 drivers supplied by HP(elitebook 8560p), and had no issues reading my car with my already installed CDM20824 FD232 driver(). Have you tried other devices in those ports?(flash drives, etc?)Can you give a little more info on your setup? Did you run XP through a VM. Van dyke parks orange crate art rare. If so what is your main OS? My main OS is Win 7 and I could only get it to install through Windows 8 VM.

What did you need to download the USB drivers from HP for? Wasn't your USB 3 already operational. Everything else (USB sticks and cameras) work in both USB ports. Last edited by ItsThaMonsta; at 11:40 PM. Can you give a little more info on your setup?

Did you run XP through a VM. If so what is your main OS? My main OS is Win 7 and I could only get it to install through Windows 8 VM. What did you need to download the USB drivers from HP for? Wasn't your USB 3 already operational.

BMW E90 How To Code **INSTANT** Auto Folding Mirrors With Remote FOB Using NCS Expert DIY - Duration: 57:27. Vehicular DIY 78,402 views.

Driver Windows Xp

Everything else (USB sticks and cameras) work in both USB ports. Main OS is Windows XP Pro. Downloaded the drivers to make the USB 3 ports work(hadnt bothered until now., its a dedicated shop/diagnostic laptop) Plugged in my cable to the USB 3 port(rather then the USB 2 port i normally use) and it worked just fine. Does your cable show up in device manager under COM ports as a Serial Converter? Try the driver i linked to. You have Set obd.ini to the same port as the device manager says?

You have ediabas.ini set to STD:OBD, and have previously run the obd.exe hardware setup? Last edited by legoman67; at 12:21 AM.

Main OS is Windows XP Pro. Downloaded the drivers to make the USB 3 ports work(hadnt bothered until now., its a dedicated shop/diagnostic laptop) Plugged in my cable to the USB 3 port(rather then the USB 2 port i normally use) and it worked just fine. Does your cable show up in device manager under COM ports as a Serial Converter? Try the driver i linked to.

You have Set obd.ini to the same port as the device manager says? You have ediabas.ini set to STD:OBD, and have previously run the obd.exe hardware setup?Yup I have all of those set up properly.

I think the difference with your setup is that you are natively running XP with USB 2.0 ports. FTDI documentation says that the drivers wont install on USB 3.0 unless you have windows 8. The work around for older OS systems is to install the drivers through USB 2.0 first, then they will work with the 3.0 port. This is essentially what you did. I have no USB 2.0 ports so I can only get the drivers installed on windows 8. I tried 3 sets of drivers 2.08.30, 2.10.0 and 2.12.0. They all installed but can't get communication with the car.

Try the driver pack I made up in this thread- You'll need to do a manual install (the have disk option) and point it to ftdiport.inf and then repeat to ftdibus.inf There's nothing special it uses for the drivers, just regular FTDI ones, but the latest 2.12 drivers have been bricking modules which has annoyed a lot of people, including microsoft. The end users have no idea where the ftdi chips were sourced, and no way to check. If FTDI wan't to get legal, they should go after the manufacturers.Man, I'm trying this exact thing and it's not taking. So frustrating.

- - - Updated - - - Actually, I see that INPA recognizes ignition on/off and battery but everything else says 'no response from car or module'. I think it's the wrong drivers issue.