The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
| Version |
Location |
Description |
Submitted by |
Date submitted |
| Printed |
Page 10
The last complete paragraph on the page reads: "The event logging |
service does not support the capability of creating user-defined or
application-specific event logs."
This is not true. The native NT event viewer can only see the three standard
logs, but as Kevin Miller in "Professional NT Services" WROX Press points
out, the event logging API allows you to create any additional logs you want.
You will just have to write your own custom event viewer for examining these
logs.
|
Anonymous |
|
| Printed |
Page 157
In the first code example on the page, I believe that the hyphen |
(dash) characters are invalid in the filenames in:
LanguageNames=(
English=0x409:Evt-English-0x409
German=0x407: Evt-German-0x407
French=0x40C: Evt-French-0x40C
)
Underscores do seem to be acceptable
|
Anonymous |
|
| Printed |
Page 163-165
In the sample source code for DisplayEventLogRecords() |
routine, there are two problem issues:
1. The prior source sample, ReadAllLogRecords(), refers to a routine
named ParseEventLogRecords(). ParseEventLogRecords() does not exist
in the book. However, DisplayEventLogRecords() has the same calling
parameters and usage ... I suspect. Maybe one of these two names
should become the other?
2. In the source code on page 164, pData and pStr are never
initialized before the while() loop starts. So it is possible for
the first iteration of the loop to incorrectly assume that data is
available.
The pStr case is fine. The loop that processes it will exit before
using the bad pointer.
The pData case will print "Binary Data:
" when in fact there is no
binary data. Again the bad pointer is not actually used due to the
processing loop's exit prior to using the bad pointer.
Trivial issues? Yes. But should someone copy/paste portions of this
code, they could end up with bugs ... and unhappy about it.
|
Anonymous |
|