I tried running Diacom on a 750 MHz Celeron HP laptop and wouldn't link in either ALDL or Diagnostic, even using the /f switch (Diacom-p.exe /f)

Booted to a DOS prompt (not shelled out From Windows) using both the Windows ME Emergency Start up Disc and a DOS 6.22 boot disc; same result.

Tried both cables, 91006 and 91007, same result; no link.

Sound familiar?

Called Rinda and they sent me a new version of Diacom, 2.86 that has a slightly different Diacom-p.exe file, date of 11 May 2001.

Still wouldn't link in ALDL but using the 91007 cable, it would link in Diagnostic, but ran much slower than before when using a Compaq laptop and startup idle was raunchy.

I was able to drive the car with Diacom running in Diagnostic mode and logged the data, but in Diagnostic Mode, no ignition timing was shown and some other less important stuff didn't show either.

I tried changing to all of the four different Parallel port configurations in "Setup", ECP, Bi-Directional, Normal and EPP and only in Normal would the Diagnostic Mode link.

Rinda said it won't run in Bi-Directional, EPP or ECP modes and that 86 Vettes (like mine) and other 'F' bodies have a unique problem with Diacom that later year cars don't have.

I believe it also has a lot to do with the laptop since Diacom ran fine with the old (and now broken) Compaq laptop.

Guess it's back to the used computer store for me to try to find an old 486 33 MHz.

Here's an update, thought it might help some of you having the same problem.

This is the last msg from Rinda:

"Jake,

First you can try all the suggestions below only if you don't have an AMD processor. If you do, Diacom will not work with your laptop and you can skip all suggestions below.

The 91006 must be used only with 1986-1988 Corvettes.

Any ECP or EPP parallel modes will not work with Diacom. You'll have to check that.

Also, if you find yourself poking into BIOS disable any power saving features, especially if they shut off the hardrive(s).

You may try the following procedures:

1. Connect a jumper from a point connected to your laptop's chassis to a good ground on your vehicle.

2. If suggestion above fails then try this:

Carefully clip pins number 7 on your Diacom parallel cable. It is OK to do and it wont affect cable's normal operation.

If all these suggestions don't make a difference, you might need to get a different laptop.

Best regards,

Bogdan"

Hope this helps,

Jake

 

Just an update:

Took the car out for a 40 mile drive with Diacom running in DIAGNOSTIC Mode using 91007 adapter. I tried to monitor the laptop screen as much as I could while driving on the Interstate and in traffic.

Screen showed all normal data values and no error codes.

Saved the data to 2 GDF files and later reviewed them at home. The date was all screwed up. All sorts of values from one end of the numerical spectrum to the other - RPM as low as 163 and as high as over 6300, etc. Engine never went over 3000 RPM.

Had all sorts of error codes in the trace; Closed Loop indicator cycled from "on" to "off" every few frames, BLM and Intergrator values all over the place, etc. CRAZY!

Corrupted data! Not reliable, since engine never missed a beat.

I just learned of two other Diacom switches /N and /D; I'll give those a try next to see what, if any, difference they make.

So it's back to the drawing board.

Jake

 

Like you said find a $25 laptop, and get back to having it work right.

I like being able to run junker laptops since the most folks won't even bother stealing a 486/33......

 

Here's the latest; GOOD NEWS!

Using a HP laptop with Windows ME installed, 750 MHz Celeron CPU, 128 MB ram. I was finally able to get Diacom to link and record data in ALDL Mode.

Rinda sent me a new version of the Diacom software, 2.86 which has a modified Diacom-p.exe file and it works. That file name gets changed to GMECM.EXE when it's installed, don't ask me why they wrote it that way.

I loaded it and was able to again link in ALDL mode using the 91006 cable..

In 'SETUP" I set the parallel port setting to "Normal", then used a Windows ME Emergency Boot Disc to boot to a DOS prompt.

Switched to the 'C' drive, typed in"Diacom-p /N" and was able to link and record data in ALDL which was all normal. I then tried starting Diacom WITHOUT the switch /N and it started and linked without the switch as well.

Whatever the difference was between versions 2.85 and 2.86, it worked for me.

Here's the step by step:

I Boot to DOS using a Windows ME Emergency Start Up disc I created in Windows ME, Control Panel, Add/Remove Programs.

Once booted, I switch from "A" drive to "C" drive and type in Diacom-P (I ususally leave off the file extension, which I believe is "bat").

I verify that the displayed VIN is correct, hit ENTER and get to the data screen. Before I do anything else, I go to "Mode" to make sure the default "ALDL" is selected. I then go to 'OPTIONS" and change the RATE to "FAST". I back out of there, then go to CONFIGURE and make sure the Directory is correct (C:\Diacom-P).

I then back out of there, go to "LINK" and hit the ENTER key; I then get the "Linking to Vehicle", I believe it reads.

Now is when I make my dashboard connection using the 91006 cable. I insert the ignition key and start the engine. Links almost instantly now.

Just thought you'd want to know. Hope this helps.

Jake