Honeywell Thor VM2 User Manual page 291

Vehicle-mount computer with microsoft windows embedded ce 6.0
Hide thumbs Also See for Thor VM2:
Table of Contents

Advertisement

Message
Registry read failure at re-
enter user mode
Registry read failure
Reset system work area
failure
Shift pressed
Shift
Show taskbar
Switching to admin-back-
door
Switching to admin-hotkey
press
Switching to admin-kbd-
hook.dll not found
Switching to admin-key-
board hook initialization
failure
Switching to admin-registry
read failure
Switching to Taskbar-
ScreenMode
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
ToUser after admin-app
still open
ToUser after admin-no app
or cmd line change
Unable to move desktop
Explanation and/or corrective action
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 Ap-
pName 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 ap-
plication information is not required. If the AppName value is not available, Ap-
pLock 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 admin-
istration 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 ad-
ministrator.
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 pass-
word 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 val-
id 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 dis-
played 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 ini-
tialized 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 admin-
istrator presses the hotkey. The mode switch is being attempted after a hotkey
press.
The switch to user mode is being made via a hotkey press and the administrator
has left the application open and has not made any changes in the configuration.
If user mode is being entered via a hotkey press, the administrator may have left
the configured application open. If so, AppLock does not launch the application
again unless a new application or command line has been specified; otherwise,
it just locks it.
The desktop is moved when switching into user mode. This prevents them from
being visible if the application is exited and restarted by the timer. This error
does not affect the screen mode switch; processing continues.
Level
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
LOG_EX
LOG_EX
LOG_ERROR
10 - 13

Advertisement

Table of Contents
loading

Table of Contents