Honeywell Thor VM2 User Manual page 290

Message
Hot key pressed
Hot key set event failure
Hotkey press message re-
ceived
In app hook:WM_SIZE
In app hook:WM_WIN-
DOWPOSCHANGED
Initializing keyboard hook
procedure
Keyboard hook initialization
failure
Keyboard hook loaded OK The keyboard hook dll exists and loaded successfully.
L after Ctrl
Loading keyboard hook
Open failure
Open registry failure
Opened status file
Out of memory for encrypt-
ed pwd
pRealTaskbarWndProc al-
ready set
Pwd cancelled or invalid-
remain in user mode
Read registry error-hot key The hotkey registry entry is missing or empty. This is not considered an error.
Read registry failure-app
name
Read registry failure-Cmd
Line
Read registry failure-Inter-
net
Registering Backdoor MSG The AppLock system communicates with the keyboard hook via a user defined
Registering Hotkey MSG
Registry read failure at re-
enter user mode
10 - 12
Explanation and/or corrective action
Processing the hotkey and backdoor entry
When the administrator changes the hotkey configuration the hotkey controller
must be notified. This notification failed.
The user just pressed the configured hotkey.
In addition to preventing the locked application from exiting, AppLock must also
prevent the application from enabling the taskbar and resizing the application's
window. This message traps a change in the window size and corrects it.
In addition to preventing the locked application from exiting, AppLock must also
prevent the application from enabling the taskbar and resizing the application's
window. This message traps a change in the window position and corrects it.
AppLock is calling the keyboard hook initialization.
The keyboard filter initialization failed.
Processing the backdoor entry.
When AppLock first loads, it loads a dll that contains the keyboard hook process-
ing. 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 be-
cause 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 suc-
cessfully.
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 keyboard hook uses an embedded default if the value is not set in the reg-
istry.
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 ap-
plication.
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.
message. Both AppLock.exe and Kbdhook.dll register the message at initializa-
tion.
The AppLock system communicates with the keyboard hook via a user defined
message. Both Applock.exe and Kbdhook.dll register the message at initializa-
tion.
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 appli-
cation name or command line.
Level
LOG_EX
LOG_ERROR
LOG_
PROCESSING
LOG_EX
LOG_EX
LOG_
PROCESSING
LOG_ERROR
LOG_EX
LOG_EX
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