Service Forum

[g]

I have gotten two false positives in EraseOn.

(The first one was pretty exciting as I thought it had found the password!)

I am scanning for the User Password on a SATA drive, not ASCII mode -- EraseOn identified the password as AARAARA and proceeded to unlock the drive -- but unfortunately neither KeyOn nor my T60p's BIOS recognized this as the password...
In a re-scan w/ the same dict file -- no passwords were identified.

Just now EraseOn "found" AAAAAAA as the password (different dict file -- I am trying a new set of permutations) -- but same results -- KeyOn, BIOS, and EraseOn (w/ a seconds try) do not acknowledge this.

Is this an indication of something? Should I be changing any settings?

[victor]

Sorry for the late reply.

The problem here is your IDE2SATA bridge. Seems like is having a drop from time to time.

I will explain shortly the process:
EraseON, after sending the Secure_Erase command for the given password, waits for the drive to acknowledge (or not) this command. The drive acks only if the password doesn't match, if the passowrd is correct, it will begin the erase process at once and and all requests are nacked (drive is bussy).

Now, if your adapter slows down in this process, EraseON eratically may reports a match, just because the drive is not responding in a given time.

To compensate the gap you have to open eraseon.ini and increase:
DRDY_Timeout=2500

If errors still happen, increase by 500 again.

DRDY- Drive Ready flag represents the cycles counted waiting for the drive to ACK.

Another thing, the erase process should take about 30 minutes or more depending on the drive size. If you see EraseON reporting a match, but the following erase process stops after a short while, then is clear a false alarm.
The reason, as I said, could be the IDE2SATA convertor, which may not support such speeds.


BTW, you may email us anytime to our support@, I could give you a faster reply and support for any problem encountered.
_________________
Victor Voinea
ALLservice HQ, Romania.