5/29/2023 0 Comments Uefitool unable to editThe item selected in messages tab is barely visible. Let's say the focus is in the tree/structure, something like in the image above. For me, it should be something like this: This takes me to that section, but the parent GUID is hidden. Let's say I have clicked a few messages, than I want to click a previous message, in reverse order. If somehow every GUID in that area is expanded from previous searches, it will get very confusing and you need to always visually check the parent. It is helpful to have the parent GUID in bold, to know where you are standing. Notice that the focus is in Messages tab, I have double-clicked one of the messages and it has scrolled in the tree to that section. Keep up the good work.Ĭlick to expand.Here is the first case: I do know there aren't many users of this tool, so any report is useful, and detailed reports are very useful. Please explain further (some drawing will be nice, because if it comes to UI stuff, I'm becoming pretty dumb), how it should work and why. More to say, if a section is really misaligned, parser code can't find it, because section header is too generic to be found by pattern matching.Ībout positions in tree: right now I'm just using scrollTo(item), so I have no control over it. N-bytes alignment is not "make the size of this chunk NxSomething", but "start this chunk at NxSomething offset". MMTool includes 2 additional empty bytes of FFS alignment, which have nothing to do with a file itself and are part of firmware volume. That CapsuleX64.ffs is 0x2F6E bytes long, with a UI section of 0x0E bytes, and UEFITool extracts it exactly like this. UEFITool does the extraction according to FFS file header, and if it's size is not 8xSomething, no additional bytes will be included. MMTool includes FFS alignment bytes as part of an extracted file for some reason, so all MMTool-extracted files have 8xSomething in size, with 0 to 7 empty bytes at the end. 0xFF in like 99,99% cases and 0x00 otherwise). There are also alignment requirements for FFS files, they must be aligned to 8 bytes boundary by default, and default alignment byte for FFS files depends on volume's erase polarity (i.e. Alignment bytes must be 0x00 according to the spec (MMTool uses 0xFD, AFAIR, but it's not the bug I'm talking about). Specs says that all sections must be aligned to 4 bytes boundary, with 0 byte beginning right after FFS file header. I think you have some wrong assumptions about section alignment, and MMTool proves them to be correct because of a bug in it. Good thing is: if you don't touch it - it won't be modified at all. I will try to implement more convenient way to parse RAW file, so if there are something wrong, no subitems will be shown. In the meantime, it can be useful to users who want to extract or update the information inside a BIOS file.The whole thing about parsed-but-not-showed contents pisses me off too, but the main reason for this is that all reconstruct* routines are using tree items and only them for reconstructing BIOS image, that is why I'll better not add something malformed into the tree. In a nutshell, UEFITool makes quite an impression, although it's still got a long way to reach the peak of its development. Once you're done with the editing part, you can export the image locally, for later use. The operations that you can carry out with UEFITool are various and make quite the list you can extract data from an image (or just the body) or you can insert items inside the structure of the image, as well as to insert or remove unwanted pieces. UEFITool is compatible with a variety of BIOS image types, including ROM, BIN, CAP, BIO, FD, WPH and EFI, which are loaded and displayed inside a structured view, alongside details such as name, type and subtype. The application sports an extremely simple design and is less impressive in terms of appearance the compromise it makes on looks is certainly compensated in functionality, if we look at the bigger picture. This is not to say that anyone can handle an application such as UEFITool however, with a minimum level of knowledge in BIOS modding, users can make the most of it and achieve modified versions of an UEFI image in a complication-free manner. The management of UEFI images is said to be a job for professionals, although UEFITool delivers an approach that doesn't target advanced users exclusively. UEFITool is brought in a line of work that was less exploited and advertised up until recently. UEFITool is a versatile application that accepts BIOS image files as input in order to facilitate the visualization and editing of the data inside them.
0 Comments
Leave a Reply. |