12.8 Troubleshooting Applications
12.8.2 Troubleshooting NT/2000 applications
Windows NT and 2000 often run into very much the same application errors that the Windows 9x operating systems have. For example, the application properties may be incorrect, the Registry entrees might be missing or corrupt, or the .DLL files may be corrupt. However, the Windows NT/2000 operating systems are usually part of an integrated network, which means that a whole new host of problems associated with the applications can occur. Users may not be able to gain access to folders, permissions that are set on files or folders may be too restrictive for the end user trying to access them, or the permissions may not be restrictive enough. The end users then may not be able to set any NTFS permissions on the files or folders containing the files.

Windows 2000 Task Manager
Windows 2000 provides a useful tool to use when troubleshooting applications. It is called the Task Manager. Access the Task Manager by pressing the CTRL+ALT+DEL buttons and then click the tab labeled Task Manager. The Task Manager displays a list of active applications and helps to identify the applications that are currently not responding. It can switch to a particular application to troubleshoot it if there are problems with it. Alternatively, choose to end the application, which will shut down the application if it has crashed and is not responding.

The processes tab provides information used to identify applications that might be slowing down the operations of the system. Sometimes when an application crashes it hangs the systems processor up as well, which will cause the rest of the system to lock up or slow down to a state that makes it unusable. The process tab tells the percentage of CPU usage that a particular application is using. If an application is not responding and it is "hogging" the CPU, shut down the application and see if the system returns to normal.

The performance tab allows users to view a graphical interface showing the processor performance and memory usage. Past and current usage can be viewed to obtain information about the applications that were running and at what point they caused the system to lock up.