PC-3000 Forum

This happens randomly and I haven't found any pattern as to when or why. It only happens when writing WD ROM (seemingly all families) from within utility (not using BootRom method). It's becoming a real PITA.
Anyone else experiencing this?

Ive never seen this (yet!). After writing, does the PCB being written to start OK or no power?

Forgot to mention, after this happens and repower drive, I just get a dim green busy light. Only solution is using BootRom to re-write ROM (or unsolder, manually write rom in ROM reader device).

I've just got this fault verifying fault on a 2060-800022-001 REV P1. This is the SATA version of SpyGlass. I only have one, and it has been used successfully in previous recoveries. However, now if I write by ATA and BootRom COM port the ROM contents is corrupted. When I read back the written ROM and compare (in WinHex) it with the original I can see that there are significant differences.

Did you ever work out what was causing the issue?

I suspect that the PCB has a fault. In every other way the PCB works OK! It means that I have to write the ROM using an external reader, or on a different PCB, then physically transfer to this PCB. A 'PITA' for certain - must find another matching PCB for comparison testing.

Regards.
J

I thought it may be due to 32bit windows. Hasn't happened since upgrading computer (which included an OS upgrade to windows 10 64bit; from Windows 7 32bit).

Are you sure you're writing to a PCB with the same size ROM chip? Sometimes in the numbers after the dash or the REV there could be a change in the size of the ROM. Doesn't effect many models, but there are some where different sizes are used.