Login  •  Register


The time is now: Sat Jul 11, 2020 3:39 pm

Emaculation wiki  •  Delete all board cookies



Post new topic  Reply to topic Page 1 of 1 [ 14 posts ]
Print view Previous topic  |  Next topic
Author Message
PostPosted: Sun Jun 14, 2020 3:30 am 
Offline
Space Cadet

Joined: Sat Dec 13, 2014 1:45 am
Posts: 7
System Version 10.13.6, Security Update 2020-003.

I was using SheepShaver earlier today without issue, but then decided to install the latest security update. After the install, all I get when I boot SheepShaver is a black screen. I've tried all kinds of things to get it going again, but no luck. Console doesn't provide much feedback - just these 3 lines at first before messages about the app burning CPU.

launchservicesd CHECKIN:0x0-0x9f09f 987 com.emaculation.sheepshaver
SheepShaver AEGetDescData of non-desc type 'reco' not a good idea
SheepShaver LSExceptions shared instance invalidated for timeout.

I couldn't see anyone else mentioning the issue.

Among things I've tried is using both of the scripts to first zap PRAM and then to delete the preferences. I had been using the May 2019 build, so downloaded and tried the latest from March 2020. I also downloaded the SheepShaver folder as well as a new ROM file and tried to run the app from that folder without the virtual hard disk. Nothing made a difference. I'm going to download the security update and try running it again to see if that's makes a difference.

Any thoughts would be appreciated. Thanks


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Sun Jun 14, 2020 7:39 am 
Offline
Expert User
User avatar

Joined: Thu Feb 09, 2006 10:24 pm
Posts: 6017
Location: Amsterdam, Netherlands
If you had SheepShaver set to launch in full-screen mode, you could have been bitten by this issue: viewtopic.php?f=20&t=10392
But that should have been solved after deleting both nvram and prefs files as SheepShaver will launch in window mode by default.

Do I understand correctly that you deleted the nvram file first, then tried again, and then deleted the prefs file?

Try to delete both nvram and prefs file first and make sure the ROM file is in the SheepShaver folder with SheepShaver itself and is (re)named "Mac OS ROM".


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Sun Jun 14, 2020 9:08 pm 
Offline
Space Cadet

Joined: Sat Dec 13, 2014 1:45 am
Posts: 7
Tried the zap/delete combo, but no luck. ROM file is the same one I've been using for years, but I did double check the name. And, I've never used full screen mode.

I downloaded the security patch, but it doesn't seem like I'll be able to try running it again. Unfortunately I've got an old Mac Pro 3,1 running a patched version of High Sierra, so it's not the most cooperative when running software updates. I could try and roll it back, but I don't really want to mess with that.

Hopefully though, this is just a problem for me and won't pop up for anyone else. I do have an old PowerPC laptop that will run what I need in Classic. Not as convenient, but sufficient.

Thanks for the tips.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Mon Jun 15, 2020 10:23 am 
Offline
Expert User
User avatar

Joined: Thu Feb 09, 2006 10:24 pm
Posts: 6017
Location: Amsterdam, Netherlands
SheepShaver is running fine here in Catalina 10.15 5 (with the latest 10.15.5 supplemental update). I cannot imagine how the latest High Sierra security update would prevent SheepShaver to run as the updates for later macOS versions should contain the same security patches. Maybe it is related to your non-standard installation. We will soon know if this is a general issue with the High Sierra security update. You are certainly not the only one running SheepShaver in High Sierra.

In the meantime:
- Does everything else on your machine run as expected?
- If your ROM file is not named "Mac OS ROM" and resides in the same folder with SheepShaver, SheepShaver will not run after deleting the prefs file.
- Where do you have SheepShaver and its related files installed?


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Mon Jun 15, 2020 3:20 pm 
Offline
Forum All-Star
User avatar

Joined: Fri Nov 27, 2009 5:11 am
Posts: 2998
Location: Emaculation.com
Is it possible the Gatekeeper metadata got reset during the update? Possibly running xattr in recursive mode will fix the problem.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Mon Jun 15, 2020 7:03 pm 
Offline
Expert User
User avatar

Joined: Thu Feb 09, 2006 10:24 pm
Posts: 6017
Location: Amsterdam, Netherlands
The problem is not that SheepShaver won't run. It opens with a black screen.
Also, the March 2020 build is signed and notarized.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Mon Jun 15, 2020 8:17 pm 
Offline
Space Cadet

Joined: Sat Dec 13, 2014 1:45 am
Posts: 7
I'm still assuming something went awry with the security update and hoping to figure out a way to rerun the installer.

Everything else on the computer seems to be running okay so far. I booted off a USB stick and ran Disk First Aid and all was fine with the startup disk. Suppose I can try purging caches or something, but that will have to wait.

Mini breakthrough though. I stumbled across an old backup folder of Sheepshaver that had the v2.4 February 2014 build of the app. It opened normally, but wasn't stable. I then downloaded the v2.4 July 2018 build. It also opens up normally and it seems stable, but all I did was copy a file and open and close an app. This is using the same folder with the same ROM and same preference file. It apparently just doesn't like the 2.5 versions of the app.

I usually only use SheepShaver on the weekends, so I'll give the old version a try Saturday and see how it goes.

Thanks again for the feedback.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Mon Jun 15, 2020 9:56 pm 
Offline
Forum All-Star

Joined: Tue Oct 14, 2008 12:12 am
Posts: 1194
SheepShaver 2.5 runs normally here in High Sierra with the latest security update.


Last edited by emendelson on Tue Jun 16, 2020 7:32 pm, edited 1 time in total.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Tue Jun 16, 2020 9:51 am 
Offline
Expert User
User avatar

Joined: Thu Feb 09, 2006 10:24 pm
Posts: 6017
Location: Amsterdam, Netherlands
So, those version 2.4 builds work fine, while the version 2.5 builds do not.
The v2.4 builds are 32-bit and use SDL1, the v2.5 builds are 64-bit and use SDL2. The v2.5 builds open with a black screen. That suggests a graphics issue that could be related to SDL2. You have High Sierra installed on an unsupported machine. Maybe the High Sierra security update created an incompatibility with the graphics hardware that prevents SDL2 to work properly?


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Tue Jun 16, 2020 12:29 pm 
Offline
Master Emulator
User avatar

Joined: Wed Apr 10, 2013 9:32 am
Posts: 316
I’m also running High Sierra 10.13.6 with the newest Security Update (2020-003), but on a Hackintosh. SheepShaver 2.5 is running fine here.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Wed Jun 17, 2020 9:11 pm 
Offline
Space Cadet

Joined: Sat Dec 13, 2014 1:45 am
Posts: 7
The title of my original post is probably unfair to the security update, but I don't suppose there's a way to change that.

Thanks to those who confirmed that it is almost certainly just a "me" issue.

And, yes, the later v2.4 build does open correctly and seems at least at basic tasks to be stable. Although to be clear on v2.5, I think it might be more than just the screen being black. I can't be sure, but I don't think it's opening up correctly besides the black screen. I think the screen is black and the program is hanging. I alluded to it in the original post as after a few moments, console begins showing messages about SheepShaver burning CPU.

Regardless, until I can either reinstall the security update or a new security update comes out, I'll assume something went awry during the update and hopefully I can just get by with the older version.

Thanks for everyone's feedback.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Thu Jun 18, 2020 7:09 am 
Offline
Expert User
User avatar

Joined: Thu Feb 09, 2006 10:24 pm
Posts: 6017
Location: Amsterdam, Netherlands
I do not know if High Sierra converted your file system from HFS+ to APFS.
If it did: Note that in the older versions 'the shared folder / Unix disk' feature does not work correctly on a host with APFS file system. Files moved through the Unix disk will loose their resource fork and Type/Creator metadata.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Thu Jun 18, 2020 9:38 am 
Offline
Granny Smith

Joined: Thu Nov 09, 2017 12:06 pm
Posts: 136
The issue may due to default rendering method of SDL2.

@Darko66
If you can build SheepShaver, try latest source:

https://github.com/kanjitalk755/macemu

And append to ~/.sheepshaver_prefs:

Code:
sdlrender software


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Sun Jun 21, 2020 2:18 am 
Offline
Space Cadet

Joined: Sat Dec 13, 2014 1:45 am
Posts: 7
All my drives are still HFS+.

I guess sometimes software updates break the patches, so I ran the post-install tool again to see if that would help. It didn't.

I used the v2.4 July 2018 build today w/o any issues, so I'll probably just stick with that for now. Maybe when the next security update comes along we'll see what happens and I'll report back.

Thanks


Top
 Profile  
Reply with quote Post a reply  
Display posts from previous:  Sort by  
Post new topic  Reply to topic Page 1 of 1 [ 14 posts ]


Who is online

Users browsing this forum: No registered users and 11 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
 

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group