Forum - RE: ME Analyzer: Intel Engine Firmware Analysis Tool

Win-Raid Forum (Drivers - Firmware - Modding) � Special Topics � Intel Management Engine � ME Analyzer: Intel Engine Firmware Analysis Tool Discussion

Page 14 of 21 � Page 1 ... 9 10 11 12 13 14 15 16 17 18 ... 21 Page �

Topic settings

Print view

Jump to forum

General & Forum related Topics News / Announcements Forum-related Questions & Suggestions Off Topic Important Drivers (AHCI/RAID, NVMe, USB etc.) General: Storage Drivers (AHCI/RAID, NVMe and USB) Specific: Intel AHCI/RAID Drivers Specific: NVIDIA nForce Chipset Drivers (incl. AHCI/RAID) Specific: NVMe Drivers Other Drivers System Performance RAID Performance AHCI/NVMe Performance Solid State Drives BIOS Modding BIOS Modding Guides and Problems BIOS modules (PCI ROM, EFI and others) BIOS Modding Requests Reports: BIOS Modding Results Offers: Already modded special BIOSes Special Topics Intel Management Engine CPU Microcodes NVMe Support for old Systems Other Tools (not BIOS modding related) Interesting PC Hardware & Software OS related Topics Windows 11 Windows 8-10/Server 2012-2019 Windows 7/Vista/Server 2008 Windows XP/2000/Server 2003 DOS/Windows 3.X/9X/ME - Retro Gaming Other Operating Systems

#196 | RE: ME Analyzer: Intel Engine Firmware Analysis Tool datum

Sun Sep 11, 2016 7:36 pm (Last edited: Sun Sep 11, 2016 7:39 pm)

ME Analyzer v1.6.3

@ CodeRush:

So, if I understand properly, I should have instead a BlockLength of 0x1000 with NumBlocks 0x37B0 which equals an FVLength of 0x37B000. Am I correct? I generally noticed that all volumes have a NumBlocks value of 0x1000 and the equivalent BlockLength (to get FVLength) is obviously not a power of 16.

reply

#197 | RE: ME Analyzer: Intel Engine Firmware Analysis Tool datum

Sun Sep 11, 2016 8:52 pm

Then I've just messed up with order. 0x1000 is obviously a BlockSize of 4K, and other value that is changing is NumBlocks.

reply

#198 | RE: ME Analyzer: Intel Engine Firmware Analysis Tool datum

Sun Sep 11, 2016 9:04 pm (Last edited: Sun Sep 11, 2016 9:05 pm)

That's ok. So should it be left as before (changing BlockSize only)? Usually the other volumes are like that, meaning with a steady NumBlocks (0x1000) and variable BlockSize based on FVLength.

reply

#199 | RE: ME Analyzer: Intel Engine Firmware Analysis Tool datum

Mon Sep 12, 2016 8:09 am

No, please change the order of values, i.e. on before it's 0x417 x 0x10000, and on after it should be 0x37B x 0x10000. First value here is NumBlocks, second is BlockSize, which must remain constant and be a multiple of 0x10.

reply

#200 | RE: ME Analyzer: Intel Engine Firmware Analysis Tool datum

Mon Sep 12, 2016 3:03 pm (Last edited: Mon Sep 12, 2016 3:04 pm)

Alright, that's what I had done before so I'll leave it as it is. I see what you mean, the documentation states that first value is BlockSize and second is NumBlocks, when the opposite is true, thus the confusion. Maybe they assume Little Endian, kind of weird for a human-readable structure but who knows. Anyway, now I can fix such images for tool parsing and if we see it regularly then I'll open an Issue ticket at github to either fix automatically or fallback to raw parsing.

reply

#201 | RE: ME Analyzer: Intel Engine Firmware Analysis Tool datum

Sun Sep 25, 2016 8:44 pm

ME Analyzer v1.6.4 & DB r65

reply

#202 | RE: ME Analyzer: Intel Engine Firmware Analysis Tool datum

Mon Oct 03, 2016 4:08 pm (Last edited: Mon Oct 03, 2016 4:08 pm)

ME Analyzer v1.6.5 & DB r66

Performance:

1.6.4 (Unoptimized, UEFIFind disabled) vs 1.6.5 (Optimized, UEFIFind disabled)

0.73 sec
0.15 sec

Improvement: 80%

1.6.4 (Unoptimized, UEFIFind enabled) vs 1.6.5 (Optimized, UEFIFind enabled)

2.05 sec
1.46 sec

Improvement: 30%

1.6.4 (Unoptimized, UEFIFind enabled by default) vs 1.6.5 (Optimized, UEFIFind disabled by default)

2.05 sec
0.15 sec

Improvement: 1350%

Note 1: UEFIFind is not included with MEA anymore by default. If you want to use Engine GUID detection (-enuf) then make sure to include it alongside MEA's executable.

Note 2: Most people use default settings with no parameters so they should see the 1350% improvement at MEA v1.6.5. People who had UEFIFind disabled (UBU and UEFIStrip) will see an 80% or so improvement . Even with UEFIFind Engine GUID detection enabled, you should expect at least 30% improvement.

@SoniX @lordkag

Remove the old "-disuf" from UBU and UEFIStrip as UEFIFind Engine GUID Detection is disabled by default now. If you want it enabled somewhere, use "-enuf" instead. MEA will ignore any "-disuf" parameter/filename input until your tools are adjusted accordingly.

reply

#203 | RE: ME Analyzer: Intel Engine Firmware Analysis Tool datum

Tue Oct 04, 2016 4:32 pm (Last edited: Tue Oct 04, 2016 4:34 pm)

ME Analyzer v1.6.6 Dev 1

Fixed issue that caused temporary files to not be deleted

Note: You should clean your %temp% folder and update MEA

Note: Affected versions are v1.6.3 - v1.6.5

@SoniX

Please update UBU with this Dev version