Heb je in je bios niet een optie als "boot from other devices" ofzo? Dan kun je gewoon van de extra controller booten. En hoef je ook niet al je drives persee aan je Ultra66 aan te sluiten.
En wat als je je onboard IDE helemaal disabled?
Is de MBR van je HD wel in orde? (Doe voor de zekerheid een FDISK /MBR).
Of is de partitie op je nieuwe boot-disk nog niet op active/bootable gezet? (FDISK, drive kiezen, set active ofzo).
Ik heb trouwens m'n Ultra66 naar FastTrak66 omgesoldeerd
, m'n ultra66 is nu dus een RAID-controller, echt perfect! De RAID-controller wordt door het systeem als een SCSI-drive gezien, dus in m'n bios staat ie nu als "boot from SCSI".
Het leuke is, dat je met het kaartje als RAID gewoon meerdere disks als 1 grote SCSI-drive kunt mappen (dus geen C, D, E, F - drive meer maar gewoon een grote virtuele C-drive die bestaat uit meerdere fysieke disks!). En de transfer-rate is bij mij nu meer dan vier keer zo hoog (ik heb er vier disks aanhangen die via striping worden aangesproken
)
Het enige nadeel is, dat je dus alleen harddisks aan de FastTrak66 kunt aansluiten (geen CDspelers, DVD, etc), dus alle andere apparaten moeten aan de onboard controllers.
Van de promise site:
QUESTION: How do I boot from the Ultra66?
ANSWER: There are two ways to make the Ultra66 be the bootable device. One way is to make sure there are no HDDs on
the motherboard controllers. The motherboard will not find a bootable device, and allow the Ultra66 to boot. The other way is
to change the Boot Sequence in your CMOS to boot from SCSI first. Since the system will see the Ultra66 as a SCSI
controller, this will tell the motherboard to ignore it’s own controllers and allow our card to be the boot device. Some
motherboards do not allow this, so it may not be an option for you. You MAY also be able to turn the auto-detection off on
your motherboard and set all the HDDs in the CMOS to "None" or "Not Installed". This is if you have devices (other than
HDDs) connected to the motherboard. Again, this last suggestion MAY work. Your motherboard may not allow this type of
workaround.
QUESTION: How do I boot from the Ultra66 if I already have a SCSI card in the system?
ANSWER: If you have an actual SCSI controller in the system, the computer will attempt to boot from whichever controller is
seen first. To get one controller to be seen before another, you must get it’s BIOS to load first. Manipulating the BIOS address
that the card is set to use normally does this. However, the Ultra66 is fully PnP. This means that only the PnP BIOS on the
motherboard can control which resources our card uses. In most cases, the PCI slot with the highest priority will be assigned
the lowest BIOS address. On most motherboards, the PCI slot with the highest priority is PCI slot #1.
QUESTION: Why will my existing HDD not boot when connected to the Ultra66?
ANSWER: Will the system boot from a floppy? If so: Can you access the HDD? Can you run programs from the HDD? Can
you copy files to and from the HDD? If the answers to all the above questions are, "yes," the MBR on the HDD is unreadable
for some reason. Here is how to reset it. (NOTE: While this shouldn't cause any problems, there is a possibility of data
corruption. Make sure you have any important data backed up.) - Boot the system from a floppy. - Type "FDISK /MBR" at
the command prompt. - Type "SYS C:" at the command prompt. If that doesn't help, or you answered "no" to any of the
questions above, the problem is that the Ultra66 cannot properly recognize the format of the HDD. This is due to a slight
difference between the LBA translation of your motherboard and that of our card. The only way you will be able to get around
it is to repartition/reformat your HDD while it is connected to the Ultra66.
.. weet iemand een oplossing hiervoor?.. alvast bedankt..
:strip_icc():strip_exif()/u/557/goomba2_small.jpg?f=community)