لطفا منتظر باشید ...
Troubleshooting Procedures
This section provides basic instructions for troubleshooting problems that might occur when running Windows 2000. For troubleshooting information related to topics not found in this chapter, see the related chapter in this book. Use the Quick Guide at the beginning of this chapter to determine which chapter contains the troubleshooting information you are looking for.
Using the Hardware Compatibility List
The most common cause of hardware problems is using hardware that is not compatible with Windows 2000. The Hardware Compatibility List (HCL) outlines the hardware components that have been tested for use with Windows 2000. It is especially important to refer to the HCL if you plan to use modems, tape backup units, and SCSI adapters. If several different models of a device are available from one manufacturer, only those models included in the HCL are supported; a slightly different model might cause problems. Where special criteria are required for a model to be supported (for example, a particular version of driver), this information is described in the HCL. The HCL is a Web-based searchable database which is updated as additional hardware is tested and approved. For more information about supported hardware devices, see the HCL link on the Web Resources page at http://windows.microsoft.com/windows2000/reskit/webresources.
Checking Hardware for Problems
If your hardware components are listed on the HCL, and you still have problems, try the following:
Ensure that all physical connections are secure, that expansion cards are fully inserted in their slots, and that cables are tight. You might also try using new cables or moving a card to a different slot.Check that resources, such as IRQs, DMA channels, and I/O addresses, are properly assigned and configured. For instances of device conflicts, reassign a configurable device to use an available resource.Check with the manufacturer for possible updated Windows 2000 drivers or for known issues and workarounds.
If you are using a SCSI device, check its termination. Even if you are sure that the termination is correct, open the computer case and check again. Use active rather than passive SCSI terminators whenever possible.
NOTEVerify that the SCSI cables are not longer than necessary. If a two-foot cable is long enough to connect the device to the controller, do not use a three-foot cable just because one is available. The acceptable lengths vary depending on factors such as whether you are using basic SCSI, SCSI-2, wide SCSI, ultra-wide SCSI, or differential SCSI; the quality of the termination; and the quality of the devices being used. Consult your hardware documentation for more information.Check your hardware configuration. I/O and interrupt conflicts that went unnoticed with other operating systems must be resolved with Windows 2000. Likewise, pay close attention to CMOS and EISA BIOS configuration parameters when using Windows 2000, such as ensuring the Plug and Play OS BIOS parameter setting is set to No or Disabled, and enabling Advanced Configuration and Power Interface (ACPI) support on ACPI-compatible systems. For more information, see your motherboard or system manual documentation. Check the Knowledge Base for information about hardware problems. There are several articles about memory problems, memory parity errors, SCSI problems, and other hardware information in the Knowledge Base. For information about these issues, see the Knowledge Base link on the Web Resources page at http://windows.microsoft.com/windows2000/reskit/webresources.
Terminators provide the correct impedance at the end of a cable. If the impedance is too high or too low, internal signal reflections can occur. These echoes represent noise on the cable and can corrupt subsequent signals, resulting in degraded performance or data loss.
Passive terminators are resistors with the appropriate resistance value for the characteristic impedance of the cable. Active terminators can better maintain the correct impedance necessary to eliminate signal reflection.
Troubleshooting Problems with System Startup and Shutdown
Problems which prevent the computer from completing startup or shut down can be frustrating. However, there are several techniques that you can use to isolate and solve these problems.
Startup Problems
If a computer fails to complete the Windows 2000 startup process, note whether any new hardware or software has been added since the last startup. If so, remove the new component to see whether this resolves the problem.If nothing has been added or changed on the system, restart the computer in Safe Mode. If successful, you might be able to resolve the problem from within Safe Mode. Starting Windows 2000 in Safe Mode can help you resolve issues that occur when you start Windows 2000 normally, including (but not limited to):
Setup freezes during the first restart.Error messages are displayed.The system stops responding.You lose functionality.
Starting Windows 2000 in Safe Mode bypasses the current configuration and loads a minimal configuration, enabling only basic Windows 2000 device drivers and system services. If the startup failure does not occur in Safe Mode, you might have a conflict with hardware settings or system resources; incompatibilities with Windows programs, services, or drivers; or registry damage.In Safe Mode, use the following tasks to find a startup problem. Many of these steps require changes to system configuration files. The changes are to isolate the conflict that is causing the problem and are not intended to be permanent. For more information about Safe Mode, see "Safe Mode" earlier in this chapter.To troubleshoot startup problems in Safe Mode
To enter Safe Mode, restart the computer, and then press F8 when the screen displays the prompt "For troubleshooting and advanced startup options for Windows 2000, press F8."On the Windows 2000 Advanced Options Menu, select Safe Mode, and then press ENTER. Determine whether the startup failure is resolved. If not, check for hardware problems such as defective devices, improper installation, cabling, or connector problems. Remove any newly added hardware to see whether the problem is resolved.If you cannot complete the startup process and you suspect your computer might have corruption in the registry, restart the computer, press F8, and on the Windows 2000 Advanced Options Menu, select Last Known Good Configuration. Press ENTER.If you can complete the startup process in Safe Mode, start System Information. Open the Run dialog box, and then type: msinfo32 For more information about System Information, see "System Information" earlier in this chapter.Within System Information, check the Conflicts/Sharing section under Hardware Resources and the Problem Devices section under Components for known issues. Address any issues found by reconfiguring or disabling the devices in conflict, and then restart the computer. If you disabled a device to resolve the problem, check that the device is listed on the HCL and that it was installed correctly; or check it on another computer to see whether the device might be defective. Try using Windows Update to see whether any updated drivers are available. If not, try visiting the manufacturer's Web site to see whether an updated driver is available.If there were no conflicting devices reported in System Information, under Software Environment, check the Startup Programs section for programs that are automatically started when the computer is started. Disable these programs and restart the system.
NOTE
Links to startup programs can be in a variety of places, including in the registry under the following subkeys:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionRunHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionRunOnceHKEY_USERS.DEFAULTSoftwareMicrosoftWindowsCurrentVersionRunOnceHKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionRunOnceAlso look for startup programs in C:Documents and Settingslogon_nameStart MenuProgramsStartup and in C:Documents and SettingsAll UsersStart MenuProgramsStartup. If the user is a member of the local administrators group, check C:Documents and SettingsAdministratorStart MenuProgramsStartup.
If the problem is resolved by disabling the startup programs, re-enable them one at a time, and restart the computer each time to determine which program causes the startup failure.If disabling the Startup Programs does not resolve the problem, check the boot log file, %SystemRoot%Ntbtlog.txt. Rename this file to indicate that it is a Safe Mode boot log file, and compare its contents to a recently saved boot log file from a normally started session. If a normal boot log does not exist, create one by restarting the computer, pressing F8 at the "Starting Windows" screen to display the Windows 2000 Advanced Options Menu, selecting Enable Boot Logging, and then pressing ENTER. The normal boot log file can indicate which driver file did not load properly.
NOTE
Some startup problems occur so early in the startup process that they prevent the system from saving the boot log file to disk.
Examine the Safe Mode version of the boot log file to see which drivers were not loaded. This list of skipped drivers is a good starting place to look for the driver that is causing the startup process to fail.
If the problem is a Stop message (also known as a blue screen), see the troubleshooting tips in the chapter "Windows 2000 Stop Messages" in this book.
Shutdown Problems
The Windows 2000 shutdown process involves sending messages to the installed devices, system services, and applications to notify them that Windows is preparing to shut down. The system waits for responses from open applications to make sure that they shut down properly, and save unsaved data to disk. Each running device, system service, and application usually respond to the shutdown message, indicating that it can be closed.Typical causes for problems with Windows 2000 shutdown include:
Device drivers not responding correctly, if at all.System services not responding or sending busy request messages to the system.Applications not responding, particularly 16-bit Windows programs.
To resolve problems with shutdown, try the following suggestions:
Check that the system properly shuts down in Safe Mode. If so, check the boot log file. Note the services that were disabled under Safe Mode, stop them one at a time in normal mode, and then shut down to see whether the system works properly. After the problem driver or service is identified, if the file is corrupted, either reinstall it, search for an update, or uninstall it until the problem can be resolved.Press CTRL+SHIFT+ESC to start Task Manager and see which applications are currently running. Manually quit the applications before shutting down to see whether that resolves the problem.Check with your computer manufacturer to be sure that you have the latest BIOS update for the system.
If the problem occurs immediately after a change to the system, such as installing or upgrading applications, system services, or hardware with device drivers, undo the last change made to the system and test the system.
Using Windows File Protection
Earlier operating systems did not prevent shared system files from being overwritten by program installations, causing unpredictable performance results, such as program errors or an unstable operating system. This problem affected files such as dynamic-link libraries (DLLs) and executable (EXE) files. Windows 2000 includes a feature called Windows File Protection (WFP) that prevents the replacement of certain protected system files and significantly minimizes file version mismatches. WFP uses the digital file signatures and catalog files generated by code signing to verify whether protected system files are the correct Microsoft versions. WFP does not generate signatures. WFP is notified when a file in a protected folder is modified. WFP determines which file was changed, and if the file is protected, WFP compares the digital file signature of the replacement file to those in the catalog files to determine whether the new file has been certified by Microsoft. If it has not, the original file is restored from the %SystemRoot%System32Dllcache folder (if it is located in the Dllcache folder) or from the Windows 2000 operating system CD.
Checking for Correct File Versions
You can use the System File Checker (SFC) tool to scan for system files that have been changed by applications and alert you to discovered changes. If necessary, SFC prompts you to restore the original file from the Windows 2000 operating system CD.For more information about using SFC, see "System File Checker" earlier in this chapter.
Updating System Files and Drivers
Windows Update lets you update system files and device drivers specific to your computer. Any new system files downloaded by using Windows Update are automatically registered with WFP.For more information about updating your computer's Windows 2000 installation, see "Windows Update" earlier in this chapter.
Checking Whether a Required File Is Missing or Damaged
If a particular hardware device or system service fails to work properly after starting the computer, especially after encountering problems with disk corruption, it is possible that the driver file did not properly load when the computer was started. To determine whether failures when loading driver files are the problem, restart the computer and enable boot logging. For information about how to enable boot logging, see "Safe Mode" earlier in this chapter. To check for driver files that did not load at system startup
Restart the computer. At the Starting Windows screen, at the prompt "For troubleshooting and advanced startup options for Windows 2000, press F8" press F8 to display the Windows 2000 Advanced Options Menu.Select Enable Boot Logging, and then press ENTER.After the computer has completed the startup process, start Windows Explorer and navigate to the %SystemRoot% folder. Locate the file Ntbtlog.txt and double-click it to open it in Notepad.
The log file lists a long series of drivers that the computer loaded or attempted to load. Files that were loaded are preceded by the phrase "Loaded driver," followed by the path and file name of the specific driver. Files that did not load are preceded by the phrase "Did not load driver." A quick scan for these listings can help you identify the location and names of files that might be missing or corrupted. For more information about the choices in the Windows 2000 Advanced Options Menu, see "Safe Mode" earlier in this chapter.If a file that is needed to load or run Windows 2000 becomes corrupted or is deleted, the system typically displays an error message and might generate information in the event log. You can use this information to find the problem.On rare occasions an executable file or DLL does not report missing or corrupted files. If there is no indication of an error, but you think some component did not start correctly due to a required file that is missing or corrupted, you can run a few tests to attempt to resolve the problem.Check to see whether all of the Windows 2000 system files exist and appear to be uncorrupted. Symptoms of file corruption can be unpredictable, but include a file being an unusual size (for example, zero bytes or larger than its original size) or having a date or time that does not match the installation date. Compare files in %SystemRoot%System32 and its subfolders with files in these folders on another computer running the same Windows 2000 version and Service Packs. Run SFC to inspect all installed system files. Also, run an antivirus program designed to work with Windows 2000 to scan for virus corruption.If you think that you might be having a problem with a missing Windows 2000 system file, you can run Windows 2000 Setup and repair the installation by running the Fast Repair process. For more information about the Fast Repair process, see "Emergency Repair Process" earlier in this chapter.
Device Driver Problems
Corrupted or faulty device drivers and system services can cause problems such as hardware peripheral device or system feature failure and startup failures. To troubleshoot these problems, you need to isolate the cause.
Checking Device Configuration
Conflicts between devices that are trying to use the same system resources can cause errors. You can view your device configuration by using either System Information or Device Manager.System Information collects information such as devices installed or device drivers loaded, and displays the associated system topics. Device Manager provides a central place where you can verify that devices are configured correctly, and to change device resource settings.To check for resource conflicts among devices
Open System Information.Expand the Components category, and then select Problem Devices. Devices with hardware conflicts are identified.To determine the resource in conflict, expand the Hardware Resources category and select Conflicts/Sharing. If neither of the devices are listed under Problem Devices, they are probably sharing the resource.
NOTE
Peripheral Component Interconnect (PCI) devices can share resources.
If necessary, change the devices' resource settings by using Device Manager. To open Device Manager, in Control Panel click System, click the Hardware tab, and then click Device Manager.
NOTEFor more information about using System Information to check for device conflicts, see "System Information" earlier in this chapter. For more information about Device Manager and troubleshooting problems with devices, see "Device Management" in this book. For more information about troubleshooting problems related to device detection, see "Setup and Startup" in this book.
If you use multiple hardware profiles, first select the appropriate configuration by using the list in the device's Resource properties page.
Identifying a Problem Driver
If you can log on to your computer, use the Drivers tool on the Windows 2000 Professional Resource Kit companion CD to display information about the device drivers that are currently loaded. If you have previously printed the output from the Drivers tool (by redirecting the output to a printer or a file), you can compare it to your current output. You can also run the Drivers tool on a similar computer and compare the results.It might also be helpful to look at System Information's display on Drivers and Problem Devices. For more information about System Information, see "System Information" earlier in this chapter.
Identifying a Service That Does Not Start
Some services are configured to start automatically on Windows 2000. The specific services depend on your computer configuration, and which network services and protocols you are using. You can use the Services option in Administrative Tools to view which services are set to start automatically and which did not start, as seen in Figure 31.8.
Figure 31.8 System Services Window
In Figure 31.8, TCP/IP NetBIOS Helper Service is configured to start automatically, but it did not start. Try to manually start the service or change the startup type status by double-clicking it to open the Service Properties dialog box, shown in Figure 31.9.
Figure 31.9 Service Properties Dialog Box
NOTE
You must have administrator privileges to change the startup type of a service.
Saving Output from Troubleshooting Tools
Most of the command line-based troubleshooting tools produce useful information in the form of reports, but lack a command-line switch that offers to save their reports to disk.When using these tools, you can redirect the display output to a text file that can be viewed in Notepad. At the command prompt, type:Toolname /switch > Toolname.txtUse the standard command-line syntax to produce the report you want to save, including any optional command-line switches to produce the specific results you need. The redirector, the greater-than sign (>), transfers the screen output to the text file specified at the end of the command.
NOTE
Unless directed otherwise, the output file is stored in the current folder by using the preceding syntax.
Disaster Recovery
Disaster recovery is primarily used to restore your system in the event that your hard disk fails and you have to replace or reformat it. You can also restore your system if critical system files have been accidentally erased or have become corrupted and you need to reformat your hard disk. Disaster recovery is for use only after you have attempted to repair your system using Safe Mode, Recovery Console, and the Emergency Repair Process, described earlier in this chapter.
Preparing for Disaster Recovery
To perform a complete disaster recovery you need a recent backup of your entire system, including the system state data, the system files, and your data files. The system state data includes the registry, the Component Services class registration database, and the system files required to start your computer (also known as the boot files). The Backup tool provides two methods for backing up your entire system, including the system components mentioned earlier: the first method relies on the Backup Wizard to select files and folders and set backup options; the second method gives you maximum control over the backup process because it relies on you to set backup options and select the files and folders to back up.
IMPORTANTTo prepare for disaster recovery by using the Backup Wizard
You must be a member of the Backup Operators group or a member of the Administrators group on the local computer to back up the system state.
Start Backup. From the Start menu, click Programs, Accessories, System Tools, and Backup.On the Welcome tab, click Backup Wizard.At the "Welcome to the Windows 2000 Backup and Recovery Tools" screen, click Next.Click Back up everything on my computer, and then click Next.Select a Backup media type, select Backup media or file name, and then click Next. Click Advanced to set advanced backup options, including backup type, data verification, hardware compression, media labels and ownership, and scheduling. Otherwise, the Backup Wizard sets the following options by default:
Backup type: normal.Migrated Remote Storage data: do not back up.Data verification: none.Hardware compression: on (if backing up to tape); off (if backing up to file).Ownership/permissions: not set.Overwrite/append data to media: overwrite.Backup and media labels: set to time and date that Backup is performed.Schedule: Not set (runs Backup immediately).
Click Finish to start the backup operation.
The advanced backup options that appear when you run the Backup Wizard are a subset of the options you can set in the Backup tool. To prepare for disaster recovery and configure other options, use the following procedure.To manually prepare for disaster recovery
Start Backup.On the Backup tab, select the volumes, files, and folders to back up. Select System State or you cannot use the backup set for disaster recovery.In the Backup destination list box, choose the type of media to which to back up, and then choose Backup media or file name. On the Tools menu, click Options to configure backup options, and then click OK.Click Start Backup, and then make any changes you want to the Backup Job Information dialog box.Click Advanced to set advanced backup options, and then click OK.Click Schedule to add the backup operation to the Task Scheduler so that it runs automatically at some time in the future.Click Start Backup to start the backup operation.
Because you can only back up the system state data on the computer that is running Backup, you cannot prepare remote computers for disaster recovery. However, you can indirectly automate a remote system backup of each computer on a network by scheduling regular file backups of the System State data on each computer and then backing up those backup files by making a regular network backup of each computer. The procedure is described below.
NOTETo perform a complete system backup on a remote computer
You can use third-party software to remotely back up the system state data.
Log on as an Administrator or a Backup Operator to the remote computer, and then start the Backup Wizard.At the "Welcome to the Windows 2000 Backup and Recovery Tools" screen, click Next.Select Only back up the System State data, and then click Next.Under Backup media type, select File. Under Backup media or file name, enter the path and file name for the backup. The file must have the .bkf file name extension. Save it in a shared folder on the local computer or on a network share for which you have write permission. Click Next.Click Advanced, and then follow the instructions to set advanced backup options and schedule the backup to run unattended. You do not need to back up migrated Remote Storage data and you do not need to set the backup type because the System State data is always treated as a Copy backup type. Also, schedule the backup to run on a regular basis (for example, weekly or monthly). Click Finish to add the backup job to the task scheduler and finish setting up the remote computer.
NOTE
The remote computer must have the logon account used on the computer running the backups listed in either the Administrator or Backup Operator local groups to gain access to volumes on the remote computer. It is recommended that you use the administrative shares, such as C$, to back up the contents of the volumes.
Log on as an Administrator or a Backup Operator, and then start Backup.On the Backup tab, select the shared folder containing the System State backup file you scheduled. Select all of the shared volumes for the remote computer. Click Start Backup, and on the Backup Job Information dialog box, click Schedule to schedule the backup. Schedule the backup to run after the backup job you scheduled to run on the remote computer has completed.Click Start Backup to add the backup job to the task scheduler.
There are several backup options that you can set. For more information about Backup, including backup and restore options, see "Removable Storage and Backup" in this book.
Performing Disaster Recovery
The disaster recovery process typically begins after you have installed a new hard disk or reformat your existing disk. If you installed a new hard disk, you need at least as much storage capacity as the original hard disk. Also, it must have the same volumes as the original hard disk, including volume drive letter, volume size, and file system, or disaster recovery might not succeed.To start the disaster recovery process, install a new version of Windows 2000 and run Backup to restore (recover) your system and data files. The installation folder for the new system must be in the same location as the installation folder of your original system. This applies to the drive letter and the folder name. If your original system was installed to the default Setup location (C:Winnt), you can simply install a fresh copy of Windows 2000, and then begin the disaster recovery process. However, if your original system was installed in a different location, for example at D:Windows, your new system must be installed at D:Windows.
NOTEThe Windows Setup program does not prompt you for the installation folder unless Winnt already exists on the volume that you intend to use for the installation. To perform disaster recovery on a computer that did not use the default Windows 2000 installation volume and folder name, create a Winnt folder on the installation volume before you run Setup. You can do this by using either the Recovery Console or a startup disk for MS-DOS, Windows 95 or Windows 98. Both methods are discussed in the following sections.
Backup allows you to restore files to an alternate location, but does not restore the System State data in a form that recovers your system. When you restore or recover a system you need to restore all files, including the System State data, to the original location.
NOTEUsing the Recovery Console to Create a Winnt Folder on a VolumeYou can use the Recovery Console to create a Winnt folder on an unformatted volume. If the disk has not been partitioned, you can also use the Recovery Console to create volumes. To perform this procedure you need access to a computer with a text editing program (for example, Notepad) and a floppy disk drive. If you do not have access to a computer with a text editor and a floppy drive, see the next section.To create a Winnt folder on an empty volume by using the Recovery Console
You can designate a different installation folder during an unattended installation by specifying the folder name in the "TargetPath=" parameter in the answer file. For more information about unattended installations, see "Customizing and Automating Installations" in this book.
Open the Recovery Console by using either the four Windows 2000 Setup disks or the Windows 2000 operating system CD. Choose the repair option by pressing R when prompted, and then press C to choose the Recovery Console. You do not need to log on as the Recovery Console starts because there is no system installed.If there are no volumes on your disk, use the diskpart command to create an installation volume on your hard disk (type diskpart with no switches to start a user interface for managing volumes). The volume must have the same drive letter and be at least as large as the installation volume that was on your hard disk when it was last backed up. You might need to create more than one volume to reach the appropriate drive letter. For example, if the original installation was on drive D, create drive C first, and then create drive D.Use the format command to format the volumes you created in step 2. Format the new installation volume with the same file system the original installation volume or you can lose data and other file and folder features. For example, if your original installation volume was drive C and it was formatted with NTFS, type the following command:format c: /q /fs:ntfsUse the map command to display the Advanced RISC Computing (ARC) path for the new installation volume. Write this information down. It is needed for step 6. On drive C, the ARC path typically looks similar to the following:DeviceHarddisk0Partition1.On another computer, use a text editor to create a file called Setup.log and save it to a floppy disk. Be sure the file ends with the file name extension .log and not .txt.Add the following information to the Setup.log file and save it. After TargetDevice= and SystemPartition= you must type the ARC path you wrote down in step 4. The ARC path must be inside double quotes. For example:
[Paths] |
Restart your computer from the Windows 2000 operating system CD or the four Windows 2000 Setup disks to run the Setup program. When you are prompted, press R, and then press R again to choose the Emergency Repair Process.Select the Manual Repair option by pressing M. This displays a screen with three manual repair options. Clear all of the options except Verify Windows 2000 System files. When you are finished, select Continue (perform selected tasks), and then press ENTER.When you are prompted for the Emergency Repair Disk, insert the disk you created in steps 5 and 6, and then press ENTER. This creates a Winnt folder on your installation volume.
NOTEUsing a Windows 98 Startup Disk to Create a Winnt Folder on a VolumeYou can create a Winnt folder on an unformatted volume by using a Windows 98 startup floppy disk.When you use a Windows 98 startup disk to create a Winnt folder, you can only format the volume with the FAT16 or FAT32 file systems. If your original installation volume was formatted with NTFS, and you want to restore your system to the same file system, you can use this procedure to create a Winnt folder on your volume. Use the Windows 98 disk partitioning tool Fdisk to create the volume to the original size, then format the volume with FAT32. If the original volume used NTFS, use the convert command to convert the FAT volume to NTFS after you create the Winnt folder and install a fresh copy of Windows 2000, but before you restore your system from backup.
The Recovery Console offers an md command, but by default, you cannot create a folder at the root folder. You can change the default behavior of Recovery Console to allow this type of action with local Group Policy settings, but because the hard disk does not yet have an installation of Windows 2000 on it, you cannot implement policies or change the default behavior for Recovery Console.
NOTETo create a Winnt folder on a volume using a Windows 98 startup disk
The Windows 98 startup disk must contain the files Fdisk.exe and Format.exe from the C:WindowsCommand folder in Windows 98 to complete this procedure.
Start your computer by using a Windows 98 startup disk.If your disk does not have an installation volume, use the fdisk command to create a primary DOS partition with the same drive letter as the original installation volume. It must also be at least as large as the original installation volume. Make the partition active to be able to use it as an installation volume. You might need to create more than one volume to reach the drive letter your original installation used. Once fdisk is finished, the computer restarts. If your hard disk already has a formatted installation volume, skip to step 5.Restart your computer by using the Windows 98 Startup disk.Use the format command to format the volumes created in step 2.
NOTE
The Format tool cannot format FAT16 volumes made by Windows 98 that are larger than 2 GB. Format larger volumes using FAT32.
Use the md command to create a Winnt folder on the volume in which you want to install Windows 2000.
Installing a Fresh Version of Windows 2000Before you can recover your system and your data files, you must install a fresh copy of Windows 2000. If your original installation folder used the default volume and folder name (C:Winnt) and no other volumes exist on the disk, simply restart your computer with the Windows 2000 operating system CD or the four Windows 2000 Setup disks, and follow the instructions on your screen. If you have more than one usable volume, Setup asks you to choose the volume on which to install Windows 2000. Choose the volume whose drive letter matches that of the original installation. If the original installation was on drive D but used the default folder name, Setup automatically begins the installation by using the default folder name (Winnt) unless you already created a Winnt folder on that volume. If there is a folder named Winnt on the volume, Setup prompts you for the name of the installation folder.To install a fresh version of Windows 2000 during disaster recovery
Start your computer by using the Windows 2000 operating system CD or the Windows 2000 Setup disks.If prompted, select a volume to use for the installation.When asked whether to format the volume or leave it as it is, choose Leave the current file system intact (no changes). This preserves the Winnt folder on the installation volume. If you format the disk, the Winnt folder is erased.If your original installation used the default installation folder name, proceed to Windows 2000 Setup and skip the remaining steps in this procedure.If you manually created a Winnt folder on your installation volume, Setup prompts you to confirm whether or not you want to use the Winnt folder for this installation. Create the folder name you originally used.When you are warned that there is a Winnt folder already on your computer, press ESC to choose a different installation folder. Enter a new installation folder, press ENTER, and then follow the instructions that appear.
If you installed Windows 2000 on a FAT16 or FAT32 volume, and your original installation volume was formatted to use NTFS, convert the new installation volume to NTFS before you restore the system. When the installation finishes, log on as the local administrator, and use the convert command. From the command prompt, type
convert drive_letter: /fs:ntfs |
where drive_letter is the installation volume.Restoring the System and Data FilesTo finish the disaster recovery process, restore your system from the most recent backup. To fully recover your system, restore the following:
System filesData filesSystem State data
Use the Restore function of Backup to restore these components to their original locations. This is especially critical when you restore the System State. After you finish restoring your files and system data, restart the computer. Your fully-restored system is in the same state it was in when you backed it up.
