NPA_System_Alert
Allows a CDM or HAM to display hardware or software alert messages to the console screen and/or the system error log from the current thread (or a separate thread) without providing the console's screen handle.
LONG NPA_System_Alert ( LONG npaHandle, BYTE *controlString, LONG alertMask, LONG targetNotifyMask, LONG alertID, LONG alertClass, LONG alertSeverity, LONG parameterCount, args... );
Value |
Description |
---|---|
0x00000002 |
NOTIFY_EVERYONE_BIT |
0x00000004 |
NOTIFY_ERROR_LOG_BIT |
0x00000008 |
NOTIFY_CONSOLE_BIT |
This field is usually set to NOTIFY_CONSOLE_BIT.
(IN) Alert number where the upper word equals the Novell assigned module ID and the lower word equals a driver-defined unique alert number.
IMPORTANT:If a valid unique number is passed in, the ALERT_ID_VALID_MASK bit must be set in the alertMask field.
This function accepts up to four additional arguments.
The following table lists return values and descriptions.
One purpose of NPA_System_Alert is to provide CDMs and HAMs with a method of displaying alert messages on the server console screen or directing those messages to the system error log (or both). In NetWare 6.x, the console screen is the screen from which the driver was loaded, not the Logger screen.
Another purpose of NPA_System_Alert is to provide a mechanism to display alerts on the console screen without the need for a specific screen handle. The only time that a CDM or HAM has access to a valid console screen handle is during a call to HAM_Load, the load-time initialization function, or during a call to HAM_Unload_Check, the unload check function. The handles passed to these two functions should not be saved. They are only valid during the context of the respective functions.
Because displaying strings requires a significant amount of time, it might be necessary during time-critical areas to have NPA_System_Alert display the alert on a separate thread (other than the thread that called the function) by queuing the alert message.