Rating: 
Summary: 2000 Systems Programming at its best!!!
Review: As a former systems programmer on Burroughs (Unisys) systems, I was always used to knowing how the OS did things. It is a real treat after working on PCs for so long, to finally get a book that makes it interesting to learn the internals again. This book is full of things that will give you an appreciation of any OS, but the way it cracks into the guts of 2000 is great. The experiments in this book make it really easy to learn how 2000 is organized and apply it to existing programming projects. Learning 2000 from the inside via the debugger is just a great way to do it. No offense to David, but Mark's influence is obvious. If you are a fan of his Internals column, you will like this book even better. The fact that he does it without source code is even more amazing. Wait a minute...why hasn't Microsoft paid these guys whatever they want to build the next version of 2000?
If you appreciate a good OS and an even better manual on it...Buy This Book...
Rating: 
Summary: Well written book
Review: I bought this book to supplement my knowledge on OS implementations and more immediate to understand better programming technicues found in Jeffrey Richter book. The book covers wide variaty of issues from logon to cache manager. Some chapters written excellent like thread scheduling and interrupt handling, while others are barely readable. Memory management chapter is far from being clear, so is cache manager. The security chapter could contain more material. Another issue is chapter order, I believe memory management chapter should be sooner. Chapters are too tight connected, sometimes you need to read chapters in parallel to understand. But, if you already familiar with windows programming on advanced level this book is good purchase.
Rating:
Summary: Well written book
Review: I bought this book to supplement my knowledge on OS implementations and more immediate to understand better programming technicues found in Jeffrey Richter book. The book covers wide variaty of issues from logon to cache manager. Some chapters written excellent like thread scheduling and interrupt handling, while others are barely readable. Memory management chapter is far from being clear, so is cache manager. The security chapter could contain more material. Another issue is chapter order, I believe memory management chapter should be sooner. Chapters are too tight connected, sometimes you need to read chapters in parallel to understand. But, if you already familiar with windows programming on advanced level this book is good purchase.
Rating:
Summary: The Dream Team (David & Mark)
Review: I got this book 6 days ago, and I've read chapter 1 - 7 so far, the way these two gods explain and show how the internal win 2000 system works is just impressive. If you have read Inside Windows NT 2nd edition by Daveid A Solomon, you know what you are up for, David teamed up with a crazy russian Mark Russinovich which has practically made Windows NT (2000) Magazine worth reading. ;)The only thing I'd love to see in the future is a little more coverage of the terminal services part of it. (2 pages isn't enough), and maybe a little more deep hands on experiments. All handson experiements seems to be pretty much "overview and simple". But you can't have it all, this nearly 1000 page book is like a design document for NT/2000. >=] But no doubt, if you develop NT tools or sysadmin NT network this book is a *MUST*! If you don't have it, HURRY UP AND BUY IT NOW! Also, remember to visit http://www.sysinternals.com for the best utils for NT. (And maybe the most stable ones. ;)) Terje
Rating:
Summary: Is a good book, but not very good
Review: I have interest in mechanism of microsoft windows 2000/NT, since windows isn't a free OS, I have to read books instead of source code. The book is a famous one focused on system mechanism of win2k,I read it, sure, I got much knowledge from it,but I find it's a little mussy, and not very clear, it's also not detailed enough to understand microsoft win2k/NT.
The book "Understanding the Linux Kernel" By Daniel P. Bovet, Marco Cesati is much better than this one.
Rating:
Summary: Good for students
Review: That's a great book for students that wants to learn how work modern operating systems.
Rating:
Summary: Must have for any Windows Develepor
Review: This book explains windows 2000 internal workings in reasonable breadth and sufficient depth. This book is MUCH better than the 2nd Edition of Inside Windows NT, perhaps because of Mark's contributions.
The only problem with this book is that, inspite of being huge, it is only one volume. I think Windows 2000 is too extensive to fit in one book, and though the book is great for getting at many of the principles, you need to look at the DDK/SDK documentation to get more details, and actually use them in your work. At this level the book provides a great starting point to delve into OS internals, but perhaps someone needs to write a book for each chapter to do justice.
Rating:
Summary: Great book
Review: This book has it all. The most comprehensive overview of Windows you will find anywhere
Rating:
Summary: Great Book
Review: This book is filled with more info than I could've hoped for (aside from source code examples). In addition, the correlation between Win32 APIs and OS implementation is quite helpful. Highly recommended for anyone that needs to gain an understanding of how the OS they are using / developing for works.
Rating:
Summary: clear and interesting, but some things are left out
Review: This book is interesting for people who want to learn about what goes on under the hood of Windows 2000. The authors' style is clear and easy to understand and there is a good wealth of precious, in depth information.
It would have been even better if more details were included: some system mechanisms are mentioned, but the details are left out (particularly on LPCs). Also, the book is not oriented toward experimenting with the system by means of writing kernel mode code: nearly all of the experiments are based on the usage of tools. I think the book could have had room for something more if a number of pages of data structures listing (returned by Kd commands) were left out, particularly since these listings have very few comments and therefore add very little to what everyone can get from the debugger.
| 
