0.17.8 is out. Changes: - solved some possible memory leaks and minor bugs found by Coverity Scan static analyzer - solved a bug with extended volume header handling in growVolume routine found by PVS Studio static analyzer - EFI11 and Tiano compression code reworked to remove duplication (which makes application file a bit smaller) I'm working on my master thesis and can't develop any new features, but I have prepared code base (not committed yet) for working from console instead of GUI, which makes application file three times smaller and can be helpful for scripting. At first, there be only uefiextract utility, that will extract an image to DUMP folder like PhoenixTool does, any other CLI features will be implemented later.
0.17.9 is out. Changes: - CRC32 checksum on GUID-defined section with GUID FC1BCDB0-7D31-49AA-936A-A4600D9DD083 is now checked and recalculated properly. I haven't seen a single case of problems caused by invalid CRC32 there, but if I can recalculate it - why not. - a bit better handling of compressed GUID-defined sections based on known GUIDs instead of trial-and-error approach. Consider inspection your BIOS images modified by previous versions for invalid CRC32 checksums and correct them by performing "Rebuild" action on affected GUID-defined section.
0.17.10 is out. Changes: - some additional info like GUIDs, versions, etc. to information window for all suitable item types - removed useless check for rev1 volume alignment (I wasn't work as expected anyway, and correct implementation will cause too many error messages for nothing) - 800 Kb lesser executable due to use of Qt4 instead of Qt5 All rev1 volumes I have seen are using the same attribute pattern, that means "all possible alignments from 2 to 64K supported", but not a single vendor gives a single f*ck about actually supporting alignments upper 8K, so I chose not to bother too. There were numerous spec breaks at the time of rev1 volumes, so it's stupid to go all bonkers about this particular one.
UEFIExtract utility is out. It's my first approach to implement a part of UEFITool functionality with console UI, for that I've received many requests. Usage: uefiextract imagefile.bin (you can also drop image file on executable file icon to run it) Utility will create a folder named after supplied image file name with ".dump" suffix added, and unpack all tree items recursively into this .dump directory. Each directory will contain maximum of 3 files: header.bin (can be absent if there is no header), body.bin (can be absent if there is no body) and info.txt, as well as subdirectories for all child items with the same structure. Just try it and see what it's all look like.
Hi, Does not work, i get this error. Fred Code: Process: UEFITool [23851] Path: /Users/USER/Downloads/UEFITool.app/Contents/MacOS/UEFITool Identifier: com.yourcompany.UEFITool Version: ??? Code Type: X86-64 (Native) Parent Process: launchd [160] Responsible: UEFITool [23851] User ID: 501 Date/Time: 2014-05-08 08:09:22.970 +0200 OS Version: Mac OS X 10.9.3 (13D55) Report Version: 11 Anonymous UUID: 3058837D-552F-1360-052D-37CDD830CC37 Sleep/Wake UUID: 50177CD6-C6F9-4787-A734-C46CCAB4A1C3 Crashed Thread: 0 Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000002, 0x0000000000000000 Application Specific Information: dyld: launch, loading dependent libraries Dyld Error Message: Library not loaded: /usr/local/Trolltech/Qt-4.8.6/lib/QtCore.framework/Versions/4/QtCore Referenced from: /Users/fred/Downloads/UEFITool.app/Contents/Frameworks/QtGui.framework/Versions/4/QtGui Reason: image not found Binary Images: 0x7fff6d976000 - 0x7fff6d9a9817 dyld (239.4) <042C4CED-6FB2-3B1C-948B-CAF2EE3B9F7A> /usr/lib/dyld 0x7fff8d688000 - 0x7fff8d6d6ff9 libstdc++.6.dylib (60) <0241E6A4-1368-33BE-950B-D0A175C41F54> /usr/lib/libstdc++.6.dylib 0x7fff925b5000 - 0x7fff925b6ff7 libSystem.B.dylib (1197.1.1) <E303F2F8-A8CF-3DF3-84B3-F2D0EE41CCF6> /usr/lib/libSystem.B.dylib
FredWst, rebuilt and reuploaded, thanks for report. It was a problem with macdeployqt's flags, I hope it's gone now.
Hy folks, i would like to integrate ozmosis stuffs into hp bios, uefitools dont permit me this, someone has some doc about if it's' posible?