Windows NT Setup Fails when SCSI Controller is Not Detected

 Last reviewed: February 17, 1995
Article ID: Q126126
The information in this article applies to:
  • Microsoft Windows NT Workstation 3.5
  • Microsoft Windows NT Server version 3.5

SYMPTOMS

During the upgrade process to Windows NT version 3.5, Setup does not detect the SCSI controller on your computer. When you supply the driver from the SCSI controller manufacturer, the computer stops responding (hangs) or the following message appears: 

   STOP 0x0000007B
   Inaccessible Boot Device

CAUSE

This problem occurs when Setup fails to copy the SCSI controller driver from the manufacturer-supplied disk to the %SYSTEMROOT%\SYSTEM32\DRIVERS directory.

WORKAROUND

If you are installing Windows NT on to a file allocation table (FAT) volume:

  1. After Windows NT Setup reboots the computer (after the MS-DOS-based portion of Windows NT Setup completes), place an MS-DOS boot disk in the bootable floppy disk drive (usually drive A).

  2. Copy the manufacturer-supplied driver to the following directory: 

          %SYSTEMROOT%\SYSTEM32\DRIVERS

  3. Restart the computer.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.5. A fix to this problem is in development, but has not been regression-tested and may be destabilizing in production environments. Microsoft does not recommend implementing this fix at this time. Contact Microsoft Product Support Services for more information on the availability of this fix.

Additional reference words: prodnt 3.50 trap 0x7b lock
KBCategory: kbsetup kbbug3.50 kbfix3.50
KBSubcategory: ntsetup ntstop

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: February 17, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.