SUCCESS repair Maxtor ATHENA POKER with PC3000 v.14(cracking)

[sej4ti]

To : Master (Almazz) and lighting

hello Almaz and lighting, hello all of big-forum family

I was succsess repair Maxtor 2b020H1 WAK21R90 S/N B1HNLH9E KMBA,
using PC3000V.14 (crack), with knowledge where I get from this forum.,
BRAFO big-forum and thank for all,

but I have one problem, after i turn off computer, and turn again ....the disk become athena again, so I need help from Master Almazz and lighting, or from all big-forum family, what solution for this......


Thank you very much

[allfun]

I think u did not follow the correct procedure .
Tell me what u did to the drive ?
I will tell u what wrong did u do .

[phoerien]

I think u did not follow the correct procedure .
Tell me what u did to the drive ?
I will tell u what wrong did u do .

hi, master

do you have good procedure to run it

[sej4ti]

- I use HD on Primary master c:\pc3000 (ONE PARTION)
- the LDR and RAM I copy at c:\pc3000 too
- Athena poker on Secondary (position on safe mode)

I turn on computer and type SHELL so (F11)
I select Maxtor ==>> Poker
On start menu I select LDR-file loading and select file xxx.ldr (success)
I select Re-read drive ID (disk ID look 2B020H1 WAK21R90) so
I select standart menu.
I select disk firmware zone and select work with memory buffers and write memory buffers and select xxx.ram (success)
I select disk firmware zone again and select work with SA and select Modules repairing (all of command successed e.g: repair P-List,repair G-list)
I select disk firmware zone again, select work with SA and select Spindle Stop
and the last step, I exit and F12 enter
and exit so CTRL+ALT+DEL (my computers restart)

THANK'S ALLFUN for your replay

[allfun]

Wrong procedure .
You dont need to write RAM .
Put hdd in safe mode .
Load appropriate LDR.
Do a Structure test .
Check for bad modules and rewrite them.
Your hdd will be OK .

[sej4ti]

thank you allfun
good procedure

Thank you very much

[phoerien]

good job
big-forum is the best

[Lightning]

This was a simple case : probably a typical g-list or p-list overflow / header corrupted. Did you recover ALL the data and was the drive stable ?
It's when the going gets tough that things get more complicated.