How to build your own computer: Ask Ars DIY Series, Part II—software

In Part II of our text-and-video Ask Ars DIY Series, we show you what happens …

In 1998, Ask Ars was an early feature of the newly launched Ars Technica. Now, as then, it's all about your questions and our community's answers. Each week, we'll dig into our question bag, provide our own take, then tap the wisdom of our readers. To submit your own question, see our helpful tips page.

Instead of replying to a reader's question on Ask Ars, we've got Part II of new PC-building guide, complete with informative (and entertaining) video clips that both inform and entertain. Last week we were all about hardware assembly. Today, we're picking up where we left off, covering first boot and software tweaking. If you're in the process of building your own PC and are wondering what to do now that the hardware is in place, read on.

EFI (or BIOS) configuration

When we last left our PC-building saga, we had assembled all of our computer components together in the case, powered it on, and had just gotten to the BIOS, or Basic Input-Output System, of the motherboard. (Technically speaking, our Sandy Bridge motherboard doesn't have a BIOS; instead, it has a new BIOS replacement called the Extensible Firmware Interface, or EFI, but we will stick with the term BIOS because it is familiar and rolls off the tongue much nicer.) BIOSes are not at all basic anymore, and the one attached to the Asus P8P67 is downright pretty, but it does start off in easy mode and gives us access to relatively few settings.

We can set the boot order by dragging and dropping, and tell the computer whether to optimize for relative silence, performance, or some kind of middle ground. To make more tweaks, we can switch to the BIOS's advanced mode by a button in the top right corner of the screen. Before you do a lot of playing around in the BIOS, make sure you read through the user guide that comes with your motherboard.

Ask Ars Computer Building Series Episode Two, Part One: The BIOS

The guide will tell you what most things mean—though the occasional omission or error is a common feature of motherboard manuals—and will also fill in the gaps between the setup of our motherboard's BIOS and others. The P8P67's menu setup isn't representative of all motherboards, but the general ideas are the same.

You may remember from Part I of the computer-building saga that the first time we tried to boot the computer, it looked like the motherboard couldn't see the hard drives because they were plugged into the gray Intel chipset's SATA ports and not the navy blue Marvell ones. Going into the Advanced menu and selecting SATA Configuration shows that the motherboard can indeed see the hard drives.

The error message has nothing to do with functionality—the computer will boot an operating system from drives plugged into the Intel chipset—but the computer will keep showing the message and an extra splash screen, so this is an annoyance we want to fix.

If we go back in the Advanced menu to Onboard Devices Configuration and scroll down to the Marvell Storage Controller option, we can set it from "AHCI Mode" to "Disabled." Now, during the power-on self-test, we won't see that extra screen trying to scare us into thinking there are no hard drives.

If you're looking to overclock your processor, you'll find all the settings for that under AI Tweaker for this motherboard. Setting AI Overclocking Tuner from Auto to Manual will let you tune all of the CPU's operating stats to your heart's desire, but you should not mess around with this unless you have installed a really good CPU cooler and have a good grasp of the hardware.

Under the Monitor menu, you can set the lower limit on how fast your CPU and case's fans spin, and profile menus let you prioritize the fan's behavior for less noise or more performance. Choosing Standard or Silent can help your computer draw slightly less power, and more importantly make less noise, but if you're going to be making heavy demands on your hardware, be wary of setting them too low. You can also choose Manual and tweak your CPU and case's maximum operating temperature, but do not play with these numbers unless you are completely aware of all of the performance and lifespan tradeoffs that will come with changing those numbers. If you prevent the fans from spinning as fast as they need to, crashes are a very real possibility.

Last, we can check that the boot order is good to go. By default, the computer will check the hard drive and then the solid state drive, and if there's nothing there then it looks to the optical drive. This is a fine order for us, because now we are going to install our operating system of choice: Windows 7 Home Premium.

Operating system time

Video Ask Ars Computer Building Series Episode Two, Part Two: The Operating System

Retail copies of Windows include both the 32-bit and 64-bit versions. We recently wrote about which one you should use, and why: the short answer is, go for 64-bit unless you absolutely must use software or hardware that only works in 32-bit. 64-bit lets you install a lot more RAM (as well as being potentially a little faster and a little more secure): it’s the natural choice for any new build.

You can also opt for the OEM version of Windows. If you do this, you’ll have to pick whether to buy 32- or 64-bit—unlike retail copies, OEM versions only include one bitness—and you will have to buy it along with a piece of hardware. OEM versions are cheaper—Home Premium is $100 for OEM to the retail version's $180—but will be tied to the hardware configuration you install it on. Changing out the RAM won't invalidate the OEM version of windows, but switching to a different motherboard might. A retail copy of Windows can be installed again on a different computer, but can only be activated on one machine at a time.

Windows installation nowadays is both straightforward and quick—a couple of menus will ask for your native language, the date and time, and your compliance with their terms of use.

If you have more than one hard drive or solid state drive installed, at one point Windows will ask you to specify which one you want the OS to live on. This question is easy enough to answer (your solid state drive, if you have one), but charging ahead and installing when there are two drives present could cause you some difficulties in the future.

Regardless of which drive you decide to put Windows on, the installer will place 100MB of "System Reserved" information on the drive in the first position when there is more than one drive. If that drive isn't the same drive Windows is installed on, removing that drive from your configuration will result in a computer that does not boot. Furthermore, if that hard drive fails, you also will not be able to boot.

Backing up properly will protect you against these issues for the most part, and if you decide to use the drives separately you will just have to spend a few minutes repairing Windows. But for simplicity's sake you may want to just unplug the drive you won't install the OS on from its SATA port while you're installing Windows, to protect yourself from its file-scattering habit.

Windows will ask at this point what should be done with the updates that have been released since the install DVD was printed. You can choose not to install any of the updates or install only the critical ones, but unless there is some update in particular you need to avoid, it's fine to go with the recommended settings, which will install all updates.

Huge. Having walked countless people through some or all of these steps - or, worse, given up on them and just done it myself - this is a godsend. Must have been a ridiculous job to script, execute, film and edit, too. Thanks, Casey.

Why no Linux? I think the target audience is not the most tech savvy user. Whatevr Linux distro you choose can still be a major PITA if you have some pice of hardware that your OS of choice doesn't recognize automatically. Windows is just easier. Download driver, doubleclick, accept everything like a cheap prostitute and maybe reboot.

Wow, Ninite looks very useful. I also love FileHippo, which isn't so automatic (though they do have an update checker), but does keep a repository of previous and beta versions of each program.

Edit: Apparently Ninite doesn't list Avira AntiVir, which is a glaring omission. I've found to be the fastest, least RAM-intensive free antivirus prog, better than AVG. Plus they've been at the top of the accuracy charts Ars has posted about.

This was worth the read if only to be reminded of Ninite. The next time I hose my system (or build a better one), this will certainly be one my new stops. Looking forward to checking out the videos when I can freely listen to the audio. Thanks once more for useful information, Casey!

You no longer have to buy a piece of hardware in order to get an OEM copy. I've heard in the past that you'd get a piece of broken equipment if you ordered just the OEM copy, but I'm pretty sure that's no longer required. I had no such problems the last two times I bought OEM.

I love these stupid comments... if it had been a guy, no one would have said boo.

Quote:

Why no Linux? I think the target audience is not the most tech savvy user. Whatevr Linux distro you choose can still be a major PITA if you have some pice of hardware that your OS of choice doesn't recognize automatically. Windows is just easier. Download driver, doubleclick, accept everything like a cheap prostitute and maybe reboot.

Because the only people that care about Linux already know how to build a computer. Also, installing Ubuntu is about as easy as installing Windows 7. Put the CD in and wait. Maybe click a few times and enter account information.

Props on recommending Ninite. I've recommended it to my Windows-savvy friends, and always get a "Woah, no way!" response.

Clovis42 wrote:

You no longer have to buy a piece of hardware in order to get an OEM copy. I've heard in the past that you'd get a piece of broken equipment if you ordered just the OEM copy, but I'm pretty sure that's no longer required. I had no such problems the last two times I bought OEM.

Say linux is only for the tech savvy is a major misconception, IMO. It's as easy or as hard as you make it and depends on the distro. Installing Windows 7 or installing Ubuntu is on the same level of difficulty. Ubuntu's gotten rather robust in this area with it's "additional drivers" detection. I've had it auto-detect wireless and video cards where windows has not.

"Unless you have all of the relevant CDs assembled next to you, the best place to score drivers is from the Internet."

Even if you have all the driver CDs, there's a good chance the drivers on them are obsolete. This matters less for some components than others, but mobo chipset drivers can be a big factor for stability; and GPU drivers are a huge factor for gaming performance. Unless you don't have internet access I'd always go to the hardware vendors for drivers instead of using the CDs.

If you are building your own computer, please install windows THEN install something like ubuntu next to it. I say that because if you are of the type who will build their own computer, and loves computers, you will eventually love linux. You still may need windows but over time you will come to understand and really appreciate and admire what linux/open source is all about. It can take a while, but stay with it. Mess around with it when you have free time. I have never bought an off the shelf computer and loved building computers, installing/reinstalling windows over the years (since 94). Now I only run windows 7 (just to keep up with the times) and XP in virtual machines on ubuntu and its just the most awesome PC.

I'm not talking about the OS recognizing all hardware but about how easy it is to install drivers for unknown hardware. I know Linux as a whole has become a lot better in this regard but still Windows is... easier.

If you are building your own computer, please install windows THEN install something like ubuntu next to it. I say that because if you are of the type who will build their own computer, and loves computers, you will eventually love linux. You still may need windows but over time you will come to understand and really appreciate and admire what linux/open source is all about. It can take a while, but stay with it.

And with the multiboot setup, basic premise is this: you partition your drives for multiple OSes, and you let GRUB be your boot manager to select between the OSes. Here it is being done with ubuntu (can be done with any and all linux distros): https://help.ubuntu.com/community/WindowsDualBoot

And with the multiboot setup, basic premise is this: you partition your drives for multiple OSes, and you let GRUB be your boot manager to select between the OSes. Here it is being done with ubuntu (can be done with any and all linux distros): https://help.ubuntu.com/community/WindowsDualBoot

Right, but there's also some technical details to consider. I think WinXP demands that it be installed before some particular (and kind of obscure, frankly) cylinder limit on the first logical partition, and Vista/Win7 (IIRC) at least require some sort of bootcode to go up front. Maybe GRUB handles this? I haven't messed with it in a couple years. I remember fighting with LILO though.

What I'd really like is to do it with a GPT rather than a clunky old MBR, but I'd be surprised if many other readers were interested.

If you are building your own computer, please install windows THEN install something like ubuntu next to it. I say that because if you are of the type who will build their own computer, and loves computers, you will eventually love linux. You still may need windows but over time you will come to understand and really appreciate and admire what linux/open source is all about. It can take a while, but stay with it. Mess around with it when you have free time. I have never bought an off the shelf computer and loved building computers, installing/reinstalling windows over the years (since 94). Now I only run windows 7 (just to keep up with the times) and XP in virtual machines on ubuntu and its just the most awesome PC.

I can't agree with all of this, but I second your "install Windows first" sentiment. Windows tends to get pushy and bury GRUB if you do Linux first. Granted, it's not too hard to get back, but why deal with the extra frustration?

And with the multiboot setup, basic premise is this: you partition your drives for multiple OSes, and you let GRUB be your boot manager to select between the OSes. Here it is being done with ubuntu (can be done with any and all linux distros): https://help.ubuntu.com/community/WindowsDualBoot

Right, but there's also some technical details to consider. I think WinXP demands that it be installed before some particular (and kind of obscure, frankly) cylinder limit on the first logical partition, and Vista/Win7 (IIRC) at least require some sort of bootcode to go up front.

What I'd really like is to do it with a GPT rather than a clunky old MBR, but I'd be surprised if many other readers were interested.

Oh, that would be interesting.

HisMajestyTheKing wrote:

@ raylinth

I'm not talking about the OS recognizing all hardware but about how easy it is to install drivers for unknown hardware. I know Linux as a whole has become a lot better in this regard but still Windows is... easier.

Ah, unrecognized hardware is always a toughy and typically the vendor focuses on the drivers for windows rather than linux. I see what you are saying.

I'm not talking about the OS recognizing all hardware but about how easy it is to install drivers for unknown hardware. I know Linux as a whole has become a lot better in this regard but still Windows is... easier.

Actually, it is not, in my experience. It used to be. I seem to need driver CDs to get everything working in windows.

Example cases

1. 4 year old ATI mobile graphic chipset on laptop windows 7: Driver discontinued by ATI, no options except buy new laptop or use generic 640x480 graphics.Linux: same situation for ATI driver, but fully worked anyway with 3D acceleration and blur, because an open source driver is still ongoing development and was automatically used.

2.USB to serial adapters. win7: 5 different USB to serials laying around wouldn't work and drivers (XP) wouldn't work. Went and bought new one - used driver CD to get it working. Linux: No driver installation at all - shows up as comm port instantly. Noticed approximately 20 different chipsets supported natively in kernel.

3. USB soundcard - found laying around, black box with line out jack - no idea who made it. Plugged into linux machine - instantly available as soundcard without any messages or interaction, other than setting it as current output device. Windows: unknown USB device. Driver search on windows update - nothing found. Identified VID/PID on linux and tracked it down finally on driverguide.com.

And with the multiboot setup, basic premise is this: you partition your drives for multiple OSes, and you let GRUB be your boot manager to select between the OSes. Here it is being done with ubuntu (can be done with any and all linux distros): https://help.ubuntu.com/community/WindowsDualBoot

Right, but there's also some technical details to consider. I think WinXP demands that it be installed before some particular (and kind of obscure, frankly) cylinder limit on the first logical partition, and Vista/Win7 (IIRC) at least require some sort of bootcode to go up front. Maybe GRUB handles this? I haven't messed with it in a couple years. I remember fighting with LILO though.

What I'd really like is to do it with a GPT rather than a clunky old MBR, but I'd be surprised if many other readers were interested.

Well, I would be I'm about to migrate to Win7-64 on a new SSD in my PC, and I'm trying to work out if I have any reason / benefit to use GPT ie will it make managing the usual tussle of boot priorities between Linux and Windows any easier?

1. Set up user accounts. IIRC the official Ars recommendation is to NOT be admin for daily tasks. Though maybe this matters less in Win7 than Vista or XP?2. Reassign the user directory to a different partition, or better, a different drive entirely. I've saved my own hide a number of times because I moved "My Documents" to the D drive instead of C. Of course, a synchronized backup solution is better.

I'm not talking about the OS recognizing all hardware but about how easy it is to install drivers for unknown hardware. I know Linux as a whole has become a lot better in this regard but still Windows is... easier.

Actually, it is not, in my experience. It used to be. I seem to need driver CDs to get everything working in windows.

Example cases

1. 4 year old ATI mobile graphic chipset on laptop windows 7: Driver discontinued by ATI, no options except buy new laptop or use generic 640x480 graphics.Linux: same situation for ATI driver, but fully worked anyway with 3D acceleration and blur, because an open source driver is still ongoing development and was automatically used.

2.USB to serial adapters. win7: 5 different USB to serials laying around wouldn't work and drivers (XP) wouldn't work. Went and bought new one - used driver CD to get it working. Linux: No driver installation at all - shows up as comm port instantly. Noticed approximately 20 different chipsets supported natively in kernel.

3. USB soundcard - found laying around, black box with line out jack - no idea who made it. Plugged into linux machine - instantly available as soundcard without any messages or interaction, other than setting it as current output device. Windows: unknown USB device. Driver search on windows update - nothing found. Identified VID/PID on linux and tracked it down finally on driverguide.com.

Other examples but I have to get back to work...

That is contrary to my experience but it certainly shows that there is a variety of circumstances. In my experience, Linux on old laptops has been frankly annoying as hell. It's where I really want to use it to get some use out of dated hardware but I always have serious issues getting the onboard graphics to do the proper resolution or external monitors. The onboard Wifi never seems to work unless I go jump through hoops to extract some driver from a package and use a wrapper to get it somewhat functional.

WinXP was typically "install NIC driver from CD or flash drive then download drivers for every other piece of hardware". So far my luck on Win7 has been so much better, even on the older laptops. Out of the box I will get everything major working and after the first Windows update it has the specific drivers for everything else. Only issue I had out of maybe 7 or 8 installs (I know, not a huge sample size) was a USB DJ controller/sound card that didn't install automatically but it even gave me a link to where I could download the third party package.

I guess it would have been cool if they did a Windows install/setup article and a companion Linux setup article with Ubuntu or other common distro. That way people can try different setups and see how they work on their hardware. Despite being Win-centric I do enjoy playing around with Linux in dual boot. I just don't typically use it too much since the vast majority of software I use is available on Windows and much of it has no real alternative on Linux. Not so much a fault of Linux as it is a reality of the platforms from a user standpoint.

If you are building your own computer, please install windows THEN install something like ubuntu next to it. I say that because if you are of the type who will build their own computer, and loves computers, you will eventually love linux. You still may need windows but over time you will come to understand and really appreciate and admire what linux/open source is all about. It can take a while, but stay with it. Mess around with it when you have free time. I have never bought an off the shelf computer and loved building computers, installing/reinstalling windows over the years (since 94). Now I only run windows 7 (just to keep up with the times) and XP in virtual machines on ubuntu and its just the most awesome PC.

There's only two things I hate more than Windows, and that's rebooting my computer or not being able to use DX11 for my games. I didn't pay $300 for a videocard to run in DX9. Yes, there is a difference.... mostly just faster+better shadows for now.

No Windows reboot jokes, when I installed Win7 RTM from MSDN, it had 4 months of up-time with no hiccups before I finally applied Windows Updates. The only times I currently reboot is for a monthly Windows Update. I love how Video drivers don't require restarts anymore.

Once Linux finally get DX11, can work with the newest videocard and the drivers become stable, then it'll be worth it for a gaming computer.

DX12 is coming out soon, so I hope Wine gets that. I heard developers say that DX11 is great and it should port over fast.. Still waiting. I should hope DX12 is similar to DX11 so they can port it before the version after that comes out.

It might be worth a mention in teh article of how to re-enable AHCI after windows is installed. It's too much effort to install with AHCI support most of the time, but with the reccomendation to disable the comnputer loses the ability to hot swap e-sata and I believe you lose NCQ for SDDs.

It might be worth a mention in teh article of how to re-enable AHCI after windows is installed. It's too much effort to install with AHCI support most of the time, but with the reccomendation to disable the comnputer loses the ability to hot swap e-sata and I believe you lose NCQ for SDDs.

Do most people who build their own computers do it for the gaming? If so, they will perhaps NOT like linux. I am just a person who likes computers and am an embedded FW engineer so maybe most of you will not feel the way I do. I enjoy getting things working and customizing and understanding and maybe swearing a few times along the way. Knowing I have the source code and could compile everything from scratch (of course almost never compile anything) Its the DIY mentality.

Random question from a (currently) non-builder: why were the gray Intel SATA connectors used instead of the blue Marvell connectors? (I know, probably LMGTFY, but it think others may be curious as well).

Also, maybe it's just me, but Casey needs to not smile at the beginning of each "cut" within a scene...it's kind of distracting when she just finishes explaining something all serious-cat-like. Completing a scene without making obvious cuts would probably fix it as well.