Jump to content


  • Content Count

  • Joined

  • Last visited

About BuXb

  • Rank

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Kauai, Hawai'i

Recent Profile Visitors

16,184 profile views
  1. @boris1 modify it to go to hibernate or sleep if it’s idle for a long time: hmm, I'm really neither a bash nor an Applescript Pro, much rather an apprentice in maybe his 2nd year, so I can't answer if or how this is possible in either of the two script languages. You would need to websearch that. I do know however that that is possible with Bernhard Baehr's sleepwatcher command-line binary which you can download on his minimalist homepage. The downside is that it's badly documented, and you'd probably encounter a rather steep learning curve. or the battery is at a higher level, for example 50%?: SleepOnLowBatterySound.scpt: edit if Pct ≤ 10 and Pct > 8 then into if Pct ≤ 50 and Pct > 8 then save
  2. @ all : is this 100% working for you? I still have the darn notifications regularly after wake from sleep!! Looks as if sleepwatcher + a launcher is required ..
  3. This is a one-(double) click implementation of Rob Griffiths' "Remove the macOS Catalina guilt trip from macOS Mojave" over at his awesome macOS repertoire "The Robservatory". Just hit Install, input your password, hit ENTER/ RETURN, and that should be it. I added 'RunAtLoad' to the property list so it runs immediately during install, and on account log-in. The launch agent runs on a per user basis. If you still get a Upgrade to Catalina notification with Rob's "every day at 6am, noon, and 6pm" settings: I also supplied 4, 5 and 6 hrs scripts in the InstallerData folder. Simply copy the desired launch agent one level higher and run 'Install' again. A uninstaller is included, too. How does it run for you? Let's keep dwelling in Hayikwiir Mat'aar BuX v.1.0 2019-11-30 No More Upgrade to Catalina Notification v.1.0 2019-11-30.zip
  4. BuXb

    AppleALC — dynamic AppleHDA patching

    I've looked at the AppleALC documentation and can find no mention of this feature and can't find any examples of it on-line. How exactly please does that line in info.plist look like?
  5. MAJOR update: 2019-11-15 v. 1.1 • BUG FIX: changed all occurrences of ExternalChargeCapable to ExternalConnected in all Apple Script .scpt files (SleepOnLowBattery.scpt, SleepOnLowBatterySound.scpt, demo.scpt) to restore functionality • IMPROVEMENT: made queries of MaxCapacity and CurrentCapacity more compatible to work with hopefully any system • NEW: added Catalina compatibility to install scripts; verified Mojave compatibility • NEW: Sound script uses voice Allison if installed, otherwise automatically defaults back to another English standard voice (Daniel, Alex or Fred) SleepOnLowBattery (SOLB) by BugsB v.1.1 (2019-11-15).zip @Allan @onemanOSX @TombaFI
  6. oh, something changed: in all Apple Script .scpt files (SleepOnLowBattery.scpt, SleepOnLowBatterySound.scpt, demo.scpt), ExternalChargeCapable needs to be changed to ExternalConnected That makes more sense anyway. I took that over from the original script. Maybe in OS X back then there wasn't even a parameter or property ExternalConnected I'll post an updated release as soon as possible (too late & tired now already).
  7. BuXb

    VirtualSMC — SMC Emulator

    What's the recommended method for getting the CPU frequency with VirtualSMC installed? Still Intel Power Gadget, or is there any alternative (rather than FakeSMC + plugin kexts + HWMonitor)?
  8. Would someone please upload or attach v.5.0 for Mac OS - it is nowhere to be found anymore, not even on the App store. Thank you. @Andy Vandijck ?
  9. @cvad : have you tested your Kext Utility in Mojave?
  10. BuXb

    miniPCI Wireless - any stable ones?

    sorry Nancy, no idea.
  11. getting closer, partial success: What I did was, copy the DiskManagement.framework from your Disk Utility for Mojave (not there yet).app into Disk Utility 13 (607).app, overwriting the old one (after backing it up). Obviously the volumes in the side bar on the left are now missing. I did some testing back and forth of the folders and files inside DiskManagement.framework: the DiskManagement binary is the "do-jobby" here and thus the ONLY culprit file to fix, at least for High Sierrra. I see both binaries have the exact same byte count, so I compared them with Hex Fiend: there is 66 differences (most just one or a few bytes), which is too much for byte restore debugging. You apparently have more experience with and a better handle on byte patching, so I'm sure you'll succeed. Getting this to work in High Sierra seems like a good basis for Mojave GOOD JOB !!!!!
  12. @Tetonne you are welcome. @dimosgmx that's good news. I also got your message but reply here for best exposure and open collaboration. I have also been debugging via Terminal: File: Debug Disk Utility 13 (607).command (attached) #!/bin/bash clear echo "Put this script next to Disk Utility 13 (607).app" echo "" cd "$(dirname "$0")" sudo ./"Disk Utility 13 (607).app/Contents/MacOS/loader.sh" with the following results (10.13.6): On start: Failed to connect (cancelRecreate) outlet from (DUWindowController) to (NSButton): missing setter or instance variable Failed to connect (repairSheetInfo) outlet from (DUWindowController) to (NSTextField): missing setter or instance variable 10.4-style NSNumberFormatter method called on a 10.0-style formatter, which doesn't work. Break on _NSNumberFormatter_Log_New_Methods_On_Old_Formatters to debug. This message will only be logged once. Click onto: 1. New Image; File/ New Blank Disk Image (same error): *** Assertion failure in void *FinderKitLibrary()(), /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppKit/AppKit-1561.60.100/Nav.subproj/NSSavePanel.m:810 2. Convert; Verify; File/ New Disk Image from Folder; Open Disk Image (same error): *** Assertion failure in void *FinderKitLibrary()(), /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppKit/AppKit-1561.60.100/Nav.subproj/NSNavFinderViewFileBrowser.m:48 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 AppKit.framework It might be necessary to kill any running default OS process of the same name DU 13 needs to access. It might also be helpful to run DU13 via terminal debug in Sierra 10.12.6 (I don't have it installed) to see how the messages should look like. But maybe that would be an extra step. Does anyone know if this got broken from 10.12.6 to 10.13.0, or if it was still running in the initial High Sierra and got broken with a 10.13.x update (as did the diskmanagementd command requiring a killall after the 10.13.4 update)? It would be much easier to debug within a High Sierra update line, just looking at the files of the culprit update. Good luck! Let me know if I can test anything. I might be a bit unresponsive the next three days, but then things should lighten up a bit. Debug Disk Utility 13 (607).command
  13. BuXb

    Disk Utility (patched_v2)

    Here you go: Disk Utility v.13 built 607 with Debug Options for macOS Sierra & High Sierra up to 10.13.6 Not tested yet in Mojave.
  14. @MaLd0n a from YOU weighs 1k fold - obrigado amigo Do you (or @dimosgmx etc.?) happen to have any idea which files(s) from Sierra might be needed to revive the file window functions? If we manage to figure that one/ these out, we'll again have a full-fledged DU for High Sierra (and hopefully beyond). Also: can you test my built on Mojave?
  15. BuXb

    Disk Utility v13 for macOS Sierra.zip

    Here you go: Disk Utility v.13 built 607 with Debug Options for macOS Sierra & High Sierra up to 10.13.6 Not tested yet in Mojave. I recommend everyone to update their v.13 (606) because this mod of mine also fixes the original Disk Utility Error: framework unable to communicate with disk management daemon tested with Disk Utility v.17.