Slashdot Mirror

I keep a WinXP install around to play Civ4. Yes, I could do something in VirtualBox, but the installation's already there, the game's there, why bother?

Anyway, what I did (making the very big and probably incorrect assumption that you're not playing games that use the network) is removed all the network services (I was not familiar with the process for doing this before, but found a very handy guide here). Basically cut its balls off, and it's been smooth sailing ever since. Hell, the first time I've had a Windows install last more than two years without slowdowns, still boots up in like 40 seconds, I'm up and playing Civ before I'm done with a cigarette. I can't play multiplayer, but /shrug.

Yowtch, extreme! ...and here I am, getting all flustered at the 25sec. span it takes Ubuntu to come to login. Although... with my Win2k dual-boot, the time does increase to 45 sec. (not taking in all the startup services and call-home updates taking place) Leave it to MSFT to have a system that looks booted without really being "booted".

My best suggestion for a P/Pro system (more like a PowerPC than AMD or P4) would be to go for full-uptime; have it on 24/7 (idling at login screen when you're not using it)

For that solution, uninterruptible power would be key, and with the preeminent conditions of your area, it would seem to be a necessity! Those with serial DB-9 or USB interface would be best; gives feedback to a Windows applet and even appends to system events.

Other keys for speed; RAM RAM RAM... you can get most SDRAM (does it even take SDRAM?) on the real-cheap from discount places like http://www.geeks.com/.

Other tips generally come in the form of; reduce your startup items* and/or pace them with delay software* so they aren't chewing-up CPU so much during boot; shut-off unnecessary services or keep them from auto-starting until they are needed; and remove unnecessary devices in Device Manager.

* The above software links are only suggested titles I've used myself among many other options out there.

In addition to the other Denverite; I'll throw my hat into the ring with an old Athlon 1.1GhZ that seems to overheat too easily. The MoBo and ram seem to be the tops. (takes DDR 266 or "PC 2100") Don't underestimate the benefit of a faster hard-disk, either!

These tips come compliments of another who has burned the crucible of aging hardware time and time again. (after all, the $500 cost for a serious upgrade only comes along every year or so) Currently using (at home) a 1.7GhZ Sempron within a Soyo barebones kit. (all told, the Kit, CPU and RAM only cost about $250 at the time) My next project, Home-Theater PC with Linux.

The BSOD has been highly customisable for a while now, don't you know!

Way ahead of you, Microsoft. Change The BSoD color If your error crashes my computer, I'm not going to care if it was a "red" level of severity or a "blue" level of severity. I already know it was severe enough to crash my computer.

The blue screen of death's colour actually isn't constant ;^)

Where does the ram go? Well in windows, I don't know.

Into the damn ether, that's where. For Windows XP, you may want to look at this list of services and turn off as many as you can. It really helped my sister's computer (256MB).

I'm not sure if you're trolling or trying to be funny, but never mind.

However, you can actually change the colour of the BSOD to make it more PSOD (pink screen of death) or maybe YSOD (yellow screen of death).

Details are here although many Slashdotters probably won't like to admit that on W2K/XP they might never actually see the fruits of their labour.

You've been able to do that ever since Win NT4, maybe even 3.51. Here ya go. Another great innovation, only from Microsoft.

I think what you want is:

[386Enh]
MessageBackColor=4