Message Explanation and/or corrective action Level
Registering Backdoor
MSG
The AppLock system communicates with the keyboard hook via a user defined message.
Both AppLock.exe and Kbdhook.dll register the message at initialization.
LOG_PROC-
ESSING
Registering Hotkey MSG
The AppLock system communicates with the keyboard hook via a user defined message.
Both Applock.exe and Kbdhook.dll register the message at initialization.
LOG_PROC-
ESSING
Registry read failure at
reenter user mode
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.
LOG_ERROR
Registry read failure at
reenter user mode
The registry has to be read when switching into user mode. This is because the admin-
istrator 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.
LOG_ERROR
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 available, AppLock cannot switch into user mode.
LOG_ERROR
Reset system work area
failure
The system work area is adjusted when in user mode to cover the taskbar area. The sys-
tem work area has to be adjusted to exclude the taskbar area in administration mode.
AppLock was unable to adjust this area.
LOG_ERROR
Shift pressed The Shift key has been pressed and trapped by the HotKey processing. LOG_EX
Shift Processing the hotkey and backdoor entry LOG_EX
Show taskbar The taskbar is now being made visible and enabled.
LOG_PROC-
ESSING
Switching to admin-back-
door
The system is currently in user mode and is now switching to admin mode. The switch
occurred because of the backdoor key presses were entered by the administrator.
LOG_PROC-
ESSING
Switching to admin-hot-
key press
The system is currently in user mode and is now switching to admin mode. The switch
occurred because of a hotkey press by the administrator.
LOG_PROC-
ESSING
Switching to admin-
kbdhook.dll not found
The keyboard hook load failed, so AppLock switches to admin mode. If a password is
specified, the password prompt is displayed and remains until a valid password is
entered.
LOG_PROC-
ESSING
Switching to admin-key-
board hook initialization
failure
If the keyboard hook initialization fails, AppLock switches to admin mode. If a password is
specified, the password prompt is displayed and remains until a valid password is
entered.
LOG_PROC-
ESSING
Switching to admin-reg-
istry read failure
See the explanation of the “Registry read failure” above. AppLock is switching into Admin
mode. If a password has been configured, the prompt will be displayed and will not be dis-
missed until a valid password is entered.
LOG_PROC-
ESSING
Switching to Task-
barScreenMode
In administration mode, the taskbar is visible and enabled. LOG_EX
Switching to user mode
The registry was successfully read and AppLock is starting the process to switch to user
mode.
LOG_PROC-
ESSING
Switching to user-hotkey
press
The system is currently in admin mode and is now switching to user mode. The switch
occurred because of a hotkey press by the administrator.
LOG_PROC-
ESSING
Taskbar hook failure
AppLock is unable to control the taskbar to prevent the locked application from re-ena-
bling it.
LOG_ERROR
Taskbar hook OK AppLock successfully installed control of the taskbar. LOG_EX
4-54
