User guide

support.dell.com Installing and Configuring SCSI Drivers 3-15
$% 
The boot manager for Windows NT contains recovery logic to allow you to return to
the last known good configuration. If you have changed your host adapter configura-
tion and Windows NT no longer boots, perform the following steps to recover it:
1. Undo any hardware changes that you have made to the computer since it was
last operational.
2. Reboot the computer. Watch the display carefully during start-up. If the following
message appears, press the spacebar, type
l
at the next screen, and then fol-
low the instructions on the screen to continue booting with the last known good
configuration:
Press spacebar NOW to invoke the Last Known Good menu
3. When your computer is operational again, check all of the hardware and software
configuration changes that you want to make. Look specifically for conflicts with
parts of the existing system configuration that are not being changed.
If you cannot determine the source of the error, see, "Getting Help" in the Installa-
tion and Troubleshooting Guide for instructions on contacting Dell for technical
assistance.
$% 
Any error that occurs while the driver is initializing prevents it from loading. If an error
does occur, the driver causes the computer to beep and then display the following
numbered error message:
xxx message
The xxx indicates the error code and message is a line of text describing the error. The
error codes are divided into three categories:

000-099 — Non-host-adapter specific

100-299 — Host-adapter specific

300-999 — Reserved
Specific error codes, such as those in the following subsections, appear only if you
have installed the host adapters and drivers that generate them.
*  %%+
The following error codes alert you to error conditions caused by factors not related to
the host adapter:
000 Failed ParseDriverParameters call
A call to NetWare's ParseDriverParameters routine has failed for some unknown rea-
son. The command line contains errors, or you pressed <Esc> at the port or slot
prompt.