Instruct: Classify a given Amazon review as either positive or negative.
Query: Not as advertised, but useful

This book isn't really about "how to debug" - it's more a reference on the Microsoft toolset. Prentice-Hall seems pretty bad about hype on the cover. But in that context, it isn't bad. The appendixes are fairly detailed on stop codes, error codes, and as a command reference. The chapters are pretty well written. It's obvious in places that the author moved from describing NT4 to describing Windows 2000 a little carelessly. He skims over some of OEMTOOLS stuff (like driver verifier), and is a little terse on how to write debugger extensions. The sections on setting up and using the tools is good, the sections on remote debugging seem useful. Lot of good stuff, even if not as deep as could be. If you're looking for tutorial on how to isolate deadlocks by tracking through thread structures for locks, then ain't it. Take the osr course ... . Is it worth my $40 as a driver developer? I think it is.