System information

stack that the application was on when the error occurred. The fifth field is
the time/date that the error occurred.
•
The next two log sections indicate what was in the various CPU registers at
the time of failure. The 32-bit registers are listed separately in the second
register section.
•
The System Info section provides information about the system and
Windows. User name and Organization are taken from Windows .INI files.
•
The Stack Dump section is divided into frames. You can find out what was in
the stack before the fault occurred in this section, in the first frame (0), by
locating its memory location in the stack. The memory location was
indicated in the third field of the $tag$ line.
•
The final section lists the applications running from the tasks list. The
number of tasks running can be found in the System Info section.
A user description appears at the end of the log. These lines are preceded by a
#> (for example, 1>, 2>, and so on).
2.2.7.2 Troubleshooting with Dr. Watson
The Dr. Watson log file is intended for debugging purposes. The more Windows
NT knowledge you have, the more useful the Dr. Watson log file will be. At the
very least, it can help isolate what application and module caused the error. In
general it is more important which module caused the error than the application
you were in when the error occurred. For example, the following log in the
failure report section shows an error that could have been associated with the
display driver:
Dr. Watson 0.80 Failure Report- Wed Apr 17 16&colon42&colon34 1996
Write had a ′ Code Segment (Read)′ fault at Display 2: ld70
$tag$WRITE$Code Segment (Read)$Display 2: ld70$mov
In this example, the program that caused the error message was Write and the
module is Display. The first troubleshooting step in this case would be to test
Write while using a different video driver.
It is important to remember that Dr. Watson is a diagnostic tool, and not a cure
for a problem. Having Dr. Watson will not prevent an error from occurring, but
the information in DRWATSON.LOG can help isolate the problem.
2.2.8 Windows NT License Management
Windows NT Server has its own License Management built in. This can handle
the client access licenses of the Microsoft BackOffice products installed in the
network. Microsoft BackOffice Products are NT Server, MS SQL Server, MS SNA
Server and Systems Management Server (SMS).
The purchase of any product able to access the MS Server Products does not
automatically include a client access license. For example, Windows 95 does not
include a license to access a Windows NT Server. For every server product, an
access license must be purchased separately except with the BackOffice Client
Access License which includes all server products.
Microsoft has two different license agreements:
•
License by server
•
License by seat
Chapter 2. NT Systems Management Functions 65