Honeywell MX7 Tecton User Manual page 135

Message Explanation and/or corrective action
Opened status file The status information is being saved to a file and the file has been opened suc-
cessfully.
Out of memory for en- Not enough memory to encrypt the password.
crypted pwd
pRealTaskbarWnd- The taskbar control has already been installed.
Proc already set
Pwd cancelled or inval- The password prompt was cancelled by the user or the maximum number of
id-remain in user mode failed attempts to enter a password was exceeded.
Read registry error-hot The hotkey registry entry is missing or empty. This is not considered an error.
key The keyboard hook uses an embedded default if the value is not set in the reg-
istry.
Read registry failure- AppName registry value does not exist or is empty. This constitutes a failure for
app name switching into user mode.
Read registry failure- AppCommandLine registry entry is missing or empty. This is not considered an
Cmd Line error since command line information is not necessary to launch and lock the
application.
Read registry failure- The Internet registry entry is missing or empty. This is not considered an error
Internet since the Internet value is not necessary to launch and lock the application.
Registering Backdoor The AppLock system communicates with the keyboard hook via a user defined
MSG message. Both AppLock.exe and Kbdhook.dll register the message at initial-
ization.
Registering Hotkey The AppLock system communicates with the keyboard hook via a user defined
MSG message. Both Applock.exe and Kbdhook.dll register the message at initializa-
tion.
Registry read failure at The registry has to be read when entering user mode is the AppName is miss-
reenter user mode ing. This user mode entry is attempted at boot and after a hotkey switch when
the administrator has closed the application being locked or has changed the
application name or command line.
Registry read failure at The registry has to be read when switching into user mode. This is because the
reenter user mode administrator can change the settings during administration mode. The read of
the registry failed which means the Administration key was not found or the Ap-
pName value was missing or empty.
Registry read failure The registry read failed. The registry information read when this message is
logged is the application information. It the Administration key cannot be
opened or if the AppName value is missing or empty, this error is logged. The
other application information is not required. If the AppName value is not avail-
able, AppLock cannot switch into user mode.
Reset system work The system work area is adjusted when in user mode to cover the taskbar area.
area failure The system work area has to be adjusted to exclude the taskbar area in admin-
istration 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- The system is currently in user mode and is now switching to admin mode. The
backdoor switch occurred because of the backdoor key presses were entered by the ad-
ministrator.
Switching to admin- The system is currently in user mode and is now switching to admin mode. The
hotkey press switch occurred because of a hotkey press by the administrator.
Switching to admin-kb- The keyboard hook load failed, so AppLock switches to admin mode. If a pass-
dhook.dll not found word is specified, the password prompt is displayed and remains until a valid
password is entered.
Switching to admin- If the keyboard hook initialization fails, AppLock switches to admin mode. If a
keyboard hook initial- password is specified, the password prompt is displayed and remains until a
ization failure valid password is entered.
Level
LOG_EX
LOG_ERROR
LOG_EX
LOG_EX
LOG_ERROR
LOG_ERROR
LOG_ERROR
LOG_ERROR
LOG_PROCESSING
LOG_PROCESSING
LOG_ERROR
LOG_ERROR
LOG_ERROR
LOG_ERROR
LOG_EX
LOG_EX
LOG_PROCESSING
LOG_PROCESSING
LOG_PROCESSING
LOG_PROCESSING
LOG_PROCESSING
129