@vmanuelgm

Are you serious or joking? These are the basic foundations of Hex, Dec, Oct, Bin. :)
The easiest way to convert this is to use the Calculator in Windows, in the Programmer mode.

OROM VROC RAID 6.2.0.1034
Size (Dec) 112640 byte -> (Hex) 0x0001B800 -> {00 B8 01 00}

@SoniX
The thing is I'm more on the letters side, so don't be rude with me!!!
Thanks a lot again.
;)

I recommend deleting this message, to avoid further confusion.



PS. If I have an issue updating uCodes (not all entries get updated), should I ask here, or send PM to someone specific ?

@agentx007

Let's consider this situation. For example, you have a chip 82579, and Device ID 1539. To which version can upgrade without a problem?

Yes, there are BIOSes in which microcodes can be placed in different GUIDs. Only the standard GUID is updated, the second must be updated manually.

I own Sabertooth X79 and Rampage IV Black Edition (both with Intel® 82579V).
I attached X79 Sabertooth "stock" non-moded BIOS in this post.

Since "Recommended" option for update is 0.0.24/0.1.13 - I went with that, BUT it displays "can install up to 6.6.04/1.5.62", and only after that it proceded to update to 0.0.24/0.1.13.

Since you said newer version worked fine, I'm confused as to why there is such message ?
Just to be clear : I don't use Wake-On LAN at all. I simply wanted to clear things out.

PS. My Intel I218V board (Maximus VII Hero), also displays "up to 6.6.04/1.5.62" message...

Here's how uCode thing looks like (it's on Hero as well) :

@SoniX
The new GOP 1096 is not recognised by UBU once pasted in 1152v2 folder (unknown). UBU 1.76.0.1 won't allow using it as replacement, no replace option.
Is it safe to use this new 1096 with 212 RAW GOP???

@vmanuelgm

Yes, I know, I need to add an update to DrvVer.

If your versions 1082-1095 work fine, then you do not need to update the VBT.

@agentx007

I didn’t just ask you a question.
There are rules under which the necessary files are updated and work normally. UBU, when replacing, uses these rules. And if there is nonsense, then UBU replaces files with compatible versions. This message warns of this,

So... since I see this message with both recommended and the alternative options - I can safely assume both will work (because both options will use the same "compatible version" with my card, just as mentioned message suggests).

Did I understand this correctly ?

If the LAN chip configuration on the motherboard is correctly indicated, then the UBU will replace with the correct file versions.

Zitat von SoniX im Beitrag #548

---

Explain more specifically.

---

DrvVer v0.27.1 in Cloud


@pipes80

I do not know why it is so. They sent an archive of a folder with files that you can’t get. And BIOS file.

Zitat von Lost_N_BIOS im Beitrag #534

---

@pokuly - before I do anything, message that user and see if he ever tested that BIOS.

---

This link from the UBU main page is down -
Download the latest version of the 7z-archive named "Intel_RST (e)" from >here< (developer's hoster) and unzip it somewhere outside the UBU tool folder.
Where can i download?

I've got my Video OnBoard, Network, Other Sata Controller & CPU Microcodes updated using the UBU Tool but i can't figure out how to update the Disk Controller - EFI/OROM Intel RST for sata.
I've manually updated the EFI one using the mmtool with file satadriver90.ffs but then couldnt figure out how to manually update the Orom one. Just stuck at this point now.
p8z77-v premium.
bios 2104.

thanks

@KiLLz420

You do not have access to the page on this link?
https://cloud.mail.ru/public/SJtt/FeyYSFD6m