search

platomav / MCExtractor

Intel, AMD, VIA & Freescale Microcode Extraction Tool
Other
759 stars 103 forks source link

Breaks in a table #46

Open LSSoniX opened 2 years ago

LSSoniX commented 2 years ago

Hello Plato! :)

Look at this please

MCE v1.70.0 + DB 207 Example BIOS file https://download.asrock.com/BIOS/1700/Z690%20Taichi(1.43)ROM.zip

Command mce.py [-ubu] -skip -exit

Result screen

The main table is bursting with messages about new microcode. Is that how it should be now?

Thanks.

platomav commented 2 years ago

Hi! Do you mean that the DB is outdated?

LSSoniX commented 2 years ago

No, not a DB. Displaying the table. It just didn't happen before. In my opinion, it has always been like this - first, a complete table with all microcodes, and below the table there are messages about new microcodes.

platomav commented 2 years ago

Ah, I see. I guess -ubu parameter does not show the input filename so that's why the confusion. This is how it actually looks (notice the "temp" files):

Capture

As you can see, the "single/temp" microcodes are different input files. This is because the initial two microcodes include "Extended Headers" so each one includes 2 microcodes basically, so 4 in total.

Capture1

MCE parses the initial 2 microcodes (first table) and IF it finds extended microcodes, it extracts them and automatically re-inputs them to parse them separately. It stores them in temp files and parses them after the initial ones. So they appear in different tables because they are different files.