Zitat von SoniX im Beitrag #2640

---

I got it! I'm a slowpoke. It shows the version in the image of the BIOS, and not in the computer BIOS chip.
And as if to write correctly? :)

---

1) MEI = Management Engine Inteface so Driver, not Firmware
2) If a BIOS/SPI has TXE or SPS, it will still say "MEI" which is obviously wrong

Parameter "-extr" is used for Extractor/UEFIStrip and outputs 5 firmware attributes separated by spaces at a single line. We have:



The command is:

for /f "tokens=1-5" %%a in ('MEA\MEA.exe bios.bin -extr -adir -disuf') do (echo      WHATEVER)
 

%%a = Type (ME,TXE,SPS)
%%b = Full File Name
%%c = SKU
%%d = Version
%%e = Date

UBU should only use a,c, d and optionally e. Not b, this is only useful for Extractor/UEFIStrip which needs to extract and rename the extracted file appropriately. So, instead of saying FW MEI, you can say FW %%a. Also, "FW" text is not needed: UBU obviously deals with firmware. I don't see RST being mentioned as FW anywhere because it's obvious.

Now, someone needs to answer me this question:

Why does MEA make people believe that it shows the FW of their system and not the (obvious, maybe to me only?) fw inside their just loaded BIOS/SPI image? Why don't they (in a similar fashion) believe that the RST or CPU Microcode or LAN modules shown above are the ones the system currently uses? Why is MEA any different? I really cannot understand that logic.

I have tried to explain this many,many,many times and even added a dedicated message at UBU, when people press 9 to see their BIOS/SPI image (not system's) Engine firmware version.



So, for the new UBU Menu text shown I see two possible solutions:

1) The above purple text is added at the UBU Pre-Menu screen when Engine firmware is detected
2) The echo text at the for /f command shown above needs to say that this is the Engine FW of the just loaded BIOS/SPI image

Regardless of that, I have decided that from next version of MEA, parameter "-info" will be removed entirely and MEA will only show the fw of the loaded image just like it always did and just like it's intended.

@ SoniX:

Parameter -dker is not needed for UBU (it will appear automatically if the SKU cannot be detected for post-SKL firmware). If you want to have it, just add it automatically and not mention DKER because noone knows what it is or what it does other than 3-4 people.

Parameter -info will be removed from MEA but I can create an additional exe at the Dev folder which will just print those 2 lines or an error if MEI/TXEI is not installed. However, it makes no sense to have this. Anyone can load an Intel image while working on an AMD system or a system without MEI or TXEI drivers installed, which will cause an error and thus -info will not show anything at that system. I wouldn't be surprised at all if people complain because they cannot use -info at their AMD or VIA system.