en:docs:win16:api:kernel:fatalappexit

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
en:docs:win16:api:kernel:fatalappexit [2023/05/01 14:01] – created prokusheven:docs:win16:api:kernel:fatalappexit [2025/11/06 11:10] (current) – prokushev
Line 1: Line 1:
 {{page>en:templates:win16api}} {{page>en:templates:win16api}}
  
-======  ======+====== FatalAppExit ======
  
 ===== Brief ===== ===== Brief =====
 +
 +Display a message box and terminate the application when the message box is closed.
  
 ===== Syntax ===== ===== Syntax =====
 +
 +VOID WINAPI FatalAppExit(UINT uAction, LPCTSTR lpMessageText);
  
 ===== Parameters ===== ===== Parameters =====
 +
 +  * uAction
 +Reserved; must be zero.
 +  * lpMessageText
 +Points to a null-terminated string that is displayed in the message box. The message is displayed on a single line. To accommodate low-resolution screens, the string should be no more than 35 characters in length.
  
 ===== Return Code ===== ===== Return Code =====
 +
 +none
  
 ===== Notes ===== ===== Notes =====
 +
 +The FatalAppExit function displays a message box and terminates the application when the message box is closed. If Windows is running with a kernel debugger, the message box gives the user the opportunity to terminate the application or to cancel the message box and return to the application that called FatalAppExit.
 +
 +An application calls FatalAppExit only when it is not capable of terminating any other way. FatalAppExit may not always free an application's memory or close its files, and it may cause a general failure of Windows. An application that encounters an unexpected error should terminate by freeing all its memory and returning from its main message loop.
  
 ===== Example Code ===== ===== Example Code =====
Line 20: Line 35:
  
 ===== See also ===== ===== See also =====
 +
 +[[en:docs:win16:api:kernel:FatalExit]]
  
 {{page>en:templates:win16}} {{page>en:templates:win16}}