IDE Controller Marked as SCSI in Boot.ini File

 Last reviewed: March 27, 1997
Article ID: Q155118
The information in this article applies to:
  • Microsoft Windows NT Server version 4.0
  • Microsoft Windows NT Workstation version 4.0

SYMPTOMS

After installing Windows NT 4.0 on an IDE hard disk, you may 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 disk
   hardware.

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

CAUSE

This problem can occur if the IDE hard disk is misdetected as a SCSI drive in the Boot.ini file.

RESOLUTION

To resolve this problem, follow these steps:

  1. Edit the Boot.ini file. Replace "scsi" with "multi" (without quotation marks).

  2. Delete or rename the Ntbootdd.sys file in the root folder.

MORE INFORMATION

Note that the resolution listed in this article may also resolve the problem if you receive the following error message when you reboot your computer after installing Windows NT 4.0: 

   OSLoader ver 4.00 SCSI0 DISK0 – Windows\System32\NTOSKRNL.EXE
   Windows NT could not start because the following file is missing or
   corrupt: Winnt\system32\ntoskrnl.exe
   Please re-install a copy of the corrupt file

Additional query words: ntoskrnl
Keywords : kbenv NTSrvWkst prodnt winboot
Version : 4.0
Platform : WinNT
Issue type : kberrmsg

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 27, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.