Microsoft KB Archive/214748

From BetaArchive Wiki
Knowledge Base


Article ID: 214748

Article Last Modified on 11/19/2003



APPLIES TO

  • Microsoft BackOffice Small Business Server 4.0
  • Microsoft BackOffice Small Business Server 4.0a
  • Microsoft BackOffice Small Business Server 4.5



This article was previously published under Q214748

SUMMARY

This article describes how to create a disk to boot a Small Business Server (SBS) computer from a drive with a faulty boot sequence on an Intel x86-based computer.

This disk can boot SBS from a drive that has the NTFS file system installed. You can use the procedure in this article to work around the following boot problems:

  • Corrupted boot sector
  • Corrupted master boot record (MBR)
  • Virus infections
  • Missing or corrupted Ntldr or Ntdetect.com files
  • Incorrect Ntbootdd.sys driver

NOTE: You can also use the boot disk to boot from the shadow of a broken mirror, although you may need to change the Boot.ini file to do so.

You cannot use the Windows NT boot disk for the following problems:

  • Incorrect or corrupted device drivers that are installed in the %SystemRoot%\System folder.
  • Boot problems that occur after the Osloader screen is displayed.

NOTE: To work around or fix these problems, use the Emergency Repair Disk, load the last known good control set, or reinstall Windows NT if necessary.

MORE INFORMATION

The floppy disk you create must include the following files:

  • Ntldr
  • Ntdetect.com
  • Boot.ini
  • The correct device driver for your SCSI hard disk (if your SCSI controller has its BIOS disabled)

Use the following steps to create the floppy disk:

  1. Use the DISKCOPY command to create a copy of the first Windows NT Setup disk. Click Start, point to Programs, click Command Prompt, and then type diskcopy a: a:. The source disk is the original Setup disk. The target disk is a blank floppy disk that is used as the boot disk.
  2. Leave the Ntdetect.com file on the floppy disk, and delete all other files.
  3. Copy the Ntldr file to the floppy disk from the I386 subfolder on the SBS CD-ROM or from the root folder of the system drive on another computer running SBS or Windows NT. Rename the Ntldr file to Setupldr.bin on the floppy disk.
  4. Create a Boot.ini file on the floppy disk. To do this, type the following (or similar) lines in Notepad, name the file Boot.ini, and save it to the floppy disk. Note that the following sample works for a single-partition SCSI drive with Windows NT installed in the Winnt.sbs folder. The exact value in the [operating systems] section depends on the configuration of the Windows NT system you want to boot:

    [boot loader]
    timeout=30
    Default= scsi(0)disk(0)rdisk(0)partition(1)\WINNT.SBS
    
    [operating systems]
    scsi(0)disk(0)rdisk(0)partition(1)\WINNT.SBS="BackOffice Small Business Server"
                            

    If your computer boots from an IDE, EIDE, or ESDI hard disk, or a SCSI controller with the BIOS enabled, replace "scsi(0)" with "multi(0)."

    For additional information about modifying the Boot.ini file, please see the following article in the Microsoft Knowledge Base:

    102873 Boot.ini and ARC Path Naming Conventions and Usage

  5. If you use "scsi(x)" in the Boot.ini file, copy to the floppy disk the correct device driver for the SCSI controller in use on the computer, and then rename it to Ntbootdd.sys. This is the driver that is stored in the Winnt.sbs\System32\Drivers folder (for example, the Aic78xx.sys file).
    If you use "multi(x)" in the Boot.ini file, you do not need to do this.
  6. Start your computer using the floppy disk, and then log on to the SBS computer.

Troubleshooting

You may encounter one or more of the following problems when you attempt to start your computer using the boot disk you created:

  • 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. Please check the Windows NT (TM) documentation about ARC configuration options and your hardware reference manuals for additional information. Boot Failed.

  • If you select an incorrect SCSI driver 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. Please 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.


REFERENCES

For additional information, please see the following articles in the Microsoft Knowledge Base:

101626 Windows NT Removable Media Requirements and Limitations


117131 Master Boot Record Not Written to Mirrored Shadow Partition


141702 How to Recover Mirroring Windows NT Using IDE Devices


121517 How to Recover From a Corrupt NTFS Boot Sector


128630 How to Recover From a STOP 0x00000058 FTDISK_INTERNAL_ERROR


155222 How to Determine the ARC Path


162330 Err Msg: Windows NT Could Not Start...


169375 STOP 0X0000007B on HP NetServer LH Systems


155892 Windows NT Boot Problem: Kernel File Is Missing From the Disk


181345 How to Replace Files In Use at Windows NT Restart


167045 Windows NT Will Not Boot from a Shadow Mirror Drive


155053 Black Screen on Boot


126690 Windows NT 4.0 Setup Troubleshooting Guide


117131 Master Boot Record Not Written to Mirrored Shadow Partition


197667 Installing Windows NT on a Large IDE Hard Disk



Additional query words: smallbiz

Keywords: kbinfo KB214748