I'm not sure but perhaps the IntelSnbGopDriver's code includes some kind of microcode-GUID chars inside "17088572-377F-44EF-8F4E-B09FFF46A070" and your UEFITool's 0.28.0/A58 parser thinks is a new microcode section when are just some GUID chars inside the DXE driver code. However, if I remove the IntelSnbGopDriver, the "pad-file" dissapears and, then, I can remove some DXE drivers and everything works ok. If I open it with the 0.28.0, no alignment warning appears, but I simply cannot remove any DXE driver or the bios will be incorrectly re-generated and the board won't boot. and a "pad-file" is generated just after the SandyBridgeGop DXE driver. UEFITool is a cross-platform open source application, that parses UEFI PI-compatible firmware image into a tree structure, verifies image integrity and provides a GUI to manipulate image elements. I'm trying to make a mod for an Asus Maximus V Gene board (latest bios 1903) from here:īut I've found an issue: when I open the bios using the A58(new engine), some "parseFileHeader: file alignment 10h is greater than parent volume alignment 8h" warnings appear.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |