Note The procedure for RISC-based computers is different .

Note: The following procedures apply to the situation where access to a computer running Windows NT or 2000 does not exist.

• Damaged boot sector
• Damaged master boot record (MBR)
• Virus infections
• Missing or damaged Ntldr or Ntdetect.com files
• Incorrect Ntbootdd.sys driver
• To boot from the shadow of a broken mirror

Note that you may have to modify the Boot.ini file to do this.

Note that you cannot use the Windows Emergency Repair disk (ERD) to help resolve the following problems:

• Incorrect or damaged device drivers that are installed in the System folder.
• Boot problems that occur after you see the Windows Startup (Osloader) screen.

The Windows boot disk must include the Ntldr (or Setupldr.bin in Windows NT 3.5), Ntdetect.com, and Boot.ini files, and may require ntbootdd.sys, which is the device driver for your hard disk controller renamed to ntbootdd.sys.

Note The Ntldr, Ntdetect.com, and Boot.ini files typically have their file attributes set to system, hidden, or read-only. You do not have to reset these attributes for the bootable disk to work. For additional information about the structure of the Boot.ini file, click the article number below to view the article in the Microsoft Knowledge Base: 102873 BOOT.INI and ARC Path Naming Conventions and Usage You Do Not Have Access to a Computer Running Windows

1. Create a copy of the first Windows Setup disk by using the diskcopy command. To do this:
   1. Click Start, and then click Shut Down.
   2. Click Restart the computer in MS-DOS mode, and then click Yes.
   3. At a command prompt, type the following command, where a is the drive that contains the Windows Setup disk and b is the drive that contains the blank floppy disk that you want to become the Windows startup disk:

      diskcopy a: b:

2. Copy both the Ntdetect.com and Ntldr files from the I386 folder on the Windows CD-ROM to the new floppy disk.
3. Rename the Ntldr file to Setupldr.bin.
4. Create a Boot.ini file.

   The following sample Boot.ini file provides an example for a single partition SCSI drive with Windows installed in the Winnt folder; however, the exact value in the [operating systems] section depends on the configuration of the Windows computer that you want to start up:

   [boot loader]
   timeout=30
   Default= scsi(0)disk(0)rdisk(0)partition(1)\winnt
   [operating systems]
   scsi(0)disk(0)rdisk(0)partition(1)\winnt="Microsoft Windows 2000 Advanced Server" /fastdetect

   If your computer boots from an IDE, EIDE, or ESDI hard disk, replace scsi(0) with multi(0). If you are running Windows NT 3.5 or Windows NT 3.51 and your computer boots from the first or second SCSI drive, then you can also replace scsi(0) with multi(0).

   If you are using scsi(x) in the Boot.ini file, copy the correct device driver for the SCSI controller that is in use on the computer, and then rename it to Ntbootdd.sys. If you are using multi(x) in the Boot.ini file, you do not have to do this.

5. Start your computer by using the startup disk, and then log on to Windows.

You may experience one or more of the following problems when you try to start your computer with your Windows bootable disk:

• If the path that points to the system files is incorrect or includes the drive letter, you may receive the following error message:

  Windows NT could not start because of the following ARC firmware boot configuration problem: Did not properly generate ARC name for HAL and system paths.

  Check the Windows NT (TM) documentation about ARC configuration options and your hardware reference manuals for additional information. Boot Failed.

• If an incorrect SCSI driver is selected or if the Ntbootdd.sys file does not exist, you may receive the following error message:

  Windows NT could not start because of a computer disk hardware configuration problem. Could not read from selected boot disk. Check boot path and disk hardware.
  Check the Windows NT (TM) documentation about hardware disk configuration and your hardware disk configuration and your hardware reference manuals for additional information.
  Boot Failed.

• If the Boot.ini file does not correctly reflect the correct %SystemRoot% folder for Windows, you may receive the following error message:

  Windows 2000 could not start because the following file is missing or corrupt:

  SystemRoot \System32\Ntoskrnl.exe

  For additional information about creating startup disks, click the following article numbers to view the articles in the Microsoft Knowledge Base: 305595 HOW TO: Create a Boot Disk for an NTFS or FAT Partition in Windows XP 301680 HOW TO: Create a Boot Disk for an NTFS or FAT Partition in Windows 325879 HOW TO: Create a Boot Disk for an NTFS or FAT Partition in the Windows Server 2003 Family

The above applies to:

• Microsoft Windows 2000 Server
• Microsoft Windows 2000 Advanced Server
• Microsoft Windows 2000 Professional
• Microsoft Windows 2000 Datacenter Server
• Microsoft Windows NT Server 3.1
• Microsoft Windows NT Server 3.5
• Microsoft Windows NT Server 3.51
• Microsoft Windows NT Server 4.0
• Microsoft Windows NT Workstation 3.1
• Microsoft Windows NT Workstation 3.5
• Microsoft Windows NT Workstation 3.51
• Microsoft Windows NT Workstation 4.0
• Microsoft Windows NT Advanced Server 3.1
• Microsoft Windows NT Advanced Server 3.5
• Microsoft Windows NT Advanced Server 3.51
• Microsoft Windows NT Advanced Server 4.0
• Microsoft BackOffice Small Business Server 4.0a