Here I am

Alex C. Peper - OBD II software & Win2k?

Attention: TDR Forum Junkies
To the point: Click this link and check out the Front Page News story(ies) where we are tracking the introduction of the 2025 Ram HD trucks.

Thanks, TDR Staff

From Amsoil to Rotella? Problems?

Old Smoky "Power Pins"

Alex C. Peper

http://www.obd-2.com



Is anyone out there running this software on a laptop using Windows 2000???? I've tried two seperate laptops (both Compaqs).



The serial port is enable in the bios. Running the latest version of the software : 1. 06



I'm out of ideas at the moment. It won't "connect", its the Tricom. Tried it on my Dads 01 Ford F150 SuperCrew, my sisters 99 Pontiac Grand Am and of course my truck... ..... all no connection.



Tips? Suggestions?
 
Same thing happened to me... . it didn't work on the two PowerStrokes I tried it on. It did, however, work on my own 2001 Dodge. Never did fool with it enough to find out why.

I'm running Windows XP, not 2000.
 
Last edited:
a little debugging

Have you ever used hyperterm in Windows (it's in accessories | communications)? If so, you might pop the tricom adapter off the other end of the serial cable and plug it into a second computer's serial port. If you know the serial parameters used by the OBDII software (baud rate, etc. ) you can verify that the computer running the software is at least communicating across the cable. The OBD II software should connect with hyperterm and spew out some data. The hyperterm end won't talk back, but will tell you whether both sides are talking at least.
 
You probly know this but just in case. It will not connect till you put in the sn for the software. It will look like it is trying but will never connect.
 
Originally posted by SEmerson

You probly know this but just in case. It will not connect till you put in the sn for the software. It will look like it is trying but will never connect.



That was the first thing checked. Even uninstalled and started over to verify it was done correctly. Thanks for the suggestion, I'm hoping it is something simple and got overlooked.
 
The ODB II website claims the software is NT/2K/XP compatible, which means it must communicate appropriately with the serial interface through the OS and not directly... direct access to the h/w should not be required. Still, you never know what someone's software really does.
 
I remember reading something on the VAG-com site (VW TDI software) about now working with a compaq laptop. Something about a hardware serial port vrs a software serial port, but when I went back I could not find anything. Here are some other tips I saw there



Go through all the stuff in your System Tray:



Right-Click on each little icon. If there's a "Disable" or "Exit" option, do it!



Windows 2000 with SP1: Install IE 5. 5 or SP2.



Windows 95/98/Me: Pull up a task list by pressing CTRL-ALT-DEL. Kill everything except Explorer and Systray.



All versions of Windows: Start -> Run -> MSCONFIG. Take a look at what other non-essential stuff Windows is loading and disable it.



STOP or remove PCMCIA Cards, especially anything made by Xircom. Some IBM brand cards are also problematical.



Try turning Off your COM Port's FIFO buffers. Open the properties sheet for the COM Port in Device Manager. Select the Port Settings tab. Click the Advanced button. Uncheck the "use FIFO buffer" checkbox.
 
Back
Top