If you leave it setup as raid will windows see it. Plus with out the other disk being connected. Just throwing some stuff out there for you.
I figured out a work-around. I was able to install Windows with ACHI enabled. I
think the slip-streamed Win7 install DVD I made, along with releasing the VelociRaptor drives from the logical disk (detailed below) I'd made with the mobo RAID controller previously
finally allowed me to install Windows with ACHI.
I entered BIOS and enabled the RAID controller, rebooted, then CTRL-F'd to get into the RAID BIOS.
I deleted the RAID and left all the drives on their own, unconfigured. Rebooted, then when back into BIOS and disabled the RAID controller again (switched back to ACHI).
Got Windows setup to see the individual drives (YAY!) and then installed the OS to the SSD.
I then booted into Windows, and used Windows Disk Managment to create a striped RAID from the now individual VelociRaptors that windows could see as the RAID controller no longer had them configured in a bound logical drive.
Presto! Working boot SSD and RAID 0 array.
Ran Crystal Disk Mark and I got awesome numbers from both the SSD and the RAID - it took me 4 days of bashing my head against the wall,
still never got windows to play nice with the hardware RAID controller in BIOS, but got what I wanted in the end with performance numbers BETTER that what I had with my old build with the same RAID drives!
Thanks for the help guys.
OCZ-Vertex II (SATA II) 120GB - Old Win boot drive:
My new Samsung EVO 850 (SATA III) 250GB - New Win boot drive:
--------------
VelociRaptors using the 990FX-UD3 hardware RAID(0) controller in the old Win7 install:
VelociRaptors configured using Windows Disk Managment in a RAID 0:
Windows boot time is faster than ever, obviously the new SATA III SSD helps, but because I'm not using the built-in mobo RAID controller, there are no pauses anymore during POST on boot-up as the hardware controller waits and displays the configured drives before finally booting to the OS. \o/