cww.blog!

Well, I don't really want to kill the salesman. He was really just a happy, completely socially uncomfortable nerd.

Anyway, the motherboard in my desktop computer exploded yesterday, so I bought a new one. I also got a new processor, a new video card, new RAM, a new hard drive, and even the new 64-bit Windows XP (because 64 bits are better than 32 in processors and operating systems!). It's all very shiny.

There's a problem, though. When I'm trying to install the new Windows, I get these errors five or six times during the copy process that say a file got corrupted during the copy, and would I like to try again? Well, sure, I say, and it does its thing. The file copying completes, it goes into graphical install mode, and sure enough, within five minutes, there's a blue screen. I've seen it happen with a variety of reasons now, too. cdfs? ntfs? irql? If it's a four-letter acronym, I've seen it in a blue screen in the past 24 hours.

This could be a hard drive problem, I thought, because I sort of dropped the drive when the bi^H^Hwoman at Fry's was checking my receipt on the way out the door and didn't give me enough time to adjust my fingers in the bags before she snatched one out of my hand. So, I bought a different drive today. No dice. Same thing happens with the new one.

My next guess is the motherboard. Sigh.

Just to make sure it's not the new 64-bit Windows, though, I'm going to try installing the old Windows XP on it. Just in case.

It'll be a super-neat system if it ever works. I'll even get to play EverQuest II with Taylor on it.

Quick stats on the new box:
- AMD Athlon 3000+ 64-bit.
- ATI Xtasy 256MB.
- Maxtor 80GB Serial ATA.
- Abit AN8.
- Kingston 2x512MB PC3200 400MHz.

That's all the news that's fit to print.