Thanks to everyone for the additional tips and insights. Also MechBGone's site, referenced earlier, is great for it's wealth of pictures and things that wren't included here for the sake of basic info and brevity.
I limited my guide on purpose. Why? Because the whole world doesn't run Windows. I usually triple boot between XP, Vista AND whatever flavor of linux seems neat this month. And I can't possibly cover every build and hardware config. But I can cover the basic, Processor, Heatsink, Motherboard, Memory, Video Card, basics.
I also left out Raid stuff, because I typically don't use it.
One side tip: Using XP on newer SATA based boards and whatnot, some boards have to be placed in "Native Mode" to get XP to recognize the harddrive.
I run into this problem quite frequently at work, older setup with early SATA adoption, harddrive goes out and system needs rebuilt.
Yes you can use a USB floppy and try to boot the drivers. The last build on my MSI K9N Diamond didn't seem to like that solution for XP.
Same process for most BIOS flashes if the new board does not take the even newer processor.
Now I'm running XP Pro 32-Bit, Vista Business 64-bit, and Sabayon Linux 64 bit.
But for those Windows folks, as soon as the OS gets loaded, hit it with your factory motherboard CD. Most the time you'll get your base drivers without a hitch.
Just make sure Windows Update doesn't go and try to fix up your hardware without your knowledge. I have liked systems with NVidia Chipsets because one driver download from NVIDIA fixes pretty much ALL hardware on the board. The ATI chipsets, you do a lot of looking on their site for the right driver.
64bit OS's usually require downloads that aren't on the factory CD, or it could be that the factory CD doesn't default to run on a 64 bit OS and the drivers ARE on the CD. Case in point the Elite Systems Group Black Series motherboard. Drivers are on the disc, but the installer won't run on a 64bt os. And under XP or Vista tries to install the incorrect hardware for the sound. That's poor workings on ESG's part.
When you get to Windows, Or Linux, or OSX (hackintosh anyone??) Drivers can be really tricky. If you stick with well established names for your chipsets, most of the time you'll do OK.
Also if I didn't mention it. Don't canibalize your old machine for parts until you've got the new one running. Helps to have one up for internet research or for downloading drivers if you need em.
BSOD's are usually the result of a bad setting, a piece of hardware that doesn't have a driver, bad memory, or a faulty windows install.
I'm sure there's a lot of stuff I'm still leaving out, but after building and rebuilding so many times, you sort of go on auto-pilot and leave a few things out here and there cause they just automatically come.
Once you've got a stable running base system, prior to all your game installs or other software packages, make an image of your disk and keep it in a safe place. Then doing a restore is pretty simple. You get your OS, your base drivers and everything simple quick and easy. ALSO if you upgrade hardware from the last base image, make a new image so long as the system's running fine.
PC/Network Tech. Former Factory Tech for HP/Compaq. MCSA Since 2003. Custom Builder since 2000