Honeywell MX9 Reference Manual page 97

Microsoft windows embedded ce 5 operating system
Hide thumbs Also See for MX9:
Table of Contents

Advertisement

Message
Registry read failure at
reenter user mode
Registry read failure at
reenter user mode
Registry read failure
Reset system work area
failure
Shift pressed
Shift
Show taskbar
Switching to admin-
backdoor
Switching to admin-
hotkey press
Switching to admin-
kbdhook.dll not found
Switching to admin-
keyboard hook
initialization failure
Switching to admin-
registry read failure
Switching to
TaskbarScreenMode
Switching to user mode
Switching to user-hotkey
press
Taskbar hook failure
Taskbar hook OK
Timeout looking for app
window
ToUser after admin, not
at boot
Explanation and/or corrective action
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.
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.
The system work area is adjusted when in user mode to cover the taskbar area. The
system work area has to be adjusted to exclude the taskbar area in administration mode.
AppLock was unable to adjust this area.
The Shift key has been pressed and trapped by the HotKey processing.
Processing the hotkey and backdoor entry
The taskbar is now being made visible and enabled.
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.
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.
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.
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.
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
dismissed until a valid password is entered.
In administration mode, the taskbar is visible and enabled.
The registry was successfully read and AppLock is starting the process to switch to user
mode.
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.
AppLock is unable to control the taskbar to prevent the locked application from re-
enabling it.
AppLock successfully installed control of the taskbar.
After the application is launched, AppLock must wait until the application has initialized
itself before proceeding. The application did not start successfully and AppLock has timed
out.
The user mode switch is attempted when the device boots and after the administrator
presses the hotkey. The mode switch is being attempted after a hotkey press.
Level
LOG_ERROR
LOG_ERROR
LOG_ERROR
LOG_ERROR
LOG_EX
LOG_EX
LOG_
PROCESSING
LOG_
PROCESSING
LOG_
PROCESSING
LOG_
PROCESSING
LOG_
PROCESSING
LOG_
PROCESSING
LOG_EX
LOG_
PROCESSING
LOG_
PROCESSING
LOG_ERROR
LOG_EX
LOG_ERROR
LOG_EX
4-53

Advertisement

Table of Contents
loading

Table of Contents