Zitat von Fernando im Beitrag #1111

---

@ bolt4brekfast:

Welcome at Win-RAID Forum! It is a pleasure for me, that you are a member of my Forum.

---

Zitat von Fernando im Beitrag #1113

---

@ bolts4brekfast:

If you don't want to wait for SoniX's answers and need the SataDriver43_x79 v13.5.0.2164, please let me know it. Then I will create the file for you and other X79 chipset users.

---

And I assume that afterwards, Intel RST will report 13.5.0.2164?

UPDATE: It works! Thank you so much for taking the time to do this!

Zitat von bolts4brekfast im Beitrag #1116

---

---

@Sonix and Coderush

I am grateful for your kind words, since both of you were a major influence in starting this, but I don't plan to release it to the general public, not even on a separate thread on this forum. My coding skills are at high-school levels and are bound to stay there, because of some personal problems, plus I'm not that sociable to be in front of a project. I just wanted to have this discussed like gentlemen. It was my way of asking for pardon or acceptance, since it is a little rude to have this published on your thread and with your code. If it is OK with you, I will only post once in a while, when I add/fix something important, to not clutter this thread. Fixes happen all the time in the background, but I won't publish them until there is a great need for them.

I will use this post to publish another version, since I have added something useful. Now the Extractor tries to detect the GUID for those OROMs placed out of CSMCORE. It should catch most cases, where the OROM follows after header, especially in Insyde BIOS. If there should be misses, I will try to do something when I'll have test cases, but I feel it would be close to impossible without a full parser. There are some lines (546-549) in Z.Version.py for extracting the ffs containing OROM, if it should be needed, but right now I'm only extracting the OROM itself.

I have also noticed that OROMs might get extracted multiple times for APTIO, when CSMCORE or CSM-EFI is uncompressed. This can be prevented by adding a variable in lines 170-171 of Extractor.bat and search main volume only in that case. But this might skip some strangely placed OROMs in APTIO, so it would be better to just uncomment line 767 in Extractor.bat if you want to have a clear distinction.

@lordkag
Thank you for your utility is very useful. Keep it up! Always looking forward to your news. :)

PS Check definition versions of files in the archive.
Add:
Unfortunately many of the files associated with USB, do not display the version.

I'm getting "file size exceeds the volume size" with UBU 1.8.15 trying to update microcode on Rampage IV Black Edition 0801 bios.

Zitat von HydrasunGQ im Beitrag #1120

---

I'm getting "file size exceeds the volume size" with UBU 1.8.15 trying to update microcode on Rampage IV Black Edition 0801 bios.

---

Zitat von SoniX im Beitrag #1121

---

Zitat von HydrasunGQ im Beitrag #1120

---

I'm getting "file size exceeds the volume size" with UBU 1.8.15 trying to update microcode on Rampage IV Black Edition 0801 bios.

---

This is not a bug in UBU, it is a problem of free space in the BIOS.
Give a link to the BIOS and microcode which you specifically need?

Edit:
If you need to update only for SandyBridge-E (06D6/06D7) choose option "2".

---

Zitat von HydrasunGQ im Beitrag #1123

---

I'm trying to update IB-E microcode.

---

I have a 4960X