SheepShaver MacOS Sonoma

[macman]

I just upgraded my 2022 MacStudio with Apple M1 Max silicon to Sonoma 14.0 and the latest build of SheepShaver 2.5 (build from 2023_08_10) is working fine. Not sure about printing since I never print except to a PS file. But so far so good.

[jonandali]

Just done same thing on new mac book air 15" with Sheepshaver 2.5 on sonoma. I _can_ get my set ups to boot up (System 8.5) but they hang when I start up in full screen once I get to desktop of applescripts start running. I can start up windowed then toggle to full screen and all is well but was hoping ultimately to get it working in fullscreen right off the bat. Also I cannot access settings -just greyed out in the sheepshaver dropdown. Admitedly I've just jumped from an intel mac running Mojave so even getting used to the fact the prefs tool no longer works, but any pointers gratefully received as to why any of these things I am mentioning are happening. Thanks

[Ronald P. Regensburg]

Just done same thing on new mac book air 15" with Sheepshaver 2.5 on sonoma.

Note that SheepShaver versions are identified by the build date, not by the version number. All 30+ builds since 2018 have version number 2.5.

Also I cannot access settings -just greyed out in the sheepshaver dropdown.

Which SheepShaver build do you use? This issue was first seen in macOS 13 (Ventura) when Apple decided to rename the "Preferences" menu item to "Settings". It was solved in the December 2022 SheepShaver build. Best use the latest build, now the 10 August 2023 build.

[Ronald P. Regensburg]

I _can_ get my set ups to boot up (System 8.5) but they hang when I start up in full screen once I get to desktop of applescripts start running.

I am not sure I understand. SheepShaver should run fine when launched in full-screen mode. Do you have AppleScripts being launched at startup?

[jonandali]

Thanks for your replies, much appreciated. I will look at what I have done so far more closely later this week: I have only been configuring my new macbook for a day. Anyway, re: sheepshaver, the build I downloaded is, 'SheepShaver_universal_20230810.zip' so am guessing it's the latest build. I took the new app and replaced the old one with it but left everything else as was. What happens when I open this new version, is sheepshaver starts booting System 8.5 with a screen size of 640x480 and when it reaches its desktop an applescript automatically opens a Macromedia Director projector. If I toggle out of fullscreen mode while system 8.5 is booting then everything starts up ok albeit slower than previously. However if I leave it in fullscreen mode it gets as far as trying to open the Director projector and then hangs until a spinning beach ball appears signaling that sheepshaver is no longer responding. I have waited a minute or so at this point but have always ended by forcing sheepshaver to quit. Also, the settings are greyed out in sheepshaver so cannot access them in drop down menu. My first thoughts (I am no expert here) is that maybe there's a permissions issue (not sure why works when not starting up fullscreen though) and also perhaps I need to edit the prefs manually to be more friendly to new macos (Sonora) running the emulator. However I need to go look at what values do what when editing the prefs manually, which I will try and work out later. However if anything else occurs to you please do suggest away, and thanks again.

[Ronald P. Regensburg]

I suppose you have this applescript (or an alias of the script) in the Startup Items folder in the 8.5 System Folder to have it launch at startup. If you remove it there, can you then run the script after startup in full-screen mode is completed?

The Settings item in SheepShaver menu being greyed out with my latest SheepShaver build is strange. Are you sure it is the only build on your machine and an older build is not launched accidentally? I cannot test it myself in Sanoma because I always wait till after at least the first update before I install a new macOS version. Do others see a greyed "Settings" item in SheepShaver menu in Sanoma?

If you have doubts about the settings in your prefs file, you can post its content here so we can judge your settings. Open the file in a text editor and copy and paste all content here in your reply.

[jonandali]

Firstly thanks for your reply again, and thank you for building Sheepshaver to run in these current OS's: it's very greatly appreciated. I went through what you said and can report I had mistakenly been using the 2018 build and everything is working fine with the most recent one. Apologies for taking up time here but thank you for going through this with me: everything is working, which is AMAZING!!

[mhmyers]

I was using Sheepshaver in Mojave perfectly. I just upgraded to a new MacBook Air with Sonoma. I replaced the app with one created 2/28/2024, and replaced the scripts folder.
The app opens and seems to run but the cursor is very jerky and I am getting a lot of errors ("Syntax error- an array was expected")

Is there something I missed?

Thank you

[Ronald P. Regensburg]

I do not know what could be wrong. Did you do a regular user migration from from the old Mac to the new one?

Please post here the content of your prefs file.
You can open the prefs file with the script "Edit prefs file". Select all content and paste it here in your reply.

[mhmyers]

Thank you for the reply.
I used Migration Assistant to transfer to the new mac. But when things got messed up in SS, I recopied the old folder to the new Mac and replaced the app and the scripts folder.
Here is the prefs file:
cdrom /dev/poll/cdrom
cdrom /dev/poll/cdrom
cdrom /dev/poll/cdrom
cdrom /dev/poll/cdrom
cdrom /dev/poll/cdrom
cdrom /dev/poll/cdrom
cdrom /dev/poll/cdrom
cdrom /dev/poll/cdrom
cdrom /dev/poll/cdrom
cdrom Mac OS 9.dmg
extfs
screen win/1280/1060
windowmodes 0
screenmodes 0
seriala /dev/cu.Bluetooth-Incoming-Port
serialb /dev/null
rom Mac OS ROM
bootdrive 0
bootdriver 0
ramsize 134217728
frameskip 8
gfxaccel true
nocdrom false
nonet false
nosound false
nogui false
noclipconversion false
ignoresegv true
ignoreillegal true
jit false
jit68k false
keyboardtype 5
hardcursor false
hotkey 0
scale_nearest false
scale_integer false
cpuclock 0
yearofs 0
dayofs 0
mag_rate 0
swap_opt_cmd false
sound_buffer 0
name_encoding 0
init_grab false
ether
keycodes false
keycodefile
mousewheelmode 1
mousewheellines 3
dsp /dev/dsp
mixer /dev/mixer
idlewait true

[mhmyers]

also for comparison, here is the prefs file from the old mac that runs properly:

disk /Users/mhmyers/SS/Mac OS 9.dmg
disk /Users/mhmyers/SS/Mac OS 8.6.dmg
disk /Users/mhmyers/SS/Mac OS 7.6.dmg
cdrom /dev/disk2
extfs /
screen win/1024/768
windowmodes 0
screenmodes 0
seriala <none>
serialb <none>
rom /Users/mhmyers/SS/ROM
bootdrive 0
bootdriver 0
ramsize 268435456
frameskip 1
gfxaccel false
nocdrom false
nonet false
nosound false
nogui false
noclipconversion false
ignoresegv false
jit true
jit68k false
keyboardtype 5
ether slirp
keycodes true
keycodefile /Users/mhmyers/SS/BasiliskII_keycodes
mousewheelmode 1
mousewheellines 3
dsp /dev/dsp
mixer /dev/mixer
ignoresegv false
idlewait true

[mhmyers]

Perhaps I fixed it partially.
I changed the refresh rate in the settings to 60 instead of 7.5 and the cursor is smooth now, however some things still don't run was they used to.

[Ronald P. Regensburg]

Many settings are not right, your prefs file looks really weird. I cannot imagine how this could have happened. The new SheepShaver build will add a couple of new default settings, but much more changed. Also in the old prefs file some settings are not as they should have been and not as our setup guide advises. I have to go now, but I will send you a corrected content of what your prefs file should look like later. You can then copy that and paste it to your prefs file.

[mhmyers]

Thank you, looking forward

[Ronald P. Regensburg]

This prefs content assumes that you have your "SS" folder in the same location as on your old Mac: /Users/mhmyers/SS/ and that the content of that folder is also the same as before.

Select all lines (click SELECT ALL), and copy. Open your prefs file with the Edit prefs file script, select all content, paste the copied lines, save and close.

I do not know how old your keycodes file is, maybe you need to replace it with the latest one. See SheepShaver for MacOSX downloads: viewtopic.php?t=7360

Code: Select all

disk /Users/mhmyers/SS/Mac OS 9.dmg
disk /Users/mhmyers/SS/Mac OS 8.6.dmg
disk /Users/mhmyers/SS/Mac OS 7.6.dmg
cdrom /dev/poll/cdrom
extfs /
screen win/1024/768
windowmodes 0
screenmodes 0
seriala 
serialb 
rom /Users/mhmyers/SS/ROM
bootdrive 0
bootdriver 0
ramsize 268435456
frameskip 0
gfxaccel true
nocdrom false
nonet false
nosound false
nogui false
noclipconversion false
ignoresegv true
ignoreillegal false
jit true
jit68k false
keyboardtype 5
hardcursor false
hotkey 0
scale_nearest false
scale_integer false
cpuclock 0
yearofs 0
dayofs 0
mag_rate 0
swap_opt_cmd false
sound_buffer 0
name_encoding 0
init_grab false
ether slirp
keycodes true
keycodefile /Users/mhmyers/SS/BasiliskII_keycodes
mousewheelmode 1
mousewheellines 3
dsp /dev/dsp
mixer /dev/mixer
idlewait true

[mhmyers]

Thanks so much. Everything works now. I also replaced the key codes file and changed the prefs to reflect that.