SheepShaver closes immediatly

[Jordan882]

i just got SheepShaver on mac OS Sierra. I put in the ROM file but when I open SheepShaver it closes. Below is an image of the files I have in my SheepShaver folder.

[Ronald P. Regensburg]

1. The ROM file must be in the same folder as SheepShaver and must have the exact name "Mac OS ROM".

2. The SheepShaver application must be set to run in 32-bit mode (see Finder Info for the app.)

3. There is an issue with Sierra (in fact an additional new security feature in Sierra) that prevents a newly installed SheepShaver to run. The workaround is described by Cat_7 in another thread:

The procedure to get it running is simply to copy the program to the desktop, remove the old program in the SheepShaver folder and move the new copy from the desktop to the SheepShaver folder.

[aharmon]

Thanks for the info - Ronald I had sent you a a message on this same thing earlier. If you could add this tid-bit to the main SheepShaver Mac OSX thread that might help some other folks. Regardless - thanks for the info, I got it up and running

[Ronald P. Regensburg]

Edited "Compatibility notes" in the main thread.

[Noam.bechhofer]

I've been using SheepShaver for about a week on macOS Sierra. Everything was fine. Then, while playing Age of Empires 2 (the reason I installed SheepShaver in the first place) in fullscreen, the screen suddenly went dark. Command-Q didn't work, and Control-Esc didn't either. Command-Tab also wasn't helping. I was stuck. So I rebooted my computer, and now, well, "SheepShaver closes immediately". Nothing has changed in the preferences, and the SheepShaver folder still has everything that should be there.
Here's my Console log when I try to start SheepShaver:
default 13:38:15.611041 -0500 opendirectoryd Client: <private>, UID: 0, EUID: 0, GID: 0, EGID: 0
default 13:38:15.611413 -0500 opendirectoryd Client: <private>, UID: 0, EUID: 0, GID: 20, EGID: 20
default 13:38:15.611986 -0500 opendirectoryd Client: <private>, UID: 501, EUID: 501, GID: 20, EGID: 20
default 13:38:15.619346 -0500 taskgated MacOS error: -67062
default 13:38:15.621855 -0500 mds directQueryFetchResultsReply 86017 1795162112 35
default 13:38:15.622041 -0500 mds directQueryFetchResultsReply 86019 1795162112 35
default 13:38:15.649817 -0500 opendirectoryd Client: <private>, UID: 501, EUID: 501, GID: 20, EGID: 20
default 13:38:15.659543 -0500 launchservicesd UNIX error exception: 22
default 13:38:15.660689 -0500 launchservicesd MacOS error: -67062
default 13:38:15.663385 -0500 SheepShaver subsystem: com.apple.SkyLight, category: default, enable_level: 0, persist_level: 0, default_ttl: 7, info_ttl: 0, debug_ttl: 0, generate_symptoms: 0, enable_oversize: 0, privacy_setting: 0, enable_private_data: 0
default 13:38:15.693791 -0500 SheepShaver SLPSGetCurrentProcess(): This call is deprecated and should not be called anymore.
default 13:38:15.693874 -0500 SheepShaver set_foreground_operation_state(): This call is deprecated and should not be called anymore.
default 13:38:15.722083 -0500 gamed GKClientProxy: clientForBundleID:
default 13:38:15.722704 -0500 gamed GKClientProxy: clientForBundleID:
default 13:38:15.722790 -0500 gamed GKClientProxy: updateIfRecentlyInstalled
default 13:38:15.806125 -0500 gamed GKClientProxy: clientForBundleID:
default 13:38:15.806205 -0500 gamed GKClientProxy: updateIfRecentlyInstalled
default 13:38:15.811071 -0500 opendirectoryd Client: <private>, UID: 501, EUID: 501, GID: 20, EGID: 20
default 13:38:15.817866 -0500 SheepShaver WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.3 instead of 10.12.3. This is not a bug in Gestalt -- it is a documented limitation. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
Call location:
default 13:38:15.817986 -0500 SheepShaver 0 CarbonCore 0x955f1256 ___Gestalt_SystemVersion_block_invoke + 101
default 13:38:15.818021 -0500 SheepShaver 1 libdispatch.dylib 0x9f7559cc _dispatch_client_callout + 50
default 13:38:15.818068 -0500 SheepShaver 2 libdispatch.dylib 0x9f75595c dispatch_once_f + 41
default 13:38:15.818113 -0500 SheepShaver 3 libdispatch.dylib 0x9f7565a6 dispatch_once + 24
default 13:38:15.818159 -0500 SheepShaver 4 CarbonCore 0x95576ef0 _Gestalt_SystemVersion + 982
default 13:38:15.818206 -0500 SheepShaver 5 CarbonCore 0x955766e7 Gestalt + 148
default 13:38:15.818249 -0500 SheepShaver 6 SDL 0x000299ed SDL_SoftStretch + 14394
default 13:38:15.838198 -0500 gamed GKClientProxy: clientForBundleID:
default 13:38:15.839562 -0500 gamed GKClientProxy: updateIfRecentlyInstalled
default 13:38:15.884218 -0500 opendirectoryd Client: <private>, UID: 0, EUID: 0, GID: 0, EGID: 0

And that's it. 9 seconds later, it moved on to a random AppleIDAuthAgent process.

[Ronald P. Regensburg]

Most keystrokes will be intercepted by SheepShaver and combos like command-Q will not work to quit SheepShaver. With SheepShaver full-screen, nothing that would bring up a modal dialog will work either with SheepShaver permanently in front. The only key strokes that might have worked are control-escape (force quit SheepShaver) and control-return (toggle between full-screen mode and window mode).

I do not know what the problem is now. I get the same lines in Console during a successful launch of SheepShaver. Do you have a backup of the HD image file from before the incident? Put (copy) that backup file back in place, delete the nvram file using the "Zap PRAM" script that came with the SheepShaver download, and make sure that in SheepShaver preferences window mode is set. The setup guide has instructions for changing that setting without the use of SheepShaver itself.

[Noam.bechhofer]

I do not have a backup. I didn't have anything important on there, so I will start over, but I would like to prevent this problem from affecting me in the future if at all possible.

[adespoton]

Best solution is to make a backup of the disk image once you've got everything set up again.

One thing I remember well from the Mac OS days is doing something that corrupted the filesystem and discovering that rebuilding the desktop and running disk first aid wasn't enough to fix the problem. Restoring the system folder from backup however, that always worked.

[Noam.bechhofer]

Okay, thanks for the advice!

[JosephMacintoshBat]

ronald we have never met as a bat like i am before but i am struggling to open sheepshaver or mac emulation and stays open but the problem is it closes automatically what the hell? but i did upgrade my mac mini though. it said it's for arm cpu but i don't think intel is making a comback though.

[JosephMacintoshBat]

i just got SheepShaver on mac OS Sierra. I put in the ROM file but when I open SheepShaver it closes. Below is an image of the files I have in my SheepShaver folder.

yeah but this time i got the same problem while trying to upgrade the stable mac os 15 on my intel mac mini. but there is arm cpu apple silicon out there.

[Ronald P. Regensburg]

Please describe more precisely your issue.

Did you have a working SheepShaver setup and did it stop working correctly after the macOS update or upgrade? Or are you trying to do a new SheepShaver setup?
Upgrade or update from which macOS version to which macOS version?
What "said it's for arm cpu" and where?
Which model is your Intel Mac Mini?
Which SheepShaver build (build date!) do you use?
Does SheepShaver quit on launch before it shows a window or does it actually start up and does it close later. At which point?

[JosephMacintoshBat]

Please describe more precisely your issue.

Did you have a working SheepShaver setup and did it stop working correctly after the macOS update or upgrade? Or are you trying to do a new SheepShaver setup?
Upgrade or update from which macOS version to which macOS version?
What "said it's for arm cpu" and where?
Which model is your Intel Mac Mini?
Which SheepShaver build (build date!) do you use?
Does SheepShaver quit on launch before it shows a window or does it actually start up and does it close later. At which point?

yes it closes window which it is the same problem i just wanted to run thinkin' things on there. but it doesn't work for me.

[Ronald P. Regensburg]

Without a clear description of the problem, of the circumstances under which you try to run SheepShaver and af the actions that lead to the problem, there is no way I, or anyone here, can figure out what your problem is. Sorry.