Bootable RAID Array

[DieMaker]

Does anyone know how to set the RAID array to bootable (with the "*") or how to prepare/reset HDs to get the system to make the array bootable?

History/Info:
I'm using a SOYO DRAGON+ with BIOS K7VXA-2BA7 and PROMISE FastTrak100 "Lite" BIOS 2.0.00.23. I have first boot device set to SCSI and boot order set to "RAID/ATA,SCSI". This all worked for me a few months ago. I took out RAID and used just the 2 drives alone. WinXP Pro still saw one drive as SCSI and was slow at bootup. I am now trying to implement RAID again, but I can't get the "*" bootable indicator to show up. Using the FastBuild utility V1.32, the option to make bootable using space bar is not available under "define" array as it shows in the manual (I don't have define array option, only (3) view array or (1) auto setup). I can still install XP and boot without a problem - but I have a third HD on IDE2 as master. That drive is removable, and when I remove it, I can't boot. If I install XP without the 3rd drive, and then put it in, the system will not boot.

I keep having problems with my HDs. I would love to have some simple utility that can tell you what is really on the HD - partitions, MBR, etc. and just reset the drives to "factory" settings. I have been using FDisk to clear/delete out things and to make active partitions and rewrite the MBR, but nothing is working. Any ideas?

[DieMaker]

Well, I had to figure this one out by myself - it took longer than I expected, but all is working now. I guess a bootable RAID array is not as interesting as the newest video card... !

I flash my BIOS on a regular basis, and from the release notes, "New Promise BIOS(ver:2.0.00.23), can support 130GB or higher HDD". It looks like they also changed the menu options and how the "*" works to indicate a bootable array. The other thing is not to follow the manual - don't make SCSI the first bootable device, make it third, with floppy first and CDROM second. Also, install OS without the 3rd drive in place. Once the system install is complete, put the HD back, boot, and let the OS find the new HD and do the setup. I suspect that with the 3rd dirve in place, the OS was writing the MBR to that drive, but I'm not sure about that. This worked for me, I imagine other ways will work too.