PDA

View Full Version : Err 1400, Invalid Window Handle



Mr. P.
December 18th, 2009, 07:20 PM
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.

mr.prick
December 19th, 2009, 03:43 AM
I had that error yesterday too.
The PC crashed afterward, I thought it was a Windows issue. :nixweiss:

ScarabEpic22
December 19th, 2009, 05:54 AM
Its been happening to me since build 99, I havent upgraded to 100 yet because of time constraints.

W7 Ult x64

Blacky
December 19th, 2009, 08:13 AM
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

Mr. P.
December 20th, 2009, 05:18 AM
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...

Mr. P.
December 20th, 2009, 06:08 AM
Also got an Invalid Floating Point Operation trying to manipulate the 3D chart display with the right mouse button in {B3647}.

Blacky
December 20th, 2009, 08:37 AM
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...
Thanks, I'll check it out.
Paul

Blacky
December 20th, 2009, 08:38 AM
Also got an Invalid Floating Point Operation trying to manipulate the 3D chart display with the right mouse button in {B3647}.

I'm about to post up a new version (later today) that fixes the Invalid Floating Point error. Its a bug caused by incorrect magnification settings on the 3D surface.

Regards
Paul

mr.prick
December 20th, 2009, 09:16 AM
After the auto update it still shows build 100,
is this OK?

joecar
December 20th, 2009, 09:42 AM
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).

Blacky
December 20th, 2009, 10:05 AM
I haven't posted 101 publicly yet.
I'm just cleaning up a few glitches and I'll post it later today.
Paul

joecar
December 20th, 2009, 02:12 PM
Ooops... I got ahead of myself...