Both tools have been developed and is still kept up-to-date by our Forum member CodeRush.Īt first view the usage of the UEFITool may not be as comfortable and easy to understand as the usage of the related AMI Aptio IV or Aptio V UEFI MMTool, but these are the benefits the users of the UEFITool will get:ġ. My favorite UEFI BIOS modding tool for these specific tasks is the normal “UEFITool” (don’t use the _NE variant for this purpose). (AMI) doesn’t allow to offer their AMI Aptio UEFI MMTools for the public, you may have to use another tool, if you want to manually modify an AMI UEFI BIOS according to your wishes. Since the company American Megatrends Inc. AMI-specific features like NCBs, ROM_AREA structure and other things like that can't be implemented by me because of the NDA I have.All users, who want to manually optimize the UEFI BIOS of their manboard/system:.If someone wants to write an unpacker for such crappy files - I will be glad to use it. The program is meant to work with BIOS images, not some vendor-specific BIOS update files, that is why some of that update file either cant be opened at all or return errors on reconstruction.It's on my high priority features list, so I hope it will be corrected soon. Some images may not work after modification because of no FIT table support implemented yet.Some images has non-standard calculation of base address of TE images, so the program can rebase them incorrectly after modifications.Don't rush it, because reconstruction process can also generate some usefull messages, which will be lost if you open the reconstructed file immediatelly. If anything goes wrong on the reconstruction, an error will pop up, otherwise the program will prompt if you need to open the reconstructed file.
After you've finished the modifications, you need to initiate image reconstruction using Save image file command from the File menu.
0 kommentar(er)
