Honeywell MX3PLUS Reference Manual page 91

Message
Keyboard hook loaded OK
The keyboard hook dll exists and loaded successfully.
L after Ctrl Processing the backdoor entry.
When AppLock first loads, it loads a dll that contains the keyboard hook processing. This message is logged
Loading keyboard hook
prior to the load attempt.
The status information is being saved to a file and the file open has failed. This could occur if the file is write pro-
Open failure
tected. If the file does not exist, it is created.
If the Administration registry key does not exist, the switch to user mode fails because the AppName value in
Open registry failure
the Administration key is not available.
Opened status file The status information is being saved to a file and the file has been opened successfully.
Out of memory for
Not enough memory to encrypt the password.
encrypted pwd
pRealTaskbarWndProc
The taskbar control has already been installed.
already set
Pwd cancelled or invalid- The password prompt was cancelled by the user or the maximum number of failed attempts to enter a pass-
remain in user mode word was exceeded.
Read registry error-hot The hotkey registry entry is missing or empty. This is not considered an error. The keyboard hook uses an
key embedded default if the value is not set in the registry.
Read registry failure-app
AppName registry value does not exist or is empty. This constitutes a failure for switching into user mode.
name
Read registry failure-Cmd AppCommandLine registry entry is missing or empty. This is not considered an error since command line infor-
Line mation is not necessary to launch and lock the application.
Read registry failure-Inter- The Internet registry entry is missing or empty. This is not considered an error since the Internet value is not
net necessary to launch and lock the application.
Registering Backdoor The AppLock system communicates with the keyboard hook via a user defined message. Both AppLock.exe
MSG and Kbdhook.dll register the message at initialization.
The AppLock system communicates with the keyboard hook via a user defined message. Both Applock.exe
Registering Hotkey MSG
and Kbdhook.dll register the message at initialization.
The registry has to be read when entering user mode is the AppName is missing. This user mode entry is
Registry read failure at
attempted at boot and after a hotkey switch when the administrator has closed the application being locked or
reenter user mode
has changed the application name or command line.
The registry has to be read when switching into user mode. This is because the administrator can change the
Registry read failure at
settings during administration mode. The read of the registry failed which means the Administration key was
reenter user mode
not found or the AppName value was missing or empty.
The registry read failed. The registry information read when this message is logged is the application infor-
mation. It the Administration key cannot be opened or if the AppName value is missing or empty, this error is
Registry read failure
logged. The other application information is not required. If the AppName value is not available, AppLock can-
not switch into user mode.
Reset system work area The system work area is adjusted when in user mode to cover the taskbar area. The system work area has to
failure be adjusted to exclude the taskbar area in administration mode. AppLock was unable to adjust this area.
Shift pressed The Shift key has been pressed and trapped by the HotKey processing.
Shift Processing the hotkey and backdoor entry
Show taskbar The taskbar is now being made visible and enabled.
Switching to admin-back- The system is currently in user mode and is now switching to admin mode. The switch occurred because of the
door backdoor key presses were entered by the administrator.
Switching to admin-hotkey The system is currently in user mode and is now switching to admin mode. The switch occurred because of a
press hotkey press by the administrator.
Explanation and/or corrective action Level
LOG_EX
LOG_EX
LOG_PROC-
ESSING
LOG_ERROR
LOG_ERROR
LOG_EX
LOG_ERROR
LOG_EX
LOG_EX
LOG_ERROR
LOG_ERROR
LOG_ERROR
LOG_ERROR
LOG_PROC-
ESSING
LOG_PROC-
ESSING
LOG_ERROR
LOG_ERROR
LOG_ERROR
LOG_ERROR
LOG_EX
LOG_EX
LOG_PROC-
ESSING
LOG_PROC-
ESSING
LOG_PROC-
ESSING
4-49