Known issues with the March 2016 Pre-Release

Printable View

March 22nd, 2016
Blacky

Known issues with the March 2016 Pre-Release
Currently known issues and possible workarounds for the March 2016 Pre-Release of the EFILive Software and Firmware

Download the March 2016 pre-release here: https://forum.efilive.com/showthread...ve-Pre-Release
Download the public stable-release here: http://www.efilive.com/latest/cat/download-efilive

Pre-release software versions:
- Software: V7.5.7.303
- Software: V8.2.2.294
- FlashScan/AutoCal firmware: V2.07.97
Issue 1:
If you are Black Box Logging PIDs from an ECM and TCM simultaneously and you have selected a PID from the transmission controller (TCM) that has an identically named PID in the engine controller (ECM), then when the log file is loaded back into the V8 software for viewing, that TCM PID will be displayed as if it originated from the ECM. The PID's data will have correctly been logged from the TCM, only its name will appear to indicate that it was logged from the ECM.
Workaround:
None.
It is a restriction of the *.efi (V7.5 log file format). That restriction will be removed and the TCM PIDs will display their true origin once the V8 scan tool software is available.

Issue 2:
When logging DMA PIDs (i.e. PIDs whose names end with "_M" or "_DMA"), if the ignition is switched off for an extended period while data logging but data logging is not terminated, then when the ignition is switched on again the data log automatically continues. However the DMA PIDs may no longer return valid data.
Workaround:
EFILive recommends stopping the data log and restarting the data log when switching off the ignition for extended periods.

Issue 3:
"Invalid floating point" error when opening E78 OS 12654014 tune files.
Workaround:
Download 12654014.calz and save it into the folder: C:\Program Files (x86)\EFILive\V7.5\Calibrations\E78, overwrite the existing file.
March 23rd, 2016
Road

I don't know if the issue is on me or EFI but when I download 7.5 or 8 I get a error: The signature of this program is corrupt or invalid. And find no way around the error to install it.... Thanks

Never mind it's me. If it happens to you go to your downloads and right click the download and select run anyways.
March 23rd, 2016
Blacky

Quote:

Originally Posted by Road

I don't know if the issue is on me or EFI but when I download 7.5 or 8 I get a error: The signature of this program is corrupt or invalid. And find no way around the error to install it.... Thanks

Never mind it's me. If it happens to you go to your downloads and right click the download and select run anyways.

Which version of windows are you using?

I highly recommend downloading the files again. If you attempt to install a file with a damaged/faulty signature then you may be installing a compromised version of EFILive that may contain malware, virus, trojans or just plain corrupted. The whole reason we digitally sign the EFILive installation files is to detect any modifications whether malicious or accidental to the downloaded files while they are en-route from EFILive to your PC.

If the signature is not correct DO NOT INSTALL the software. Re-download it and try again.

Regards
Paul
March 23rd, 2016
Road

I was windows 7. I downloaded it 3 times and got the same error everytime. It was different type than the normal one that windows 10 gives. I will re-download it and see what happens.
March 23rd, 2016
Road

1 Attachment(s)

Just downloaded it on my windows 10 computer and getting the same message.
March 23rd, 2016
Blacky

After some investigation, turns out Microsoft have brought forward their deprecation of SHA-1 certificates and, as of Jan 1, 2016 require installers to be signed with SHA-256 certificates.
https://www.globalsign.com/en/blog/m...igning-policy/

EFILive will need to re-issue the downloads with a SHA-256 certificate. We'll do that asap.

Regards
Paul
March 23rd, 2016
ScarabEpic22

Quote:

Originally Posted by Blacky

After some investigation, turns out Microsoft have brought forward their deprecation of SHA-1 certificates and, as of Jan 1, 2016 require installers to be signed with SHA-256 certificates.
https://www.globalsign.com/en/blog/m...igning-policy/

EFILive will need to re-issue the downloads with a SHA-256 certificate. We'll do that asap.

Regards
Paul

Ah yes, found this out at work last week. Had to update all the servers with SHA256 certs as we were using SHA1. Now I know there's an actual reason we did it!