Microsoft KB Archive/106482

= Err Msg: Windows NT Could Not Start Because of a Computer.... =

Article ID: 106482

Article Last Modified on 11/1/2006

-

APPLIES TO


 * Microsoft Windows NT Advanced Server 3.1
 * Microsoft Windows NT Workstation 3.1
 * Microsoft Windows NT Advanced Server 3.1

-



This article was previously published under Q106482



SYMPTOMS
When Windows NT is installed on a system that has a SCSI drive as drive C, it copies the appropriate SCSI driver to the root of drive C as a file called NTBOOTDD.SYS. If the host adapter is changed to a different adapter model or brand, Windows NT will not start (boot) and you will receive the following error message:

Windows NT could not start because of a computer disk hardware configuration problem.

Could not read from the selected boot disk. Check boot path and boot hardware.

Please check the Windows NT documentation about hardware disk configuration and your hardware reference manuals for additional information.

Boot failed.

The reason for the boot failure is that the incorrect SCSI driver is being loaded. This can be resolved by copying the appropriate driver to the root directory of drive C and renaming it "NTBOOTDD.SYS" prior to installing the new adapter.



CAUSE
When Windows NT is installed onto a system that has a SCSI drive as drive C, it copies the appropriate SCSI driver to the root of drive C as a file called NTBOOTDD.SYS. This file has SHR attributes. If the SCSI controller is changed to a different type or brand, the NTBOOTDD.SYS file will not be the correct driver for the new controller. To change controller types, you must install the SCSI adapter through Windows NT Setup, and copy the appropriate driver to the root of drive C as NTBOOTDD.SYS. A detailed explanation follows:



MORE INFORMATION
For the purpose of explanation, assume that Windows NT is initially installed on a system where the drive C is connected to an Adaptec 1542c. Now attempt to change the 1542c to an Adaptec 1742a controller. To do this, do the following BEFORE physically installing the new adapter:


 * 1) From the Main group in Program Manager, run Windows NT Setup.
 * 2) From the Options menu in Windows NT Setup, choose Add/Remove SCSI Adapters.
 * 3) Choose the Add button.
 * 4) Read the Setup message, and then choose the OK button.
 * 5) Select the Adaptec 174x adapter.
 * 6) Enter the appropriate path for the installation media, and then choose the Continue button.

Windows NT Setup will install the selected driver.

You will now see a list of the SCSI adapters installed on your system. You should see both the Adaptec 154x and 174x SCSI adapters.
 * 1) Highlight the Adaptec 1542c and choose the Remove button. Read the Setup message, and then choose the OK button.

The Installed Adapter list will again be displayed. Choose the Close button and quit Windows NT Setup.
 * 1) Open File Manager and allow viewing of Hidden/System Files. Do this choosing By File Type from the View menu and then select the Show Hidden/System Files check box.
 * 2) In the root directory, highlight the hidden file NTBOOTDD.SYS.
 * 3) Rename the file to NTBOOTDD.OLD.
 * 4) Copy the appropriate driver from the \SYSTEM32\DRIVERS directory. In the example, the file for the Adaptec 1742 is AHA174X.SYS. Copy this file to the root of drive C.
 * 5) Rename the file just copied to the root directory (in the example it is the file AHA174x.SYS) to NTBOOTDD.SYS and place the Hidden, System, and Read Only attributes to the file.
 * 6) Quit all applications and shut the system down.

You can now replace the Adaptec 1542c adapter with the Adaptec 1742a adapter. When you reboot Windows NT, the appropriate drivers will be in place to let you use the 1742a adapter as the controller for drive C.

The Adaptec products included here are manufactured by a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

Additional query words: prodnt change fail changing adapter

Keywords: kbother KB106482

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.