A little over a year ago, I found a good solution to the problem of repairing Windows NT. This solution uses a utility that I purchased off the Internet: ERD Commander Professional by Winternals Software. This wonderful utility is available from the Winternals Web site for about $324 US (winternals).
ERD Professional creates a series of boot floppies that can gain full read and write access to any partition on a Windows NT system. Because the utility was built on top of the three boot floppies that ship with Windows NT, it can access stripe sets and mirror sets. This utility can access things like the Service Control Manager directly from the command prompt without having your to edit the Registry. You can even use it to change Windows NT passwords from the command prompt of a damaged system. In short, ERD Commander Professional is an absolutely awesome utility, and it's worth every penny of the price if you still support Windows NT 4.0 systems.
Unfortunately, ERD Commander Professional has one big flaw. It supports all the built-in Windows NT mass-storage devices and disk controllers--but if you're using a disk controller that requires a third-party driver, you're out of luck (at least in the year-old version that I have).
Have you ever experienced a Windows NT 4.0 system crash? In such a situation, the ideal reaction is to simply format the hard disk and reload it using a standard disk image. Unfortunately, many smaller companies aren't set up to use standard workstation configurations. In such companies, users often save data to their own local hard drives. Similarly, you don't want to reformat the hard disk on a server if you can avoid doing so.
In these situations, performing a repair can be extremely difficult because of the way that Windows NT protects itself. However, Windows 2000 offers a new utility called the Recovery Console that can help you recover from an operating system crash much more quickly. In this article, I'll discuss the Windows 2000 Recovery Console. As I do, I'll explain how to install it, and I'll provide some basic information for using the extended command set that's associated with the Recovery Console.
Trying to Repair Windows NT
Before you can truly appreciate the Recovery Console, you need to know something about repairing Windows NT 4.0 the old-fashioned way. The difficulty of repairing a Windows NT crash depends on several factors, including whether the operating system will start, the amount of free hard disk space, and the file system loaded on the system's hard disk.
The problem with repairing Windows NT is that NT is designed to prevent you from accessing the hard disk (assuming it's formatted with NT File System [NTFS]) unless you do so through the operating system. If Windows NT has crashed completely, you can't even begin to think about repairing Windows, because you can't access the hard disk. Even if your hard disk happens to be formatted in the file allocation table (FAT) format, accessing it could be impossible outside Windows NT if the hard disk is part of a stripe set or mirror set. It could also be impossible to access certain types of hard disks--such as SCSI disks--outside of Windows NT.
If the NT operating system has crashed completely and you can't access the hard disk from a boot floppy, you have only a couple of options. First, you can reformat the hard disk, reload Windows NT, and restore a backup. However, this solution is no good if you don't have a backup or if you need to preserve any data added to the system since the last backup.
The recommended Microsoft solution is to install a second copy of Windows NT. Naturally, this copy should go in a different directory than the original copy. Once you've installed the second copy, you can use it to access the hard disk and thus repair the original damage. This method has several problems, though. First, it won't work if you don't have enough free hard disk space to load a second copy of Windows NT. Second, even if you do manage to load the second copy and are able to access your hard disk, you still face the difficult task of trying to repair the original problem without being able to use any portion of the old operating system.
For example, suppose you enabled a service in Windows NT that caused the operating system to crash. Now, suppose this service starts automatically upon boot-up and results in an instant blue screen of death. You'd have to be really sharp to repair this problem using the second copy of Windows NT, because you wouldn't be able to access the Service Control Manager directly to shut down the menacing service. Instead, you'd have to figure out which files composed the Registry and edit those files to disable or remove the service that's causing the problem. Doing so can be very difficult, especially if you don't live and breathe Windows NT--if you don't know exactly what you're doing, you can further damage the old operating system.
Repairing Windows 2000
Here are some of the new commands available in the Recovery Console DOS window:
As you can see, repairing a failed copy of Windows NT 4.0 can be difficult and time consuming, at best. However, Windows 2000 has a much better solution directly built into the operating system. The Recovery Console utility lets you access the hard disk of a failed system directly from the command prompt.
Once you access the command prompt, you can perform a variety of hard-disk repair functions by using built-in utilities. You can also perform any necessary file manipulations regardless of the file system or the type of hard disk the files reside on.
About the only edge ERD Commander Professional (discussed in the sidebar "Repairing Windows NT with ERD Commander Professional") has over the Recovery Console is the ability to reset passwords. This ability is very handy, should someone "accidentally" change the Administrator password, because you can't access the Recovery Console without providing the Administrator password. Fortunately, according to the Winternals Web site, ERD Commander Professional will work with Windows 2000 as well as with Windows NT 4.0. Therefore, I recommend keeping a copy of ERD Commander Professional around for resetting changed or damaged passwords. I recommend using the Recovery Console for all other critical Windows 2000 repairs.