Difference between revisions of "Aladdin DiagnostiX"
From ATTWiki
Line 2: | Line 2: | ||
We use this software for when our software cannot access the key or returns unexpected errors. This software was written by Aladdin developers. If it cannot read the key, then the issues are deeper than our software, and we report this to Aladdin directly. | We use this software for when our software cannot access the key or returns unexpected errors. This software was written by Aladdin developers. If it cannot read the key, then the issues are deeper than our software, and we report this to Aladdin directly. | ||
+ | |||
+ | ==INSTALLATION== | ||
Line 19: | Line 21: | ||
The Key Access History log should show information. If there is a failure, then information will be red. | The Key Access History log should show information. If there is a failure, then information will be red. | ||
+ | |||
+ | ==SAVING MEMORY REPORTS== | ||
+ | |||
+ | By checking the "Save memory to reports file (encrypted)" feature, you can save extended data to an encrypted "memory.xml" file. We can read this file for in-depth analysis of the information in the key. (No one else can.) | ||
--[[User:Mcone|Mcone]] 14:23, 3 August 2007 (EDT) | --[[User:Mcone|Mcone]] 14:23, 3 August 2007 (EDT) |
Revision as of 18:27, 3 August 2007
We use this software for when our software cannot access the key or returns unexpected errors. This software was written by Aladdin developers. If it cannot read the key, then the issues are deeper than our software, and we report this to Aladdin directly.
INSTALLATION
This is a link to that program: http://www.advancedtubular.com/key/Aladdin_Diagnostics.zip
- Please download that file.
- Open the file
- Unzip and run the aksdiag32_setup.exe file.
- Copy the two DLL files into the C:\Program Files\Aladdin\DiagnostiX folder (in the same folder as the diagnostix.exe file).
- Please determine which kind of key you have before running the diagnostix.exe program. Look for letters YQGMB or IGBXA. If you have YQGMB, then rename the custom_time.dll to custom.dll. If you have the IGBXA, then rename the other one to custom.dll.
- Run the diagnostix.exe program.
- Select the HASP icon in the treeview
- Select the Use customized file radio button
- Press Check Key
The Key Access History log should show information. If there is a failure, then information will be red.
SAVING MEMORY REPORTS
By checking the "Save memory to reports file (encrypted)" feature, you can save extended data to an encrypted "memory.xml" file. We can read this file for in-depth analysis of the information in the key. (No one else can.)
--Mcone 14:23, 3 August 2007 (EDT)