-
Notifications
You must be signed in to change notification settings - Fork 647
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UEFIExtract folder names in OS X #38
Comments
Thanks for reporting, I will add a workaround to show GUIDs for firmware volumes even if their text fields aren't empty. Patch is ready, new binaries will be done tomorrow. |
Please excuse me for not building those binaries, I will be in Russia up to the 6th of December, will build them after returning home. |
Ooops got lost on my mental queue. Don't worry, I got UEFITool building in OS X (pretty easy, great work!) and created something for what I wanted to do using UEFITool core code. |
Will do. Closing this issue now, will release a never version today after restoring the build environment lost to a broken SSD. |
Hi,
UEFIExtract will not use the GUID for firmware volumes for OS X EFI images. It instead uses "AppleCRC32 AppleFSO" text field that shows ip on UEFITool.
Instead of this code in FfsEngine::recursiveDump
QString childPath = QString("%1/%2 %3").arg(path).arg(i).arg(model->text(childIndex).isEmpty() ? model->name(childIndex) : model->text(childIndex));
it probably should be
QString childPath = QString("%1/%2 %3").arg(path).arg(i).arg(model->name(childIndex));
Personally I find it more useful to have the GUID as folder name instead of that text.
Best,
fG!
The text was updated successfully, but these errors were encountered: