Tools that can be borrowed when Windows NT system crashes

Windows NT is an operating system with high reliability and advanced level. It is also one of the most advanced and reliable systems. But any operating system may be out of order. Windows NT is no exception. And as one of the most complex systems, it can crash from time to time, and even a very serious crash can be helpless. If this is a serious situation, some of the tools described below may be helpful to the user. Power failure sound card repair In the CD-ROM version of Windows NT, there are a lot of tools, which can play a role in the system crash. They are stored under the directory \\SUPTOOLS. The following will be introduced one by one. CPU installation settings NTDETECT This command can be used to assist in hardware troubleshooting when a system failure occurs during machine startup to detect hardware failure. This command is actually used as a .COM file and a .CMD batch file. NTDETECT has a mechanism for data dumping of boot information detected by Windows NT during system startup. With NTDETECT, after the information has been dumped, it can be determined whether the source of the fault is because it has not found its part. 2. SMBTRACE This is a character type application. It captures SMB information from servers and channel indicators and controls and selects how information is captured, how captured, and whether it affects system performance. As a server message fast tracking program, it plays a huge role in helping network experts determine network failures, or in some ways, has the role of network detectors. 3. The two software functions I386KD.EXE and MIPSKD.EXE mainly recognize and display fault conditions in the Windows NT kernel. They act as kernel debuggers and can be considered the most unusual tool given to software by operating system manufacturers. They are extremely powerful and their use is far beyond the scope of this book. To put it simply, to use the kernel debugger, first connect the machine to be debugged with another computer using a modem or a null modem cable, run the debug software on the other computer, and perform the test on the machine being tested. Kernel testing. Just to say this, users may not be able to learn to use the software, but they can use the Windows System Development Toolbox (System DeveloPment Kit) or Microsoft's toolbox to learn more. On the CD-ROM, there is a file SUPTOOLS.HLP under the \\SUPTOOLS directory, which contains help information for each tool. However, for this command, it is very simple to talk about, only a few lines of help information. 4. PMON.EXE This is a character file. Its task is to monitor process resources and give detailed information about process execution, including line flow statistics, the size of the working set, and other content. Compared with the Windows NT performance monitoring program, it not only completes the NT performance monitoring function, but also provides an optional user interface, so the information provided is more detailed and comprehensive. 5. PVIEWER.EXE This is a graphics program. Its functionality is consistent with PMON.EXE and provides detailed information about the process. It also includes the functionality of the Windows NT Performance Monitor, which provides an optional user interface for the user. 6. DRIVERS.EXE This program functions to display information about the device driver software. It is extremely helpful for accessing low-level hardware devices to debug faults. 7. EXETYPE.EXE This program functions to display the type of an executable and its subsystems. It is a simple program with only a few command lines. When the system runs an executable file, the command can be: exetype where the file name indicates the executable file name of the problem. At this point, the command will specify what program the current program is, whether it is Windows NT, OS/2, or a 16-bit Windows NT program, which specifies the set of instructions that may be helpful in pinpointing the cause of the failure. 8. PSTAT.EXE This is a character type program. Its function is to display all programs running in the system and their status information. 9. REGINI.EXE This is a command line program. Its function is to change the command of the registry by changing the command draft (scriPt). If you want to modify the registry contents of each system, you can use the registry script and execute the command REGINI.EXE on the command line. This also means that with the system's login script, you can change the registry contents of multiple systems at the same time. However, this command is powerful and dangerous (similar to the registry editor). When the manuscript was changed, several registries were changed at the same time, but at the same time, all the servers (or workstations) were changed like machine guns, so use them with caution. In Microsoft, the manuscript format of the registry is not available. However, some related registry document formats can be found in the FIFO.OFF and FIFO.INI files. Those files are related to the FIFO.CMD file and are placed in the directory SUPPORT/SUPTOOLS/I386 on the CD. However, remind the user again, use this command with caution. Before using the REGINI.EXE function, test it on a single Windows NT workstation and make sure that the changes do not cause the system to restart before it officially acts on other systems, especially the server. This will confirm that the modification is safe. 10. FIFO.CMD This file is actually a batch file. Its function is to enable the modem to support first-in first-out buffering when needed. This feature can also be implemented through a series of equivalent operations in the Registry Editor, or it can be set in "Ports" by "ControlPanel". Multiple character files are mentioned here, the purpose of which is to emphasize that these files can be run in ScriPt manuscript files. Microsoft has made the following recommendations for these tools: These tools were developed as part of MicrosoR Product SuPPort Services and are only intended to be trouble-shooted under the direction of a Microsoft Systems Support Engineer. Any other use is an adventurous act. In addition, these tools are provided without any authorization. Microsoft does not recognize the use of them for any commercial warranty or other specific purposes. When users really want to use these tools to test certain failures, it is best to have a Microsoft Knowledge Base on the Tech Net CD or ComPuserver; the Microsoft Knowledge Base, where the information stored will provide guidance to the user. However, when the user encounters a problem that no one has ever encountered (such as when the Windows NT was just loaded), no reference information will be found in the Knowledge Base at this time, because the support in the knowledge base is now available. There is too little information. At this time, it is best not to rack your brains, or to ask engineers, especially for low-level failures.