E-Maculation

Hi all,
On my macOS Catalina 10.15.3 system, SheepShaver Version 2.5, 8 March 2020 quits immediately after launching.
But the old SheepShaver Version 2.5, 4 May 2019, reinstalled in the same directory, works.
As far as I remember, previous december 2019/january 2020 releases were working on my system.

What I tried:
Deleting ~/.sheepshaver_prefs has no effect.
Deleting ~/.sheepshaver_nvram has no effect.
Trying with other 4MB-old-world ROMs has no effect.

The macOS Console tool lists these errors:
SheepShaver (CoreFoundation) AddInstanceForFactory: No factory registered for id <CFUUID 0x6000034d9b60> F8BB1C28-BAE8-11D6-9C31-00039315CD46
SheepShaver (CoreAudio) HALC_ShellDriverPlugIn::Open: Can't get a pointer to the Open routine
SheepShaver (CoreAudio) HALC_ShellDriverPlugIn::Open: Can't get a pointer to the Open routine
SheepShaver (HiServices) SignalReady: pid=54497 asn=0x0-0x2f02f0
SheepShaver (LaunchServices) SIGNAL: pid=54497 asn=0x0x-0x3080944
distnoted register name: com.apple.nsquiet_safe_quit_give_reason object: com.emaculation.sheepshaver token: f428b pid: 54497
...
runningboardd (RunningBoard) [executable<SheepShaver(501)>:54497] Death sentinel fired!

Strange. The 8 March build runs fine here in Catalina 10.15.3 with both old world and new world rom files.

To check that nothing is wrong with the download, I downloaded the zip archive again myself. No problems running the newly downloaded SheepShaver build.

I also see nothing like this in Console. Where, in which log or report, do you get these messages?

Anyone else?

To get these messages, I run the Console tool, searched for "SheepShaver", then run Sheepshaver. And by the way, i was missing all the messages. There are dozens of lines. Here is what I get at the beginning:
sysextd Unable to find a SystemExtensions directory at /Applications/Emulation/Micros/Apple/Mac/PowerMac/SheepShaver.app/Contents/Library/SystemExtensions

lsd Non-fatal error enumerating at <private>, continuing: Error Domain=NSCocoaErrorDomain Code=260 "Impossible d’ouvrir le fichier « PlugIns » car il n'existe pas." UserInfo={NSURL=PlugIns/ -- file:///Applications/Emulation/Micros/Apple/Mac/PowerMac/SheepShaver.old.app/Contents/, NSFilePath=/Applications/Emulation/Micros/Apple/Mac/PowerMac/SheepShaver.old.app/Contents/PlugIns, NSUnderlyingError=0x7f82c7484230 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}

sysextd Unable to find a SystemExtensions directory at /Applications/Emulation/Micros/Apple/Mac/PowerMac/SheepShaver.new.app/Contents/Library/SystemExtensions

lsd - 45683955: Checking whether application is managed at file:///.file/id=6571367.8656016969//com.emaculation.sheepshaver

dmd Received xpc stream event (distributed notification matching) with name: com.apple.LaunchServices.applicationRegistered user info: {
bundleIDs = (
"com.emaculation.sheepshaver"
);
isForcedUpdate = 1;
isPlaceholder = 0;
}

lsd Non-fatal error enumerating at <private>, continuing: Error Domain=NSCocoaErrorDomain Code=260 "Impossible d’ouvrir le fichier « PlugIns » car il n'existe pas." UserInfo={NSURL=PlugIns/ -- file:///System/Volumes/Data/Applications/Emulation/Micros/Apple/Mac/PowerMac/SheepShaver.app/Contents/, NSFilePath=/System/Volumes/Data/Applications/Emulation/Micros/Apple/Mac/PowerMac/SheepShaver.app/Contents/PlugIns, NSUnderlyingError=0x7fb3e7f196f0 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}

lsd - 45683955: Checking whether application is managed at file:///System/Volumes/Data/Applications/Emulation/Micros/Apple/Mac/PowerMac/SheepShaver.app//com.emaculation.sheepshaver

nehelper Handling an apps installed notification with bundle IDs (
"com.emaculation.sheepshaver"
)

and so on...

The list of messages in Console (after searching for "SheepShaver" in the searching cell) is very, very long. And full of regular noise.
I dumped the list to a text file to better see the real warning messages. So here is what seems interesting:

sysextd Unable to find a SystemExtensions directory at /Applications/Emulation/Micros/Apple/Mac/PowerMac/SheepShaver.app/Contents/Library/SystemExtensions

lsd Non-fatal error enumerating at <private>, continuing: Error Domain=NSCocoaErrorDomain Code=260 "Impossible d’ouvrir le fichier « PlugIns » car il n'existe pas." UserInfo={NSURL=PlugIns/ -- file:///Applications/Emulation/Micros/Apple/Mac/PowerMac/SheepShaver.old.app/Contents/, NSFilePath=/Applications/Emulation/Micros/Apple/Mac/PowerMac/SheepShaver.old.app/Contents/PlugIns, NSUnderlyingError=0x7f82c7484230 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}

lsd Non-fatal error enumerating at <private>, continuing: Error Domain=NSCocoaErrorDomain Code=260 "Impossible d’ouvrir le fichier « PlugIns » car il n'existe pas." UserInfo={NSURL=PlugIns/ -- file:///System/Volumes/Data/Applications/Emulation/Micros/Apple/Mac/PowerMac/SheepShaver.app/Contents/, NSFilePath=/System/Volumes/Data/Applications/Emulation/Micros/Apple/Mac/PowerMac/SheepShaver.app/Contents/PlugIns, NSUnderlyingError=0x7fb3e7f196f0 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}

SheepShaver Registering for test daemon availability notify post.

SheepShaver notify_get_state check indicated test daemon not ready.

SheepShaver AddInstanceForFactory: No factory registered for id <CFUUID 0x600003048880> F8BB1C28-BAE8-11D6-9C31-00039315CD46

SheepShaver HALC_ShellDriverPlugIn::Open: Can't get a pointer to the Open routine

SheepShaver HALC_ShellDriverPlugIn::Open: Can't get a pointer to the Open routine

distnoted register name: com.apple.nsquiet_safe_quit_give_reason object: com.emaculation.sheepshaver token: f4297 pid: 55268

hidd Connection removed: IOHIDEventSystemConnection uuid:D35530B6-0D2C-4EDC-BE35-39D3FB9E63FD pid:55268 process:SheepShaver type:Passive entitlements:0x0 caller:HIToolbox: ___GetIOHIDEventSystemClient_block_invoke + 26 attributes:(null) inactive:1 events:0 mask:0x0

runningboardd [executable<SheepShaver(501)>:55268] Death sentinel fired!

runningboardd [executable<SheepShaver(501)>:55268] Ignoring jetsam update because this process is not memory-managed

runningboardd [executable<SheepShaver(501)>:55268] Ignoring suspend because this process is not lifecycle managed

runningboardd [executable<SheepShaver(501)>:55268] Ignoring GPU update because this process is not GPU managed

runningboardd RBSStateCapture remove item called for untracked item 352-188-2422 (target:executable<SheepShaver(501)>)

runningboardd RBSStateCapture remove item called for untracked item 352-188-2421 (target:executable<SheepShaver(501)>)

Your posts were not yet published because they were waiting for approval. Posts by new users with less than three approved posts are queued for approval by one of the moderators.

I will answer later.

When I launch SheepShaver, none of the messages you mention are shown in Console.

I do not understand most of the Console output. There are a few lines, though, that seem to indicate that something on your Mac is looking for a file PlugIns inside SheepShaver.app that is not available there:
I do not know why anything would look for a file PlugIns (fichier = file). There is certainly not a file PlugIns anywhere in SheepShaver.app and such a file is not supposed to be there. When I search my Mac for files named PlugIns (including hidden files and files inside packages), I find most PlugIns files in System and some in applications that are unrelated to SheepShaver.

Maybe I made a mistake while notarizing the application? It could be that such a mistake will not be apparent on the machine it is built on. I will build a new notarized SheepShaver application.

The 15 March build now available, see links and downloads topic.

It should be identical to the 8 March build, so I do not expect a change. But if this one runs normally on your machine, then something must have been wrong with the 8 March build.

It works!!
I mean, the latest Version 2.5, 15 March 2020 you just published works again on my Mac.
I seriously don't know why, but many thanks for your efforts!
I just put the new executable into my existing directory, double-click on it and, then, my MacOS 9.04 copy started as it did before the 08 March version.
So, many, many thanks to you!! You're fantastic!

For what it's worth, yserra's experience is not unique. With the 8th March version I had exactly the same quit on startup as yserra and after several attempts likewise reverted to the previous version. I also find that the 15 March 2020 version works (thank you!).

I have absolutely no idea what could have been wrong with the 8 March build, but I am glad that whatever was wrong with it appears to be solved in the 15 March build.

Odd thing is, I've been having zero problems with the 8 March build under Catalina. It could be due to GateKeeper already authorizing the location or something.

Hi, I have a problem with 15. march build on High Sierra.
When I doubleclick sheepshaver it immediately closes with only the following in the console: When I go into package contents and start SheepShaver executable, it works with no problem.

Best regards,
Goran

How did you install the downloaded application?
The download is a zipped folder. After expanding the zip archive, you will need to move the included files (SheepShaver.app and keycodes) out of that folder to the intended location. That could be a SheepShaver folder that is part of an existing setup or it can be the separately downloaded SheepShaver folder for a new setup.

Did you do that?

This procedure is needed since macOS 10.12 (Sierra) for applications that are bundled together with other files in a download.

(The fact that the 15 March build comes bundled with the keycodes file inside a "SheepShaver" folder may be confusing.)

I put new version of Sheepshaver into existing folder, replacing the previous version. That version (2.5, 12 January) is working ok in the same folder. And new version is working in the same folder if I launch /SheepShaver/SheepShaver.app/Contents/MacOS/SheepShaver executable.

Best regards,
Goran

Strange. I have no idea what could make it impossible for you to launch the latest SheepShaver build normally. Anyone else see this issue?

Edit: Maybe you could try this: Create a copy of SheepShaver.app elsewhere (like on your desktop), trash the original app, then drag the copy in place of the original.

Ronald P. Regensburg wrote: Edit: Maybe you could try this: Create a copy of SheepShaver.app elsewhere (like on your desktop), trash the original app, then drag the copy in place of the original.

Incredibly, this worked! Thanks. What's the reasoning for this to work?

Best regards,
Goran

It is a security feature in macOS, introduced in Sierra. The user needs to consciously install the application, actually move or copy a downloaded application from a downloaded folder or .dmg image to a different location. Moving the app may not have worked correctly on your side. When you made a copy of the app, the system considered it again a new app that will work after it has been moved to the desired location.