Which version should you get? Get them all!
I found that reading the 4th edition helped in my understanding of the 5th edition (but am not sure if it's helping in the 1st ½ of the 6th Edition)
All the interesting stuff (IMO) is in the 2nd half (the debugging stuff). I've had the 1st half since it came out and haven't finished it yet (it helps me to fall asleep!).
While Amazon says it'll be released on 2 October - they also tell me that I won't get it until sometime after 9 October (I pre-ordered).
Not a big deal for me as I have a lot of reading to do - I also ordered:
Inside Windows NT (Windows Internals, 1st Edition)
Inside Windows NT, 2nd Edition (Windows Internals, 2nd Edition)
Inside Windows 2000, 3rd Edition (Windows Internals, 3rd Edition)
I've finished the first edition and am ½ way through the 2nd edition now.
It gives an interesting historical perspective - and some views on how the changes in later version came to be.
The Windows Internal books update with every version of Windows and are not retroactive, so you will not see content about Windows XP/Vista on the newest edition of the book. So personally to me the best option would be to get the latest one first to start off with, and then once you've gotten your feet wet a little, you can carry on to the previous versions so you can ascertain the differences between how Windows 7 works internally compared to Vista or XP. The 4th edition covering XP will show you how drastic in difference things are that changed when entering the Vista/Server2008 realm, but you won't notice these differences if you don't already have knowledge about the environment in the first place!
Also, mgrzeg, that's a sweet find, and looks like it got a good review already from Dmitry Vostokov (author of the Memory Dump Analysis Anthology). I'll snatch it up asap. Though despite its young age, I find it very odd that the guy would refer to "rings" for one. Rings is an old, old terminology dated back to the time of WinNT and 98, so that kinda sets a red flag for me. Nonetheless, it's cheap and looks valuable so I'll have a look-see. Thanks!
Bump. Added some databases to main article under Links O' Plenty. Always good to have large heaping amounts of data at your fingertips. I obviously didn't include DBs here at this site (or carrona sister site) since those are evidently already linked plentifully around here and everyone should know bout em by now.
Hmm, about the Pool tag database and its respective pooltag.txt file that you can put in the triage folder for your Windbg installations, I'm contemplating whether it's preferable to do that or not. It's evident there's a lot more tags in the one included with Windows 8 version of Windbg (188KB for mine) to the site's (92KB). However I do believe there's tags that were added by users of the site that are not incorporated into the default pooltag.txt file for Windbg. I'd like to merge new entries into the default pooltag file that are new from the site's, but not sure of the best way to do that.
w00t! Just received Part 2 of Windows Internals 6th Edition
A lot more Crash dump stuff than I recall from previous editions too!
Gonna have to read up on the Startup/Shutdown chapter also - so I can be prepared for even more changes in Win8.
I'm jealous. It sounds like it has a whole lot more in each section than the previous edition. I'm definitely planning on nabbing myself a copy in due time, though I have higher priority items to deal with at the moment. In due time, in due time.
It only shows up when the anchor name exactly matches the text to show to the user. If you or I were to, say, put an underscore before all anchor names, the problem would disappear entirely. But that is not a great solution. I will look into it. But if it is too hard, I might have to re-name your anchors in this way.
I am pretty sure that the problem lies in the "Automatically parse titles from external links" checkbox. When the URL (anchor) exactly matches the text to show to the user, it tries to parse the page title, and causes the problem you see. However, when anchor name does not match URL, it believes that the title has already been parsed, or has been set manually, so it does not re-parse it.