Honeywell MX9 User Manual page 159

Message
Loading keyboard hook
Open failure
Open registry failure
Opened status file
Out of memory for encrypted pwd
pRealTaskbarWndProc already set
Pwd cancelled or invalid-remain in user
mode
Read registry error-hot key
Read registry failure-app name
Read registry failure-Cmd Line
Read registry failure-Internet
Registering Backdoor MSG
Registering Hotkey MSG
Registry read failure at reenter user mode
Registry read failure at reenter user mode
Explanation and/or corrective action
When AppLock first loads, it loads a dll that contains
the keyboard hook processing. This message is
logged 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 protected. 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 the Administration key is not available.
The status information is being saved to a file and
the file has been opened successfully.
Not enough memory to encrypt the password.
The taskbar control has already been installed.
The password prompt was cancelled by the user or
the maximum number of failed attempts to enter a
password was exceeded.
The hotkey registry entry is missing or empty. This
is not considered an error. The keyboard hook uses
an embedded default if the value is not set in the
registry.
AppName registry value does not exist or is empty.
This constitutes a failure for switching into user
mode.
AppCommandLine registry entry is missing or
empty. This is not considered an error since
command line information is not necessary to
launch and lock the application.
The Internet registry entry is missing or empty. This
is not considered an error since the Internet value is
not necessary to launch and lock the application.
The AppLock system communicates with the
keyboard hook via a user defined message. Both
AppLock.exe and Kbdhook.dll register the message
at initialization.
The AppLock system communicates with the
keyboard hook via a user defined message. Both
Applock.exe 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 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.
The registry has to be read when switching into user
mode. This is because the administrator can
change the settings during administration mode.
The read of the registry failed which means the
Administration key was not found or the AppName
value was missing or empty.
Level
LOG_PROCESSING
LOG_ERROR
LOG_ERROR
LOG_EX
LOG_ERROR
LOG_EX
LOG_EX
LOG_ERROR
LOG_ERROR
LOG_ERROR
LOG_ERROR
LOG_PROCESSING
LOG_PROCESSING
LOG_ERROR
LOG_ERROR
6 - 17