That noise you heard? The faint sound of thumping that kept you awake last night? Yeah, sorry. That was me putting a dent in my desk with my forehead.
In the ongoing battle to get my computer working properly, you see, the computer is winning. The bright spot – if you want to call it that – is that I have probably pinpointed the culprit. On a reboot late yesterday afternoon the system refused to properly boot. This has been a recurring theme lately, and I had presumed that this was a potential problem with my Asus motherboard’s BIOS, as I had read some people were having trouble getting a Serial ATA RAID array to work reliably. I don’t run a RAID array (at the moment, anyway), but being that it’s SATA-related I figured there were probably some compatibility issues with the (still relatively new) SATA standard. Flashing my BIOS caused some other problems though so I went back to the original BIOS until I read up more about it.
Last night though, it wouldn’t boot back up. No matter how I cajoled, fiddled or cursed, whether normal or safe mode or directory services restore mode or debug mode, it just. would. not. boot. It would get so far, and then would start accessing the hard drive in perpetuity to apparently no useful end. I even let it run for half an hour or so, on the off chance that it was running some kind of scandisk operation that just happened not to have any screen output to tell me it was doing so. (Hey, Windows has surprised me with its oddities before) But I got fed up when it just wasn’t getting anywhere.
So, I stick in the WinXP disk, boot from it, force a HAL mode (owing to its odd inability to properly detect that I have a dual core processor) and perform a repair install. While it dutifully copied all the relevant files and rebooted properly to begin the repair process, it flatly refused to actually boot into that process. It just kept getting stuck in a spontaneous reboot cycle.
Several hours later I hang up the boxing gloves and install a fresh copy of XP on a different partition. It was about at this point, too, that I noticed the beginnings of a faint, high-pitched noise coming from the hard drive, the sort a slightly worn bearing would make when it’s spinning at 7200RPM, or a metal cutting blade on an angle grinder might make when it’s just grazing a piece of PVC pipe. Understand that this is a 500GB SATA-300 drive I bought about a year ago and paid $500 for (which I can now get for under $200). I’m naturally rather upset. But at least now I am pretty confident that this is what’s been causing most of the problems all along, and the drive does have a 5 year warranty, so that’s another thing I’m going to have to RMA. Meanwhile I’ve got to call my local computer store and see if they’ve got a 500GB SATA-300 drive in stock so I can buy one this weekend and ghost everything from the old drive on to the new one before I RMA it.
So, now my home computer is running on a bare minimum compliment of software. (No point installing more than necessary since I plan to be up on a new drive and the old Windows this weekend)
I can’t believe the horrible luck I’ve had with this latest upgrade, though. So far, that makes one hard drive, one power supply and two 1GB sticks of RAM I’ve had to RMA in the past two months. This is not including the ($750) video card that died last summer, nor the mouse whose receiver I stupidly killed last week. I think in less than a year I’ve spent about $2000 just replacing supposedly top-quality components that just crapped right the hell out. Just where the hell has all the QC gone? It’s like “you get what you pay for” needs to be updated to say “No matter what you pay for it, it’s still going to be crap.”
Frustration, thy name is technology.