Essential Windows NT System Administration by AEleen Frisch Unconfirmed error reports are from readers. They have not yet been approved or disproved by the author or editor and represent solely the opinion of the reader. This page was updated June 19, 2000. Here's a key to the markup: [page-number]: serious technical mistake {page-number}: minor technical mistake : important language/formatting problem (page-number): language change or minor formatting problem ?page-number?: reader question or request for clarification Unconfirmed errors and comments: ?54? The Footnote makes no sense where referenced (3rd Sentence, 1st BulletedItem of "Resources for Custom Services"). Perhaps it should be referenced somewhere in the previous section ("Creating a System Initialization Script"). Or perhaps some clarification is required. (203) The second paragraph of the section Other options for backing up the registry. The word "hives" should be "files". {271} 6th paragraph; The correct syntax for using NET PRINT command to manipulate a print job is: NET PRINT \\HOST N /CMD, without specifying \PRINTER (419) The link for www.ntsecurity.net, is no longer valid. {434} Under "User Account Tools," it reads: "UseStat.Exe" Should read: "UsrStat.Exe" {436} NOTE sidebar; The redirection syntax is incorrect. Both of the examples that follow the phrase "In other words," need to have the numeral 2 precede the ">" greater-than symbol rather than succeed it. As printed: The form "2>&1" used by the UNIX Bourne shell to combine standard output and standard error is supported only if it follows the initial I/O redirection construct. In other words, "> file >2&1" but ">2&1 > file" doesn't. Should read: The form "2>&1" used by the UNIX Bourne shell to combine standard output and standard error is supported only if it follows the initial I/O redirection construct. In other words, "> file 2>&1" but "2>&1 > file" doesn't.