Hardware Restoration Tools and Equipment

Hardware Restoration Tools and Equipment

by Coral1

Hmmmm.... I guess this is as good a time as any to say something about the tools you might like to have handy.

While everything listed below is not necessary to work on computer hardware, the more the better. However, I will try to group things according to the level of need.

A beginners toolkit has to have:

That's it. Really! Oh, OK. You will need a Slot-head screwdriver for unhooking most of the heatsink clips still out there. But most of the repairs/upgrades you do can be done with a Phillips screwdriver.

Alright, so you want to do more than just swap out video cards. These should get you going.

The Basic Toolbox

Here is a list of things you will need to start your adventures in hardware.

notes

Even better

When you get the chance, add these to your collection.

While this is by no means a complete list, it should get you well on your way to becoming the "Go To" person when friends and family need work done on their systems.

Odds and Ends

This list is almost endless, so I will just mention a few things. The good news is that you can get most of it when stripping old systems down.

Basically you want to become a packrat.

Serious Hardware Geeks

This is where the REAL fun begins.

I feel I should warn you though. While working on computers is usually not dangerous, you will get nicks, cuts, burns, and even shocked from time to time; then there is the occasional vampire system.

When you get to the Serious Hardware stuff, you can Really get hurt if you are not careful. I am talking about losing chunks of meat and big-time body damage.

Benchmark Programs

I don't use these much myself. Not being a gamer or running resource intensive apps, if I do not notice an improvement after an OC (overclock), a setting tweak, or hardware swap, I usually put it back the way it was. For stability. On a hardware swap, I will leave it in.

Still, a few comments on the subject are needed.

Other than bragging rights, the main reason to run benchmarks is to optimize your system for whatever you are using it for.

There are a lot of tricks to tweaking your system, but to put it simply:
The first thing you do is BackUp any data and info you do not want to lose!! Then fire up a benchmark that tests the part(s) you want to optimize and run it on your system, as it is now. This is called a baseline reading. You can either get the latest bios and driver updates before or after you run the baseline (if you want to see they how much they help). Then you start playing with the settings IN SMALL INCREMENTS, and run the benchmark between each change. You keep doing this until the score starts to drop or the system hangs/crashes. Set it back to the last working setting. Now you need to run a BurnIn test to make sure there are no BSOD's or random memory/harddrive errors. If there are, you need to back it down a little more, until it is stable again.

The other reason is to see how different hardware combinations work together (or driver versions). Say you have 2 video cards. One has a slightly better frame-rate with a certain mobo setup. But the other one has the better frame-rate on another setup. Now you know which card to use in which rig.

The same with drivers. If the new drivers (for whatever) give a worse score than the old ones, you sure don't want to keep using the new ones, do you?

The two main types of testing are:

The Work Area

I have repaired systems on every surface from the Living-room floor, to my bed (when I have been sick and bored), and everything in between. While any place that has some elbow room can be used as a work area, certain things need to be kept in mind.

  1. When working on carpeted floors, static electricity can be a major problem. Work on a piece of paneling turned upside down or at least a thick layer of newspaper or cardboard. Read up on and understand how to ground yourself properly! Regularly touching the metal part of the case while it is plugged into an AC outlet, will usually do the trick (system does not have to be turned ON). Anti-static mats and/or straps are not that expensive anymore.

  2. When working on counter-tops, Dining-room/Kitchen tables, coffee tables, or any other finished surface, putting something between it and what you are working on is also a good idea: for a different reason. It seems that nothing irritates the 'Love of Your Life' more than scratching up the furniture.
I have a small stack of 1" x 1" x 12" (2.5 x 2.5 x 30cm) pieces of wood that I use for this purpose. Two or three will let you lay a case on its side without scratching up anything. Even better under a mobo when testing it outside of the case. This also solves the problem of putting in addon cards without having to put the mobo on the edge of the table so the metal tabs on the bottom of the cards don't stop them from going all the way into the slot. I prefer using three of them under a mobo to keep it from flexing when pushing down on whatever I am trying to install. It also allows for good airflow from the "casefan" I have blowing on it.

The most functional setup I have seen (and currently use) is a wooden workbench that is high enough so that you can work at it standing up without having to bend over. Add a stool (padded of course) tall enough to let you sit or lean on it. This way you can move around as needed, while what you are working on stays in a comfortable work position. The main work area is wide enough so you can grab the tools you need on the left, right, and across it, without having to stretch for them. For me this is about 4 ft (1.2m) high, 5ft (1.6m) wide, and 30in (75cm) deep. After loading the edges with tools, shelves, and everything else you need to get the job done, I still have an area a little over 3ft x 2ft for work.

A word of warning. No matter how large the room, no matter how many benches, shelves, and cabinets you put up, you always end up running out of space!

The TestBed

To put it simply, this is a working computer that is not in a case.
Actually, by the time you finish putting it together, it's about 5 or 6 computers. Check this out. My testbed consist of:

Granted, I have been putting this thing together for years and some of the stuff is mostly just gathering dust now; but it gives you an idea of what you will need to be able to test all the things you will be working on. Think of it as a kind of do-it-yourself Leggo set.

One Common Scenario:

Let's say a computer comes in that sounds like it is booting up. The front LED lights up, the HD's and fans spin, but nothing shows up on the monitor. After unhooking, taking out, and/or disabling everything but the power supply, cpu, video card and ram, it still doesn't boot.

Now you need to figure what is bad. The cpu, ram, video card, or mobo.

So you need to try known working parts (from your pile, err.. stock) in this computer. As a double check, you need to test the parts from the non-booting computer in a known working system (your testbed); one thing at a time.

After doing these test, you have either found out what is bad, or that you need to go to the next level of testing.

Quitting Time

I think that just about covers it. Since I am starting to get hungry, we will call it a day. I am going to see what I can scratch up for supper, and then temporarily lower my IQ by watching some TV.

Until next time ...

May you spend many happy hours cursing your decision to ever start this line of endeavor.

NS,NR!!

post to Dzone Digg this! Add to del.icio.us Googleize this Add to reddit Save to myYahoo Add to furl Add to Netvouz! Spurl this! Add to Linkroll! Save to Simpy Give if thumbs up on StumbleUpon Save to Blinklist Add to Tektag Save to Bibsonomy Submit to Tweako
Search ERT on the Tools Page
Did you know? You can discuss this article with the mentor who wrote it and others interested in the topic? You are invited to join the discussion with Go to the forum

Got a technical article or tutorial you want to publish on the Internet? Join Go to the forum in the Round Table Forum and let the Mentors know what you have. If it meets ERT standards, is factual and can help ERT visitors, then ERT Mentors and Editors can help you (without charge) polish your offering so it can be published and promoted by ERT. An article published on ERT may be read by as many as 10,000 visitors a week; promoting you, your site, and your ideas. Please note ERT does not publish re-prints; promotional handouts, or pieces consisting mainly of links. So original technical content only please. If you prefer you can email the Editor