@ lordkag :
Sorry, I haven't studied, and thanks for the pic's. When I used replace it didn't work, when I used the legacy rom it did. What I don't get is, why did it work in legacy, when I am running UEFI, shouldn't I only see the 13.1 series OROM if I was booting in legacy (BIOS ) and not in UEFI, if I am making the error of using option rom ?

I have checked system and it shows UEFI, also when I boot I see Asrock, if I was booting BIOS I would see windows load and not Asrock load. I will take a look at the original GUID in a clean BIOS file, and look at the SataDrivers posted by you and Fern and see which ones match.




P.S. Does anyone know what's up with Station Drivers, they use to list all the RST, RSTE OROMS and all drivers. I can't find any but one, and the one under BIOS for motherboard drivers ?

@ Fern:
Thanks Fern, but they just had a listing of Intel hardware like a week agao, now the format is different and only one RST. I just hope they can post it back.


@ Lordkag :
I will need to go back an re read your postings and Ferns in mod section. Under MM tool, the GUID for SataDriver 12 starts 5BB2F356. Then looking at the actual .FFS with Hex - the top Hex line shows for my original SataDriver 12 as - 56 F3 B2 5B 4A.
Your SataDriver 12 shows as the same. Ferns SataDriver Universal shows as 55 AA EC E9 D2. I guess I don't know if I am suppose to match the top Hex line for the SataDrivers, but like I said, Ferns worked.

Not sure how to explain this. The GUID using MM tool is not the same as looking at the actual .FFS file with Hex. I guess I only have the Hex line to compare one .FFS to another .FFS SataDriver. I don't see how to check the GUID of a .FFS file.

Sorry, if I am not getting it, if you don't get what I post, I understand, I will just ask someone to mod if I need it, so I don't torture you. Thanks for all the help already.

@ Fern :
Thanks, now I see it.

@odiebugs

I am sorry if I offend it you, but you do need to read a bit before asking some questions. It is not that I am condescendent, but it should be the unwritten rule of any learning process. I try to help as much as I can and even go overboard by providing the final mod, when Fernando started this forum as a DIY and not as a "user request".

If you watch my posts you will see that I post and try to help to the extent of my limited knowledge. But I try to avoid the questions that have (or should have) an answer in the same forum.

As a final thought, I think you again mixed ffs with OROM. The second 55 AA EC E9 D2 you posted seems to come from a bin file, which always starts with the 55 AA signature. I could be wrong of course, but I haven't seen any SataDriver with that GUID. I learned a lot by reading and hex comparing different modules. I also learned a lot by reading Fernando's guides.

Again, sorry for the somewhat strong tone, but it is a lot better to try to fill only the blankets with the help of others, than to ask them at each step.

@ Lordkag :

You don't have to say sorry, and you have done nothing but help, I just having a hard time getting it. The 55 AA EC E9, is the top line from Hex HxD, it's Fernando's 13.1 SataDriver Universal, mod for TRIM. You didn't offend me, I said sorry because I have a hard time and hate to ask so much.

Let me just post what I have tried. I used MM tool, used replace, I tried your 13.1 SataDriver 12, I also tried Fren's SataDriver 13.1 mod TRIM. It goes in, when I check the modded BIOS file and extract the SataDriver 12 it shows 13.1. When I flash the BIOS it's still has the 12.7.

The only way I can get the 13.1 option rom to show at boot, is to use the option rom link in MM tool. Like I said, I am in UEFI mode, I don't get a windows post, I get a Asrock post at boot. I get a AS-SSD score of 1628 with the 12.7 option rom. I get a 1642 score with the 13.1 option rom.

I get that the option rom link in MM tool is legacy, but I am in UEFI booting, and I do have the 13.1 option rom showing, so I have no clue why it's working and why just replacing the SataDriver didn't.


Again, thanks to all, I appreciate the help, will try and spend time tonight reading over the forum.

When you have an option rom showing during booting you're not on UEFI. On pure UEFI you should have the RAID menue inside the BIOS just below your USB and Intel ME in the advanced chapter. There should be an entry like Intel 12.7.xx Sata Driver, when you enter there you'll see your array. For that you have to disable CSM.

Edit
I can see "BIOS mode = UEFI" in the picture you uploaded but that means only that your BIOS is of UEFI type and not that you boot in pure UEFI mode

@ hanson :
Lost me. On the advanced tab, I have folders, CPU, North, South, Storage, USB, ME, under folders, is instant flash. In side the storage is RAID settings, I don't see anything with any sata version. I don't suppose you have a pic or one from your manual that shows what your saying ?

I see you looked at the pic, but I don't see in my BIOS the 12 or 13 SataDriver, all I know is I booted from USB flash in UEFI, installed win 8.1, I know that if I boot BIOS I see windows loading, in UEFI I see Asrock loading. How can I see if I am in pure UEFI ?


***** In BIOS Under BOOT tab, there is ADDon ROM Display which is on, I can disable it and the rom won't post.

You have to set your booting to standart first (no fast or ultra fast booting). Then you have to enter the ACPI menue inside advanced options. There you set CSM to disabled. Then you reboot and enter the BIOS. Now you should see the Sata Driver entry and - if you like - you can set booting to "ultra fast". Also you should activate secure boot. By the way, do you have a discrete graphics card of the GTX 700 series? If not this function (UEFI mode) will not be supported by the card. With a GTX 600 you could be lucky and ask EVGA for example for a UEFI BIOS for your card, this is absolutely needed.

Regards hanson

@ hanson :
Thanks, I can't run in pure UEFI, can't disable CSM as my GTX 670 won't let me, so stuck with half UEFI.



@ Fern :
I must have hit the wrong file after ONEDRIVE opened, I see now the 90 starts with 94, and the 91 starts C1.

@odiebugs

First use Hanson's advice and test with CSM = Disabled. This way you will boot in UEFI mode. Secondly, you can work with Hanson even further, since he has a very similar board. From your screen, BIOS mode = UEFI means that you installed Windows in UEFI mode, not necessarily that you are still running in UEFI.

The line 55 AA EC E9 does indeed come from a RAID OROM and not from a SataDriver. A small hint: usually OROMs are xyz.bin and UEFI drivers are xyz.ffs.

The GUID, ID and others things are stored in little indian, which means hex reversed. You have to watch though, that only the first 3 pairs from GUID are reversed, the last 2 are in visual order. Also know that those numbers are actually hex numbers and every two make a byte.



When modding your BIOS, always have this in mind:
- Legacy uses CSMCORE + CSM Enabled + Link Present + ID like 8086-55AA + bin file for modding + signature of 55 AA when opening the bin file in hex.
- UEFI uses standalone drivers + CSM Disabled + GUID and name like SataDriver12 + ffs file for modding + GUID in little indian when opening the ffs in hex.

@ Lordkag :
Thanks, I have to flash a clean BIOS, I was able to boot in fast mode, and in fast mode CSM option is missing, but when running windows in fast boot, I was getting problems, so maybe it was of the way I modded my BIOS.

Maybe the entire time I figured I was using the SataDriver I wasn't. I bet there is no easy way to see if the SataDriver is being used just as EFI boot. I wonder if my CSMCORE legacy was replaced with 11 series and the SataDriver was 13, if I open the Intel rom to make a array and it was 13, would this prove it was using the SataDriver ?


@ Fern: Sorry, for asking for help in this area.


************** What a goof, here the whole time I thought I was using SataDriver, I have been using legacy, it's why when I only mod SataDriver to 13.1 series I still see 12, and when I hit rom link it worked.


&&&&&&& Thanks Lordkag, for the CSM, legacy info. I can't boot pure UEFI or use SataDriver, this whole time I have been booting legacy orom, but because I was booting with Asrock and system info showing UEFI, I though it was the SataDriver. Until I get a card that will allow pure UEFI, I am stuck using a RAID OROM replacement.

Sorry to all who I wasted your time, now I know highlighting in MM tool is not the key, it's using legacy or not.