Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
I am one of the followers of the Dosdude religion. As such, I have all the family members running "unsupported Macs", in particular I have a 2011 with Catalina patcher and a 2012 running supported (for few more months) Catalina. Said that, is Dosdude still keeping with the Monterey Patcher plan? We all are waiting for the Dosdude WORD. Thank you Dosdude, you are the best!
Dear @Giovamille959, I love @dosdude1 too, but his post you refer to is from a long time ago.
So, I doubt @dosdude1 will continue to develop a patcher for Monterey, not least because macOS Ventura has now been released. And since then, OCLP has been vastly improved.
 
Dear @Giovamille959, I love @dosdude1 too, but his post you refer to is from a long time ago.
So, I doubt @dosdude1 will continue to develop a patcher for Monterey, not least because macOS Ventura has now been released. And since then, OCLP has been vastly improved.
Dear @OKonnel, thank you! My heart is bleeding! If @dosdude1 does not develop the new patcher ... as soon as Catalina becomes unsupported (I believe at the end of this year) I will proceed with the OCLP!
 
  • Love
Reactions: OKonnel
Thank you! From the OCLP 0.4.11 Change Log

  • Remove duplicate OS builds in macOS downloader
    • Avoids Apple's odd bug of publishing 2 different 12.5.1 products
  • Implement deeper macOS installer parsing
    • Provides better version detection than Apple provides in .app
The first item definitely addresses the duplicate OS issue- nice. I wonder if that second item addresses the "anomalous" OS build issue that I observed? i.e. installing a different OS version and build than the one selected for download. I'm still trying to figure out where OCLP came up with Monterey 12.5 (21G82).

View attachment 2053089
This picture says it found the installer in your Applications folder, meaning it’s already an installer you had on your machine. Try deleting that from the apps folder and see if it will let you download the newer 12.5.1 installer.
 
  • Like
Reactions: OKonnel
Weird issue with OCLP post-install root patches. Applying them causes TotalFinder to throw the "Apple Events cannot be delivered" error message.

Post-root patch:
Screen Shot 2022-09-09 at 5.52.55 AM.png
What in these 3 patches would cause that?

Pre-root patch:
Screen Shot 2022-09-08 at 6.40.04 AM.png

Any thoughts or help would be appreciated. Thank You.
 
Weird issue with OCLP post-install root patches. Applying them causes TotalFinder to throw the "Apple Events cannot be delivered" error message.

Post-root patch:
View attachment 2056349
What in these 3 patches would cause that?

Pre-root patch:
View attachment 2056350

Any thoughts or help would be appreciated. Thank You.
Did you make sure to disable SIP? SIP needs to be disabled fully for using totalfinder iirc
 
Did you make sure to disable SIP? SIP needs to be disabled fully for using totalfinder iirc
SIP settings aren't an issue as I am still booted into macOS with OCLP SIP settings. In any case, per the BinaryAge dev,
TotalFinder requires that you have at least CSR_ALLOW_TASK_FOR_PID and CSR_ALLOW_UNRESTRICTED_FS disabled, in addition to whatever else may already have been disabled for you.
OCLP by default has Unrestricted_FS and Unauthenticated_ROOT on my machine, I'm simply adding Task_for_PID

Regardless, I have already tried fully disabling SIP in both the GUI and TUI versions of OCLP. Reset NVRAM, rebooted etc etc. The only way to have TF show up is to revert the post-install root patches. Again for my machine.
 
Weird issue with OCLP post-install root patches. Applying them causes TotalFinder to throw the "Apple Events cannot be delivered" error message.

Post-root patch:
View attachment 2056349
What in these 3 patches would cause that?

Pre-root patch:
View attachment 2056350

Any thoughts or help would be appreciated. Thank You.
But do you really need "Total Finder" to prefer it to a new and well protected OS, ie macOS Monterey that works well thanks to OCLP, even if your Mac is not supported?… ;)
And then there is someone in the Forum who has doubts about the security of OCLP... :cool:
 
But do you really need "Total Finder" to prefer it to a new and well protected OS, ie macOS Monterey that works well thanks to OCLP, even if your Mac is not supported?… ;)
And then there is someone in the Forum who has doubts about the security of OCLP... :cool:
In my case, in a Mac Mini M1, yes. I have sip disabled, and minimum security, so I can run Total Finder. Also sip disabled in my Mac Pro 5,1 Monterey OCLP.
 
  • Like
Reactions: OKonnel
But do you really need "Total Finder" to prefer it to a new and well protected OS, ie macOS Monterey that works well thanks to OCLP, even if your Mac is not supported?… ;)
And then there is someone in the Forum who has doubts about the security of OCLP... :cool:
I have gone this far on a unsupported mac, and at this point it's not really about the NEED. It's more of the why isn't it working, with what appear to be basic patches?
 
  • Like
Reactions: OKonnel and rehkram
I have gone this far on a unsupported mac, and at this point it's not really about the NEED. It's more of the why isn't it working, with what appear to be basic patches?
I have "Total Finder" with regular license and so far I have not installed it to avoid overloading the System.

As for SIP, I was convinced that just to use a "curated" "Total Finder" it was necessary to disable SIP and I suspected you tried using a "curated" copy. Unfortunately, however, I have just visited the official site and I discovered, reading the Instructions, that even the original and "untreated" "Total Finder" requires the deactivation of the SIP.

At this point I regret having purchased the License and it remains a mystery to me how it is possible to sell and use software that alter an important function of System and that perhaps jeopardize security, in exchange for actions that can be done in another way...
 
I have macOS Monterey 5.1 installed on my cMP 5,1 (using OCLP 4.11 nightly) - specs below.

Although OCLP ensures I can through System Preference switch on Voice Control>speech recognition to activate dictation without triggering an AVX kernel panic it has introduced a considerable delay after speaking before text appears. The delay is for 2 minutes: 32 seconds; this renders dictation not practical.

I had reported a similar delay with macOS 12.4 (due to the performance loss from the VMM flag when VMM flag is switched on) and its fix (on another thread https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/post-31124806 ). When it was switched off the delay disappeared.

My question is, is there something I need to switch off in my config.plist generated with this OCLP installation to allow dictation without the delay? Or anything else I need to do to remove the delay

Thanks

Edited
 
Last edited:
Mac Pro 5, 1 mid-2012. After success with OCLP 4.10 on my startup drive (NVMe PCIe) I tried to clone it to my internal SATA SSD, using SuperDuper. The second drive didn't like that at all, so just repeated the usual OCLP routine with the SATA drive et voila: a bootable working backup drive. Dunno why cloning seems not to work with a patched drive copying to a fresh unspoiled SSD — settings, perhaps? Next task is to install a new NVMe drive and give it the OCLP treatment. Will use Migration Assistant or just drag my files across to the new drive. I'll take notes and post the results.
 
Mac Pro 5, 1 mid-2012. After success with OCLP 4.10 on my startup drive (NVMe PCIe) I tried to clone it to my internal SATA SSD, using SuperDuper. The second drive didn't like that at all, so just repeated the usual OCLP routine with the SATA drive et voila: a bootable working backup drive. Dunno why cloning seems not to work with a patched drive copying to a fresh unspoiled SSD — settings, perhaps? Next task is to install a new NVMe drive and give it the OCLP treatment. Will use Migration Assistant or just drag my files across to the new drive. I'll take notes and post the results.
Not settings, it is deeper in AFPS and the way the macOS system volume uses it (sealed), as far as I understand. It‘s the same with CCC which I use instead of SuperDuper.
CCC doc says the APFS replication utility ("ASR") won‘t copy the system volume alone and leave the data volume intact. CCC thus chose to make data-only clones normally, and erase left-over systems. SuperDuper may do the same.
So your procedure of installing with OCLP after cloning was quite right…
In CCC there is an option to clone both system and data, which makes sense if cloning to an empty drive.
 
Last edited:
I have "Total Finder" with regular license and so far I have not installed it to avoid overloading the System.

As for SIP, I was convinced that just to use a "curated" "Total Finder" it was necessary to disable SIP and I suspected you tried using a "curated" copy. Unfortunately, however, I have just visited the official site and I discovered, reading the Instructions, that even the original and "untreated" "Total Finder" requires the deactivation of the SIP.

At this point I regret having purchased the License and it remains a mystery to me how it is possible to sell and use software that alter an important function of System and that perhaps jeopardize security, in exchange for actions that can be done in another way...
I never had or needed to run too many things, but TF has never overloaded my system, it's a pretty small footprint.

Posted earlier about the active dev stating about only having partially disabled SIP. She's (@akemin_dayo) working on a updated version that addresses some issues. You can follow along on the forum HERE (hopefully that hotlink is ok?)

It is unfortunate that many people have bought it before they discontinued service. It does happen as developers can't predict how system updates can effect their product. Fortunately for me, I had many years of service of TF before this. It is considered freeware now, the OG developer @darwin has posted the license name / key HERE.

I've stopped worrying about security on my machine years ago, yah crap can happen, I'm just cautious. But the devs have always tried to bring TF in a way to try and maximize security as much as possible. Just like OpenCore. It's a balance of security and function. Sometimes it pans out, sometimes it doesn't.
 
  • Love
  • Like
Reactions: OKonnel and 0134168
I never had or needed to run too many things, but TF has never overloaded my system, it's a pretty small footprint.

Posted earlier about the active dev stating about only having partially disabled SIP. She's (@akemin_dayo) working on a updated version that addresses some issues. You can follow along on the forum HERE (hopefully that hotlink is ok?)

It is unfortunate that many people have bought it before they discontinued service. It does happen as developers can't predict how system updates can effect their product. Fortunately for me, I had many years of service of TF before this. It is considered freeware now, the OG developer @darwin has posted the license name / key HERE.

I've stopped worrying about security on my machine years ago, yah crap can happen, I'm just cautious. But the devs have always tried to bring TF in a way to try and maximize security as much as possible. Just like OpenCore. It's a balance of security and function. Sometimes it pans out, sometimes it doesn't.
Same here.
 
I never had or needed to run too many things, but TF has never overloaded my system, it's a pretty small footprint.
Posted earlier about the active dev stating about only having partially disabled SIP. She's (@akemin_dayo) working on a updated version that addresses some issues. You can follow along on the forum HERE (hopefully that hotlink is ok?)
It is unfortunate that many people have bought it before they discontinued service. It does happen as developers can't predict how system updates can effect their product. Fortunately for me, I had many years of service of TF before this. It is considered freeware now, the OG developer @darwin has posted the license name / key HERE.
I've stopped worrying about security on my machine years ago, yah crap can happen, I'm just cautious. But the devs have always tried to bring TF in a way to try and maximize security as much as possible. Just like OpenCore. It's a balance of security and function. Sometimes it pans out, sometimes it doesn't.
Thank you @ChrisOSX ! You have been an Angel!
I am really grateful to you for the cordial, exquisite response, full of useful information and links, etc. And I repeat that you are an Angel :)
And thanks also to @******* who confirmed
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.