
AppLock Error Messages
Any messages whose first word is an ‘ing’ word is output prior to the action described in the message. For example, “Switching
to admin-hotkey press” is logged after the administrator has pressed the hotkey but prior to starting the switch process.
For all operations that can result in an error, an Error level message is displayed when a failure occurs. These messages
contain the word “failure”. These messages have a partner Extended level message that is logged which contains the word
“OK” if the action completed successfully rather than with an error.
For processing level messages, “Enter…” is logged at the beginning of the function specified in the message and “Exit…” is
logged at the end (just before the return) of the function specified in the message.
Message
Explanation and/or corrective action
Level
Error reading hotkey
The hotkey is read but not required by AppLock.
LOG_EX
Error reading hotkey;
using default
A hotkey is required. If there is a failure reading the hotkey, the internal factory default is
used.
LOG_ERROR
App Command Line=
<Command line>
Command line of the application being locked
LOG_PROC-
ESSING
App= <Application
name>
Name of the application being locked
LOG_PROC-
ESSING
dwProcessID= <#>
Device ID of the application being locked
LOG_EX
Encrypt exported key len
<#>
Size of encrypt export key
LOG_EX
Encrypt password
length= <#>
The length of the encrypted password.
LOG_EX
Encrypted data len <#>
Length of the encrypted password
LOG_EX
hProcess= <#>
Handle of the application being locked
LOG_EX
Key pressed = <#>
A key has been pressed and trapped by the hotkey processing.
LOG_EX
*****************
The status information is being saved to a file and the file has been opened successfully.
LOG_EX
Address of keyboard
hook procedure failure
AppLock found the kbdhook.dll, but was unable to get the address of the initialization pro-
cedure. For some reason the dll is corrupted. Look in the \Windows directory for
kbdhook.dll. If it exists, delete it. Also delete AppLock.exe from the \Windows directory and
reboot the unit. Deleting AppLock.exe triggers the AppLock system to reload.
LOG_ERROR
Address of keyboard
hook procedure OK
AppLock successfully retrieved the address of the keyboard filter initialization procedure.
LOG_EX
Alt pressed
The Alt key has been pressed and trapped by the HotKey processing.
LOG_EX
Alt
Processing the hotkey and backdoor entry
LOG_EX
Application handle
search failure
The application being locked did not complete initialization.
LOG_ERROR
Application handle
search OK
The application initialized itself successfully
LOG_ERROR
Application load failure
The application could not be launched by AppLock; the application could not be found or
is corrupted.
LOG_ERROR
Backdoor message
received
The backdoor keys have been pressed. The backdoor hotkeys provide a method for cus-
tomer service to get a user back into their system without editing the registry or reloading
the device.
LOG_PROC-
ESSING
3-46
Summary of Contents for THOR VM1
Page 17: ...Components Front View 1 Power Button 2 Speakers 3 Ambient Light Sensor 4 Microphone 1 3 ...
Page 43: ...IBM 3270 Overlay 2 25 ...
Page 162: ...Hat Encoding 3 100 ...
Page 163: ...3 101 ...
Page 175: ...About This tab displays information on the Gobi 2000 radio installed in the Thor VM1 3 113 ...
Page 179: ...3 117 ...
Page 199: ...Enter user name password and domain to be used when logging into network resources 3 137 ...
Page 206: ...3 144 ...
Page 220: ...3 158 ...
Page 228: ...4 8 ...
Page 301: ...Click the Request a certificate link Click on the advanced certificate request link 6 45 ...
Page 302: ...Click on the Create and submit a request to this CA link 6 46 ...
Page 312: ...7 4 ...
Page 318: ... Shift 9 Shift 0 8 6 ...