You can add and remove pieces as you see fit, as long as you know what you’re doing. Image types you can fiddle with include BIN, BIO, ROM, CAP, WPH, FD, and EFI. If you’re wondering about BIOS compatibility, you’ll be happy to know that there are many functions you can play with and enjoy. UEFITool presents the information to you in an easy-to-read format. Of course, you’ll need some basic knowledge of what you’re looking at before you can make any changes. Everything is laid out neatly for you in windows where you can find all the data you need. 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.The first section that makes UEFI-changing life easier for you is the simple EUFITool interface. 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. 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 |