Table of Contents
Advertisement
Frequently Asked Questions
Q: How can I change the system boot sequence in order to boot from the
RAID Function array?
A: The boot sequence is controlled by the system BIOS. As far as the system BIOS is
concerned, the RAID Function controller and defined arrays are categorized as a
"SCSI" device (even though the BIOS will not attempt to access the RAID Function
Lite 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
MBFastTrak133 Lite) 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 RAID Function 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
RAID Function RAID array?
A: Since all PCI devices are all PnP, it is difficult to determine which device is addressed
first. Some newer motherboard BIOS 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 on the PCI bus so that the boot device is in
the highest priority slot number (see previous question). If you do not require the
RAID Function 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 RAID Function
BIOS so that it does not affect the boot sequence at all.
8-3 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 Win-
dows
resides. This causes the RAID Function 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 Em's stealth feature to correct this problem.
6 5
Advertisement
Table of Contents
