Message

Explanation and/or corrective action

Level

 

 

 

Switching to admin-

See the explanation of the “Registry read failure” above. AppLock is switching

LOG_PROCESSING

registry read failure

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.

 

 

 

 

Switching to Taskbar-

In administration mode, the taskbar is visible and enabled.

LOG_EX

ScreenMode

 

 

 

 

 

Switching to user

The registry was successfully read and AppLock is starting the process to

LOG_PROCESSING

mode

switch to user mode.

 

 

 

 

Switching to user-hot-

The system is currently in admin mode and is now switching to user mode. The

LOG_PROCESSING

key press

switch occurred because of a hotkey press by the administrator.

 

 

 

 

Taskbar hook failure

AppLock is unable to control the taskbar to prevent the locked application from

LOG_ERROR

 

re-enabling it.

 

 

 

 

Taskbar hook OK

AppLock successfully installed control of the taskbar.

LOG_EX

 

 

 

Timeout looking for

After the application is launched, AppLock must wait until the application has

LOG_ERROR

app window

initialized itself before proceeding. The application did not start successfully

 

 

and AppLock has timed out.

 

 

 

 

ToUser after admin,

The user mode switch is attempted when the device boots and after the admin-

LOG_EX

not at boot

istrator presses the hotkey. The mode switch is being attempted after a hotkey

 

 

press.

 

 

 

 

ToUser after admin-

The switch to user mode is being made via a hotkey press and the administra-

LOG_EX

app still open

tor has left the application open and has not made any changes in the configu-

 

 

ration.

 

 

 

 

ToUser after admin-no

If user mode is being entered via a hotkey press, the administrator may have

LOG_EX

app or cmd line

left the configured application open. If so, AppLock does not launch the appli-

 

change

cation again unless a new application or command line has been specified; oth-

 

 

erwise, it just locks it.

 

 

 

 

Unable to move desk-

The desktop is moved when switching into user mode. This prevents them from

LOG_ERROR

top

being visible if the application is exited and restarted by the timer. This error

 

 

does not affect the screen mode switch; processing continues.

 

 

 

 

Unable to move task-

The taskbar is moved when switching into user mode. This prevents them from

LOG_ERROR

bar

being visible if the application is exited and restarted by the timer. This error

 

 

does not affect the screen mode switch; processing continues.

 

 

 

 

Unhook taskbar wnd-

AppLock could not remove its control of the taskbar. This error does not affect

LOG_ERROR

proc failure

AppLock processing

 

 

 

 

Unhook wndproc fail-

AppLock could not remove the hook that allows monitoring of the application.

LOG_ERROR

ure

 

 

 

 

 

Unhooking taskbar

In administration mode, the taskbar should return to normal operation, so Ap-

LOG_EX

 

pLock’s control of the taskbar should be removed.

 

 

 

 

Unhooking wndproc

When the administrator leaves user mode, the device is fully operational; there-

LOG_EX

 

fore, AppLock must stop monitoring the locked application.

 

 

 

 

WM_SIZE adjusted

This message denotes that AppLock has readjusted the window size.

LOG_EX

 

 

 

X after Ctrl+L

Processing the backdoor entry.

LOG_EX

 

 

 

Ret from password

Return value from password dialog.

LOG_EX

<#>

 

 

 

 

 

Decrypt data len <#>

Length of decrypted password.

LOG_EX

 

 

 

Window handle to

The window handle that is passed to the enumeration function. This message

LOG_EX

enumwindows=%x

can be used by engineering with other development tools to trouble shoot ap-

 

 

plication lock failures.

 

 

 

 

WM_WINDOW-

Output the window size after it has been adjusted by AppLock

LOG_EX

POSCHG adjust-

 

 

ed=%x

 

 

 

 

 

6 - 18