How to continue running script if .exe program fails

[sjwnih111]

I have a Perl script that calls an .exe program, but the .exe program sometimes fails. When failing, the .exe opens up a dialog that prompts the user to click "ok." When the user clicks "ok," the perl script resumes, moving on to the next piece of data that it is supposed to send to the .exe file. I would like to automatically select ok, so that, even without a user, the Perl script can continue to run if the .exe file crashes. Is this possible? I was wondering if it would be possible to just set a timer, so that if the .exe program runs for longer than 10 minutes, the perl script would kill it--whether it gives the pop-up or not (would it also kill it if it gave a pop-up?)\ Thanks again.

[dasgar]

I'm assuming that the reference to "an .exe program" and your description of what I call a pop up window would indicate that you're on a Windows system. Is that correct?

If so, the answer to your question is yes. Here's how I would approach this task:

• start a new thread that will do the task of calling the .exe program
• have a while loop checking to see if the thread is joinable
  • check to see if the pop up window exists
  • if the pop up window exists, automate the response
• join the thread
• repeat the above steps for any subsequent .exe calls

For the window automation, you can use Win32::GuiTest. It will have functions that will help you find the pop window and to interact with it (mouse clicks, keystrokes). My recommendation would be to use keystrokes rather than mouse clicks with the Win32::GuiTest stuff.

Another alternative to the Win32::GuiTest would be to use AutoIt. In that case, you would create an AutoIt script and then either call that script from your Perl code or make your AutoIt script an .exe program and call that from your Perl code.

Personally, I would recommend sticking with Win32::GuiTest rather than using AutoIt. However, you might find it useful to get AutoIt for its AutoIt Window Info Tool, which can be used to get information about the windows that you are trying to automate.

[Anonymous Monk]

Try  use Win32API::File(); Win32API::File::SetErrorMode(2); https://metacpan.org/module/Win32API::File#SetErrorMode is SetErrorMode function (Windows)

[zork42]

However, you might find it useful to get AutoIt for its AutoIt Window Info Tool, which can be used to get information about the windows that you are trying to automate.

I use http://www.catch22.net/software/winspy-17 to find the info I need (normally the Window Class, and the Window's title).
(Or you might already have the Spy++ utility that ships with Microsoft Visual Studio.)

Then you call Win32::GuiTest's FindWindowLike() to get a handle to the window. Then you can manipulate the window.