WD1600AABS firmware

[kal2005]

Hi everybody
I'm a beginner with pc3000 and I have WD1600AABS DATE : 09 DEC 2007 THAILAND Sata with burn board I changed the board with other and tried to write firmware with something close to the date of production I got eeror that it can't write .
Should I put the drive in safemode and if so how I do this which jumbers ???
Should I use kernal Mode in the software???
If the firmware i'm going to write is from harddisk not the same of production date what problems would happen????
Pls help me Thank you in advance

[harddrivespecialist]

There is very good explaination in a PC3000 manual for such proceedures.

[kal2005]

thank you for your replay
could you give more help pls and show me how??

[beto]

well that model if im not wrong ROM (Adaptive´s info) its inside MCU, so its not possible to change PCB, without special equipment, and the knowledgment the tools not are the only wich u need

Regards

[kal2005]

Dear beto
what special equipment needed , I need to write the firmware of this hard on other PCB using PC3000
thank you in advance

[pcimage]

You need PC3000 UDMA, or Salvation Tools.

Both costs $1,000's

If you don't want to spend $1,000's then you need a pro (with these tools) to do it for you.

Any decent honest pro shouldn't charge a lot for this procedure.

End of story, no otherway. Sorry

[scratchy]

Hi everybody
I'm a beginner with pc3000 and I have WD1600AABS DATE : 09 DEC 2007 THAILAND Sata with burn board I changed the board with other and tried to write firmware with something close to the date of production I got eeror that it can't write .
Should I put the drive in safemode and if so how I do this which jumbers ???
Should I use kernal Mode in the software???
If the firmware i'm going to write is from harddisk not the same of production date what problems would happen????
Pls help me Thank you in advance

It is lucky that the drive did not allow you to write the modules, it may have detected it was the wrong revision.

Trying to write the firmware on a drive with a damaged board is not a good idea. There are many modules that are unique to the drive.. Best thing is to study the section of the PC3000 manual and practive until you know exactly what you are doing. There is even a solution to the problem you have in there and generally it does not involve re-writing firmware..