I've got a dead 750G Barracuda built in late '07 for my HP desktop. My issue seems exactly like the busy error. The only thing is, I was not home when this occurred, I came home to the system frozen on the boot screen with HP logo, it never could POST due to the hard drive. Although my CD-ROM is first in the boot order it wouldn't boot from a CD, it would still freeze on the BIOS startup. I couldn't get into BIOS, run setup, or anything else until I removed the hard drive, and now I can get into BIOS etc. and boot from a cd. I never saw any error messages though, which makes me wonder if I really have the BSY problem. Everything else fits the bill though. My question is, do you have to see the error to know it is the BUSY problem? I had a generic Nokia CA-42 with working drivers... I can pass the loopback test connecting with three different wires. I know I know, this is deprecated, but I just figured I'd try while waiting on a proper cable which I plan to order tonight. I am struggling through trying to find the right wires since two of three will pass the loopback test and either could be RX/TX. I am on my on there I know. My question is, when you connect to the TTL of the PCB, should you see whatever you type or should the screen be blank until you hit Cntrl-Z? Depending on which wire I connect, I can see everything I type except the Cntrl-Z. Cntrl-Z does nothing. Should I be able to see everything else? If I order the USB to TTL does it come with a diagram stating which wire is which, similar to the way the SERIAL to TTL circuit has them printed on the board? Gosh I wish HP and Seagate would just treat us fairly and repair the problem. I'm giving it 1 more week before I start searching for someone willing to unbrick this thing for a reasonable price. Thanks!