No Boot-Up with Adaptec SCSI Card

Over the weekend I have built a new PC using an MSI  MS6758 875P NEO Motherboard with an MSI FX5600 TD256 Graphics Card.
The CPU is an Intel 3.0 gig P4
The system has 2Gb of 400DDR Memory, a Seagate SATA 150 160Gb Hard Drive and a Western Digital 20Gb ATA Hard Drive and an MRI Connexant Modem.
The system also has a Sony 3.5 Floppy Drive, a Sony DVD Re-Writer and a TDK CD Re-Writer.
The OS is Windows XP Professional.
The system as configured above works fine, the problem starts when I attach my Adaptec AHA-2940U2W SCSI Card which has a Hewlett Packard HP C1533 DDS2 Tape Drive attached to it.
When the card is attached the system goes through the Boot-Up procedure, it finds the Floppy Drive, the Hard Drives, the CD-Rom, and DVD Drive, it then finds the SCSI Card and the Tape Drive, then the SATA Controller and then the Boot-up hangs.  If I remove the SCSI Card it Boots up fine.
I have altered the IRQ address on the SCSI Card but this made no difference. The default address for the Card is IRQ 7.
I have configured IRQ 7 on the Motherboard BIOS to ISE/EISA and this made no difference either.
I have tried the SCSI Card in each of the PCI Slots and still will not Boot.
I have replaced the Card and Tape Drive back into the system it came out of and it works fine.
Has anybody had this experience?

Quote
Originally posted by valkyrie
The problem is not MSI, it is Adaptec. I have an Adaptec 2940U2W as well. Same situation when I first installed it. To fix the problem you must go to adaptec.com and download the firmware update:
http://www.adaptec.com/worldwide/support/driverdetail.html?sess=no&language=English+US&cat=/Product/AHA-2940U2W&filekey=2940u2w_bios_v2572.exe
The firmware update must be done from MS-DOS (bootable floppy). The firmware update & utility will fit on a bootable floppy. You probably will need to apply the update using a different PC (not MSI Neo2). After you are finished, you will see the Adaptec BIOS shows a date of 2000. Once complete, you can boot from the Adaptec SCSI card and there is no need to disable the SCSI BIOS. I have running (booted from) the machine I'm using to type this.
Val
Hi Val,
Thank you for that, I will carry that out and let you know what happens.
Regards
Danny.

Similar Messages

  • Adaptec scsi card 29320A-R

    In this neteware 6.5sp5 server, I have above card installed. Bios recognise
    this card. But when I load adpu32.ham v.3.01.13 6 Aug 2004. system console
    report a error: INVALID OPTION C04020AA 'SLOT' INVALID SLOT NUMBER.
    I have another netware 6.5sp5 server using the identical adaptec scsi card.
    it does not have problem to recognise this card in slot 1.
    The startup file loads the same ADPU320.HAM. The startment in the
    startup.ncf file read as follows:
    ADPU320.HAM SLOT=1
    The only difference between startup.ncf of these 2 servers is:
    The one which recognise the card in slot 1 has a statement to load
    nwtape.cdm and the one which does not recognise the card in slot 1 and
    produce above error has no such statement to load nwtape.cdm
    Any idea. What do I miss out?
    Wai Chu

    > In this neteware 6.5sp5 server, I have above card installed. Bios
    recognise
    > this card. But when I load adpu32.ham v.3.01.13 6 Aug 2004. system
    console
    > report a error: INVALID OPTION C04020AA 'SLOT' INVALID SLOT NUMBER.
    >
    > I have another netware 6.5sp5 server using the identical adaptec scsi
    card.
    > it does not have problem to recognise this card in slot 1.
    >
    > The startup file loads the same ADPU320.HAM. The startment in the
    > startup.ncf file read as follows:
    >
    > ADPU320.HAM SLOT=1
    >
    > The only difference between startup.ncf of these 2 servers is:
    > The one which recognise the card in slot 1 has a statement to load
    > nwtape.cdm and the one which does not recognise the card in slot 1 and
    > produce above error has no such statement to load nwtape.cdm
    >
    >
    > Any idea. What do I miss out?
    >
    the slot number might be influenced by a different bios configuration in
    both servers. this could lead to another slot numbering.
    please try to load the driver without as slot number, like:
    LOAD <path>ADPU320.HAM
    and it will ask for the slot number.

  • Adaptec SCSI card

    I've had a back-up tape drive working (just fine) on a G4 400 running OS X 10.3.9 for a couple of years. I want to move this tape drive to a newer (old) computer, a G4 1.25 now running 10.4.11. I dug around and found the Adaptec driver I apparently installed to enable the SCSI card 2906 on the G4 400. On the newer computer with the newer OS, though, I'm getting kernel attacks.
    I searched the Adaptec site for a newer driver, and there are none. In fact, they indicate "the version 1.1 driver is embedded in Mac OS X 10.2 and later, there is no need to download and install this driver if you are running Mac OS X 10.2 or later."
    I guess my question is, does anyone know if this driver is still embedded in Mac OS 10.4? If so, do you know what it's called - where it's located, so I can make sure it's there. (I actually installed the driver I had from several years ago, so if it wasn't there, it should have been then, but I still had kernel attacks.) Any other ideas on this problem?
    Thanks.
    Ginny

    Thanks, all, for the suggestions. I'm totally flustered with this issue. Been working on it most of the day! According to what BDAqua found, I see that this card may not work with OS 10.4, but kind of hard to believe it wouldn't. (Hope that's just a post that was only current up through the 10.3 era.) The "Ask Adaptec" site Michael found does include 10.4.
    I did find that 1.3 driver, and it is designed for Classic - not OS X (as is the SCSI probe). Fact is, this computer also runs an old (but still good) scanner booted in Classic mode, and everything is working great from that side. (Only use the scanner 4-5 times a year - hate to buy a new one when it still works.)
    I do seem to have all the possible, appropriate extensions in OS X. In fact, I dumped all and reinstalled them through Pacifist. Still have the problem. This tape drive is accessed only through Retrospect, and I'm wondering if something in Retrospect is causing the problem instead of the SCSI connection, but I thought kernel panics were generally hardware related. When I access the drive in Retrospect (like to configure it), even if I don't "use" it, I get a kernel panic when I close Retrospect. If I try to restore a file, as it searches a tape, I get a kernel panic.
    I examined the kernel panic log. Obviously, it doesn't mean much, but the text on every crash ends with:
    com.apple.iokit.SCSITaskUserClienp
    or
    com.apple.iokit.SCSITaskUserClient(1.4.9) . . . and some numbers/letters.
    I also see "SCSI" in a couple of other places in the report, so I do believe it's a SCSI problem, but I'm baffled.
    I might reinstall Retrospect and see if it helps, but I'm not optimistic that it will. Guess I might also try installing 10.3 in a partition that already exists on the drive, boot in 10.3 and see if the SCSI connection starts working. (If it would, guess I'd have to reformat the drive, reinstall everything and stop with the 10.3 install.)
    Any other ideas?
    Thanks,
    Ginny

  • Adaptec SCSI Card Solution (worked for me anyway)

    I know there has been a lot work put into this issue, and even this solution mentioned once before but since it completely worked for me, i figured id post because its inevitable that someone else will ask it soon.
    Like everyone else, once upgrading to Tiger, my Adaptec 2930CU card (supposedly the biggest offender of them all) would kick in kernel panics almost every time I tried to write a DVD-5 DLT and would never get through a DVD-9.
    I took someones advice and deleted the extension for this card in my System/Library/Extensions folder. This completely eradicated the problem and it works as good the old days. I have another machine with a different Adaptec card, not sure which, did the same thing and that solved it.
    Hopefully this will be beneficial to somebody out there as im sure anyone who didn't spend a million dollars on a card a while back probably bought Adaptec

    Thanks for taking the time to come back and let us know - it is valuable to see when a fix has worked for someone.

  • Windows 8.1 freezes while booting up with discrete graphic card T520

    Hi all,
    Hoping someone can help me here. If I use my discrete video card (nvs 42000m) to boot into windows, it will freeze on the sign in page or sometimes on the metro page however when Optimus is enabled it works just fine.
    So I thought it was a driver issue. I went to Nvidia and downloaded their latest video card driver for windows 8.1. No help
    Uninstalled that, went to Lenovo's support site and installed their recommended driver and all other windows 8 drivers. Again it would freeze
    Booted into safe mode uninstalled that, turned optimus back on, and this time used Windows update to install my video drivers (intel and Nvidia both this time).
    Didn't work. So I spent maybe another hour or so fiddling and after many restarts i finally found the culprit. It was the Lenovo monitor driver. As soon as I uninstalled that, everything worked fine and I could finally use my laptop with optimus disabled and discrete video card enabled.
    Windows update keeps recommending me to update the monitor driver but if I do, then it freezes again so I'm just leaving it as the default generic monitor.
    The reason why I made this thread is to inform and save potential users in the future who have a similar laptop to mine (t520 with hd 3000 and nvidia 42000m) with Windows 8 installed and they happen to choose to solely run their laptop with the discrete graphics card, remember to uninstall your monitor driver.
    I am open to recommendations and other alternatives.

    drenched wrote:
    Hi all,
    Hoping someone can help me here. If I use my discrete video card (nvs 42000m) to boot into windows, it will freeze on the sign in page or sometimes on the metro page however when Optimus is enabled it works just fine.
    So I thought it was a driver issue. I went to Nvidia and downloaded their latest video card driver for windows 8.1. No help
    Uninstalled that, went to Lenovo's support site and installed their recommended driver and all other windows 8 drivers. Again it would freeze
    Booted into safe mode uninstalled that, turned optimus back on, and this time used Windows update to install my video drivers (intel and Nvidia both this time).
    Didn't work. So I spent maybe another hour or so fiddling and after many restarts i finally found the culprit. It was the Lenovo monitor driver. As soon as I uninstalled that, everything worked fine and I could finally use my laptop with optimus disabled and discrete video card enabled.
    Windows update keeps recommending me to update the monitor driver but if I do, then it freezes again so I'm just leaving it as the default generic monitor.
    The reason why I made this thread is to inform and save potential users in the future who have a similar laptop to mine (t520 with hd 3000 and nvidia 42000m) with Windows 8 installed and they happen to choose to solely run their laptop with the discrete graphics card, remember to uninstall your monitor driver.
    I am open to recommendations and other alternatives.

  • P6N SLI Won't boot from SCSI card

    I have a P6N SLI motherboard with a SCSI card I'm trying to boot from. The BIOS sees the card (as indicated by the BIOS when "Quick Booting" is disabled), however, it doesn't run the option ROM on the card necessary for it to boot from the SCSI card. I've tried several different SCSI cards (BusLogic, LSI, QLogic, Adaptec) and using a couple different video cards, one of them PCI. The only things I have plugged into the board are the video card and the SCSI card. Nothing seems to work. Am I missing an option in the BIOS or something?
    Thanks, Mark.

    Quote from: Jack the Newbie on 13-October-07, 06:11:28
    Did you ever try with devices attached to the SCSI card?  After all, what you want to boot from in the end is a SCSI drive.  Try hooking up a SCSI drive to the card, otherwise it is hard to tell if there even is a problem at all. 
    On the board I am using for example, the Intel ICH7DH RAID BIOS is only executed if there is more than one SATA drive hooked up to the ports hosted by the controller.
    That RAID BIOS has hooks into the system BIOS so it knows whether to initialize itself or not. How a SCSI card works is by having a boot ROM which scans the SCSI chain to determine drives. My use in all this is to have my system boot from my SAN. I'm using a QLogic 2300 for this purpose - and yes, it is connected into the SAN. However, as I said, it doesn't matter what if any devices are connected. The system BIOS MUST execute the option ROM on the card before the system even KNOWS there are SCSI devices to boot from. I'm not even getting as far as that. the option ROM never executes.
    Maybe I'm not explaining myself well and my use of "option ROM" needs explaining further. When you power on a system you'll see the following in order:
    1. Memory detection and count.
    2. IDE/SATA scan.
    3. BIOS looks for external cards and option ROMs, if they exist, are executed (SCSI in this case). You see this stage when you see something like "Adaptec 2940 BIOS v xx.xx - Press Ctrl-A to enter settings" or something like that. Next you'll see a listing of devices connected to that card, SCSI devices in this case - assuming you have any plugged in.
    4. After POST status screen - displays CPU, memory, any serial/parallel/USB IO configured and all devices initialized by the system BIOS and their assigned IRQs.
    5. System BIOS loads and runs the boot sector on the configured boot device. If any option ROMs have hooked themselves into interrupt 0x13 (option ROM boot interrupt), i.e. SCSI, then a SCSI boot device is used.
    My problem is that step 3 is skipped. My system goes straight from step 2 to step 4. Without the option ROM being called by the system BIOS, there's no chance of any SCSI device being used as a boot device.
    A good explanation of what an option ROM can be found at:
    http://en.wikipedia.org/wiki/Option_ROM
    - Mark.

  • Solaris 10 x86 -Scsi Adaptec 29320ALP Card issue

    Hi
    I am trying to install Solaris 10 x86 edition . I am facing an issue with the scsi card adaptec 29320. Not detecting the disk at the time of installation. I checked the card in HCL. It is available. Any way to install.

    I'm not sure what the root cause for the firewire driver hang is.
    Maybe an issue with interrupt routing. You may want to experiment
    with BIOS ACPI / IOAPIC / PnP OS settings, and/or the
    acpi-user-options property.
    Anyway, to get rid of the firewire driver, you can probably add an
    "exclude: hci1394" line to /etc/system and reboot.

  • Symbios SCSI card working/not working with KT4

    Excuse me while I blow off some steam first... AAAAAAAAAAAAAAAAAAAAGGGGGGGGGGGGGGGGHHH HHHHHHHH!!!!!!!!!!!!
    Thanks, that helped. Now I can talk rationally (well, as rationally as I'm able to at 12.30 A.M. after spending a full afternoon with my head inside a computer case). I took my home theater computer to MSI when the KT3 UltraARU came, and since then it has been a sometimes tense, but most of the time good relationship, with a bunch of sound cards and a jump to the KT4. Then I got tired of having the KT4 Ultra version without built in LAN, so I found out I could use the one I had in my server (where I don't need that many PCI cards so I can use a PCI network card). And today the wonder arrived: one KT4 Ultra FISR (or something like that - gigabit lan, firewire, bluetooth ready and serial ATA RAID), plus a brand new AMD XP2600 Plus with a 333 bus for 166 FSB. And I took great care mounting it, for once tidying up all cables, securing good airflow and even cutting two blowholes in the top for good measure, since I knew that the 2600 runs a bit hotter than my old 1800. Then in with all the cards I had used on the former KT4 (from the top: Radeon 9500, Audigy Platinum EX, Live! Value, Pinnacle PCTV Rave, one free PCI slot and finally a ultra SCSI card at the bottom), and I was ready to go. Or so I thought... So what happened? Wel, everything seemed to fire up at first, but it got stuck on the green LEDs on 1 & 3, which should be where the graphics card starts to send messages to the screen. And it got stuck. And stuck. And even after a full BIOS reset (just in case somebody had tested this board and made a wrong setting) it got stuck the same place.
    So on to the usual suspects, then. First the memory. Out with the new stick and in with the one I used in the predecessor, which had been working earlier today. No change. OK, then it had to be the CPU. Out with the 2600 and in with the 1800. Nothing. So it had to be the graphics card, then. Out with the 9500, in wich an older ATI Radeon VE. Nothing. But since I'm methodical I simply cursed at the wife and kids, kicked the dog and relieved myself in the neighbours flower bed before I started the next phaze. And I got a hit on the first attempt. As soon as the SCSI card was out, everything functioned. I got into the BIOS, changed everything to what it should be and restarted the PC. Worked like a charm. I even had my two harddisks on the IDE 3, like I have told you before. No problems there. So in with the SCSI card, and nothing.
    I know this card works, or at least that it was working earlier today. And nothing had happened that should damage it. So this weekend, when I change mobo in my server (if I do that tomorrow my wife will call a divorce lawyer - one night inside a PC is barely tolerable, two nights in a row is marital suicide!) I'll test it on the "old" KT4 again. My bet is that it works. What can this be? The only difference I was able to see between the boards (except for the firewire and gigabit lan) was that it had a newer BIOS. I think I was on 1.1 on the former KT4 while this arrived with 1.2. Can this be it? I thought BIOS upgrades were to fix problems, not introduce new ones...
    Can anybody give me a pointer here? I'd really appreciate it since this SCSI card runs the DVD ROM inside my home theater, and it would be a full retreat to even think about having to open the door to the server room to change DVDs!  8)

    Mastiff,
    If you limit your troubleshooting options, then you were limiting the chance for solving your problem.   The diff slot suggestion is still opened for you.  
    4. Take out all other PCI slots, let only SCSI card alone.
    You only need to make sure it can BOOT right? Don't worry about messing up Windows configuration of your PCI cards. Just put them back if you've tried all possible slot configurations.

  • K9a Won't Boot with both Crossfire Cards into Vista

    My system boots fine with only one card but with second card and crossfire cables it posts and detects drives and goes all the way up to the boot screen and never starts windows.I have a K9A,Athlon 64 4600X2,4gb of XMS,2 Raptor X 150s,Dual Liteon DVD DL,in an Antec 900 case,with 2 ATI 1950 Pros,Aero Cool Zerodba ps 3.3v-32a ,5v-36a,12v1-20a,12v2-18a,620 w supply.I have to remove the second card and then boot into safe mode.I can then restart and then it will boot back into windows with only the one card.I upgraded the power supply from a 550 to this one thinking maybe not enough power.What do you think?

    Those splitrail PSU's are known for giving problems with SLI or Crossfire cards.
    Many people tried, many people failed.
    The number of watts of the PSU don't matter, it's the amps you need.
    If you want to be sure it's not the PSU, just try one with a whole lot of amps at a SINGLE 12V line.
    PC Power & Cooling has a few nice ones, with >49A on a single line, that should do it.
    Something like this one: >>link<<
    However, try to do it with XP first, see what happens, Vista is filled with buggs that could give all sorts of problems.

  • PCI scsi card for ScanMaker 4

    Hi every one!
    I have G4 running Mac OX 10.4, I'm able to scan from the ScanMaker 4 in Mac OS 9 into PhotoShop or using the scanning software, however if I try to scan in OS X there is not communication between the computer and the scanner.
    I have installed a " PCI Adaptec SCSI" card ( which work fine in OS 9x), so far no luck in Microtek web site or Adaptec trying to down load a driver, a patch or something that allow me get my scanner to work in OS X.
    Any help on this will greatly appreciated!
    Regards!

    joem,
    I have had the same problem with an Epson SCSI scanner. Either there is no driver or it does not work. The solution is shareware "VueScan" which worked presto. You can download a free trial version before buying.
    Hans

  • SCSI card Superdirve conflict?

    Do you know of any conflicts with Acards SCSI card for mac and a superdrive? When I installed the scsi card my superdrive went out ... then I restarted and my superdrive worked again but no SCSI card showed up .... any suggestions? The acard model number is AEC-67162M. My rig is a dual 2 G5 first gen.. Thanks in advance!

    Hi Christopher,
    We have had this card and it worked fine.
    Which slot are you using?
    Are you running any hardware off the card at present?
    What is the SCSI id of your CD?
    Have you checked the system profiler to see if you can see the acard software extension? Let us know and I'll try and give you a hand.
    Cheers

  • How to find QLogic SCSI card driver...

    Hi
    I am useing E2 Server its configured with RAID0 its connected with QLogic SCSI card some how its fail to reconnect to the E2 server running Solaris Sever OS 7.
    Could you give some basic knowladge how to configure or give the path where I found the driver for QLogic SCSI card......
    Thanks
    Mohammed Tanvir

    There are [at least] two examples of PCMCIA dirvers in the DDK supplimentary suite. There is also an example of simple DLPI driver.
    All you have to do is to combine those examples to get the PCMCIA DLPI driver and fine tune it to match your particular hardware. Any bells ring?
    You will definitely need your card programming manual and/or software interface description for the last phase.
    If you do not have one, you might get some open source (say, Linux or FreeBSD) driver for your card and do some code analysis to reveal the information you'll need.
    Hope this helps...
    Ilya.

  • Will OSX support Adaptec PCI Express scsi cards in an early 2008 Mac Pro?

    I need to move my scsi interface scanner from a G4 machine and the old PCI Adaptec AHA 2930 CU card won't fit.  I was using Snow Leopard on the G4 unit - it still supported the Adaptec card and all was good.  My 23" Cinema display then bit the dust and I replaced it with with a 24" Cinema display with the mini display port connector.  I purchased an adapter from Kanex to make it compatible, but the adapter was defective - so I returned it.  Their reviews aren't very good - seem to have a lot of D.O.A. adapters - not sure I want to deal with the frustration, but it would be the least expensive option.
    I do have, however, an early 2008 Mac Pro that I can use, provided that it supports the newer PCI Express scsi cards that Adaptec makes.  I'm not sure which one to get yet, either.  I'd rather not buy one and find out it won't work.  I can make a partition on the boot drive for Snow Leopard in case scsi isn't supported in later versions of OSX.  In case you're wondering, I did use a scsi to firewire adapter to run the scanner on my laptop for a while - but it stopped working and I can't locate any replacements (or the company - 2nd Wave Technologies - for that matter).  I haven't tried locating a scsi to usb adapter, but from what I can see, they are getting pretty scarce.  I'd replace the scanner, but it is fairly pricey and the newest model retails at the price of a small car - so that really isn't an option at this point.
    Thanks in advance for any info.
    Message was edited by: Jakob Richardt
    Changed name of display adapter manufacturer.

    Thanks for the response - I guess the question I should have asked is "Will OSX support scsi cards in an early 2008 Mac Pro and if so, which ones?"  I didn't realize Apple and Adaptec weren't working together - my G4 tower arrived with an Adaptec card in it when I bought it in 2000 (from a third party vendor, not directly from Apple).  It came with either OS 8.* or OS 9.  When I updated to OSX, everything continued working, so I didn't think much about it until I pondered using the Mac Pro for the scanner - at some point the G4 is going to stop working - need to have a solution before that happens.  The manuals I've been reading refer to the slots in the G4 machines as PCI.  The manual for the Mac Pro refers to the slots as PCI e.  These slots have fewer connectors, so I thought that the "Express" part of the name referred to this particular card configuration when compared to the longer card connectors in the G4 type of machines.
    Can you tell me what scsi card brands will work in the Mac Pro?  I'd still like to pursue this option.  As I mentioned in my original post, buying a new scanner isn't in the cards right now - it costs more than the computer, so, although pricey, the card option is still less expensive.
    Thanks!

  • Reliable SCSI card for G4 tower (Quicksilver or other G4 tower) with OS 9 ?

    Good morning.
    I am trying to setup a G4 Quicksilver (or another slower G4 tower) under OS 9 to be able to use a very nice Epson wide format scanner (no OS X drivers available). It has only a SCSI Centronics 50 pin connector.
    1. Is there a reliable and available (with OS 9 drivers) SCSI PCI card that will work in a variety of G4 towers under OS 9?
    2. If the card doesn't have the 50 pin Centronics connector, how do I adapt the scanner to the card input?
    Thanks for your time.

    When SCSI was built in to Macs, it was what we now call "narrow" SCSI. Apple used the DB-25, a 25-pin connector that looked like an RS-232 connector (because it was the same connector). To use it with typical 50-pin Centronics devices, a cable called a Macintosh System Cable was used. The Macintosh System cable swapped the signals around and connected the few grounds in the 25-pin connector to the many grounds in the 50-pin connector. Almost all devices came with two Centronics-50 connectors. Connecting multiple devices together was accomplished with a Centronics-50-to-Centronics-50 cable, and the last connector on the last device was filed with a Terminator.
    Most of the add-on cards available later were "fast", "wide", "fast and wide" SCSI, optimized and tuned up to run faster than the built-in's maximum 5 Mega Bytes/sec. They used more complex cables and had more rules for proper operation. Your scanner alone cannot generate data fast enough to fill up the original "narrow" SCSI. So you need none of the later stuff.
    Faced with no SCSI port on the new Blue & White G3 (the first Mac without a SCSI port since the original Macs), many users at that time installed the Adaptec 2930 card in a PCI slot to run their scanners or occasional other SCSI devices. The card is capable of Fast-20 speeds if your device supports it, and works with G3s and G4s with PCI slots. The card has an external 50-pin connector called HP-DB50, which has nothing to do with Hewlett Packard, it means Half-Pitch (the pins are twice as close together as on the DB-25 connector). HP-DB50-to-Centronics-50 cables are readily available. Support for the Adaptec 2930 is still available built into Mac OS X.
    If you go with the Adaptec 2930 card, it will run your scanner, not require any adapters -- just one cable converts to the connector you need, and if you can get an "active" 50-pin Centronics terminator with an LED, your life should be easy.
    There are tons more solutions available. Each comes with a little more added complexity and more potential features if you want to do additional things with it.

  • Boot from Raid-hdd with a controller card installed?

    Hi,
    I have a problem. I've just intalled a Windows 2000 my HDD3 (IDE-raid) and everthing went well. I've put the 1st boot option to SCSI and it boots normal. But when I add a hdd to my controller card (Promise Ultra100) it doesn't boot the raid, instead, it tries to boot from the hdd on the controller-card. I've just got this card, and had a KT3-Ultra ARU before. There I could change between "Ultra-0, Ultra-1, Raid-0 and Raid-1 etc. etc." in the bios, where Ultra stands is the Controller card and Raid in the onboard raid. So, why can't I do this on this, newer card? Any1 know how to work around it or how to fix it?
    This is what I have:
    IDE1:
            Master:  Western 180GB
            Slaev:    Maxtor  250GB
    IDE2:
            Master: NEC 1300A
            Slave:  Lite-on-it 40125W
    IDE3 (Raid):
            Master: Maxtor 80GB
            Slave:   Maxtor 80GB
    Controller card IDE4:
            Master: Western 250GB
            Slave:   Western 250GB
    Controller card IDE5:
            Master: Western 200GB
            Slave:   Seagate 30Gb
    Controller card = Promise Ultra100
    And yes, I have the modded version of the bios couse I wanted to have a real raid on my IDE-drives. How can it even be raid if it's only one drive? But that doesn't really matter, couse the boot-options are the same as before.

    Hi, I did as u said and bought a new controller card (Titan Electronics Inc. Ultra ATA/133 IDE). But it didn't help, it's the same as with the older Promise card.
    This is what happenes:
    When I add a hdd to the controller card it finds the hdd and such. Everything works normal untill the os-boot-process begins. Because there is only one alternative called "SCSI" in the bios, where u chose where to boot from it thinks it should boot from the controller card (cause it is a kind of SCSI-card). But I want it to boot from the raided-drivers on the onboard raid (whitch also is a kind of SCSI-card). The thing is that it mixes them up, and only tries to boot from the controller card i've installed, and ignores the raided-drivers. When I had my Kt3 Ultra-aru I could chose between booting from:
    IDE0
    IDE1
    IDE2
    IDE3
    CDRom
    Raid0
    Raid1
    (this options only showed up when I had my Promise ULTRA controller installed on it)
    ULTRA0
    ULTRA1
    ULTRA2
    ULTRA3
    But with this, newer and more expensive card, I can only chose SCSI in the boot sequnce.
    Any idea how to fix that? Maybe to mail to the MSI so they fast can added that choice to the BIOS in an update?
    Would be thankfull for any help possible

Maybe you are looking for