Errata
The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".
The following errata were submitted by our customers and approved as valid errors by the author or editor.
Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
Version | Location | Description | Submitted By | Date submitted | Date corrected |
---|---|---|---|---|---|
Printed, PDF | Page 409 2nd paragraph |
The text of the secnod sentence reads "was spent inside a function called COMCTL32!EditML_BuildcchLines." Note from the Author or Editor: |
Roger Orr | Jul 24, 2013 | |
Printed, PDF, ePub | Page 198 4th line of the last paragraph |
Missing 0 in hexadecimal value: |
Tarik Soulami |
Jul 01, 2013 | |
Page xxix several pages. |
Page xxix Note from the Author or Editor: |
Hans De Smaele | Jun 02, 2013 | ||
Printed | Page 220 code listing |
In the code listing at the bottom of the page, "g_fAttached = false;" should be "g_bAttached = false;". The downloaded code sample is correct. Note from the Author or Editor: |
Andy Dittrich | Apr 07, 2013 | May 17, 2013 |
Page xxix 11 pages duplicated |
Introduction (xvii - xxviii) is duplicated on xxix - xl. Note from the Author or Editor: |
joehtg | Mar 03, 2013 | Apr 26, 2012 | |
Printed | Page Introduction 5. |
Then Install the components to the C:\ DDK\ 7600.16835.1 directory, as shown in the following screen shot. This step will take several minutes to complete. |
Keith Chalmers | Oct 22, 2012 | May 17, 2013 |
Page xxvi 8th element of numbered list |
When building the Code Samples via the macro "bcz", it's important to use the same command prompt window already opened in the 7th step for setting the environment via "setenv.bat". Note from the Author or Editor: |
Stefano Capelli | Sep 10, 2012 | ||
Printed, PDF, , Other Digital Version | Page 62 Near the end of the page |
The note states that enabling kernel debugging through the boot menu results in hard-coded COM connection settings being used by the system. It then goes on to indicate that 19,200 bauds and the highest enumerated COM port are used by default. In Windows Vista and later, the defaults are now instead COM1 and 115,200. |
Tarik Soulami |
Jun 25, 2012 | May 17, 2013 |
Printed, PDF, , Other Digital Version | Page 438 1st paragraph |
On page 438 you wrote that the xperf.exe symbols are not on the symbol server and the callstack always shows xperf.exe!? |
Andr? Ziegler | Jun 04, 2012 | May 17, 2013 |
Printed, PDF, , Other Digital Version | Page 7 Service Packs paragraph |
On page 7 you write hat Vista had 3 service packs. But Vista / Server 2008 only have 2 service packs. The SP2 was released in 2009 and the mainstream support ended 2012 so there will be no Sp3. Windows XP had three Service packs. Note from the Author or Editor: |
Andr? Ziegler | Jun 04, 2012 | May 17, 2013 |
Printed, PDF, , Other Digital Version | Page 107 Code sample, line 11 |
The code refers to Console.ReadLine("Exiting..."). This is obviously a typo for Console.WriteLine. Note from the Author or Editor: |
Ben Monroe | May 26, 2012 | May 17, 2013 |
Printed, PDF, , Other Digital Version | Page 47 First listing |
When using the x86 version of windbg.exe and notepad.exe on an x64 host Windows OS, the call stack displayed by the k command stops at ntdll!KiUserCallbackDispatcher. Reason: the x86 version of the debugger doesn't handle the WOW64 call frame in this case, so it fails to decode the rest of the call stack. |
Tarik Soulami |
May 25, 2012 | |
Printed, PDF, , Other Digital Version | Page 389 Table of contents |
Chapter 13 Common Tracking Scenarios |
Tarik Soulami |
May 25, 2012 | May 17, 2013 |
Printed | Page intro xxv #5 at bottom |
"5. Then Install the components to the C:\DDK\7600.16385.1 directory, as shown in the following screenshot..." Note from the Author or Editor: |
matt grossman | May 24, 2012 |