{"id":10807,"date":"2024-01-29T07:09:43","date_gmt":"2024-01-29T15:09:43","guid":{"rendered":"https:\/\/www.coretechnologies.com\/blog\/?p=10807"},"modified":"2024-01-29T07:09:43","modified_gmt":"2024-01-29T15:09:43","slug":"close-dialog-boxes-nircmd","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/alwaysup\/close-dialog-boxes-nircmd\/","title":{"rendered":"Q&A: Can AlwaysUp Close Dialog Boxes From My Application?"},"content":{"rendered":"
\"Can<\/div>\n
\n  We’re running a VB application as a service with AlwaysUp. Everything seems to be working except for in one situation.<\/p>\n

Can AlwaysUp detect when my program hangs with a dialog box waiting to press OK to continue? The application doesn’t work properly if the dialog stays open.<\/p>\n

I found NirCmd<\/a>, which can click buttons and send text to windows, but how do I use it with AlwaysUp?<\/p>\n

— Rose<\/p>\n<\/div>\n

Hi Rose.<\/p>\n

Unnecessary prompts are an enemy of 24\/7 operation.<\/p>\n

As you’ve seen, it can be very frustrating when a silly prompt holds up the action, waiting for you to click a button or hit the escape key!<\/p>\n

Fortunately AlwaysUp can quickly dismiss those intrusive prompts on your behalf — even when you are not around.<\/p>\n

Let’s dig into the details.<\/p>\n

\n

AlwaysUp automatically dismisses standard “application crashed” dialogs<\/h2>\n

When an application crashes, Windows may throw up a prompt to inform you of the problem. And you must acknowledge that prompt for the application to terminate.<\/p>\n

But what happens if you’re not there to dismiss the crash dialog? Nothing good, unfortunately.<\/p>\n

Until you dismiss the dialog, your application’s process will linger on in a “zombie” state — dead on its feet. You’ll see it in Task Manager but it will be completely unresponsive to network requests, file changes and any other operations that would normally trigger activity. And a lifeless program can cause problems for you and your team.<\/p>\n

We built AlwaysUp to dismiss those dialogs on your behalf — quickly and automatically. To illustrate, here are three of the prompts that AlwaysUp handles.<\/p>\n

Microsoft Visual C++ Runtime Library dialogs<\/h3>\n
\"Microsoft<\/a><\/div>\n

Windows shows the “Microsoft Visual C++ Runtime Library” dialog when your application causes a problem for the Visual C++ components<\/a>.<\/p>\n

AlwaysUp will automatically click the “OK” button for you.<\/p>\n

Visual Basic run-time dialogs<\/h3>\n
\"Visual<\/a><\/div>\n

A Visual Basic<\/a> application throws up this window when it runs into trouble.<\/p>\n

AlwaysUp will automatically click the “End” button to exit the application.<\/p>\n

Windows Error Reporting (Werfault.exe) dialogs<\/h3>\n
\"Windows<\/a><\/div>\n

Windows Error Reporting<\/a> shouts when your program crashes.<\/p>\n

AlwaysUp will automatically click the “Aceptar” (OK) button to close the window for you.<\/p>\n

\nSo AlwaysUp covers the standard Windows dialogs. But what about application-specific prompts? We’ll deal with those in the next section.\n<\/p>\n

\n

Plug in an automation to complete fields and click buttons in any dialog box<\/h2>\n

While it can handle the standard dialogs, AlwaysUp needs your help to dismiss application-specific dialogs. Indeed, without your guidance, AlwaysUp has no idea what to do when faced with an arbitrary prompt from your program!<\/p>\n

For example, suppose you’re running iTunes<\/a> as a service and it starts by showing this prompt:<\/p>\n

\"iTunes<\/a><\/div>\n

You must click the OK button to dismiss the window so that iTunes can proceed.<\/p>\n

But when you start iTunes as a Windows Service with AlwaysUp, it runs in the background on an invisible desktop. Because of that, you won’t be able to see or click the OK button and iTunes will hang — indefinitely.<\/p>\n

To overcome that problem, you’ll have to:<\/p>\n

    \n
  1. \n

    Create a Windows automation that clicks the OK button on the iTunes dialog;<\/p>\n<\/li>\n

  2. \n

    Instruct AlwaysUp to run that automation periodically.<\/p>\n<\/li>\n<\/ol>\n

    Creating an automation to dismiss a dialog with AutoIt<\/h3>\n

    We recommend using AutoIt<\/a> to create your automation. It’s popular, powerful and straightforward. For example, the AutoIt script to dismiss the iTunes dialog contains a single line of code:<\/p>\n

    \n; Sends the ESC key to dismiss any iTunes prompt.
    \nControlSend("iTunes", "", "", "{ESC}")\n<\/div>\n

    You can find more about using AutoIt with AlwaysUp here<\/a>.<\/p>\n

    But you don’t have to use AutoIt. You can choose any automation utility you like. And NirCmd is a fine choice. <\/p>\n

    Creating an automation to dismiss a dialog with NirCmd<\/h3>\n

    You use NirCmd to dismiss a dialog like this:<\/p>\n

    \nnircmd dlg [Process Name] [Window Title] [Action] [Parameters]<\/b><\/p>\n

    where:<\/p>\n

    Process Name<\/b>: Specifies the process that created the desired window. You can specify only the process name or the full path of the process. If this parameter is empty string (""), the command will be executed on any process.<\/p>\n

    Window Title<\/b>: Specifies the title of the window that you want to execute the action. If this parameter is empty string (""), the command will be executed on any window, regardless the window title.<\/p>\n

    Action<\/b>: You can specify one of the following options:<\/p>\n