I don't know if I am going crazy, but really struggling to find a SATA match for this board.

Same controller 9446 on both boards.

Done many in the past with no issues from a 2060-771961-001 to a 2060-771960.

Used a chip reader but can't recall if these older drives prefer moving via terminal.

To be fair, I haven't inspected the MCU numbers to make sure of the match but this hasn't been an issue before.

The behaviour of the board with swapped Rom code is that drive does not spin and all registers are lit. The old USB board still works and the drive spins but the drive has a heads/slow responding issue.

Before I switch to the old reading method using PC3k or swapping Roms physically, has anyone come across this or have any pointers, please?

Thanks

Louis

Are the register lights bright or dim ? Did you check the donor was functional before overwriting the rom? Do you have another donor a 39 or 59 handy you can test with?

_________________
Data Recovery Services in the UK.
https://www.usbrecovery.co.uk/

Thanks for the reply and pointers.

Registers Bright (normal)

I had tried another 960 from my box and that was the same and both of these were from recent cases that did work.

I also did try a 59 or was it a 39, but it didn't match up on the screw holes exactly but the result was the same, so will check that again.

I'll also go and pick one up a few more 960 from my shelf just in case from working drives to see.

Will post back once I figure it out.

Do the SDRAMs have the same capacity?

Are the MCU revs the same? The revision code consists of two letters, eg C0.

http://www.hddoracle.com/viewtopic.php?f=59&t=205&p=14552#p18576

_________________
A backup a day keeps DR away.

Thanks for reply Fzabkar, yes, same C0 on all the ones I've tried.

I traced back to the original ACE forum post and once I get back to my desk I'll do the classic terminal ROM swap. I suspect it will work.

Well, there you have it. Rom swap via terminal did the trick.

Will need to compare the dumps, but
the ROM read / write with chip reader must corrupt the ROM and cause the pcb to not start up. I even tried to write back the saved U12 from the chip reader back via terminal to Sata board but result was same.

Using classic method worked fine.

Nothing wrong ROM reader, I just used it to convert a Spyglass to Sata unlock board.

Data recovery is a funny game.

I have written a tool to verify the ROM contents:

http://www.users.on.net/~fzabkar/FreeBasic_W32/WD/wdROMv17.exe
http://www.users.on.net/~fzabkar/FreeBasic_W32/WD/wdROMv17.bas

_________________
A backup a day keeps DR away.