OS X Ventura
Moderators: Cat_7, Ronald P. Regensburg, ClockWise
-
- Mac Mechanic
- Posts: 163
- Joined: Thu Mar 17, 2011 1:46 am
OS X Ventura
Reading this forum seems to confirm that SheepShaver is compatible with OS X Ventura. Am I correct ?
- adespoton
- Forum All-Star
- Posts: 4227
- Joined: Fri Nov 27, 2009 5:11 am
- Location: Emaculation.com
- Contact:
Re: OS X Ventura
Yup. I'm running it on Ventura with zero issues.rlesperance wrote: ↑Tue Dec 13, 2022 9:02 pm Reading this forum seems to confirm that SheepShaver is compatible with OS X Ventura. Am I correct ?
-
- Mac Mechanic
- Posts: 163
- Joined: Thu Mar 17, 2011 1:46 am
Re: OS X Ventura
Thanks.
Re: OS X Ventura
Hi
Any tricks to run Arm version. on an ext Samsung ssd
Running perfectly on my intel iMac but hangs in arm64 (rosetta don't work at all)
Copied my intel installation and changed path's
default 11:34:59.555548+0100 SheepShaver No persisted cache on this platform.
default 11:34:59.556766+0100 SheepShaver Could not get size of EAN data (IOConnectCallScalarMethod kAppleNVMeEANGetSize returned 0xE00002E2)
default 11:34:59.556879+0100 SheepShaver Failed to copy 'aptk' from EAN
default 11:34:59.556957+0100 SheepShaver Failed to copy APTicket properties. Falling back to default policy.
default 11:34:59.557048+0100 SheepShaver Creating default MGSysConfigPolicy
default 11:34:59.557339+0100 runningboardd Calculated state for app<application.com.emaculation.sheepshaver.570714.570733(501)>: running-active (role: UserInteractiveFocal)
default 11:34:59.557356+0100 SheepShaver syscfg is not initialized!
default 11:34:59.557518+0100 SheepShaver CFDictionaryRef copySyscfgDictionary(void) enumeration of <private> failed.
default 11:34:59.557565+0100 SheepShaver Failed to find key <private>
default 11:34:59.557697+0100 runningboardd [app<application.com.emaculation.sheepshaver.570714.570733(501)>:13879] Ignoring jetsam update because this process is not memory-managed
default 11:34:59.558126+0100 runningboardd [app<application.com.emaculation.sheepshaver.570714.570733(501)>:13879] Ignoring suspend because this process is not lifecycle managed
default 11:34:59.559695+0100 SheepShaver Post-registration system appearance: (HLTB: 1)
default 11:34:59.609383+0100 SheepShaver Registering for test daemon availability notify post.
default 11:34:59.609389+0100 distnoted register name: com.apple.accessibility.api object: kCFNotificationAnyObject token: 210000001e pid: 13879
default 11:34:59.609467+0100 SheepShaver notify_get_state check indicated test daemon not ready.
default 11:34:59.609554+0100 SheepShaver notify_get_state check indicated test daemon not ready.
default 11:34:59.609736+0100 SheepShaver notify_get_state check indicated test daemon not ready.
default 11:34:59.613193+0100 WindowServer <private> adding window 1497 with state "none"; now 1 window(s) exist.
default 11:34:59.613267+0100 WindowServer <private> updated window 1497 from "none" to "hidden".
default 11:34:59.613298+0100 WindowServer <private> overall window state is now "hidden"
default 11:34:59.639936+0100 SheepShaver HALPlugInManagement::RegisterPlugIns: skipping in-process plug-ins
default 11:34:59.646194+0100 SheepShaver SignalReady: pid=13879 asn=0x0-0x138138
default 11:34:59.647195+0100 SheepShaver SIGNAL: pid=13879 asn=0x0x-0x138138
default 11:34:59.647635+0100 loginwindow -[PersistentAppsSupport applicationReady:] | App: SheepShaver, ready, updating active tracking timer
default 11:34:59.647660+0100 loginwindow -[PersistentAppsSupport(Internal) updateActiveTrackingTimer] | Extending timer
default 11:34:59.651141+0100 SheepShaver Initializing connection
default 11:34:59.651170+0100 SheepShaver Removing all cached process handles
default 11:34:59.651189+0100 SheepShaver Sending handshake request attempt #1 to server
default 11:34:59.651321+0100 SheepShaver Creating connection to com.apple.runningboard
default 11:34:59.651979+0100 SheepShaver Handshake succeeded
default 11:34:59.652039+0100 SheepShaver Identity resolved as app<application.com.emaculation.sheepshaver.570714.570733(501)>
default 11:34:59.652436+0100 runningboardd Assertion 149-13879-28194 (target:[app<application.com.emaculation.sheepshaver.570714.570733(501)>:13879]) will be created as active
default 11:34:59.782175+0100 runningboardd Calculated state for app<application.com.emaculation.sheepshaver.570714.570733(501)>: running-active (role: UserInteractiveFocal)
default 11:34:59.782186+0100 runningboardd [app<application.com.emaculation.sheepshaver.570714.570733(501)>:13879] Ignoring jetsam update because this process is not memory-managed
default 11:34:59.782253+0100 runningboardd [app<application.com.emaculation.sheepshaver.570714.570733(501)>:13879] Ignoring suspend because this process is not lifecycle managed
default 11:34:59.782361+0100 runningboardd [app<application.com.emaculation.sheepshaver.570714.570733(501)>:13879] Ignoring GPU update because this process is not GPU managed
default 11:34:59.968384+0100 SheepShaver MessageTracer: Falling back to default whitelist
default 11:34:59.969887+0100 SheepShaver SetFrontProcess: asn=0x0-0x138138 options=1
default 11:35:00.107301+0100 SheepShaver Entering exit handler.
default 11:35:00.107407+0100 SheepShaver Exiting exit handler.
Any tricks to run Arm version. on an ext Samsung ssd
Running perfectly on my intel iMac but hangs in arm64 (rosetta don't work at all)
Copied my intel installation and changed path's
default 11:34:59.555548+0100 SheepShaver No persisted cache on this platform.
default 11:34:59.556766+0100 SheepShaver Could not get size of EAN data (IOConnectCallScalarMethod kAppleNVMeEANGetSize returned 0xE00002E2)
default 11:34:59.556879+0100 SheepShaver Failed to copy 'aptk' from EAN
default 11:34:59.556957+0100 SheepShaver Failed to copy APTicket properties. Falling back to default policy.
default 11:34:59.557048+0100 SheepShaver Creating default MGSysConfigPolicy
default 11:34:59.557339+0100 runningboardd Calculated state for app<application.com.emaculation.sheepshaver.570714.570733(501)>: running-active (role: UserInteractiveFocal)
default 11:34:59.557356+0100 SheepShaver syscfg is not initialized!
default 11:34:59.557518+0100 SheepShaver CFDictionaryRef copySyscfgDictionary(void) enumeration of <private> failed.
default 11:34:59.557565+0100 SheepShaver Failed to find key <private>
default 11:34:59.557697+0100 runningboardd [app<application.com.emaculation.sheepshaver.570714.570733(501)>:13879] Ignoring jetsam update because this process is not memory-managed
default 11:34:59.558126+0100 runningboardd [app<application.com.emaculation.sheepshaver.570714.570733(501)>:13879] Ignoring suspend because this process is not lifecycle managed
default 11:34:59.559695+0100 SheepShaver Post-registration system appearance: (HLTB: 1)
default 11:34:59.609383+0100 SheepShaver Registering for test daemon availability notify post.
default 11:34:59.609389+0100 distnoted register name: com.apple.accessibility.api object: kCFNotificationAnyObject token: 210000001e pid: 13879
default 11:34:59.609467+0100 SheepShaver notify_get_state check indicated test daemon not ready.
default 11:34:59.609554+0100 SheepShaver notify_get_state check indicated test daemon not ready.
default 11:34:59.609736+0100 SheepShaver notify_get_state check indicated test daemon not ready.
default 11:34:59.613193+0100 WindowServer <private> adding window 1497 with state "none"; now 1 window(s) exist.
default 11:34:59.613267+0100 WindowServer <private> updated window 1497 from "none" to "hidden".
default 11:34:59.613298+0100 WindowServer <private> overall window state is now "hidden"
default 11:34:59.639936+0100 SheepShaver HALPlugInManagement::RegisterPlugIns: skipping in-process plug-ins
default 11:34:59.646194+0100 SheepShaver SignalReady: pid=13879 asn=0x0-0x138138
default 11:34:59.647195+0100 SheepShaver SIGNAL: pid=13879 asn=0x0x-0x138138
default 11:34:59.647635+0100 loginwindow -[PersistentAppsSupport applicationReady:] | App: SheepShaver, ready, updating active tracking timer
default 11:34:59.647660+0100 loginwindow -[PersistentAppsSupport(Internal) updateActiveTrackingTimer] | Extending timer
default 11:34:59.651141+0100 SheepShaver Initializing connection
default 11:34:59.651170+0100 SheepShaver Removing all cached process handles
default 11:34:59.651189+0100 SheepShaver Sending handshake request attempt #1 to server
default 11:34:59.651321+0100 SheepShaver Creating connection to com.apple.runningboard
default 11:34:59.651979+0100 SheepShaver Handshake succeeded
default 11:34:59.652039+0100 SheepShaver Identity resolved as app<application.com.emaculation.sheepshaver.570714.570733(501)>
default 11:34:59.652436+0100 runningboardd Assertion 149-13879-28194 (target:[app<application.com.emaculation.sheepshaver.570714.570733(501)>:13879]) will be created as active
default 11:34:59.782175+0100 runningboardd Calculated state for app<application.com.emaculation.sheepshaver.570714.570733(501)>: running-active (role: UserInteractiveFocal)
default 11:34:59.782186+0100 runningboardd [app<application.com.emaculation.sheepshaver.570714.570733(501)>:13879] Ignoring jetsam update because this process is not memory-managed
default 11:34:59.782253+0100 runningboardd [app<application.com.emaculation.sheepshaver.570714.570733(501)>:13879] Ignoring suspend because this process is not lifecycle managed
default 11:34:59.782361+0100 runningboardd [app<application.com.emaculation.sheepshaver.570714.570733(501)>:13879] Ignoring GPU update because this process is not GPU managed
default 11:34:59.968384+0100 SheepShaver MessageTracer: Falling back to default whitelist
default 11:34:59.969887+0100 SheepShaver SetFrontProcess: asn=0x0-0x138138 options=1
default 11:35:00.107301+0100 SheepShaver Entering exit handler.
default 11:35:00.107407+0100 SheepShaver Exiting exit handler.
-
- Forum All-Star
- Posts: 1706
- Joined: Tue Oct 14, 2008 12:12 am
Re: OS X Ventura
Download the current version if you don't already have it. Works perfectly on M1 Macs.
And have you tried running it on your startup partition, not an external drive?
And have you tried running it on your startup partition, not an external drive?
Re: OS X Ventura
It the last one ...
Tried to run in from boot volume too !
Just starts and quits immediately
deleting .sheepshaver_prefs & .sheepshaver_nvram does not do anything ...
maybe should download the source and run it in Xcode to see why it breaks !
Alex
Tried to run in from boot volume too !
Just starts and quits immediately
deleting .sheepshaver_prefs & .sheepshaver_nvram does not do anything ...
maybe should download the source and run it in Xcode to see why it breaks !
Alex
- Ronald P. Regensburg
- Expert User
- Posts: 7821
- Joined: Thu Feb 09, 2006 10:24 pm
- Location: Amsterdam, Netherlands
Re: OS X Ventura
The latest SheepShaver build should run fine natively in Ventura on Apple Silicon. It does so here and for other users. I did not yet try to run it on my M1 iMac from an external volume.
A couple of things to note:
- A security feature in macOS will prevent the app to run in the location to where it is downloaded or where the zip archive is expanded. Download the zip archive in a different location (like your Downloads folder), expand the archive there, and then move the app into your SheepShaver folder.
- A new SheepShaver setup will not run without a compatible ROM file with the exact name "Mac OS ROM" (without a file name extension!) in the same folder as the SheepShaver app itself. If set up following our setup manual, that will be in the SheepShaver folder.
Our setup manual is here: https://www.emaculation.com/doku.php/sh ... os_x_setup
A couple of things to note:
- A security feature in macOS will prevent the app to run in the location to where it is downloaded or where the zip archive is expanded. Download the zip archive in a different location (like your Downloads folder), expand the archive there, and then move the app into your SheepShaver folder.
- A new SheepShaver setup will not run without a compatible ROM file with the exact name "Mac OS ROM" (without a file name extension!) in the same folder as the SheepShaver app itself. If set up following our setup manual, that will be in the SheepShaver folder.
Our setup manual is here: https://www.emaculation.com/doku.php/sh ... os_x_setup
Re: OS X Ventura
Hi Thanx
Got it to work, changed memory to 768 mb then it booted, and changed back to 1024 and it worked !
Im a happy SheepShaver user since many years, running framemaker since adobe never made an osx version.
/Alexis
Got it to work, changed memory to 768 mb then it booted, and changed back to 1024 and it worked !
Im a happy SheepShaver user since many years, running framemaker since adobe never made an osx version.
/Alexis
-
- Space Cadet
- Posts: 2
- Joined: Tue Dec 20, 2022 10:04 pm
Re: OS X Ventura
Here's a weird thing that's happening to me on Ventura. For some reason the settings pane are inaccessible in Ventura:
-
- Forum All-Star
- Posts: 1706
- Joined: Tue Oct 14, 2008 12:12 am
Re: OS X Ventura
Same thing happens on the system that I upgraded to Ventura a few days ago. Very strange....!
- Ronald P. Regensburg
- Expert User
- Posts: 7821
- Joined: Thu Feb 09, 2006 10:24 pm
- Location: Amsterdam, Netherlands
Re: OS X Ventura
Same thing here.
In Ventura "Preferences..." is replaced By "Settings..." in all applications. In SheepShaver the Preferences item is not really referring to preferences but to a different part of the app with the settings GUI, so it does not work anymore. I suppose kanjitalk755 can solve it in the SheepShaver source.
In Ventura "Preferences..." is replaced By "Settings..." in all applications. In SheepShaver the Preferences item is not really referring to preferences but to a different part of the app with the settings GUI, so it does not work anymore. I suppose kanjitalk755 can solve it in the SheepShaver source.
-
- Forum All-Star
- Posts: 1706
- Joined: Tue Oct 14, 2008 12:12 am
Re: OS X Ventura
I posted an issue on GitHub. If anyone wants to change their own build, you can fix this in the source by changing the strings in prefs_macosx lines 116 and 127 to `"@Settings..."` but I don't know how to create an `if ... then` statement that would make this work only in Ventura and later.
-
- Forum All-Star
- Posts: 1706
- Joined: Tue Oct 14, 2008 12:12 am
Re: OS X Ventura
I don't know anything about programming, but by searching the web, I was able to put together some replacement code that fixes the problem; tested on Monterey and Ventura. I don't know if the code is accurate, but you can find it here and experiment until kanjitalk755 provides something better:
https://github.com/kanjitalk755/macemu/ ... 1361335532
https://github.com/kanjitalk755/macemu/ ... 1361335532
-
- Mac Mechanic
- Posts: 163
- Joined: Thu Mar 17, 2011 1:46 am
Re: OS X Ventura
This group is awesome and gorgeous ! Thanks for being there !
-
- Forum All-Star
- Posts: 1706
- Joined: Tue Oct 14, 2008 12:12 am
Re: OS X Ventura
kanjitalk755 has now made a much better fix than mine.
I've updated all my apps that use SheepShaver (the SheepShaver Wrapper, the WPMacApp, and Mac OS 9 for macOS/OSX).
I've updated all my apps that use SheepShaver (the SheepShaver Wrapper, the WPMacApp, and Mac OS 9 for macOS/OSX).
- Ronald P. Regensburg
- Expert User
- Posts: 7821
- Joined: Thu Feb 09, 2006 10:24 pm
- Location: Amsterdam, Netherlands
Re: OS X Ventura
I will build and post new builds as soon as I have time to do that.
Re: OS X Ventura
My "Settings" Is greyed out also under Ventura.
- Ronald P. Regensburg
- Expert User
- Posts: 7821
- Joined: Thu Feb 09, 2006 10:24 pm
- Location: Amsterdam, Netherlands
Re: OS X Ventura
The issue was fixed by kanjitalk755, now available in my latest (22 December 2022) build: viewtopic.php?t=7360
-
- Space Cadet
- Posts: 2
- Joined: Tue Dec 20, 2022 10:04 pm
Re: OS X Ventura
haha didn't have time the last two weeks to check on this post since I was kinda busy but I'm glad it's fixed now. Y'all do such a great work!
-
- Space Cadet
- Posts: 1
- Joined: Sun Aug 20, 2023 2:01 pm
Re: OS X Ventura
Unfortunately I'm having this problem with the current (10 August 2023) version on Ventura 13.5. Settings is greyed out and disabled.
- Ronald P. Regensburg
- Expert User
- Posts: 7821
- Joined: Thu Feb 09, 2006 10:24 pm
- Location: Amsterdam, Netherlands
Re: OS X Ventura
This should not happen with the latest SheepShaver build. Here it works fine in Ventura with "Settings" available in the SheepShaver menu. Could you have more than one SheepShaver app on your machine and accidentally launched an older build?
- ndtronerud
- Space Cadet
- Posts: 8
- Joined: Fri May 15, 2015 6:41 am
- Location: Los Angeles, CA
Re: OS X Ventura
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 image, tried copying SheepShaver to and launching from my system drive (as opposed to a different storage drive); nothing seems to be working. It begins to launch, but then immediately quits. I don't even get a chance to try and reconfigure it in settings.
For what it's worth, Basilisk is also not launching.
If it matters, I am running Ventura 13.5 on an iMac 2010 using OCLP. SheepShaver (and Basilisk) work just fine in Monterey using this configuration. Mini vMac/Mini vMac II have no issues in either OS.
For what it's worth, Basilisk is also not launching.
If it matters, I am running Ventura 13.5 on an iMac 2010 using OCLP. SheepShaver (and Basilisk) work just fine in Monterey using this configuration. Mini vMac/Mini vMac II have no issues in either OS.
-
- Forum All-Star
- Posts: 1706
- Joined: Tue Oct 14, 2008 12:12 am
Re: OS X Ventura
This is one of many OCLP problems in mcOS Ventura. The only people who can help will be the OCLP developers.
Last edited by emendelson on Sat Aug 26, 2023 10:01 pm, edited 1 time in total.
- ndtronerud
- Space Cadet
- Posts: 8
- Joined: Fri May 15, 2015 6:41 am
- Location: Los Angeles, CA
Re: OS X Ventura
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.
Re: OS X Ventura
Hi, I'm with a MacBook Air M1, and I launch the binary (not the .app), with a floppy boot on disk util, but "Settings is greyed out and disabled."
macOS Ventura 13.2.1.
Regards
macOS Ventura 13.2.1.
Regards