I had replied to a thread about this issue back in August of this year, and it was explained to me that it was likely an issue with OCLP and not with Sheepshaver itself, since it works with standard installations of Ventura. However, after posting about it on the OCLP discord and essentially being t...

Ah, then it's a known issue it sounds like. That's unfortunate. Well, I'm glad I mentioned it then, rather than going on a wild goose chase.

Boy, I am just not having any luck launching SheepShaver in Ventura. I have: deleted prefs and nvram, tried several different ROM files (named correctly, sans file extensions), tried removing the keycodes file, tried re-downloading, tried multiple different builds, tried removing the startup drive i...

New build seems to work great on El Capitan!

I don't suppose there's any chance of being able to mount physical CD ROMs again though?

Well, that took care of it. So bizarre! Thank you very much for looking into it.

I don't suppose you know how this could have happened in the first place?

disk SheepShaverGames1.dsk disk SheepShaverSystem9.dsk disk SheepShaverSystem7.dsk cdrom /dev/disk1 extfs /Games/Emulation/Macintosh/SheepShaver/SheepShaver Shared Folder screen win/1024/768 windowmodes 0 screenmodes 0 seriala /dev/cu.Bluetooth-Modem serialb /dev/null rom Mac OS ROM bootdrive 0 boot...

I am using Mac OS 10.6.8 with Sheepshaver 2009-10-25 (running OS 9.0.4), but the sheepshaver version seems to not matter. It also does it with Sheepshaver 2014-02-01. (I reverted to 2009 since 2014 was a bit crashy for me.) Here are some screenshots of the behavior. It affects the drive named "...

When Sheepshaver does this, any actual CD which I have inserted after launching Sheepshaver will not mount in emulation, so it must be inserted prior to launching Sheepshaver. When this is done, the firewire drive is no longer mounted in emulation, and instead the inserted CD is mounted properly. An...