What's the Usual Procedure After Building a Desktop?

[silentmemories]

What is the usual procedure that you guys follow after building a desktop? So far, I only know that you should install the OS, and that's about it. I know that you have to install drivers as well, but I'm not exactly sure how that is done. I haven't done system building before and haven't messed much with drivers before so I don't know much about it.

Steps after completing the build:

1. Install OS.
2. Install drivers. (Should I use the CDs or install from the Internet or let Windows find it for me(?)
3. Stress-testing(?) to see if my parts were correctly installed?

Thanks in advance.

 

[Blain]

OS install, of course.
Update Windows, install programs.
Begin using the system.
If there's a problem you'll know without any "stress testing".

 

[philosofool]

I never use the CD for my drivers; if they aren't the first "stable" release drivers, they're likely to be several generations old. Except for stuff that runs on generic drivers, don't use windows to find them: get them yourself from the internet.

I have a folder on my current machine that pretty much includes all the installers for my favorite programs and drivers I'm currently using. If I'm updating my OS (haven't in awhile, and Win7 and Vista 64 drivers are usually the same anyway) I download all the drivers I want and get them on a thumb driver before the parts in question arrive. In any event, I always try to have all the files I will need to install on hand before I start. Never, ever forget to have networking drivers on a physical disk so that you can find anything you forgot!

I go like this:
-install OS, creating a system partition and user data partition in the process.
-install video card driver (hate, hate, hate non-native resolution!). [reboot]
-install chipset drivers, wireless networking driver. [reboot]
-Configure windows options (like the location of my User profile, which I always keep on a separate logical drive, set windows updates to "let me decide when to install") [reboot]
-install Windows service pack.
-have a beer.
-copy all my user files.
-install favorite software, Free AVG (which I don't really like, but....)
-play around in BIOS to reduce boot time, overclock, etc.

At this point, it's probably not done and there will be little things that I have to do. But my computer is up and running and I will cross those bridges when I come to them.

 

[TheStu]

I do a dry run outside of the case when I am assembling a complete system, nothing more annoying than mounting everything into a case only to find that something is wrong.

Then yea, install the OS. Run Windows update repeatedly until it is done, install AV (MSE is good) and then setup my programs. For me, that process mostly just involves putting shortcuts back onto my desktop, I have most of my stuff installed onto separate hard drives.

 

[philosofool]

Run Windows update repeatedly until it is done

Grabbing the latest service pack may save you a boatload of time. I once tried it this way and literally spent three hours waiting for one series of updates to install. It was hell. The installed OS was Vista 64 without SP1, and this issue may be special to that particular windows release.

 

[TheStu]

Grabbing the latest service pack may save you a boatload of time. I once tried it this way and literally spent three hours waiting for one series of updates to install. It was hell. The installed OS was Vista 64 without SP1, and this issue may be special to that particular windows release.

Yea that will save time, assuming that the service pack shows up in Windows Update. When I last re-installed Win 7, SP1 wouldn't show up in my update list, I had to hunt it down on its own.

 

[silentmemories]

I do a dry run outside of the case when I am assembling a complete system, nothing more annoying than mounting everything into a case only to find that something is wrong.

Then yea, install the OS. Run Windows update repeatedly until it is done, install AV (MSE is good) and then setup my programs. For me, that process mostly just involves putting shortcuts back onto my desktop, I have most of my stuff installed onto separate hard drives.

What's a dry run? (Also, no driver installation necessary?)

Grabbing the latest service pack may save you a boatload of time. I once tried it this way and literally spent three hours waiting for one series of updates to install. It was hell. The installed OS was Vista 64 without SP1, and this issue may be special to that particular windows release.

Yep! I'm using Vista Business with SP1 for this build.

I never use the CD for my drivers; if they aren't the first "stable" release drivers, they're likely to be several generations old. Except for stuff that runs on generic drivers, don't use windows to find them: get them yourself from the internet.

I have a folder on my current machine that pretty much includes all the installers for my favorite programs and drivers I'm currently using. If I'm updating my OS (haven't in awhile, and Win7 and Vista 64 drivers are usually the same anyway) I download all the drivers I want and get them on a thumb driver before the parts in question arrive. In any event, I always try to have all the files I will need to install on hand before I start. Never, ever forget to have networking drivers on a physical disk so that you can find anything you forgot!

I go like this:
-install OS, creating a system partition and user data partition in the process.
-install video card driver (hate, hate, hate non-native resolution!). [reboot]
-install chipset drivers, wireless networking driver. [reboot]
-Configure windows options (like the location of my User profile, which I always keep on a separate logical drive, set windows updates to "let me decide when to install") [reboot]
-install Windows service pack.
-have a beer.
-copy all my user files.
-install favorite software, Free AVG (which I don't really like, but....)
-play around in BIOS to reduce boot time, overclock, etc.

At this point, it's probably not done and there will be little things that I have to do. But my computer is up and running and I will cross those bridges when I come to them.

Alright. Is there a specific list of hardware that requires drivers to work on your computer?

-Video Chip Driver: Do we download from manufacturer's website or AMD's website? (Catalyst?)
-Chipset drivers: What are chipset drivers? (Is it the motherboard? If so, and the "Realtek® 8111E , 1 x Gigabit LAN Controller(s)" is on the motherboard instead of a PCIe expansion card, do I have to install drivers for that as well, or is it included in the motherboard drivers? The motherboard has Bluetooth (It just says '1x Bluetooth module') and sound ('Realtek® ALC 892 8-Channel High Definition Audio CODEC ") - do I have to separately install them from the manufacturer's website (Realtek for sound, ?? for Bluetooth) or are they included in the motherboard drivers pack?)

Thanks for all the answers.

 

[Snakecharmed]

What's the usual procedure after building a desktop?

If you ask me, it's curse for days because you suspect your motherboard is eight flavors of retarded until you finally return it for a working one after making time to diagnose every part in your system. The replacement, while functional, is still two flavors of retarded, probably like everything the manufacturer makes. Oh well, good enough for me. D:

But seriously...

-Video Chip Driver: Do we download from manufacturer's website or AMD's website? (Catalyst?)
-Chipset drivers: What are chipset drivers? (Is it the motherboard? If so, and the "Realtek® 8111E , 1 x Gigabit LAN Controller(s)" is on the motherboard instead of a PCIe expansion card, do I have to install drivers for that as well, or is it included in the motherboard drivers? The motherboard has Bluetooth (It just says '1x Bluetooth module') and sound ('Realtek® ALC 892 8-Channel High Definition Audio CODEC ") - do I have to separately install them from the manufacturer's website (Realtek for sound, ?? for Bluetooth) or are they included in the motherboard drivers pack?)

Thanks for all the answers.

I would get the latest video drivers from AMD's site and the chipset drivers from the motherboard manufacturer's site. The chipset drivers basically include everything that is needed for the motherboard to run optimally. All of the relevant drivers should be available on the motherboard manufacturer's site and you can be sure that they will work for your motherboard. You may have a few separate downloads for each individual component, but they should all be there on one page. I've never even been to Realtek's website. If it wasn't so easy to guess, I wouldn't even know what the URL is.

 

[Fayd]

Yea that will save time, assuming that the service pack shows up in Windows Update. When I last re-installed Win 7, SP1 wouldn't show up in my update list, I had to hunt it down on its own.

that's why you download it beforehand and slipstream it into your install DVD.

 

[Fayd]

What's the usual procedure after building a desktop?

If you ask me, it's curse for days because you suspect your motherboard is eight flavors of retarded until you finally return it for a working one after making time to diagnose every part in your system. The replacement, while functional, is still two flavors of retarded, probably like everything the manufacturer makes. Oh well, good enough for me. D:

But seriously...



I would get the latest video drivers from AMD's site and the chipset drivers from the motherboard manufacturer's site. The chipset drivers basically include everything that is needed for the motherboard to run optimally. All of the relevant drivers should be available on the motherboard manufacturer's site and you can be sure that they will work for your motherboard. You may have a few separate downloads for each individual component, but they should all be there on one page. I've never even been to Realtek's website. If it wasn't so easy to guess, I wouldn't even know what the URL is.

for my computer, i've noticed that the AHCI driver on my mobo manufacturer's website is from 2009. i know amd has released ahci updates since then, but the manufacturer refuses to release them on their website.

 

[Fayd]

What's a dry run? (Also, no driver installation necessary?)

dry run means smoke-testing it outside the case. if it don't boot, you got a problem. track down problem. get it to boot. move it to case.

 

[silentmemories]

dry run means smoke-testing it outside the case. if it don't boot, you got a problem. track down problem. get it to boot. move it to case.

... How would one dry run their parts?

For the video drivers, is it the Catalyst Software Suite that I download for the Sapphire Radeon HD 6950?

Also, could you guys go to this link and see which drivers I need to install? I have no idea if I need to install all. Thanks.

 

[Blain]

Yep! I'm using Vista Business with SP1 for this build.

Why saddle a fresh build with VISTA?

 

[spikespiegal]

I do a dry run outside of the case when I am assembling a complete system, nothing more annoying than mounting everything into a case only to find that something is wrong

This

 

[TheStu]

that's why you download it beforehand and slipstream it into your install DVD.

Can't do that when your secondary system is a Mac

 

[T_Yamamoto]

Can't do that when your secondary system is a Mac

Apple FAIL :thumbsup:
Long Live The PC

 

[silentmemories]

Why saddle a fresh build with VISTA?

I get Vista Business with SP1 from MSDNAA.

Could someone tell me how a dry run works?

 

[TheStu]

Apple FAIL :thumbsup:
Long Live The PC

I use both.

I get Vista Business with SP1 from MSDNAA.

Could someone tell me how a dry run works?

Alright, so all your parts came from <insert vendor here> as individual components.

You pull out the motherboard and place it on top of its box (not on top of the static bag it came in. They are designed to keep static out, they do you no good if you place something on them), next put the CPU into the socket and attach the heatsink. Plug in the RAM and the GPU (if a dedicated card), and hook up your hard drive. Plug the PSU into what it needs to be plugged into and situate the case so that you can hook the power button (for this it helps to have a standalone power button, but you can do without) into the motherboard as well.

It is all in the open air, nothing is screwed down (except maybe the heatsink). Power it up, and make sure nothing catches on fire (almost never happens) and if you want, install the OS now.

Once you have verified that it is all working correctly you can put it all in the case and make it pretty.

 

[mfenn]

I get Vista Business with SP1 from MSDNAA.

If you have MSDNAA, you should be able to get Windows 7 as well. Please do that (it's for your own good :awe.

Windows 7 is so good about providing drivers that I usually don't bother installing anything other than the GPU ones. Yes, the Catalyst suite is what you want for your 6950.

 

[Fayd]

Can't do that when your secondary system is a Mac

sure you can. VM's.

 

[Fayd]

... How would one dry run their parts?

For the video drivers, is it the Catalyst Software Suite that I download for the Sapphire Radeon HD 6950?

Also, could you guys go to this link and see which drivers I need to install? I have no idea if I need to install all. Thanks.

uh, just as i said, smoke testing. just turning it on, seeing a bios screen that completes without issues, hits the "no operating system" error, and stops.

 

[TheStu]

sure you can. VM's.

Yes, I could have downloaded SP1 on the incredibly crummy >1Mb connection at the hotel I was at, then downloaded VMWare Fusion, then installed Win 7 into a VM, then downloaded and installed VLite, then slipstreamed the disc, then burnt it off.

Or, I could have done what I did, which is just burn the disc and call it a day to get my desktop up and running again.

But anyway, back on topic OP. Lots of good steps here.

 

[Fayd]

Yes, I could have downloaded SP1 on the incredibly crummy >1Mb connection at the hotel I was at, then downloaded VMWare Fusion, then installed Win 7 into a VM, then downloaded and installed VLite, then slipstreamed the disc, then burnt it off.

Or, I could have done what I did, which is just burn the disc and call it a day to get my desktop up and running again.

But anyway, back on topic OP. Lots of good steps here.

i wasn't aware we were referring to you. i was speaking in general terms.

you seem very me-centric

 

[TheStu]

i wasn't aware we were referring to you. i was speaking in general terms.

you seem very me-centric

You kept saying you!

 

[parks853]

What about updating the BIOS or SSD firmware? I read here the initial BIOS settings are important and if I read right it even says to run in RAID instead of AHCI which seems like it would only work if using one hard drive. I've read that updating SSD firmware can cause the drive to be erased, so seems it would be a good idea to update before installing the OS.