Zitat von Coldblackice im Beitrag #15

---

Ah, I see. Well, following the format of your modded 12.6's, I "injected" the appropriate device and vendor id's in 12.7, but I have yet to uninstall RST and then try these out (the f6 driver of 12.7, as it seems that it's required because the installer executable wouldn't work...right?).

---

Zitat von Coldblackice

---

I'm a bit worried about a bad driver "handoff" between 11.7 and 12.7. Should I generally be alright trying these modded 12.7's out? (I understand the disclaimer that you're not responsible for anything)

---

The update of an AHCI driver is nothing to worry about, because Win7 has an inbox AHCI driver, which will allow you to boot into the OS in an emergency case (F8 option "Last good configuration").

Zitat von Coldblackice

---

On the eVGA forums, however, a member there (Henry) apparently has an x58 that was able to install native, non-modded 12+ drivers just fine, all the way to 12.6. Not sure how he was able to do that -- he claims it wasn't anything special, just normal installing.

---

If you force the installation by using the "Have Disc" button and skip all warning messages, you can install nearly each driver, even a totally inappropriate one. That is why I recommend to put the correct HardwareIDs of your Intel SATA AHCI Controller into the related INF file. This way you will get the best possible security to avoid a corrupted Operating System.

Zitat von Coldblackice

---

And side-related question -- I'm currently using a custom modded BIOS (modded by Henry) that has a 12.7 OROM. Question -- how do the OROM and Windows drivers function and/or work together? I've tried to get an answer to this on multiple sites/forums, but it seems that most don't know, or at least have a real concrete hold on it (or care to explain). I'm confused as to why both an OROM "driver" and a Windows driver are needed.
And what happens if their versions mismatch (like if OROM version is higher than Windows driver, or vice versa)? Is it recommended to have specific pairings between the two, or is it sort of like the BIOS, where once Windows "takes over", the BIOS steps out of the way and lets Window manage all the hardware directly?

---

As you can see within the Device Manager, the OS needs special "IDE ATA/ATAPI Controllers" or "Storage Controllers" to handle the storage devices (HDDs, SSDs and Optical Drives). The Intel RAID ROM is as part of the BIOS and is the "Firmware" for the Intel SATA AHCI and RAID Controller. That means, that it contains OS-independed all informations regarding the functions and the possible features of the related Controller. During each boot procedure the OS specific AHCI/RAID driver communicates directly with the BIOS and its Intel RAID OROM module. Both of them (driver and OROM) need each other and should match regarding the version branch (e.g. v11.2 or v12.7), if the users wants to get the best possible results.
Intels AHCI and RAID drivers usually are fully backwards compatible with older or even outdated OROM module versions. The only disadvantage of such mismatching combination (OROM version much older than the driver version) will be, that you will not get an optimized system. But if you have a vice versa situation (OROM version from a newer version branch as the driver) it may happen, that the combination doesn't work at all, because the OROM information are not understandable for the related older driver.