Ronald P. Regensburg wrote:
And from Mavericks onward seem to break if ran in 64-bit;
SheepShaver runs fine in 64-bit mode in Mavericks, but not in Yosemite.
Just a thought about the problem with Medusa:
In a discussion elsewhere about unrelated software, it appeared that Apple changed the alias format in Yosemite and as a result that software could not resolve aliases anymore. Could that issue be related to the problem with Medusa in your setup?
When one drags and drops a new item into Medusa, it first checks for the file type, then proceeds with file parsing operations and saves an alias into the core-data. The alias is done with a library called "Aliases.h" and is pretty much pure C. The output is pretty much binary data.
Indeed one of the methods used is deprecated (FSNewAlias). [Update: Actually, the whole library is being dropped! Damn Apple, giving me headaches.]
The fact that the error says the file is invalid doesn't mean the rom file is invalid, but maybe it could not parse it because the alias could not be resolved. I'll make a better output to avoid confusion.
So, I'll try updating this code and let's see how it goes from there. It will take some time, so please be patient.
Oh yes, Basilisk II's and SheepShaver's ability to run in Yosemite is not connected to Medusa. Medusa is a Cocoa application, it simply calls the emulators' binary file and watches the process until it is terminated. It should work just fine in both 32 and 64 bit.
If you reeeally want to try it before I fix, old versions of Medusa don't use aliases. I don't recall which is the last version, but should be 1.1b or something similar. Any downgrades require the user to delete the system files, I suggest using AppZapper.