How to Delay Loading of Specific Services
Microsoft Knowledge Base Article:
193888 - In some computers, especially
older systems and those with slower peripherals,
it may be necessary to delay the loading
of a specific Windows NT service for the
computer to boot properly.
How to Disable Dr. Watson for Windows NT
Microsoft Knowledge Base Article: 188296
This article describes how to disable
and re-enable the Dr. Watson program
for Windows NT.
How To Guard
Against Boot Failure With a Windows
NT Boot Disk
Microsoft Knowledge Base Article: 101668
When Windows NT is installed on a computer
that has an Intel x86-based processor
and the boot record for the active partition
or files required to boot Windows NT
becomes corrupted, it is not possible
to boot Windows NT or any other operating
system on that computer. To guard
against this situation, create a Windows
NT boot disk when you install Windows
NT on the computer. This disk is different
from an MS-DOS boot disk because the
entire Windows NT operating system cannot
fit on one disk as MS-DOS can. A Windows
NT boot disk contains the files necessary
to start the operating system with the
remainder of the Windows NT system files
installed on the hard disk drive |
How to Eliminate a Hung Process without Restarting the
Computer
Microsoft Knowledge Base Article: 171773 If
a program or process is not responding (hung)
waiting for user input, and cannot accept input
or be terminated, usually the only way to terminate
the process is to restart the computer.
How to Kill an Orphaned Process
Microsoft Knowledge Base Article: 197155 When
a service terminates abnormally, it sometimes
leaves "orphaned" child processes behind. This
article describes several ways to remove such
a process.
How to Perform an
Emergency Shutdown in Windows 2000
Microsoft Knowledge Base Article: 279134 - This
article describes how to shut down your Microsoft
Windows 2000 operating system in an emergency
situation.
How to Replace Files
In Use at Windows NT Restart
Microsoft Knowledge Base Article: 181345 - If
you need to replace a file that is in use by
Windows NT, you normally must use one of the
following methods:
How to Save a Device
Manager Report to a Text File
Microsoft Knowledge Base Article: 255979 - Describes
how to generate a Device Manager report and
save it to a text file.
How to Set Up a Remote Debug Session Using a Modem
Microsoft Knowledge Base Article: 148954 This
article describes the procedures for preparing
an X86 Intel- processor-based and RISC-processor-based
computer running Windows NT Workstation or Server
for a remote debug session.
How to Set Up a Remote
Debug Session Using a Null Modem Cable
Microsoft Knowledge Base Article: 151981 This
article is intended to describe the procedures
for setting up the debugger on a Windows NT
system using a Null modem cable attached to
another Windows NT system.
How to Troubleshoot
Event 9 and Event 11 Error Messages
Microsoft Knowledge Base Article: 154690 - An
error message similar to one of the following
appears in your system log (as seen with Event
Viewer), although the source can be any controller
name (for example, Atdisk, Atapi, or Sparrow):
How to Troubleshoot
Duplicate Media Access Control Address Conflicts
Microsoft Knowledge Base Article: 164903 - If
Windows NT detects a duplicate media access
control address on the network, you will receive
one of the following messages in the Windows
NT System Event Log:
How to Use the Special
Pool Feature to Isolate Pool Damage
Microsoft Knowledge Base Article: 188831 - Pool
damage may be the root cause of many of the
most evasive issues with Windows NT. Pool damage
is caused when a kernel-mode component writes
to memory outside of its allocated pool area.
By writing to memory beyond the boundary of
its allocated area, it is likely that another
area of allocated memory, possibly owned by
another component, is overwritten. This damage
can cause problems such as blue screens in completely
unrelated areas of code. A kernel-mode component
reading beyond its allocated area can also cause
problems.
Specifying the Debugger
for Unhandled User Mode Exceptions
Microsoft Knowledge Base Article: 121434 - Windows
NT allows you to specify a post mortem debugger
for unhandled User mode exceptions. A general
protection (GP) fault message is one of the
many examples of a User mode exception. This
allows you to see what went wrong in the code
by examining where the program caused the fault,
as well as the condition of registers, memory,
and the stack. By default, Windows NT used a
32-bit version of Dr. Watson as a post mortem
debugger. You can change the default debugger
for unhandled user mode exceptions, by editing
the registry
|
