Quote Originally Posted by Ace-a-Rue View Post
i used it before for raid and it worked!...don't know if that is true for AHCI.

well, after many hours of fooling with trying to make AHCI work...i finally conquered it.

i was overclocking pretty good...i thought my voltages were sufficient but not necessarily for a DOS windows install.

on the first couple of attempts my solo drive was not showing up in the windows setup...the post screen showed AHCI...the post screen was quick...i could not catch it correctly by using the "pause" key...i see part of it...the drive info went like a flash...could never read it.

after multiple re-configurations by plugging it into different Intel ports...it finally showed up when i enable the virtualization technology...that little change made the drive partitions show up...i made two partitions on the drive through my other OS...i then turned off the virtualization setting and that did not disrupt the AHCI from that point on.

i am thinking the vcore was a tad low and the ICHIO 1.5 was a tad low to support the overclock in DOS...on top of that, my memory timings were probably to tight...loosen those up too!

finally, i was able to use AHCI on the solo drive.

the procedure the way i see to utilize AHCI.

1. enable AHCI in the bios

2. set boot device order such as hard drive, sata drive (select drive name), floppy (if installed).

3. go into "hard disk booting priority" and move the drive to the top of the list that you are using for AHCI.

4. set sufficient vcore, CPU VTT, MCH, vdimm and ICHIO 1.5v to support your overclock...even if you run setup at default speed juice up vcore and ICHIO 1.5v just a little.

5. run loose timings during the OS install

that's it in a nutshell.
Wow very complete work.

Do you think this might aid/fix my raid problem?

Do I install the first one on the list here?