Supero SUPER 370DDE, User Manual

Page: 154 / 171

5-74
S
UPER 370DDE/370SDA User's Manual
Troubleshooting
Q: How can I change the system boot sequence in order to boot
from the FastTrak100 array?
A: The boot sequence is controlled by the system BIOS. As far as the
system BIOS is concerned, the FastTrak100 controller and defined
arrays are categorized as a “SCSI” device (even though the BIOS will
not attempt to access the FastTrak100 as any type of SCSI device).
This allows you to set the boot sequence in your BIOS CMOS setup
utility to boot from “SCSI” (an add-in controller like the FastTrak100)
first, rather than “IDE” (an IDE controller built onto the motherboard or
one which effectively replaces it). If there are multiple SCSI add-in
controllers in the system, then the boot sequence among them will be
determined exclusively by their PCI slot priority. PCI slot #1 will be first,
slot #2 second, etc. Put the FastTrak100 controller in the PCI slot
where it will be accessed ahead of other SCSI controllers if you want
to boot from the array.
Q: How can I change the boot sequence between a PCI SCSI card
and the FastTrak100 RAID array?
A: Since all PCI devices are all PnP, it is difficult to determine which
device is addressed first. Some newer motherboard BIOSes may use
advanced options that identify devices and allow you to select which
device will be assigned resources first. Otherwise you may have to
physically switch the device cards on the PCI slots so that the boot
device is in the highest priority slot number (see previous question). If
you do not require the FastTrak100 BIOS to boot from an array and it
is only to be used through a driver under the O/S, one simpler solution
would be to disable the FastTrak100 BIOS so that it does not affect the
boot sequence at all.
Post-Installation
(Memory Managers, FDISK)
Q: Why does my system reboot after the QEMM driver loads from
CONFIG.SYS?
A: The problem lies in the QEMM “Stealth” feature. This feature places
the drive information from the DOS System area into the upper reaches
of RAM where Windows resides. This causes the FastTrak100 to lose
track of its drives when asked to execute the next line in the
CONFIG.SYS file. This forces the reboot that you see. Disable
QEMM’s stealth feature to correct this problem.