SS will not run in Ventura (under OpenCore Legacy Patcher only)

About SheepShaver, a PPC Mac emulator for Windows, MacOS X, and Linux that can run System 7.5.3 to MacOS 9.0.4.

Moderators: Cat_7, Ronald P. Regensburg, ClockWise

trevorpsy
Student Driver
Posts: 17
Joined: Sat Jan 04, 2014 11:36 pm

SS will not run in Ventura (under OpenCore Legacy Patcher only)

Post by trevorpsy »

I just upgraded my mac from Monterey to Ventura, and now I'm getting a "Sheepshaver quit unexpectedly" crash. I can forward a long a Problem Details document, if it would be useful.

Thanks,,

Trevor Monroe

Moderator edit: changed the title to include (under OpenCore Legacy Patcher only)
emendelson
Forum All-Star
Posts: 1730
Joined: Tue Oct 14, 2008 12:12 am

Re: SS will not run in Ventura

Post by emendelson »

SheepShaver runs perfectly in Ventura. Download the latest version from the first post in this form and try again.
trevorpsy
Student Driver
Posts: 17
Joined: Sat Jan 04, 2014 11:36 pm

Re: SS will not run in Ventura

Post by trevorpsy »

I already to that. I've installed SheepShaver 2.5 August 10, 2023, and it doesn't work. It's working fine in Monterey.
trevorpsy
Student Driver
Posts: 17
Joined: Sat Jan 04, 2014 11:36 pm

Re: SS will not run in Ventura

Post by trevorpsy »

Could it be a corrupt preferences file?
User avatar
Ronald P. Regensburg
Expert User
Posts: 7852
Joined: Thu Feb 09, 2006 10:24 pm
Location: Amsterdam, Netherlands

Re: SS will not run in Ventura

Post by Ronald P. Regensburg »

If you did a regular upgrade of macOS in place, without changing any SheepShaver related file, SheepShaver should continue to run fine.

Did the latest build work fine in Monterey before you upgraded to Ventura?

If installed the newer build after upgrading macOS, first try this:
- Copy SheepShaver application (only the application itself) to a different location
- Trash the original application
- Move the copy back to where the original was.

If that does not solve the issue, please post here the content of your prefs file:
Launch Terminal (in /Application/Utilities/) and type at the prompt

Code: Select all

open ~/.sheepshaver_prefs
followed by a return.
The file will open in your default text editor. Select all content and copy and paste it here in your reply.
trevorpsy
Student Driver
Posts: 17
Joined: Sat Jan 04, 2014 11:36 pm

Re: SS will not run in Ventura

Post by trevorpsy »

Thanks for getting back to me.

Things have gone from bad to worse. Sheepshaver now doesn't respond when I double click on it.

I'm thinking I should rebuild it from scratch. Sound like a good idea?

BTW, I tried lifting the entire Sheepshaver folder over from Monterey to Ventura. The problem persists.

This is isn't a huge issue, because I can run either Monterey or Ventura. Because of this problem and other issues, I'm returning to Monterey, except for when I'm using Photoshop (which is faster in Ventura).

On the other hand, it would be useful to figure out what's wrong.

Take care and thank you for Sheepshaver. I use it every day.

Trevor
emendelson
Forum All-Star
Posts: 1730
Joined: Tue Oct 14, 2008 12:12 am

Re: SS will not run in Ventura

Post by emendelson »

Or download this:

http://www.columbia.edu/~em36/macos9osx.html

If you get a 404 error, your browser changed http:// to https:// Simply change it back.
trevorpsy
Student Driver
Posts: 17
Joined: Sat Jan 04, 2014 11:36 pm

Re: SS will not run in Ventura

Post by trevorpsy »

I'm not getting an error. Nothing is happening when I double-click SS

Just now, I tried to download the file you suggested, and I'm getting this error message: Unable to expand "Mac OS 9.zip". It is in an unsupported format.

Do you have an alternative link?

Thanks for much for your time.

Trevor
emendelson
Forum All-Star
Posts: 1730
Joined: Tue Oct 14, 2008 12:12 am

Re: SS will not run in Ventura

Post by emendelson »

Something seems to be wrong with your system. The ZIP archive expands perfectly on two different machines here. Possibly the same thing that's going wrong with expanding the ZIP is also what's going wrong with SheepShaver. You may want to reinstall Ventura on your machine. Meanwhile, try the download on your Monterey setup and you'll see that there's nothing wrong with the ZIP archive.
trevorpsy
Student Driver
Posts: 17
Joined: Sat Jan 04, 2014 11:36 pm

Re: SS will not run in Ventura

Post by trevorpsy »

I tried to open the file in Monterey when I got the error code. Monterey is working fine, including SS. No problems anywhere.

Ventura is the problem, not just with SS. Strange stuff, like the Wall Paper stopped working, as well as SS, and Firefox can't load YouTube, but it works in Monterey. (Figure that one out!)

I can easily run either OS. Looks like I'm going to stick with Monterey, other than when I'm using Photoshop, which is faster in Ventura. I just won't be able to use SS while I'm in Ventura. Not a huge deal.

Take care and thanks again,

Trevor
emendelson
Forum All-Star
Posts: 1730
Joined: Tue Oct 14, 2008 12:12 am

Re: SS will not run in Ventura

Post by emendelson »

Something seems to be wrong with your Monterey system also, and possibly whatever was wrong there got carried over into your Ventura setup. That ZIP archive was made with macOS's "compress" command, not with anything that isn't compatible with macOS. Probably a reinstall of both systems would sort things out, because none of those problems should be occurring at all.
trevorpsy
Student Driver
Posts: 17
Joined: Sat Jan 04, 2014 11:36 pm

Re: SS will not run in Ventura

Post by trevorpsy »

Thanks. This first and only time I've run into this problem. If it reoccurs, I'll go through reinstalling, which is very time consuming.
trevorpsy
Student Driver
Posts: 17
Joined: Sat Jan 04, 2014 11:36 pm

Re: SS will not run in Ventura

Post by trevorpsy »

I realized that I hadn't give the download enough and therefore downloaded an incomplete file. Now I have downloaded the complete zip file, but it still doesn't work. I'm getting error message stated the it's impossible to determine the file format.
trevorpsy
Student Driver
Posts: 17
Joined: Sat Jan 04, 2014 11:36 pm

Re: SS will not run in Ventura

Post by trevorpsy »

I looked the through the download page and found another link, which produced a successful zip file that expanded into MacOS Nine.app. When I launched app, the same crash and error message occurred: SheepShaver quit unexpectedly.

Here's the details:

Translated Report (Full Report Below)
-------------------------------------

Incident Identifier: 19F754DC-B870-4456-B491-3299CB335200
CrashReporter Key: 4D0624D6-F4B3-D458-D256-442AED663B46
Hardware Model: MacPro5,1
Process: SheepShaver [7862]
Path: /Applications/SheepShaver/MacOS Nine.app/Contents/Resources/SheepShaver
Identifier: SheepShaver
Version: ???
Code Type: X86-64 (Native)
Role: Foreground
Parent Process: Exited process [7846]
Coalition: org.wpdos.sheepshaver [7314]

Date/Time: 2023-11-13 13:03:38.5887 -0800
Launch Time: 2023-11-13 13:03:37.2115 -0800
OS Version: macOS 13.6.1 (22G313)
Release Type: User
Report Version: 104

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x00000000000003ac
Exception Codes: 0x0000000000000001, 0x00000000000003ac
VM Region Info: 0x3ac is not in any region. Bytes before following region: 140737487756372
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
shared memory 7ffffff6e000-7ffffff6f000 [ 4K] r-x/r-x SM=SHM
Termination Reason: SIGNAL 11 Segmentation fault: 11
Terminating Process: exc handler [7862]

Highlighted by Thread: 0

Backtrace not available

No thread state (register information) available

Binary Images:
0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ???

Error Formulating Crash Report:
_dyld_process_info_create failed with 1
Failed to create CSSymbolicatorRef - corpse still valid ¯\_(ツ)_/¯
thread_get_state(PAGEIN) returned 0x10000003: (ipc/send) invalid destination port
thread_get_state(EXCEPTION) returned 0x10000003: (ipc/send) invalid destination port
thread_get_state(FLAVOR) returned 0x10000003: (ipc/send) invalid destination port

EOF

-----------
Full Report
-----------

{"app_name":"SheepShaver","timestamp":"2023-11-13 13:03:38.00 -0800","app_version":"","slice_uuid":"3579a622-2666-3e58-9da0-6679a1b00e64","build_version":"","platform":0,"share_with_app_devs":1,"is_first_party":1,"bug_type":"309","os_version":"macOS 13.6.1 (22G313)","roots_installed":0,"incident_id":"19F754DC-B870-4456-B491-3299CB335200","name":"SheepShaver"}
{
"uptime" : 2300,
"procRole" : "Foreground",
"version" : 2,
"userID" : 502,
"deployVersion" : 210,
"modelCode" : "MacPro5,1",
"coalitionID" : 7314,
"osVersion" : {
"train" : "macOS 13.6.1",
"build" : "22G313",
"releaseType" : "User"
},
"captureTime" : "2023-11-13 13:03:38.5887 -0800",
"incident" : "19F754DC-B870-4456-B491-3299CB335200",
"pid" : 7862,
"cpuType" : "X86-64",
"roots_installed" : 0,
"bug_type" : "309",
"procLaunch" : "2023-11-13 13:03:37.2115 -0800",
"procStartAbsTime" : 2398515806135,
"procExitAbsTime" : 2399891075272,
"procName" : "SheepShaver",
"procPath" : "\/Applications\/SheepShaver\/MacOS Nine.app\/Contents\/Resources\/SheepShaver",
"parentProc" : "Exited process",
"parentPid" : 7846,
"coalitionName" : "org.wpdos.sheepshaver",
"crashReporterKey" : "4D0624D6-F4B3-D458-D256-442AED663B46",
"codeSigningID" : "SheepShaver",
"codeSigningTeamID" : "533UMV53L8",
"codeSigningFlags" : 570490881,
"codeSigningValidationCategory" : 6,
"codeSigningTrustLevel" : 0,
"sip" : "enabled",
"vmRegionInfo" : "0x3ac is not in any region. Bytes before following region: 140737487756372\n REGION TYPE START - END [ VSIZE] PRT\/MAX SHRMOD REGION DETAIL\n UNUSED SPACE AT START\n---> \n shared memory 7ffffff6e000-7ffffff6f000 [ 4K] r-x\/r-x SM=SHM ",
"exception" : {"codes":"0x0000000000000001, 0x00000000000003ac","rawCodes":[1,940],"type":"EXC_BAD_ACCESS","signal":"SIGSEGV","subtype":"KERN_INVALID_ADDRESS at 0x00000000000003ac"},
"termination" : {"flags":0,"code":11,"namespace":"SIGNAL","indicator":"Segmentation fault: 11","byProc":"exc handler","byPid":7862},
"vmregioninfo" : "0x3ac is not in any region. Bytes before following region: 140737487756372\n REGION TYPE START - END [ VSIZE] PRT\/MAX SHRMOD REGION DETAIL\n UNUSED SPACE AT START\n---> \n shared memory 7ffffff6e000-7ffffff6f000 [ 4K] r-x\/r-x SM=SHM ",
"extMods" : {"caller":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"system":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"targeted":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"warnings":0},
"usedImages" : [
{
"size" : 0,
"source" : "A",
"base" : 0,
"uuid" : "00000000-0000-0000-0000-000000000000"
}
],
"sharedCache" : {
"base" : 140703431159808,
"size" : 21474836480,
"uuid" : "16e792d8-c834-3734-86d7-2aabac58b63b"
},
"legacyInfo" : {
"threadHighlighted" : 0
},
"trialInfo" : {
"rollouts" : [
{
"rolloutId" : "64c17a9925d75a7281053d4c",
"factorPackIds" : {
"SIRI_AUDIO_DISABLE_MEDIA_ENTITY_SYNC" : "64d29746ad29a465b3bbeace"
},
"deploymentId" : 240000002
},
{
"rolloutId" : "63508950b3714d3622fc77f7",
"factorPackIds" : {
"SIRI_MEMORY_SYNC_CONFIG" : "63508beab3714d3622fc7808"
},
"deploymentId" : 240000004
}
],
"experiments" : [

]
},
"reportNotes" : [
"_dyld_process_info_create failed with 1",
"Failed to create CSSymbolicatorRef - corpse still valid ¯\\_(ツ)_\/¯",
"thread_get_state(PAGEIN) returned 0x10000003: (ipc\/send) invalid destination port",
"thread_get_state(EXCEPTION) returned 0x10000003: (ipc\/send) invalid destination port",
"thread_get_state(FLAVOR) returned 0x10000003: (ipc\/send) invalid destination port"
]
}

Model: MacPro5,1, BootROM 9999.999.999.999.999, 12 processors, 6-Core Intel Xeon, 3.46 GHz, 128 GB, SMC 9.9999
Graphics: AMD Radeon RX 580, AMD Radeon RX 580, PCIe, 8 GB
Display: BenQ SW321C, 6016 x 3384, MirrorOff, Online
Display: DELL UP3017, 2560 x 1600, Main, MirrorOff, Online
Memory Module: DIMM 1, 16 GB, DDR3, 800 MHz, 0x80AD, 0x484D543432475237424D5234432D47372020
Memory Module: DIMM 2, 16 GB, DDR3, 800 MHz, 0x80AD, 0x484D543432475237424D5234432D47372020
Memory Module: DIMM 3, 16 GB, DDR3, 800 MHz, 0x80AD, 0x484D543432475237424D5234432D47372020
Memory Module: DIMM 4, 16 GB, DDR3, 800 MHz, 0x80AD, 0x484D543432475237424D5234432D47372020
Memory Module: DIMM 5, 16 GB, DDR3, 800 MHz, 0x80AD, 0x484D543432475237424D5234432D47372020
Memory Module: DIMM 6, 16 GB, DDR3, 800 MHz, 0x80AD, 0x484D543432475237424D5234432D47372020
Memory Module: DIMM 7, 16 GB, DDR3, 800 MHz, 0x80AD, 0x484D543432475237424D5234432D47372020
Memory Module: DIMM 8, 16 GB, DDR3, 800 MHz, 0x80AD, 0x484D543432475237424D5234432D47372020
AirPort: spairport_wireless_card_type_wifi (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.100.24)
Bluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports
Network Service: Ethernet 1, Ethernet, en0
Network Service: Ethernet 2, Ethernet, en1
Network Service: Wi-Fi, AirPort, en2
PCI Card: AMD Radeon RX 580, Display Controller, Slot-1
PCI Card: pci1002,aaf0, Audio Device, Slot-1
PCI Card: pci1b21,625, AHCI Controller, Slot-3
PCI Card: pci1b21,625, AHCI Controller, Slot-4
Serial ATA Device: HL-DT-ST DVD-RW GH41N
Serial ATA Device: ST31000528AS, 1 TB
Serial ATA Device: WDC WD40EZRZ-00GXCB0, 4 TB
Serial ATA Device: ST2000DM008-2FR102, 2 TB
Serial ATA Device: WDC WD4005FZBX-00K5WB0, 4 TB
Serial ATA Device: WDC WD4005FZBX-00K5WB0, 4 TB
Serial ATA Device: Samsung SSD 870 EVO 2TB, 2 TB
Serial ATA Device: Samsung SSD 870 QVO 4TB, 4 TB
USB Device: USB20Bus
USB Device: USB to ATA/ATAPI Bridge
USB Device: hub_device
USB Device: Razer Diamondback
USB Device: tinkerBOY [adb.usb]
USB Device: USB2.0 HUB
USB Device: USB to ATA/ATAPI Bridge
USB Device: USB Storage
USB Device: hub_device
USB Device: 4-Port USB 2.1 Hub
USB Device: USB <-> Serial Cable
USB Device: USB3.0 Card Reader
USB Device: HD Webcam C615
USB Device: SENNHEISER USB Audio 2.0
USB Device: USB20Bus
USB Device: MFC-L5850DW series
USB Device: USBBus
USB Device: USBBus
USB Device: USBBus
USB Device: USBBus
USB Device: USBBus
USB Device: USBBus
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
FireWire Device: built-in_hub, 800mbit_speed
Thunderbolt Bus:
emendelson
Forum All-Star
Posts: 1730
Joined: Tue Oct 14, 2008 12:12 am

Re: SS will not run in Ventura

Post by emendelson »

Once again: something is clearly wrong with your system, as you made clear when you reported other problems with screen savers, etc.

The app that you reported about most recently is a different app from the one you tried earlier. The download links are on separate pages, not on the same page. Both of the two apps - the MacOS9 app and the Mac OS Nine app - download and work correclty on both Intel and Apple Silicon machines, running Monterey, Ventura, and Sonoma. No one else has reported any similar problem, and both apps have been downloaded many times.

Again, the apps work correctly in every case. Your system is the problem, not SheepShaver.

EDIT I see that you are using a Mac Pro dating from 2012 or earlier. That means that you are probably using the OpenCore Legacy Patcher. That is the source of your problem. OCLP has known problems with SheepShaver. You should take this up with the OCLP authors. SheepShaver is only supported on systems that are supported by Apple, and it won't be changed to work around bugs in OCLP. I wish you had explained this earlier - it would have saved a lot of your time in trying to make something work that will never work until OCLP gets updated to make it work.
trevorpsy
Student Driver
Posts: 17
Joined: Sat Jan 04, 2014 11:36 pm

Re: SS will not run in Ventura

Post by trevorpsy »

As far as Wall Paper is concerned, I looked it up. This is a common complaint with Ventura and Sonoma, and no one has a solution.

Other than SS/Ventura, I can't point to any other problem with the OpenCore interface. The problem with Firefox, not Chrome, not loading YouTube in Ventura only also points to something going on with Ventura, not OpenCore. I'm getting feeling that Ventura is half-baked.

I've come to the conclusion that Ventura is appropriate for Photoshop and nothing else.

Do you have any notion as to why SS and Ventura don't get along running in OpenCore?
emendelson
Forum All-Star
Posts: 1730
Joined: Tue Oct 14, 2008 12:12 am

Re: SS will not run in Ventura

Post by emendelson »

trevorpsy wrote: Tue Nov 14, 2023 12:35 am Do you have any notion as to why SS and Ventura don't get along running in OpenCore?
Have you asked the OpenCore programmers? They're almost certainly the only ones who would know.

I'll drop out of this thread now, as I can't say anything useful about OCLP systems and I don't want to waste any more time for forum members who might be reading this thread. I've added a warning on my download pages saying that the apps will almost certainly not work on OCLP systems. I hope this will save a lot of time and trouble for people who might otherwise try it.

Moderators: could the Subject field of this thread be changed to add: (under OpenCore Legacy Patcher only)? That would avoid misleading visitors who use Apple-supported systems.
trevorpsy
Student Driver
Posts: 17
Joined: Sat Jan 04, 2014 11:36 pm

Re: SS will not run in Ventura

Post by trevorpsy »

How do I contact the SS engineers? There's a lot of us using OpenCore and the number is increasing.
User avatar
Ronald P. Regensburg
Expert User
Posts: 7852
Joined: Thu Feb 09, 2006 10:24 pm
Location: Amsterdam, Netherlands

Re: SS will not run in Ventura (under OpenCore Legacy Patcher only)

Post by Ronald P. Regensburg »

You could post about your issue here: https://github.com/kanjitalk755/macemu

But I am pretty sure that the developer (kanjitalk755) will not look into issues that are specific to running SheepShaver on macOS that was installed with OpenCore Legacy Patcher. SheepShaver runs fine in Ventura (and Sonoma) on supported machines.

The only ones that could possibly shed some light on your issues (apparently not only with SheepShaver) are the OpenCore programmers.
gorans
Inquisitive Elf
Posts: 26
Joined: Wed Dec 16, 2015 5:10 pm

Re: SS will not run in Ventura

Post by gorans »

trevorpsy wrote: Tue Nov 14, 2023 12:35 am As far as Wall Paper is concerned, I looked it up. This is a common complaint with Ventura and Sonoma, and no one has a solution.

Other than SS/Ventura, I can't point to any other problem with the OpenCore interface. The problem with Firefox, not Chrome, not loading YouTube in Ventura only also points to something going on with Ventura, not OpenCore. I'm getting feeling that Ventura is half-baked.

I've come to the conclusion that Ventura is appropriate for Photoshop and nothing else.

Do you have any notion as to why SS and Ventura don't get along running in OpenCore?
SS is working with Open Core, it's not working with OCLP patched machines.

Best regards,
Goran
User avatar
adespoton
Forum All-Star
Posts: 4314
Joined: Fri Nov 27, 2009 5:11 am
Location: Emaculation.com
Contact:

Re: SS will not run in Ventura

Post by adespoton »

gorans wrote: Thu Nov 23, 2023 6:30 pm
trevorpsy wrote: Tue Nov 14, 2023 12:35 am As far as Wall Paper is concerned, I looked it up. This is a common complaint with Ventura and Sonoma, and no one has a solution.

Other than SS/Ventura, I can't point to any other problem with the OpenCore interface. The problem with Firefox, not Chrome, not loading YouTube in Ventura only also points to something going on with Ventura, not OpenCore. I'm getting feeling that Ventura is half-baked.

I've come to the conclusion that Ventura is appropriate for Photoshop and nothing else.

Do you have any notion as to why SS and Ventura don't get along running in OpenCore?
SS is working with Open Core, it's not working with OCLP patched machines.

Best regards,
Goran
That makes sense; OCLP has to do some memory tweaks that are likely SS incompatible (that 0-address memory space thing again). OC in general shouldn't be an issue.
nandrews
Student Driver
Posts: 12
Joined: Wed May 03, 2023 8:42 pm

Re: SS will not run in Ventura (under OpenCore Legacy Patcher only)

Post by nandrews »

Thanks to a suggestion by kanjitalk755 and valiant build efforts by emendelson, we now have a non-JIT build of SheepShaver current, that runs without issues on two test systems running Ventura via OCLP.

While we will miss the JIT compiler, I believe this is a solid fix.

Thanks immensely to both of you.
nandrews
Student Driver
Posts: 12
Joined: Wed May 03, 2023 8:42 pm

Re: SS will not run in Ventura

Post by nandrews »

adespoton wrote: Thu Nov 23, 2023 11:16 pm
gorans wrote: Thu Nov 23, 2023 6:30 pm
trevorpsy wrote: Tue Nov 14, 2023 12:35 am As far as Wall Paper is concerned, I looked it up. This is a common complaint with Ventura and Sonoma, and no one has a solution.

Other than SS/Ventura, I can't point to any other problem with the OpenCore interface. The problem with Firefox, not Chrome, not loading YouTube in Ventura only also points to something going on with Ventura, not OpenCore. I'm getting feeling that Ventura is half-baked.

I've come to the conclusion that Ventura is appropriate for Photoshop and nothing else.

Do you have any notion as to why SS and Ventura don't get along running in OpenCore?
SS is working with Open Core, it's not working with OCLP patched machines.

Best regards,
Goran
That makes sense; OCLP has to do some memory tweaks that are likely SS incompatible (that 0-address memory space thing again). OC in general shouldn't be an issue.
Goran — this is interesting. I was not aware that OCLP does anything to memory mapping that persists once the Mach kernel has taken over.

Is this something we can address in the JIT compiler (like, just spitballing, test for the actual memory map and use a derived value, instead of assuming one)?

I am not aware of any other code that runs badly in Ventura/OCLP, including emulators and hypervisors. Qemu PPC, Fusion, and VirtualBox all work without issues, as does the galaxy of weird software I regularly use.
nandrews
Student Driver
Posts: 12
Joined: Wed May 03, 2023 8:42 pm

Re: SS will not run in Ventura

Post by nandrews »

I’m picking up here on a thread from the closed ticket on kanjitalk755’s github repo:
Your argument is convincing.

I think it's the terminology that's bothering me. I'm not sure it's a "bug" we're talking about or something about Ventura that isn't known to developers, because if it were they would have corrected it. Upgraded versions of OpenCore are coming out almost monthly and there's really talented, dedicated people working on it. (A labor of love, because their pay can't be very good.) They are fanatical about making sure every part of the operating system is working as it should. OpenCore is their hobby, and people tend be fanatical about their hobbies. I know that I am, even though I'll never make dime.

Also, why on earth is this a problem with SheepShaver only?

I just learned the the KDK installer in OpenCore has been upgraded so that a problem with Sonoma was corrected. After I install Sonoma, I'll see if SheepShaver runs.

I did try going to the OpenCore site and looking around for a quite awhile and found no way to email them. If you know of a way, let me know, and I'll get on it immediately.

Thanks for reading,

Trevor



> On Dec 4, 2023, at 8:59 PM, nmphoenix ***@***.***> wrote:
>
>
> Trevorpsy — that’s not all that OCLP does. As Apple moves ever farther away from broad Intel support, OCLP has to make more and more adjustments behind the scenes, to make an older machine appear like a newer one to the OS. Apparently this now includes remapping memory space, to allow Ventura to run on certain models, which is what broke Sheepshaver’s JIT compiler. I’m sure there is a way around this, but it will be up to the dev team to decide whether it’s worth the effort. At this point we have a Sheepshaver binary that works on Ventura with OCLP, at least on my two test platforms, and I consider the issue resolved. On Dec 4, 2023, at 10:18 PM, trevorpsy ***@***.***> wrote:
> Not convincing.
>
>
>
> All Opencore does is relax Apple's denial of my computer working with anything beyond Mohave.
>
>
>
> Also, why has Opencore gotten along with Catalina, Big Sur, and Monterey and is suddenly having problem with Ventura/Sheepshaver?
>
>
>
> Again, I think the problem is with Ventura breaking some arcane rule.
>
>
>
> > On Dec 4, 2023, at 7:49 PM, emendelson ***@***.***> wrote:
>
> >
>
> >
>
> > How do we know that it isn't a Ventura problem?
>
> >
>
> > viewtopic.php?p=77269#p77269 <viewtopic.php?p=77269#p77269>
It’s complicated. I’m starting to understand it a little bit but a lot is over my head. I’m not really a hardware guy.

SheepShaver uses the Kheperix emulator, internally, which is ancient and arcane. It began as a hypervisor, sort of, rather than an emulator — it ran PPC versions of the Classic Mac OS *on PPC machines* — and this led to certain shortcuts. “Some of the architectural decisions made as a result have persisted” — ClassicHasClass.

There is a longstanding issue with Kheperix and memory mapping. Again, it’s arcane. It “sits on a house of cards of janky memory mapping” — SegHaxx.

As far as I can tell, to run Kheperix (and thus SheepShaver) on 64-bit systems, you have to hard-code a specific starting memory address which the emulator can treat as memory block zero, which the classic Mac OS needs because it stores essential globals there.

This works when the system memory map is standard and predictable. However, OCLP seems to change that memory map just enough that SheepShaver’s code map fails, tanking kpx_cpu (Kheperix).

SegHaxx began to sort out these memory mapping issues in a 2021 fork (macemu-flatpack), which does have releases, but which has been dormant for a while now (it seems that some discussions occurred about merging those fixes into trunk but that doesn’t seem to have happened).

I’m going to test macemu-flatpack against OCLP on my buggier machine tomorrow. Perhaps that fork will offer a more elegant solution than simply disabling JIT.
nandrews
Student Driver
Posts: 12
Joined: Wed May 03, 2023 8:42 pm

Re: SS will not run in Ventura (under OpenCore Legacy Patcher only)

Post by nandrews »

This was my earlier post about this issue:

viewtopic.php?t=11898

This is emendelson's non-JIT build of kanjitalk755 SheepShaver current. It runs on my two test machines under Ventura/OCLP. Uploaded to my server if anybody else needs it.

http://www.absurdengineering.org/sheeps ... -noJIT.zip
Post Reply