macOS Sierra
Moderators: Cat_7, Ronald P. Regensburg, ClockWise
-
- Apple Corer
- Posts: 273
- Joined: Fri Oct 26, 2007 7:56 am
macOS Sierra
From what I've read, it appears that the possibility of running application in 32-bit mode is no longer present in macOS Sierra. I wonder if that will definitively cripple SheepShaver, which can't run in 64-bit mode in El Capitan. Perhaps the QEMU solution will finally be ready by the time Sierra is released to the public.
-
- Forum All-Star
- Posts: 1706
- Joined: Tue Oct 14, 2008 12:12 am
Re: macOS Sierra
Speaking in general (because of legal restrictions): (1) don't believe everything you read and (2) don't draw unwarranted conclusions from anything you read.
Re: macOS Sierra
Just so you know, I have SheepShaver 2.4 (2014-02-01) working on macOS Sierra my Late 2009 iMac.
No changes were needed to my El Capitan setup.
No changes were needed to my El Capitan setup.
iMac 21.5-inch, Late 2009, 3.06 GHz Intel Core 2 Duo, 8 GB RAM. OS X 10.12.6
-
- Space Cadet
- Posts: 4
- Joined: Tue Sep 27, 2016 5:02 am
Re: macOS Sierra
Can anyone give advice on how to get SheepShaver working in macOS Sierra? I have installed it on my MacBook for the first time, so I never got to open it in El Capitain. For me, whether I try to open it in 32-bit or 64-bit mode, it simply quits immediately upon opening. I don't get the configuration window before that happens.
- Ronald P. Regensburg
- Expert User
- Posts: 7821
- Joined: Thu Feb 09, 2006 10:24 pm
- Location: Amsterdam, Netherlands
Re: macOS Sierra
Did you follow the instructions in the setup guide? Specifically, did you add a compatible rom file and did you (re)name it as instructed? As described in the setup guide, without such rom file SheepShaver will quit on launch.
-
- Space Cadet
- Posts: 4
- Joined: Tue Sep 27, 2016 5:02 am
Re: macOS Sierra
Yes, I used a New World ROM and renamed it to "Mac OS ROM" without any quotes or any extension. I don't even get to the Virtual Machine Settings window before SheepShaver quits. It's basically instantaneous.
Thanks!
Thanks!
Re: macOS Sierra
Same deal here. 10.12 Sierra, app immediately crashes. Only message in Console is as follows:
com.apple.message.domain: com.apple.ls.appBits
com.apple.message.32bit: 1
com.apple.message.bundle-version: 2.4
com.apple.message.has-64bit-slice: 1
SenderMachUUID: A79BC170-CAEF-DD77-E368-199302281DF2
Screenshot of my SS folder:
ROM was downloaded from http://www.redundantrobot.com/#/sheepshaver (It is the generic New World PPC ROM, but the same behavior has happened when trying with lots of other ROMs)
com.apple.message.domain: com.apple.ls.appBits
com.apple.message.32bit: 1
com.apple.message.bundle-version: 2.4
com.apple.message.has-64bit-slice: 1
SenderMachUUID: A79BC170-CAEF-DD77-E368-199302281DF2
Screenshot of my SS folder:
ROM was downloaded from http://www.redundantrobot.com/#/sheepshaver (It is the generic New World PPC ROM, but the same behavior has happened when trying with lots of other ROMs)
- adespoton
- Forum All-Star
- Posts: 4227
- Joined: Fri Nov 27, 2009 5:11 am
- Location: Emaculation.com
- Contact:
Re: macOS Sierra
Odd; I've got 4 SS VMs running (same build, same ROM) with no issues. What happens if you edit the prefs file to ignore illegal instructions? How about if you disable JIT?
Re: macOS Sierra
I too get a killed: 9 message. Also when running the SheepShaver executable inside the package. Prefs were already edited by hand...
What made SheepShaver working at my place:
I moved the SheepShaver program out of its folder into the applications folder and tried to run it. No dice.
Then I copied the program to the desktop, deleted the copy in the applications folder, and then moved the program back into the SheepShaver folder and it started working.
EDIT: The behaviour is reproducible with a new download. But 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.
Best,
Cat_7
What made SheepShaver working at my place:
I moved the SheepShaver program out of its folder into the applications folder and tried to run it. No dice.
Then I copied the program to the desktop, deleted the copy in the applications folder, and then moved the program back into the SheepShaver folder and it started working.
EDIT: The behaviour is reproducible with a new download. But 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.
Best,
Cat_7
Last edited by Cat_7 on Tue Sep 27, 2016 7:41 pm, edited 1 time in total.
Reason:
Reason:
- adespoton
- Forum All-Star
- Posts: 4227
- Joined: Fri Nov 27, 2009 5:11 am
- Location: Emaculation.com
- Contact:
Re: macOS Sierra
Ahh... I run all of mine via sheepvms located within the sheepshaver app itself. I had a similar issue when I attempted to alias the sheepvm or the inner image files from my user folder. Interesting that issues arise in Sierra and not El Cap though.
-
- Space Cadet
- Posts: 4
- Joined: Tue Sep 27, 2016 5:02 am
Re: macOS Sierra
I had added the SheepShaver folder to my Applications folder, and it didn't work then. I re-unzipped the archive and manually added the new copy of the SheepShaver executable to the SheepShaver folder in the Applications folder, and this did allow the app to open in 32-bit mode on Sierra. Maybe the first unzip was simply corrupt.
Thanks!
Thanks!
Re: macOS Sierra
We're discussing this on github: https://github.com/cebix/macemu/issues/98