Error: 'Client submitted invalid key': Difference between revisions
(Added Silicon Image work around.) |
mNo edit summary |
||
| Line 32: | Line 32: | ||
[[Category:Help - ASGS Issues]] | [[Category:Help - ASGS Issues]] | ||
[[Category:Tech Support]] | |||
Revision as of 22:40, 10 November 2007
This error comes up when the secret key ASGS created for your computer is invalid. It is usually encountered on a machine that cannot access the harddrive's SMART information.
If you have a Silicon Image RAID controller, there is a work around that has been confirmed to work on a few of their controllers.
Open up a command prompt (Start -> All Programs -> Accessories -> Command Prompt or Start -> Run -> cmd -> OK) and type in the following command:
verifier /flags 0x80 /driver scsiport.sys
Restart your computer after this command runs. ASGS should now be able to read SMART info from your RAID array (and so should any monitoring programs like SpeedFan). To disable this work around, type the following command at a command prompt:
verifier /reset
Technical Info
What the verifier command does is enable a monitor on the Silicon Image drive that monitors the DMA calls it makes.
Links : MSDN article on the command, and the one for the specific flag we are setting and the root article for the Driver Verifier.
Enabling the driver verifier somehow forces the SiL driver to properly transmit the SMART info. The downside to enabling this is that whenever your SiL driver does something bad with DMA, a BSoD will occur with bug check 0xE6 (DRIVER_VERIFIER_DMA_VIOLATION). This would be data corruption that otherwise will go unnoticed, so it may not be a bad thing after all. I am not aware of any performance difference with the verifier being enabled (other than the usual sub-par performance of SiL RAID compared to other solutions).
The solution has been tested to work on a SiL 3112A, 3114, 3512 and 0680A on Windows XP SP2. This solution DOES NOT work for Intel chipset RAID (a different driver file, but the chipset itself has broken SMART support). nVidia chipset based RAID reports SMART info correctly without any work arounds. Vista support is untested. However, the command does exist in the OS.
I don't have a RAID setup!
- If you recently upgraded your harddrive or harddrive controller, ensure SMART is enabled for your disk.
If you haven't changed your hardware configuration, or if you are getting this error the first time you've ever played Allegiance, the key will have to be validated by an FAO Administrator.
Send a private message to Tigereye, the community's head administrator and he will validate your key as soon as he is able.
If you do not get a response within 2 days, post a new topic in the Helpline forum with the title "Client submitted invalid key" and your account will be validated as soon as an administrator is available.