Post a screenshot.
Printable View
Post a screenshot.
never done that, what is the easiest way to do it, thanks
See post #10 here: Hosting-an-Image
The registry setting that the latest installer uses to figure out if an old version of the software exists is:
\\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Cu rrentVersion\App Paths\EFILive_Tune.exe
Attachment 14202
It then looks at the version number of the exe that the registry key points to, which will usually be either:
\Program Files\EFILive\V7.5\EFILive_Tune.exe (on Windows 32 bit systems)
or
\Program Files (x86)\EFILive\V7.5\EFILive_Tune.exe (on Windows 64 bit systems)
It then looks inside the *.exe file(s) and to determine their version numbers. And based on the version number it finds it may complain that an old version exists and should be uninstalled first.
It will only do that once, because after you've installed the latest version all future updates can be installed over the top of the existing install without uninstalling first.
Either way, if you delete the folder(s) referenced by the three registry keys, then the new installer should not complain that an old version of the software exists.
i.e.
\Program Files\EFILive\V7.5
\Program Files\EFILive\V8
or
\Program Files (x86)\EFILive\V7.5
\Program Files(x86)\EFILive\V8
Regards
Paul
I finally got it done, thanks for all the help, john
Hi Guys, Any help at all?? I have read this whole forum. Tried uninstalling/ re installing on 2 laptops now. one windows 7 and a windows 8. I have deleted the regedit and still no luck. Same issue on both laptops. all updates done in V8 as well. Sorry if this is not in the right section.
Error report generated by EFILive at 20:23:33 on Jul 31, 2013
Error code: ERR_WIN 0/0
Cannot open file "C:\Windows\system32\config\systemprofile\Document s\EFILive\V7.5\User Configuration\calc_pids.txt". The system cannot find the file specified
EFILive Version: 7.5.7 (Build 235)
Platform: Windows NT
Version: 6.1 (build 7600)
Processor type: Pentium 1296MHz
Directories
Temporary Cache: C:\Windows\system32\config\systemprofile\Documents \EFILive\V7.5\Temporary cache
Logged Data: C:\Windows\system32\config\systemprofile\Documents \EFILive\V7.5\Logged data
Customers: C:\Windows\system32\config\systemprofile\Documents \EFILive\V7.5\Customers
Configuration: C:\Program Files (x86)\EFILive\V7.5\Configuration
Exported Data: C:\Windows\system32\config\systemprofile\Documents \EFILive\V7.5\Exported data
Images: C:\Windows\system32\config\systemprofile\Documents \EFILive\V7.5\Images
Sounds: C:\Windows\system32\config\systemprofile\Documents \EFILive\V7.5\Sounds
Maps: C:\Windows\system32\config\systemprofile\Documents \EFILive\V7.5\Maps
Pids: C:\Windows\system32\config\systemprofile\Documents \EFILive\V7.5\PIDs
Virtual Dash: C:\Windows\system32\config\systemprofile\Documents \EFILive\V7.5\VDash
Print Reports: C:\Windows\system32\config\systemprofile\Documents \EFILive\V7.5\Print reports
Bug Reports: C:\Windows\system32\config\systemprofile\Documents \EFILive\V7.5\Bug reports
Connected: No
Auto connect: No
Scan OBDII info: No
Error retries: 1
Retry delay: 10
Message throttle: 0
Most recently used VIN: 1G1xxxxxxxxxxxxxx (Note: 1)
PCM information
Unknown: Unknown
Unknown: Unknown
Unknown: Unknown
Unknown: Unknown
Unknown: Unknown
Unknown: Unknown
Unknown: Unknown
Unknown: Unknown
Unknown: Unknown
Unknown: Unknown
Unknown: Unknown
Unknown: Unknown
Stream-Slow scan mode: Unknown
Stream-Fast scan mode: Unknown
Maximum dynamic packets: Unknown
Most recent communication with vehicle:
Report ID: 175530 (Note: 2)
Notes:
(1) The VIN sequence number is not required for this report and for your privacy it is NOT included in this report.
(2)The report ID is a checksum of the report text and is used to verify the integrity of the report.
Hi RM,
in the scantool do this:Quote:
Originally Posted by Rick Martin
Edit->Properties->Folders and look carefully at the field for User Configuration... it should be identical to the path preceding calc_pids.txt in that error message...
click Browse and browse to that same path and click Ok;
if the path is identical (you browsed to it and set it), then check that your Windows login account has privileges to access (read/write) files/directories located within system directories.
Actually, look at the spelling of " \Document s\ " vs "\Documents \"
( see the position of the space before vs after the "s" )
Quote:
Originally Posted by Rick Martin
I think those spaces are just an artifact of copy/paste between EFILive's error report screen and the forum. I'm not sure why it happens.Quote:
Originally Posted by joecar
See image below for an example.
Attachment 15618
Regards
Paul
ah, ok... ( I thought I was onto something :) )