OK this has happened a couple times to me now -
I am using EFILive 7.5.100, and upon closing the Tuning tool I get two back-to-back error windows saying error 1400, Invalid Window Handle.
Mr. P.
OK this has happened a couple times to me now -
I am using EFILive 7.5.100, and upon closing the Tuning tool I get two back-to-back error windows saying error 1400, Invalid Window Handle.
Mr. P.
I had that error yesterday too.
The PC crashed afterward, I thought it was a Windows issue.
512k RoadRunner Firmware 12.14R
FlashScan V2 Bootblock V2.07.04 Firmware V2.07.22 EFILive V7.5.7 (Build 191) V8.2.1 (Build 181)
LC-1 WBO2
_________________________________________________
Its been happening to me since build 99, I havent upgraded to 100 yet because of time constraints.
W7 Ult x64
~Erik~
2013 Sonic RS Manual - 1.4L I4T E78, tuned, turbo mods, etc.
2008 TrailBlazer SS 3SS AWD Summit White - LS2 E67/T42, bolt ons, suspension, etc.
2002 Chevy TrailBlazer LT 4X4 Summit White - 4.2L I6 P10, lifted, wheels, etc.
I've seen it too, but I can't reproduce it reliably yet :(
If anyone can generate a sequence of steps that will cause it to happen consistently please let me know.
Paul
Before asking for help, please read this.
I think the Scan tool and Tune tool have to be open at the same time - i.e. open the tune tool and load a log file, then open the scan tool and establish the cross-window data linking, then close the tune tool. In my case I have one instance of the Scan tool running and 3 instances of the Tune tool open, and when I closed the Tune tool it got all pissed-off...
Also got an Invalid Floating Point Operation trying to manipulate the 3D chart display with the right mouse button in {B3647}.
Before asking for help, please read this.
Before asking for help, please read this.
After the auto update it still shows build 100,
is this OK?
512k RoadRunner Firmware 12.14R
FlashScan V2 Bootblock V2.07.04 Firmware V2.07.22 EFILive V7.5.7 (Build 191) V8.2.1 (Build 181)
LC-1 WBO2
_________________________________________________
Mine shows 101...
but in the last few days I have been thru several uninstalls and registry entry deletions (in my attempt to define a particular bug, mentioned above).