Table of Contents
Advertisement
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-Lite 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-Lite 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-Lite 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.
Q: Why can't I see the drives on the FastTrak100-Lite under FDISK?
A:
The FastTrak100-Lite controller is dedicated to RAID array
management and does not provide any means of addressing individual
hard drives through the Int 13h interface used by FDISK. In order to
access drives on the FastTrak100-Lite from MSDOS at all, you must
first create a RAID array.
169
Advertisement
Table of Contents
