Basilisk GUI Keeps Changing Basilisk.app Location

[akator]

I have my emulators and emulator data all on an external drive. This is non-negotiable because my the internal SSD on my 2018 Intel Mini it too small.

Prior to updating to Sonoma today, I had no issues with Basilisk II, Basilisk GUI, or other emulators.

I have updated all of my emulators to the latest versions as of today, January 14 2024.

I read about the JIT error and deactivated that so Basilisk II works.

What doesn't work anymore is launching Basilisk II using Basilisk GUI. Every time Basilisk GUI launches, it changes the path to the BasiliskII.app to:

Code: Select all

/private/var/folders/kg/_5jch5y94_j7btbfv20hwgrh0000gn/T/AppTranslocation/34913139-FD00-45AF-8D93-477BD056DA7E/d//BasiliskII.app

That is not the location of Basilisk II. The only way to get Basilisk II GUI to work is to change the setting to "BasiliskII in other folder" (even though it's in the same folder) and dragging the Basilisk application to path bar. Basilisk II then starts, but this settings change doesn't persist so the process has to be repeated all over again on next use.

[Ronald P. Regensburg]

This is a security feature in recent macOS versions. The application is seen as not installed intentionally by the user in its present location and is quarantined. This can happen when applications are downloaded (and/or the containing archive is expanded) in the location where the application is to be used. It may have happend while updating BasiliskII.

Try:
Copy both BasiliskII and GUI applications (only the applications themselves) to a different location. Then delete the original applications (trash and empty trash) and move the copies back to where you use the applications.

BTW: It is not necessary to start BasiliskII from the GUI. Once BasiliskII is set up with the GUI, the emulator can be launched by itself. The GUI is then only needed when you want to change settings.

[akator]

I thought it might have something to do with macOS' constantly changing security shenanigans, but I never would have figured that out.

Thank you, sir!