On motherboards with chipset 7th always basically DevID 162. This is normal.
I do not know why Intel suggests using the script version 1.65. All the files are original, provided by Intel. Yes, versions OROM VBIOS, and the script must be the same.
This is normal. The program displays a message version of the script, not the OROM.
Collection OROM and BSF-scripts. Strange problems with storage on SendSpace and RGHost. One server is lost, and on the other does not upload. So I upload here.
Looks like there’s a password on the VBIOS_and_BSF.rar that’s on RGHost, which I can’t find anywhere.
Also, could you please expand upon what you mean with:
These versions also have the mark
in the docx. I can’t figure out what either of this exactly means for upgrading.
In my case I have Haswell-Broadwell 1028 – can I upgrade to 1039? If I apply the transfer.ssf I extracted (from a Gigabyte M1.Sniper M5 T01 bios) I get a bunch of red books (with yellow pen) if I apply it to both the 1028 and 1039 files as found in your archive.
Don’t those red books in BMP simply mean that it has applied a setting it found in transfer.ssf in a way that altered the default? Does your
Thanks, I did notice that the same file on SendSpace doesn’t have a password and just took the files from it.
As for my other questions, I kind of answered them myself by flashing the modded bios to my mainboard’s backup bios chip – and it works! GPU-Z still reports “BIOS version 1028” when booted for the main bios chip, but now “1039” when booted from the backup chip.
Thanks for your guide!
edit: One more question though – is there a changelog somewhere that shows what changed between the versions?
Hello! Having my Sandybridge VBIOS update from v2104 to 2170 I got a problem with panel fitting algorithm (scaling of screen resolutions in DOS became narrow) since version 2120 or higher. According to Release Notes 2120 “Please refer to VBIOS SPS for changes to System BIOS INT15 hook 5F34 and INT10 function 5f61”, I’ve found the “5F34h - Set Panel Fitting Hook” option enabled in my VBIOS settings. Is it safe to disable this option to allow BMP default settings without System Bios errors or crashing?
UBU found two instances for OROM VBIOS: -OROM VBIOS Sandy/Ivy Bridge - 2119 -OROM VBIOS Sandy/Ivy Bridge - 2111 -EFI GOP Driver - Not present
I updated the first one from 2108 to 2119, it is device ID 102 (as expected). With MMTool i extracted the second OROM, it has the size 0FAC (=4012), DevID 106 (mobile? Its a desktop mobo). Ideas?