<< 1 >>
Rating: 
Summary: Plan to spend a lot of time looking at other references.
Review: a = b, c, and d.
e = f, g, and h.
b > e while a < f.
ac < gh while fh < bd.
c can be diagrammed in this box if you use h.
g is shown in this truth table if you use a.Part of what makes this text so difficult to understand is the author's inability to use consistent terms while trying to explain material. In the first chapter, a simple And gate is referred to as 'AND', 'x^y', 'x.y', 'xy', '()()', and 'and'. All true, but used interchangeably while trying to explain makes the concepts incredibly difficult to decipher, particularly when variations for representing other boolean concepts are added to the fray. The best part of the book, as far as I can tell, is that the key terms are in bold so I know what to plug into Google to try and figure out what it is.
Rating:
Summary: Plan to spend a lot of time looking at other references.
Review: a = b, c, and d.
e = f, g, and h.
b > e while a < f.
ac < gh while fh < bd.
c can be diagrammed in this box if you use h.
g is shown in this truth table if you use a. Part of what makes this text so difficult to understand is the author's inability to use consistent terms while trying to explain material. In the first chapter, a simple And gate is referred to as 'AND', 'x^y', 'x.y', 'xy', '()()', and 'and'. All true, but used interchangeably while trying to explain makes the concepts incredibly difficult to decipher, particularly when variations for representing other boolean concepts are added to the fray. The best part of the book, as far as I can tell, is that the key terms are in bold so I know what to plug into Google to try and figure out what it is.
Rating: 
Summary: The best computer architecture book I have ever read.
Review: I read the entire book from cover to cover for a computer engineering course. It definitely went well beyond my wildest expectations in depht and material. Dr. Carpinelli begins each section by relating the new topic to a "Very Simple CPU", then to a "Relatively Simple CPU", and finally to an Intel 8085 processor. This gradual approach is what really makes this book so good, and is what helped me absorb the material so well.
Rating:
Summary: Excellent book for Computer Architecture.
Review: I used this book in Com. Architecture course. It's cover everything from state machine design to parallel processing. Every topics come in correct order and very clear in explanation and example. A lot of pictures and excellent organize.
Rating:
Summary: This book is a failure
Review: I was forced to buy this book for my Architecture class. I really regret wasting my money on it. In short, the book [stinks]. It assumes too many things. It does not do a very good job explaining some important pieces of information. For the most part, the student will spend the whole time trying to make sense out of what the author is saying. It is one of these "should've..could've" books!
If you are looking for an architecture book, I wouldn't recommend this one.
Rating:
Summary: This book is a failure
Review: I was forced to buy this book for my Architecture class. I really regret wasting my money on it. In short, the book [stinks]. It assumes too many things. It does not do a very good job explaining some important pieces of information. For the most part, the student will spend the whole time trying to make sense out of what the author is saying. It is one of these "should've..could've" books!
If you are looking for an architecture book, I wouldn't recommend this one.
Rating:
Summary: WOW!!!!
Review: Read this book for a Computer Architecture class and let me just say, Wow!!! This is a great book, front to back. Although the book claims to not have a prerequisite, I would not recommend it. A little background in electronics and knowledge of a high level language would surely give you a good background to get the most out of this book.
Rating:
Summary: A failure for purely academic reasons
Review: The first chapter is the most important in the book. And yet it is riddled with poor grammar, truth table errors, no answers to questions in the back of book etc. I don't understand how someone who understands the subject can convey so little meaningful information. Actually I do understand, and this book's academic blasphemy should be burnt black as ruined toast. Money down the drain, as Ricky Ricardo "splained" things to Lucy at a much higher level. This book leaves me bitter if you hadn't noticed.
Rating:
Summary: Keep Lookin
Review: This book was required for my Computer Systems & Architecture class. The other reviewers did a good job of highlighting how bad this book is. The only thing I will add is, if this book is required for a course you don't really much choice other than to buy it (so good luck). If you're buying this book for the sake of learning about computer architecture I would not recommend this one.
<< 1 >>
| 
