Oh, and there is a huge difference between working on having 2 years experience working on a computer, and troubleshooting a computer.
Indeed.
For example;
Clear your desktop of extra icons and shortcuts with windows 9x versions to increase your speed on older systems. I don't know how many times I had to clean up the family computers simply by doing this... and it allways works for the general "slow down" problems they complained about.
However... I've also dealt with much busted hardware, corrupt drives, corrupt drives, corrupt disks, etc... and spent plenty of time workign through several cutom configurations to make them work correctly. For example; old BIOS and Sound Cards on older computers allmost allwasy had very very particular parameters to function properly with your other hardware and software. When there was not a manual around to read... it became a technical "know how" to fix them. I don't know most of that stuff any more... but what computer BIOS asks how many disk head, clusters, sectors, etc... it has any more? How many Sound Cards require you to manually set up the IRQ and port information? Not any I am aware of these days... so that knowlege is gone by the wayside.
Of course... this is a scratch of what I have done, but why should I even be rambling about it?
I agree with Ozzy... Troubleshooting a wide variety of problems rather than fix a small area of known problems... and you will learn more than any book can tell you right off the top, mostly because the symptoms don't allways fit the way the book describes it, and there is allways a new kind of problem with all the new components.
Peace.