Should I paste the 2 microcodes in with HxD, and fill the rest of the microcode spacing with padding "FF"s? The site only detailed 2 situations- one is that the microcode length is identical, and the other being the BIOS having padding to make room for the new microcode. ROM file? I am fine with deleting other microcodes, especially those pre-production ones (there are total 9 microcodes, and only 3 are production). Now, my question is, what should I do to incorporate both microcode updates for 2065 into the. If I perform ‘paste write’ on microcode 20652, part of the old 20655 microcode will be replaced which is also undesirable. Thus, there is exactly 0x1C00 lines for 20652 and 0x800 lines for 20655, which is less than 0x2400 lines and 0x1000 lines in the new microcodes. ROM is the first one after a series of "FF"s, and the 20655 microcode is immediately after that, followed by even more microcodes without spacers. In HxD editor, I figured that the 20652 microcode of the. I realized that the tool has incorrectly truncated the microcode (which is supposed to be 0x2400), and hence stopped using this method and proceeded to use this guide instead: …microcodes.html I think this is by design of the tool), but the 20622 modded one throws an error: “Microcode #1 is packed or badly extracted, please report it!”. Upon opening the 20655 modded file in MCExtracter, the 20655 shows up fine(all other Microcodes are removed including the pre-production ones. Using Micro Code option, I inserted the 20652 MCU and the 20655 MCU separately into the file and obtained 2 modified files. Next, I attempted to use EzH2O V2.1.0.13 to modify this.
bin format from, I ran them in MCExtracter and they came up as 0x2400(20652) and 0x1000(20655). The new Microcodes for these CPUIDs, in comparison, are larger.
I noted that the size of the 20652 Microcode is 0x1C00 and the size of the 20655 Microcode is 0x800. Upon placing this file in MCExtracter R64, both 2065 comes up as outdated which is expected. I did this twice and verified the checksums, and got INSYDE-1.40.ROM as output. The 460M however, is strictly 20655.įirstly, I used Universal BIOS BackUp toolkit 2.0 to retrieve my BIOS. However, I might consider upgrading it to an i5 460M in the near future because they are sold for just a few bucks second-hand. Using AiDA64, I have verified that my i3 is of CPUID 20652.
Hence, I wish to modify the BIOS to add new microcodes for the following CPUID :20652, 20655 so that it is protected against Spectre V2.įrom what I have gathered, CPUID 20652 is for i3 3X0M only, and 20655 is for i3 3X0M and i5 4X0M. Hi everyone, I have a Satellite Pro L630 which (obviously) does not have a BIOS update for Spectre V2.
0 kommentar(er)
