12.07.2015 Views

HX2 Reference Guide - Delfi

HX2 Reference Guide - Delfi

HX2 Reference Guide - Delfi

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

AppLock Error MessagesAppLock Error MessagesAny messages whose first word is an ‘ing’ word is output prior to the action described in the message. For example, “Switchingto 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 messagescontain 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…” islogged at the end (just before the return) of the function specified in the message.Message Explanation and/or corrective action LevelError reading hotkey The hotkey is read but not required by AppLock. LOG_EXError reading hotkey;using defaultApp Command Line=App= A hotkey is required. If there is a failure reading the hotkey, the internal factory default isused.Command line of the application being lockedName of the application being lockedLOG_ERRORLOG_PROCESSINGLOG_PROCESSINGdwProcessID= Device ID of the application being locked LOG_EXEncrypt exported key lenEncrypt passwordlength= Size of encrypt export keyThe length of the encrypted password.LOG_EXLOG_EXEncrypted data len Length of the encrypted password LOG_EXhProcess= Handle of the application being locked LOG_EXKey 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_EXAddress of keyboardhook procedure failureAddress of keyboardhook procedure OKAppLock found the kbdhook.dll, but was unable to get the address of the initializationprocedure. For some reason the dll is corrupted. Look in the \Windows directory forkbdhook.dll. If it exists, delete it. Also delete AppLock.exe from the \Windows directory andreboot the unit. Deleting AppLock.exe triggers the AppLock system to reload.AppLock successfully retrieved the address of the keyboard filter initialization procedure.LOG_ERRORLOG_EXAlt pressed The Alt key has been pressed and trapped by the HotKey processing. LOG_EXAlt Processing the hotkey and backdoor entry LOG_EXApplication handlesearch failureApplication handlesearch OKApplication load failureBackdoor messagereceivedCannot find kbdhook.dllThe application being locked did not complete initialization.The application initialized itself successfullyThe application could not be launched by AppLock; the application could not be found oris corrupted.The backdoor keys have been pressed. The backdoor hotkeys provide a method forcustomer service to get a user back into their system without editing the registry orreloading the device.The load of the keyboard filter failed. This occurs when the dll is missing or is corrupted.Look in the \Windows directory for kbdhook.dll. If it exists, delete it. Also deleteLOG_ERRORLOG_ERRORLOG_ERRORLOG_PROCESSINGLOG_ERRORE-EQ-<strong>HX2</strong>RG-M [ 266 ] <strong>HX2</strong> <strong>Reference</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!