Errata for Windows® Internals, Part 1

Under EXPERIMENT: Viewing Process Details with Process Explorer: "The first time you run it, you will receive a message that symbols are not currently configured." Running Process Explorer v15.13 dated 2/16/12, upon first use on Windows 7 x64, no prompt or message was encountered.

Note from the Author or Editor:
The sentence should be: "The first time you run it and go to the the Threads tab of a process' property page, you will receive a message that symbols are not currently configured."

The URL http://msdn.microsoft.com/en-us/windows/hardware/gg462988.aspx was changed by Microsoft to be http://msdn.microsoft.com/en-us/windows/hardware/hh852360 It is a minor issue for now because Microsoft made a redirection from the old URL to a new one. But it can become invalid overtime.

Note from the Author or Editor:
Reader is correct, the URL has changed.

"A driver can register its own callback and context with NtSetInformationAlpcPort". It doesn't seem such a function exists - at least not on Windows 7 x86. Perhaps, you are mistaken it with nt!NtAlpcSetInformation?

Note from the Author or Editor:
Reader is correct, NtAlpcSetInformation should be used instead of NtSetInformationAlpcPort.

"Both completion lists and message zones can be set with NtAlpcSetInformationPort". Again, it doesn't seem such a function exists - at least not on Windows 7 x86. Perhaps, you are mistaken it with nt!NtAlpcSetInformation?

Note from the Author or Editor:
The reader is correct. NtAlpcSetInformationPort should be replaced by NtAlpcSetInformation.

Book text says: "Data stored in a profile’s key includes the time of the last load of the profile in the ProfileLoadTimeLow value" Comment: That was probably what the registry values ProfileLoadTimeLow and ProfileLoadTimeHigh were added for. However, their value is always set to 0.

Note from the Author or Editor:
Correct. The sentence quoted in the book text should be removed.

..., which sets priorities of 4, 8, 13, 14, 6, and 10, respectively. should be ..., which sets priorities of 4, 8, 13, 24, 6, and 10, respectively. lkd> dd nt!PspPriorityTable 82e089e0 00000008 00000004 00000008 0000000d 82e089f0 00000018 00000006 0000000a

Note from the Author or Editor:
The reader is correct with his errata.

Base Priority: 8 Dynamic Priority: 12 should be: Base Priority: 24 Dynamic Priority: 24

Note from the Author or Editor:
The reader is correct unfortunately we cannot change the image in a reprint, can we?

"Windows Server 2008 R2 Enterprise Edition and Windows Server 2008 R2 Datacenter Edition include an optionally installable component called Windows System Resource Manager (WSRM)" Since Windows Server 2008, WSRM is included in all SKU

Note from the Author or Editor:
The author is correct. The sentence should say Windows Server 2008 R2 Standard Edition and higher SKUs include an optionally installable component called Windows System Resource Manager (WSRM)

Shouldn’t the dispatch arrow go *from* ready/standby/deferred *to* 2 (running)? In the above diagram, there appears to be no way to actually reach the running state. Am I missing something? At the very least the head of the arrow should end at a node, not a label.

Note from the Author or Editor:
The reader is right and the arrow should be flipped.

"Distributed Fair Share Scheduling" is actually called "Dynamic Fair Share Scheduling"

Note from the Author or Editor:
Reader is correct.

This is illustrated in Figure 6-3 using the Sysinternals Winobj tool, showing the security descriptor for a section object in the user`s session. Should be: ... for a event object in the user`s session.

Note from the Author or Editor:
The reader is partially correct. The correct sentence should be: ... for an event object in the user's session.