Joel, thanks for your reply.
It is the weirdest thing I have ever seen, we get an error back on READ that should never happen on read: a WRITE error. Only thing I can think of the is the disks firmware being corrupt causing it to fetch the wrong error return
Corrupt firmware... Man, I say Murphy's law. Whatever you do, it'll still find a way to get you. I'll check up on the BIOS and see if I should reflash the original firmware.
Do you remember how many BLOCKS DiskPatch skipped, how many read errors during pass 1?
I'm sorry, I can't remember . I did not take any photos of the screen during Pass 1.
I doubt iRecover would work as the screen dump was taken after iRecover finished 100% of the full pass. Though it was not with the retries at 0 and timeouts at 200ms.
I'm calling it a day. It has been exhausting, channeling all my spare time on this for a week. Maybe I'll stick to Western Digital in the future. I would like to thank you and Tom for the time and help you've put into this, though futile. A saving grace would be that this is a first you've seen? It's really exceptional to be able to speak directly to the developers of a software, and if anyone asks, this is the place I'll recommend.
I hope you will be able to give me a refund on DP. I'll forward you the invoice by email. After all this, I'm going to invest in a couple of harddisk coolers. http://www.titan-cd.com/2009_WEB/product/showProhdd_en.asp?ProID=230
Three fans and a heatsink, better be enough...
Thanks and best wishes.