Losing PIDs when opening log file

[white01ss]

Running 7.5.4. Build 65 on a work machine (never been hooked up to the scan tool). When I open my log it flashes the scanned PIDs then goes down to a subset of two or three of them and I can't see the data for the PIDs that disappeared. It never did this on the 7.4 version. What is heck is going on?

[white01ss]

Is anybody out there? Has anyone else seen this before? I'm running the risk of being 100% productive at work. That just wouldn't be right.

[joecar]

We can't have any of that...

Uncheck the Supported box on the PIDs tab.

Does it still display all the pids on the Data tab...?

Post your log files.

[white01ss]

Thanks for the reply. The supported button is unchecked. It doesn't have a problem selecting PIDs when starting from an empty document. The problem only occurs when loading an existing log file. It briefly flashes the actual PIDs that were recorded then after the progress bar pop-up completes it's reduced down to 1 or 2 of the PIDs. It's really bizarre.

It doesn't do this on the laptop I use in the car, only on a computer that is 20 miles away. Is there some file that I can transfer from the laptop to the work computer to make it think it's been connected to the car and act properly? Registry entries?

It acts like it's masking PIDs based on the type of car your connecting too, but it shouldn't ever do that if you're just reading a log file. What if I want to read a log from another car?

[Tordne]

I just opened your log with the same software version and had no issue at all. Can you perhaps post a screenshot? Or send it to support@efiluve.com.

[joecar]

I opened it too and it has no problem (see attached... do these look anything like what you see...?).

[white01ss]

Thanks for checking this out. Are you guys loading it on a machine that's been hooked up to the EFI hardware? Here's a few screen captures of the same log file being loaded. I don't know if it matters, but my desktop machine here at work is running Windows Server 2003.

[joecar]

Re-enter your VIN/OS and controller (PCM) type.

[white01ss]

Re-enter your VIN/OS and controller (PCM) type.

Did that, but still not working. Being the easy going person that I am, I copied the user data and program files folders from the working laptop this morning and compared them to my work machine. Found some file differences and then made them match, but still no dice.

So I look in the registry and there is all kinds of stuff in there so I saved off a copy. I then completely uninstalled it blowing away all of EFILive's registry and files. Reinstalled, filled in all the license stuff again and it started working.

Attached is a copy of my old registry entries and a copy of the new one. There are many differences so maybe someone can debug it and find out what the problem was during the 7.4 to 7.5 update process.


Dan