Recovery from "AutoIt has encountered and error and needs to close"

[ZiggyStardust]

I have a script that will (by way of user interaction) generate the Windows standard "autoit has encountered a error and needs to close... send, don't send" and the program terminates.

Is there any way around this (other then shooting the user)? Utlimately what I would like to do is re-run the program if it crashes or better still keep this from happening.

Thanks!

[BrewManNH]

without seeing the script, there's no way to answer this.

[ZiggyStardust]

I can tell you what triggers it. I do I/O to a virtual COMPort (USB). If I pull the USB cable out of the computer while the script is running it generates the Windows crash.

"autoit.exe has encountered a problem and needs to close. We are sorry about the inconvenience". Since this is a Windows Error is there any way I can control it?

[water]

What BrewManNH meant is: We need some AutoIt code to see how you do it and if there is anything we can do about the problem.

[Melba23]

ZiggyStardust,

You are already have a thread open on this subject - why have you started another?

And you know what the end result will be if you keep on doing this.

M23

[ZiggyStardust]

Here is the lowest level I/O I do:

Func CommSend($SendStr)

$Received = ""

_CommSendString($SendStr & @CR, 0)

If @error <> 0 Then

$CommError = True

WriteLog("Error sending " & $Sendstr)

Return

EndIf

$Received = _CommGetLine(">", 100, 2000); Should get back speed

If @error <> 0 Then

$CommError = True

WriteLog("Error receiving " & $Received)

Return

EndIf

$Received = StringStripWS($Received, 8) ; Strip Carriage Returns

EndFunc

[czardas]

I presume the errors are documented in the UDF. Try and catch them and see if you can throw an exception just before it crashes.

[water]

Do you compile the script for 32 bit? The UDF states that "the dll is 32 bit so it will not work with a 64 bit app"

[ZiggyStardust]

Just thinking out loud. Since this exception can't be handled would anyone see a problem with running yet a second script which would do nothing more than make sure the first script was running. If the second script crashed with the exception the first script would simply re-run the second script.

I know from experience that, as a rule, when you get one of these exception errors you might as well reboot because nothing is going to work right. Any other input on how I can handle this?

[water]

Which version of AutoIt do you use? The latest beta has a changed way of handling COM errors - a crash should never again occur caused by a COM error if you handle @error properly.

[ZiggyStardust]

3.3.8.1? How do you tell for sure? I am a little fuzzy about what is classified as a "COM" error. I tried putting in a COM Error Handler yesterday and unplugging the USB cable. It blew right past the COM Error Handler and crashed. You really think the beta would catch this unhandled exception error and let me recover from it?

Google has failed me! What is the definition of a "COM Error". I am especially curious as to what the COM stands for. All I can find is that it is a generic term for a Windows crash.....

Edited July 23, 2012 by ZiggyStardust

[water]

If the COM error handler doesn't catch the error situation then I'm out of ideas

[ZiggyStardust]

Thanks Water. Per your suggestion I installed Beta 3.9.4.0 and there was even a COM Error Handler test. The test ran and caught the COM Error. I put the Error Handler in my script and it blew right past it and crashed.

I am out of things to try. I left a post on the CommMG UDF thread. Maybe a suggestion will turn up. Your suggestions and input were greatly appreciated!

[water]

When the script crashes even when using a COM error handler and the latest beta then COM isn't used by the UDF or is used in a way so that AutoIt can't handle the error (I'm no specialist in this area - that's how I understand it).

I hope you get some answer on the CommMg thread.