It might be necessary to kill any running default OS process of the same name DU 13 needs to access. I see from your Disk Utility for Mojave (not there yet).app (which does not even start in my 10.13.6, not even after I signed it) you already added the amework
*** Assertion failure in void *FinderKitLibrary()(), /BuildRoot/Library/Caches//Sources/AppKit/AppKit-1561.60.100/Nav.subproj/NSNavFinderViewFileBrowser.m:48 Convert Verify File/ New Disk Image from Folder Open Disk Image (same error): *** Assertion failure in void *FinderKitLibrary()(), /BuildRoot/Library/Caches//Sources/AppKit/AppKit-1561.60.100/Nav.subproj/NSSavePanel.m:810Ģ. New Image File/ New Blank Disk Image (same error): Break on _NSNumberFormatter_Log_New_Methods_On_Old_Formatters to debug. "Disk Utility 13 (607).app/Contents/MacOS/loader.sh"įailed to connect (cancelRecreate) outlet from (DUWindowController) to (NSButton): missing setter or instance variableįailed to connect (repairSheetInfo) outlet from (DUWindowController) to (NSTextField): missing setter or instance variableġ0.4-style NSNumberFormatter method called on a 10.0-style formatter, which doesn't work. I also got your message but reply here for best exposure and open collaboration.įile: Debug Disk Utility 13 (607).command (attached)Įcho "Put this script next to Disk Utility 13 (607).app" Thats where the DYLD injection comes in.ĭisk Utility Mojave attempt (not functional) - The loader is renamed and the original binary is used while testing.Īll the frameworks are from El Capitan, it seems to be the safest way. I followed that chain before and I hit a wall. In /Users/./Desktop/Disk Utility 13.app/Contents/MacOS/DiskUtility Referenced from: /Users/./Desktop/Disk Utility 13.app/Contents/MacOS/DiskUtilityĮxpected in: /System/Library/Frameworks/amework/Versions/C/AppKit But I am setting up a new machine today with high sierra I will test it further.Īs a note, if you try to execute it via terminal:ĭyld: Symbol not found: _OBJC_CLASS_$_NSStatusBarWindow I could share that file see if it takes us anywhere. I had somewhat of a progress and then i got busy with work. I did a bit of research and it appears the only way to do it is to mess with DYLD library injection. I have virtual machine with a version for mojave that i fixed most of the frameworks but it' still not there yet. Mojave 10.14, doesn't open after osascript execution. What's New in Version (built 607) See changelog ** in mySIMBL: System Info/ SIMBL application blacklist (because Afloat is NOT fully compatible with Apple Scripts (parts of Disk Utility 13 (60x)) * Disk Utility 13 (607).app/Contents/MacOS/loader.sh: If you have the SIMBL plug-in AFLOAT installed and have not included AppleScript Utility in mySIMBL's blacklist**, you MUST blacklist Disk Utility 13 (607) (see screenshot "AFLOAT users mySIMBL application blacklist")! In case of issues with the default (original/ stock/ vanilla) Disk Utility: run killall diskmanagementd, also supplied in this package. NOT WORKING (at least not in High Sierra): functions which would invoke a Finder style window, like clicks onto "New Image", "Convert", "Resize Image", "Image", "File/ New/." etc. You can use it side-by-side with the default Disk Utility. Therefore I bumped CFBundleVersion to 607 and BuildVersion to 19 to differentiate it from dimosgmx's 606/ 18 which was only compatible up to 10.13.3. It thus works in 10.12 - 10.13.6 (not yet tested in Mojave because I don't have it installed). This built (607) is dimosgmx's built 606 ever-so-slightly edited* by me (BugsB) for usage in High Sierra beyond 10.13.3. Please read his statements over there FIRST !!
#Best mac disk utility 2019 mod#
This is my mod of dimosgmx's Yosemite (10.10) Disk Utility app with the El Capitan (10.11) diskmanagementd:
!!! ATTENTION: this does NOT AT ALL work in Mojave and above !!!Īnd I don't have the knowledge to fix this - sorry, but form my side, end of the road
0 kommentar(er)
