Assist in the making of a nerd!
April 5, 2007 3:09 PM Subscribe
Please help me find resources for learning about PC hardware!
I've had an interest in learning about basic PC hardware for a couple of years now and have successfully put together 3 systems by myself. Essentially, I understand the basics. I know what components make up your standard PC system and something about compatibility issues/judging the speed and quality of those components (though I am sure I could know more). I'm looking for a book or web resource that explains things comprehensively but a bit more in-depth than something like How to Build a PC for Dummies. In other words, I want to know more than what parts I need and how to put them together. I want something beyond simply explaining the concept of, say, why FSB speed is important, and something more akin to "here is what this really means and why it is important in the scheme of things." So -- less definition, more explaining. However, I would like something both readable and operating at my level. That is, geared towards the beginner/hobbyist. Thanks in advance for your time!
I've had an interest in learning about basic PC hardware for a couple of years now and have successfully put together 3 systems by myself. Essentially, I understand the basics. I know what components make up your standard PC system and something about compatibility issues/judging the speed and quality of those components (though I am sure I could know more). I'm looking for a book or web resource that explains things comprehensively but a bit more in-depth than something like How to Build a PC for Dummies. In other words, I want to know more than what parts I need and how to put them together. I want something beyond simply explaining the concept of, say, why FSB speed is important, and something more akin to "here is what this really means and why it is important in the scheme of things." So -- less definition, more explaining. However, I would like something both readable and operating at my level. That is, geared towards the beginner/hobbyist. Thanks in advance for your time!
I Recommend http://arstechnica.com/paedia/r/ram_guide/ram_guide.part1-2.html
(and ars technica in general.)
At some point, you're going to want to understand assembly language, since that's really what the computer is 'doing.' Not sure exactly how to go from 'beginner' to understanding assembly language, though, exactly. To understand assembly, you'll probably want to first get C (which is pretty much a glorified assembler anyway.)
Also, commonly used textbooks like this one may be good-- but, again, may assume more understanding of code than you have right now.
There may be some good class notes online for 1- or 2- level Computer Science classes, too.
posted by blenderfish at 11:21 PM on April 5, 2007
(and ars technica in general.)
At some point, you're going to want to understand assembly language, since that's really what the computer is 'doing.' Not sure exactly how to go from 'beginner' to understanding assembly language, though, exactly. To understand assembly, you'll probably want to first get C (which is pretty much a glorified assembler anyway.)
Also, commonly used textbooks like this one may be good-- but, again, may assume more understanding of code than you have right now.
There may be some good class notes online for 1- or 2- level Computer Science classes, too.
posted by blenderfish at 11:21 PM on April 5, 2007
Response by poster: I'm surprised! I thought this was a question right up MeFi's alley. Thanks for the resources -- all of you! It sounds like what you're saying, blenderfish, is that there is no "in-depth" explanation of hardware without learning code? I'm still up for more books/websites if anyone else finds this.
posted by theantikitty at 7:25 AM on April 6, 2007
posted by theantikitty at 7:25 AM on April 6, 2007
Learning assembler code, while an interesting and worthwhile exercise in its own right, is absolutely not a prerequisite for understanding most of what's on PC Tech Guide at least.
Best thing you can do is keep digging deeper into areas that interest you personally. Do that enough, and they'll eventually start connecting, and you'll find you've built a "scheme of things" that works for you. And keep building systems.
posted by flabdablet at 8:24 AM on April 6, 2007
Best thing you can do is keep digging deeper into areas that interest you personally. Do that enough, and they'll eventually start connecting, and you'll find you've built a "scheme of things" that works for you. And keep building systems.
posted by flabdablet at 8:24 AM on April 6, 2007
As a professional operating system engineer, the books I most often find myself using are:
posted by atbash at 4:23 PM on April 6, 2007
- the Mindshare series, especially The Unabridged Pentium 4 (though parts of it are now somewhat dated) and PCI System Architecture
- the architecture documentation from Intel (Volume 1: Basic Architecture is most pertenent to your question), the processor datasheets and matching chipset datasheets, as well as many other pages on developer.intel.com
- as a more general reference, Computer Architecture, A Quantitative Approach, which is unfortunately priced like an engineering textbook, because it is an engineering textbook.
posted by atbash at 4:23 PM on April 6, 2007
theantikitty, it's not that you can't learn the "in-depth" way without first learning code, but the process of gaining a real in-depth understanding will also give you some understanding of code, and conversely, the process of learning to write very efficient code necessarily includes learning some in-depth workings of the machine the code is to run on.
The two are not separate things; they're different facets and specialties within one.
posted by atbash at 4:37 PM on April 6, 2007
The two are not separate things; they're different facets and specialties within one.
posted by atbash at 4:37 PM on April 6, 2007
Side note -- I see that blenderfish posted a link to the 4th edition of "Computer Architecture" (my link to which was to the 3rd edition). Thinking about this for a bit longer, as a beginner you're probably *much* better off first trying to find a copy of the first edition, as well as their other book in this series, The Hardware/Software Interface. These can basically be thought of as a 3-book series in order of and difficulty.
posted by atbash at 4:49 PM on April 6, 2007
posted by atbash at 4:49 PM on April 6, 2007
Response by poster: Thanks for all these additional answers! There's a whole lots of "in-depth" flying around in here right now. Looking forward to totally screwing up more PC systems (and fixing them) in the near future with your help. Thanks again!
posted by theantikitty at 7:35 AM on April 7, 2007
posted by theantikitty at 7:35 AM on April 7, 2007
This thread is closed to new comments.
http://en.wikipedia.org/wiki/Frontside_bus
The relationship between hardware and terms might not be explicitly stated, so understanding of the material will be required to see how everything fits in the scheme of things.
posted by PowerCat at 4:47 PM on April 5, 2007