SeaTools

[davexnet]

Hello allo,

ran the SMART check in version 12.01 of Seatools for Windows against my Barracuda .  It detected error # A9A9DE4A

an advised me to run the Satools for DOS and do a complete scan.

I created the CD image; it boots OK, but the (PS/2) mouse is frozen in the middle of screen and I'm unable

to proceed.

Does anybody have any info on the SMART error and/or the mouse problem.

TIA,

Dave

EDIT I just ran HDDscan from http://hddscan.com/ and it reports a SMART error of ULTRADMA CRC errors.

Message Edited by davexnet on 01-28-2010 12:04 PM

[fzabkar]

AIUI, the failing test is encoded as the digit "4" in your error code. I don't know which test this is, though.

About SeaTools Test Codes:

http://seagate.com/ww/v/index.jsp?locale=en-US&name=wvc&vgnextoid=573797f40cce3210VgnVCM1000001a48090aRCRD

"SeaTools Test Codes are based on the type of test that failed and the product serial number. No two codes are the same. The online RMA submission system will use the SeaTools Test Code number to help process the exchange of your product. The code tells Seagate that the drive is, in fact, bad and that there is virtually no chance that a good drive is being returned."

I don't know why your mouse is frozen. Does SeaTools still respond to the keyboard?

Can you upload the HDDScan results to a file sharing site?

Message Edited by fzabkar on 29-01-2010 10:47 AM

[davexnet]

Thanks for the info.  I'm running the extended, offline, SMART report now in HDDscan.  If there's any further info, I'll put it in here.

The quick SMART display shows ultraDMA crc errors with a count of 8.

I did have an SATA cable problem about 6 months ago.   Perhaps I'll keep an eye on it and watch the count.

When I start Seatools DOS, the keyboard is active.  It seems to be technically possible to run it without the mouse

but it's extremely cumbersome.

I also send an email to Seagate support, so I'll be interested to see what they say.

Message Edited by davexnet on 01-29-2010 12:45 PM

Message Edited by davexnet on 01-29-2010 12:45 PM

[fzabkar]

Seatools for DOS is based on FreeDOS. The version I downloaded uses the CuteMouse driver, CTMOUSE.EXE.

If you exit SeaTools, you might like to try some command line options for the mouse driver.

For example, the following lines will uninstall the driver and then reinstall it by forcing PS/2 mouse mode.

CTMOUSE /U
CTMOUSE /P

Then launch SeaTools again by typing SEATOOLS.

Type CTMOUSE /? for online help.

Here is the list of command line options:

http://www.users.on.net/~fzabkar/SeaTools/ctmouse.txt

[davexnet]

Thanks very much for that info - my version also uses CTMOUSE.

I'll give it a try.

[fzabkar]

I don't how far you want to investigate your mouse problem, but here is the home page for the CuteMouse open source project:

http://cutemouse.sourceforge.net/

"CuteMouse has three branches now. V1.9 branch uses BIOS to handle PS/2 mice. V2.0 branch uses direct hardware access for PS/2 mice, and supports the wheel. V2.1 branch uses BIOS to handle PS/2 mice but also supports the wheel, combining the best of V1.9 and V2.0. "

My version is v2.0 alpha 4, which uses direct hardware access.

Perhaps V2.1, with access via BIOS, would be a better option for you?

[davexnet]

I'd like to get it to work, I ran Seatools for DOS yesterday without the mouse; it's certainly possible.

I ran the long test on the drive in question, no errors were found.

However, Seatools for Windows still identifies the SMART error and gives me an error code.

I may look into the CTmouse thing, I'd have to recreate  the disk image, but I must admi, it would

be nice to have a version that worked straight  off without having to fuss with it.