Windows NT Setup Fails when SCSI Controller is Not DetectedLast reviewed: February 17, 1995Article ID: Q126126 |
The information in this article applies to:
SYMPTOMSDuring 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 CAUSEThis problem occurs when Setup fails to copy the SCSI controller driver from the manufacturer-supplied disk to the %SYSTEMROOT%\SYSTEM32\DRIVERS directory.
WORKAROUNDIf you are installing Windows NT on to a file allocation table (FAT) volume:
STATUSMicrosoft 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
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |