Rating: 
Summary: Not for beginners
Review: Having read this book half way, I believe it is intended for experienced developers instead of for beginners in device programming. Rather than offering a structural and formal introduction to the subject, it stresses on tricks and hints on selected topics like synchronization, pnp, read/write, etc. I now go for the DDK documentation for a more fundamental treatment. It cleared up instantly some of the questions built up as I read through the first five chapters of the book, like how a user mode application calls up the kernal mode driver. Nevertheless the author does give an authoritative insight in WDM programming. Incidentally, it is a matter of taste whether you like his informal writing style. As a beginner at the moment, I rated this book three stars. I might rate it differently when I returned to the book later.
Rating:
Summary: Be careful
Review: I am borrowing a copy of this book at work, and I agree with the other reviewers that its helpful, and it doesnt "talk down" But it can get quite rambly, the IO Request Chapter is a great example of this. That being said I actually tried to include his DEVQUEUE in my driver code im using at work...Ive been programming for 10+ years so im not a slouch. Problems:
1) C code written using C++ rules. This is annoying.
2) Doesn't compile at tighter warning levels...LOTS of warnings
3) Bug in DEVQUEUE initialization sent me on an IRP goosechase for good part of a day, and YES I did download his code service packs first. Watch out for stallcount being initialized to 1, StartNextPacket will refuse to run unless you change this to zero.
Rating:
Summary: Be careful
Review: I am borrowing a copy of this book at work, and I agree with the other reviewers that its helpful, and it doesnt "talk down" But it can get quite rambly, the IO Request Chapter is a great example of this. That being said I actually tried to include his DEVQUEUE in my driver code im using at work...Ive been programming for 10+ years so im not a slouch. Problems:
1) C code written using C++ rules. This is annoying.
2) Doesn't compile at tighter warning levels...LOTS of warnings
3) Bug in DEVQUEUE initialization sent me on an IRP goosechase for good part of a day, and YES I did download his code service packs first. Watch out for stallcount being initialized to 1, StartNextPacket will refuse to run unless you change this to zero.
Rating: 
Summary: A Painful Lesson Learned
Review: I got to this description of the first edition from a book list and ordered it. I read the book description and the reviews, but missed the one line recommendation from someone to get the second edition. So, I'm writing this as a review in the hopes that it will be more obvious so others won't waste money like I just did. Do a fresh book search on the title and buy the most recent edition. The 1 star reflects that this is an old edition. I'm sure the book itself is fine.
Rating:
Summary: WDM Newbies Warning: Use this book at your own risk!
Review: If you already know how to write WDM device drivers, you may or may not need this book. If you do not know how to write WDM device drivers, you would do yourself
a big favor by avoiding this book. It is so carelessly edited and
organized that I would feel justified in billing Walter Oney and his
publishers back for the time I have wasted dealing with things like this:
From page 184: ..."In fact, sometimes the easiest way to commence a new operation is to store
some state information in your device extension and then fake an
interrupt. Since either of these approaches needs to be carried out under
protection of the same spin lock that protects your ISR..." "Fake and interrupt?" This term is not defined or explained anywhere in the book that I could
find within an hour's search. "...the same spin lock that protects your ISR," is explained 121 pages later on page 305,
where it says "...(because the I/O Manager automatically allocates [a spin
lock] for you.)"
There are 26 pages of errata downloadable from Oney's web site. I printed
out the file, and I have to check it every page or two to make sure the
information on the page I am reading is correct. If you want to spend your time sorting through this mess
while introducing yourself to a topic as arcane as WDM, be my guest. You have been warned.
Rating: 
Summary: Must have
Review: If you are writing Windows Device Drivers, this is one of 3 books you absolutely must have. Buy it.
Rating:
Summary: Very Good Book but Misses Links
Review: If you're developing device drivers for a Windows operating system then this book is a must. I think this book is well organized and includes important information regarding all the aspects of developing Windows drivers. I also think that the book misses information on important web sites that can help developers.
Rating:
Summary: Very Good Book but Misses Links
Review: If your developing device drivers in 2000/2001 for a Windows operating system then this book is simply a must have. I purchased Chris Cant's book first because I had the misimpression that Oney's book was written a year earlier than it was and didn't really address Win2K as well as it does. I couldn't have been more wrong. Just flipping though the pages alone, it seems bigger and more authoritative. Code snips are kept quite small and the numerous diagrams and tables mean you don't have to keep refering back to the DDK as much or seaching for the right header file to find the definition of a perticular structure. You might also want to consider investing in some colored tabs at your local office supply store because you well spend a lot of time flipping between sections. If you can only get one book, get this one, or at least get this one first. But quite honestly you really need both books because each has it's strengths and it really helps to have the same thing explained in different ways and words. Plus you can never have too much sample code.
Rating:
Summary: Look No Further
Review: If your developing device drivers in 2000/2001 for a Windows operating system then this book is simply a must have. I purchased Chris Cant's book first because I had the misimpression that Oney's book was written a year earlier than it was and didn't really address Win2K as well as it does. I couldn't have been more wrong. Just flipping though the pages alone, it seems bigger and more authoritative. Code snips are kept quite small and the numerous diagrams and tables mean you don't have to keep refering back to the DDK as much or seaching for the right header file to find the definition of a perticular structure. You might also want to consider investing in some colored tabs at your local office supply store because you well spend a lot of time flipping between sections. If you can only get one book, get this one, or at least get this one first. But quite honestly you really need both books because each has it's strengths and it really helps to have the same thing explained in different ways and words. Plus you can never have too much sample code.
Rating: 
Summary: Essential for your WDM Library
Review: Is one of several *essential* books for WDM Programming. Also see Chris Cant's book. Walter's is a bit more detailed, Chris's more approachable. You need both. This is an extremely difficult topic, and Walter does a good job of making it understandable. USB Chapter is also quite good.
| 
