mod 28 selftest, arco for Mantis_RE

[pikus_09]

Hello everyone, I need a module 28, which contains the procedure for ARCO, selftest. For family Mantis_RE. I am writing about this because if you have a module it just you helped rescue my drive WD2002FAEX-007BA0. thank's for all.

[pikus_09]

I won the script. Problem solved.

[helpless]

Hi, pikus_09,
May I also win the script? Thanks.

[Moltke]

a strange script.why double step 4Ah (HOT) in the calibrator ?

[pikus_09]

a strange script.why double step 4Ah (HOT) in the calibrator ?

I don't no, I received the script, I changed it only as DCM, DCM my drive.
what's more in that script, unfortunately, does not operate Test C3 format select command error and end the procedure. Do you understand me?

You won it !

http://www.hddoracle.com/viewtopic.php?f=3&t=1395

Lol But this script not work for me, i don't no how.

Hi, pikus_09,
May I also win the script? Thanks.

Sure, it can work with you, with me he did not want.

[helpless]

Thank you Spildit.

a strange script.why double step 4Ah (HOT) in the calibrator ?

I won the script. Problem solved.

Sure, it can work with you, with me he did not want.

I don't get it: how can a strange and not working script solve the problem? The problem must have been something else.

[pikus_09]

You see, my friend, my drive belongs to the family Mantis_PL_RE and the obtained script was to drive family Mantis_RE (DragonFLY4_RE) and is a fundamental difference. Do you understand?

[pikus_09]

I have a correct script mod28 for my Mantis_PL_RE. . Problem solved.

[pikus_09]

works TPI callibrated and adjusted, Touch down, RW GAP calibrated, now goes test VDT HEAD QUAL 5 head testing. WORKS, WORKS, Am very happy, my mantis WD2002FAEX will begin to works fine Juhu:twisted: case closed.

[pikus_09]

Case cloused, because my black
ARCO procedure correctly goes, I'm after tests 6A, 6F, Zone TPI HeadQual, everything went without errors, mod 0C was filled with set values as more mod 03 has the correct value, as so far everything is OK.

So this error was caused by a problem FW and bad entries in the ROM. Everything works fine.