![]() ![]() You can see that it shows SIP as disabled, along with saying apple events seems to be permitted. TF has been the exception since I left Catalina. My MBP 6,2 seemed to have less issues then others in the unsupported world. It’s possible that OpenCore may behave differently in some minor way that is causing it to not quite work correctly on your system. You can safely forget about Xcode 14 and let it collect dust afterwards, if you would like. To fix this, just run Xcode 14 at least once, so you get the new, out-of-band amework (with macOS 13 support) installed on your system. ![]() Tl dr: Apple kind of… made an oversight on how amework works and its relation to amework. On the off chance that someone reading this thread is trying to virtualise macOS 13 on a macOS 12 host and is running into an error while trying to perform first-time restore-install (with error AMRestorePerformRestoreModeRestoreWithError = 10), please refer to my tweet thread for how to fix this. Or if you’re lazy / don’t want to think about it, you can just fully disable SIP using csrutil disable. You’ll have to add -without nvram to your csrutil invocation to disable NVRAM protections. ※ Note: If you’re getting an error while trying to set your boot-args, you’re probably running a partially-enabled SIP configuration. (And if you’re running macOS 13 in a VM like I am… well. If this somehow makes TotalFinder work on your bare-metal macOS 13 installation, I… will have to look further into what is happening. ![]() So, this is a very “might as well try it in case this somehow makes it work, I guess” suggestion, but perhaps try running sudo nvram boot-args="-arm64e_preview_abi" in a macOS 13 Terminal session, and rebooting. There is something of note that I noticed though, but from my understanding, it should only affect virtualised copies of macOS (on Apple Silicon), not when you’re running it on bare metal.īasically, in order for TotalFinder to successfully inject into a virtualised copy of macOS 13, I had to add the -arm64e_preview_abi boot-arg, otherwise the injector would always return error -1708 ( errAEEventNotHandled), which causes (or is one possible cause) of the infamous “Apple Events cannot be delivered.” message. That being said… I’m quite surprised that both of you have reported injection issues on macOS 13, as from my testing, the current public release actually does work mostly fine on macOS 13 (aside from the aforementioned Coloured Labels crash). When I updated my mac to macOS I’ve gotten TotalFinder to work on macOS 13, but there are a few issues with the current public release, including the fact that enabling the Coloured Labels feature will cause Finder to crash (due to Apple refactoring some portion of Finder, as they often do). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |