So I'm pissed. I've had this huge ordeal with getting my desktop computer to run stable. I was almost certain that I had it pinned down to the motherboard, so I sent that back. I got the new one last night. I had to go to FedEx in Tempe to get it, since I missed the delivery guy. I stopped by Leslie's for board game night, since I was over there anyway. FYI girls (or guys too) Italians don't make beer. They make wine. Afterwards I stopped by to give Jenny her book back, ended up staying and talking for a while to chat. So, by the time I got home it was too late to start on what is the not so easy task of putting my computer back together.
And the task proved to be not so easy. Basically, everything has to be put together in exactly the right order, or else there's problems. It took me 3 times to get it right. After completing the install, I let it start up the previous install of win2k. I noticed that the network wasn't coming up, but didn't think too much of it. Then, I managed to crash it again, just by running winamp. So I restarted, and tried to figure out where the network was. I'm getting no link, no device in windows, but it is enabled in the bios. That's not good. I freeze it again. Decide I should try re-loading the os, and opt to try WinXP Pro to be different (previously was Win2k). Yeah, XP is worse. It freezes on startup, or just by bringing up the start menu. I notice one of the CD drives is acting funny, so I turn the computer off and unplug that drive, and now it won't turn back on. Yeah, I'm pretty much out of ideas now.
Update 20:10
So I figured out the network, there was something wrong with the BIOS, so reflashing fixed that. However, I have more proof that XP sucks, I can't even install the network drivers before it freezes up. I could at least do that in 2k.
Update 23:30
I noticed WinXP was doing many auto-reboots instead of hanging. I caught a glimpse of a BSOD as it restarted, so I decided to turn off the "feature" that auto restarts and doesn't show you the failure. This is how it reads: "The device driver got stuck in an infinite loop. This usually indicates problem with the device itself or with the device driver programming the hardware incorrectly." The particular device driver to which it is referring is for my video card. However, it's not even staying on long enough for me to even think about updating the driver (I tried). I'm going back to win2k to see if I can capture similar output. Either way, there's a dual-dvi out card with my name on it.
yoda say: evil is windows. to the dark side for long stray not. there is no try, only computer crash or computer crash not. what would happen, if, say, you crossed yoda and william shatner...? "dave........your father.....bill gates.....is not. you.....to him.....must....nasty emails.....send, or....forever will we....be...stuck....with this....system. scotty, fix....can....you?" (disclaimer: overactive imaginations can be hazardous to your health. read with caution.)
That disclaimer is like when you watch a movie and they tell you what it was rated after the credits. Like that information is somehow more relevent then than before you view it.
Its like the fine print at the very bottom of the release form you're asked to sign, or whatever.
Due to extreme circumstances, incidents of fire related to viewing of this or any other website hosted on typhoon shall be the sole responsibility of the viewer. May cause death, or certain sexual side effects. If you are pregnant, or know someone who is, you should not use typhoon. Drinking bananna juice while viewing sites hosted on typhoon has been linked to rapid hair loss.