11 Things Most Builders Forget - Finally...
(Page 4 of 4 )
The latest version
Do you have the most up-to-date drivers and firmware? How about the secondmost? You'll need them, so why not be ready beforehand? Have you slipstreamed your Win XP with the latest Service Pack and hotfixes? While you're at it, why not build an answer file and simplify your installation? Don’t forget to print out the file and place it into the abovementioned binder.
Plan the install
What OS are you going to use? Are you planning on installing another at some time in the future? What are you going to use the machine for? How many partitions will you need and in what sizes? How should the partitions be ordered? Have you planned a backup scheme and how can you simplify that process from the beginning?
Write down what software you need to install and at what point you need to install it. You can use that list to build an unattended installation disc.
Backups
Who the heck needs backups? You do. You didn't think about archiving data when you began ordering all the components, did you? If you have a backup plan set up ahead of time, then you are likely going to use it, and it won't hurt quite as badly when that unexpected crash comes.
RTFM
Sure, you’ve been working on/with computers for years now (and/or you’re male), you don’t need no stinkin’ documentation. That is, until you can’t get the system to work correctly with both RAM sticks in. If you had read the manual beforehand, you would have known that this particular board requires RAM in both slots 1 and 2, not 1 and 3 as is standard on many other boards. Also, since you have all your documentation assembled in one place, you know exactly where that manual is.
This isn’t to be considered the end all, be all list of things to do when preparing to build a computer, but I believe it hits most of the key areas that lead into trouble while building.
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |
| Recommended by Dev Hardware |
|---|
|
