Adding 2 more..

Zitat

---

SHA1:EAE12F2A2FC8E4CF96AFB436FA637A18722B9988 : MMTool-3.19.0000-.exe
SHA1:A3E47E29A2F79D67E111B5917E61AAD0B64C6F93 : MMTool-4.50.0023-.exe

---

DB r63

@whatnot

There is also version v3.26 it's SHA1 checksum can be added as well.

SHA1:05d81e32820d6618f0b77990fa376764615c5bd8 : MMTool v3.26.exe

Got an error message reading in an Aptio V BIOS from an AMD board with v1.70 a16: "'aet' is not recognized as an internal or external command, operable program or batch file."

I searched for "aet" in the batch file and I think there's a typo on line 143: "uefifind body count 4147455341 bios.bin>nul && aet amd=1 && goto amdextr". "aet" here should probably be "set".

@ Ver Greeneyes

Version 1.70 in the Alpha stage, so many small bugs.
But thank you for the information.

Hey all
I have Hero VII Z97 MB.
In UBU i get these for Intel Lan:

@ karserasl
If Intel ChipLAN OnBoard 82579/217/218/219 update Option 1
But you can use option 2 if the chip is 82579/217/218

Zitat von SoniX im Beitrag #3892

---

@ karserasl
If Intel ChipLAN OnBoard 82579/217/218/219 update Option 1
But you can use option 2 if the chip is 82579/217/218

---

Zitat von karserasl im Beitrag #3893

---

My NIC is Intel(R) Ethernet Connection (2) I218-V
So you suggest Option 1?

---

Hello, @SoniX .

I have a few questions about Intel CPU Microcode:

1. What's MPDT ? What does it do ?
2. My BIOS (MSI Z170)have 2 Microcode module in 2 volume and first has MPDT_BOOT_NO , second has MPDT_BOOT_YES . Can I add Microcode to both volume ? Do I need replace first MPDT_BOOT_NO to MPDT_BOOT_YES ?
3. Can I Insert Microcode to 2 or 3 volume and edit _FIT to point to them ? Will it work ? Which MPDT to use ?

Seems like mCodeFIT cannot handle some situation :

1. _FIT is located after Microcode module.When I add new Microcode , the address of _FIT changed. And I need to edit the VolumeTopFile to point to new address of _FIT.
2. Microcode module is located in 2 or more volume.
3. Sometime I found mCodeFIT didn't change the size of FIT Header when I add or delete Microcode .

Best regards.

@SoniX:
Could you please add support for recognizing NvmExpressDxe_Small. Lack of support seems to cause confusion among users in the [Guide] How to get full NVMe support for all Systems with an AMI UEFI BIOS thread.

Although I've removed all character strings to conserve space, a private protocol GUID specific to this driver could be used for identification:

uefifind body list 0D85CB4033203646BA1466790571757E bios.bin

L"NVM Express Driver\0NVM Express Controller\0\0"

@ Ethaniel
For 1-3 variants of drivers CT NVMe it is possible to make corrections, but for "Small" variant it is not clear what sequence of bytes to take.

@SoniX:
Please use the following pattern to identify NvmExpressDxe_Small that is a GUID I have generated specifically for this driver:

0D85CB4033203646BA1466790571757E

@ Ethaniel
Use to determine the GUID is not true. Since someone can set their GUID,
But I'll see what can be taken as the basis for the definition of the "Small" option.

@SoniX:
This an internal protocol GUID compiled into the .efi file so cannot be modified as simply as the FFS GUID.
Note that for the FFS file I just used the standard EDK2 NvmExpressDxe GUID that is not specific to my version.