How a computer works?
Hello Folks.
In your opinion which one of below books is good for learning how a computer works really : 1- Digital Design and Computer Architecture, Second Edition by David Harris and Sarah Harris 2- Inside the Machine: An Illustrated Introduction to Microprocessors and Computer Architecture by Jon Stokes 3- Structured Computer Organization (5th Edition) by Andrew S. Tanenbaum Thank you. |
Edit
|
All of these books, while very excellent books, are all very intense. Indeed, we'd all like to know what your objective is. (And a worthy objective it is!) :) Have you explored The World Wide Web for introductory material?
|
Code, by Charles Petzold.
|
I would recommend the 3rd one, Structured Computer Organization. I read it for my semesters, Good book.
|
I'd like to join sundialsvcs and ask just what the goal is. We could explay up to any technical level how the thing works, but...will that answer your question? :)
|
Quote:
Thanks very much for your guidance. I want to know how a computer works really and my goal is learning assembly language. In your opinion, is "Digital Design and Computer Architecture" good? |
Edit
|
If you want to learn assembly lang then start with 8085 or may be 8086 microprocessors books.
|
Quote:
|
Quote:
Experts don't try to understand how something like a computer really works. An expert really understands a narrow sub topic within that, then has a general grasp of the surrounding sub topics and some vague idea about the challenges and results of the distant sub topics. Quote:
How you learn assembly language depends a lot on why you want to learn it. If you are (or intend to be) a software engineer, a very good reason to learn assembly language is to improve your abilities at designing and debugging software in high level languages. Even if you will never include any assembly source code in a final project, knowing how you could do that is very valuable for developing high level language code (especially C++). If that is your purpose for leaning assembly language, then you should focus on learning a current CPU architecture (almost certainly X86-64) and on learning assembly programming in the form of functions called via a C interface. Most books, tutorials, online advise, etc. on learning assembly focus on 1) Obsolete architectures, in theory because they are simpler, but really because they author's skills are obsolete. 2) Either whole programs in assembly or even stand-alone (from boot) code in assembly without benefit of an OS. Many combine a little of (1) and (2) to focus on assembly programs in 16-bit x86 code to run under an MS-DOS emulator. If you want to learn assembly in order to better understand current high level language software development, all the above is a massive waste. For some other purposes for learning assembly, some of the above isn't as totally wasted, but it still isn't necessarily a good place to start. For almost any reason for learning assembly, starting with a focus on assembly functions callable from C is a more gentle introduction without wasting time of useless side topics. Quote:
You learn to program by programming, not by reading about it. A good online tutorial would help, but I don't know of one. As I said above, most focus on a really stupid way of introducing assembly. Quote:
When you (a beginner) write a program, be prepared to get the program wrong many times, including sometimes hanging it in a way that needs a task manager or kill command (etc.) to stop it. But that is just the program, not the session. MS-DOS is obsolete. A real OS protects the rest of your session from almost all programming accidents and protects itself from all of them (unless you abuse root privileges). Quote:
I tried to get my sons (while they were in Boy Scouts) to learn to start a camp fire with a flint. I also taught them quite a bit of computer programming and never any 16-bit x86 (much less 8085). Starting a camp fire with a flint is more worthwhile to learn today than 16-bit x86 asm. |
Quote:
Hello. I'm grateful really for your useful guidance. I want to Learn assembly langauge for Reverse engineering, Do you have any idea? |
Edit
|
Quote:
|
Quote:
In a real OS, such as Linux, the OS portion of each process's address space is protected against access. Whether you are using C or asm, you could execute an instruction telling the CPU to overwrite a byte of the OS, and that instruction would seg fault without actually overwriting any of the OS. |
All times are GMT -5. The time now is 06:32 AM. |