Building a PC for Windows XP: A Basic Box Can Rock
Published: November 5, 2001
By Jerry Honeycutt, Windows XP Expert Zone Community Columnist
Editor's Note: Past articles by members of the online community are archived for your use. The information may become outdated as technology changes. For the most current information, please search the Web site or post a question in the newsgroups.
Build a computer for 500 bucks? Sure. Build a computer for about 500 bucks that runs Windows XP like a champ? Yeah, right...no, really, it can be done. For $560, not including the operating system, I built a basic computer that makes Windows XP snap, runs my favorite business applications well, and gives a great Internet ride. If you're short on cash but still want the best experience possible with Windows XP, let me tell you about it.
In the Basic Box
The key to building a basic computer for so little money is picking the right mainboard. The mainboard must be one of those all–inclusive boards. I went shopping for one that included onboard video, sound, and network support—all at a price about the same as a comparable mainboard without all the extras. I also wanted to make sure that the device drivers for the mainboard work with Windows XP.
What I ended up with was the Intel 815EEA mainboard for these reasons: First, it met my all–inclusive requirement; it does include video, sound, and network support. Second, it's inexpensive. Yes, it only supports Pentium III processors, making it a bit out of date, but that's OK. I chose to stay away from more expensive processors and more expensive memory. We're going for low cost, and I got the board with a 733–MHz processor and 256 MB of memory for $260. That's half the computer.
However, if you have the money to spend, this isn't the way to go. Third–party video, sound, and network cards are better than those on this type of low–end mainboard. On the other hand, you can start with the all–in–one mainboard and when you have the money, replace the built–in video, sound, and network components one at a time. You'll have to disable them in the mainboard BIOS, however. For example, I'll eventually replace the mainboard NIC with the 3Com 3C905, a NIC that I favor because it supports Remote Installation Service.
The remaining components I picked up at local computer stores. I nabbed a 40–GB Maxtor DiamondMax Plus 40 hard disk for $100 and some change. This disk meets the biggest two criteria I assigned to the hard disk: it's 7,200 RPM and it supports UltraDMA. I wasn't as picky about the floppy and CD–ROM drives, chassis, keyboard, mouse, and monitor. Because I didn't have to spend, I purchased generic brands that I found at a large computer superstore—purchasing all of the above for $200.
Device Drivers Needed a Push
So, there you have it—an inexpensive computer for Windows XP. The figure below shows what the assembled computer looks like.
One problem: Windows XP doesn't have native device drivers for the mainboard that I chose. Without them, I'm stuck with basic VGA output and no sound. This problem was easily fixed, though. First, I downloaded the device drivers from the Intel Web site. I could have just installed the device drivers after installing Windows XP, but that somehow doesn't seem right. I want the whole kit and kaboodle to work properly after the setup program finishes, which means that I don't want to fiddle around with Device Manager.
The solution that I used was to build an answer file to install Windows XP. If you're not familiar with answer files, then take a look at Deploy.cab, which is on your Windows XP CD in Support\Tools. Answer files automate the installation process so that you don't have to answer so many questions. In this case, it also allows me to add third–party device drivers so that the setup program can use the proper drivers from the get–go.
So here's how it works. First, I made a copy of the Windows XP CD. I created a new directory in the CD i386 folder called $OEM$\$$\Drivers, and copied to it the device drivers that I downloaded from the Intel Web site. Last, I created an answer file called Unattend.txt and installed Windows XP using the command line d:\i386\winnt /s:d:\i386 /u:d:\unattend.txt, where drive D contains the customized Windows XP CD, and my answer file is at the root of the CD. The following listing shows the most relevant parts of the file:
[Unattended]
DriverSigningPolicy=Ignore
OemPnPDriversPath=\Windows\Drivers
OemPreinstall=Yes
DriverSigningPolicy prevents Windows XP from prompting you to install unsigned drivers. I include this property just to avoid annoying prompts for unsigned device drivers that I know are OK. OemPnPDriversPath tells the setup program where to look for additional third–party device drivers. OemPreinstall instructs the setup program to copy the contents of the $OEM$ folder to the computer and copy the contents of $OEM$\$$ to the Windows folder. Since I put the device drivers in $OEM$\$$\Drivers on my customized CD, setup copied them to Windows\Drivers on my computer. That's why OemPnPDriversPath points to \Windows\Drivers.
Putting the Whole Thing Together
You'll notice that I'm not describing how to put the components together. I'm assuming one of two things: you already know how to assemble the components or step–by–step instructions are already available. I'm concentrating on providing hints and tips for assembling computer components with Windows XP in mind.
If my first assumption doesn't help you, then my second assumption certainly will. A few Web sites give very detailed, step–by–step instructions for assembling the components of a computer. A very well written example can be found at PC Mechanic. The article starts with buying components, and then moves on to installing the CPU. The instructions are so detailed that the author actually discusses the different ways to attach the mainboard to the chassis. Well done. I'll refer to this site in the future.
Windows XP Rocks
My total cost for this basic Windows XP computer was $560, and it shows that you don't have to drop a lot of cash in order to build a computer for the latest Windows operating system from Microsoft. I was blown away when I first started Windows XP on this computer. It rocked, booting fast and sporting a snappy user interface. It amazes me that a $500 computer runs Windows XP so well.
 | ...memory is one of the most important components for Windows XP. I see that more clearly in the basic box, where additional memory made more of an impact on Windows XP than bumping up the processor would have–dollar for dollar. |  | |
| |
|
One key is that this computer has 256 MB of memory. As I mentioned in my recent column (Build the Best Computer), memory is one of the most important components for Windows XP. I see that more clearly in the basic box, where additional memory made more of an impact on Windows XP than bumping up the processor would have—dollar for dollar.
My only disappointment is all about video. Windows XP in this configuration is perfect for browsing the Internet. It's perfect for e–mail. It's perfect for Office XP. This isn't the best configuration for 3D games, though. The onboard video component of the 815EEA mainboard just doesn't cut it when it comes to games like Asheron's Call. Further, I believe that a good monitor is second only to memory in importance. But with so little money to spend, I had to go with a small 15–inch monitor.
I'll address all of these issues in my next column when I build a computer that the whole family can love. The budget goes out the window—within reason of course. This is the box that was meant for Windows XP. I'll follow all the rules, giving it plenty of memory and the best monitor that I can afford. But I'll also build the box for games, stuffing it with the hottest video and sound cards available.
Expert Zone Columnist Jerry Honeycutt is a writer, speaker, and technologist who has written over 25 books, including Microsoft Windows XP Registry Guide (Microsoft Press, 2002). He frequently writes about customizing and deploying Windows XP.
