Page 1 of 1

Another Crash-On-Startup: OSX 10.10, Various Configs

Posted: Sat Jun 17, 2017 1:38 am
by jpodolski
So I've been plagued by startup crashes just as many others have here, and I'm at a loss so I'm wondering if any of you can help me out. Some quick specs,

Yosemite 10.10.5
15" Retina MBP, Early 2013

I have tried both the most recent release of SheepShaver, as well as the old stable release recommended for odd PPC issues as suggested in the setup guide (even though my processor is Intel...I'm desperate). I've tried pretty much every ROM, disk image, CD, or anything and it seems to have little effect on the issue.

Here's what I have been able to do. Initially, SheepShaver did not start at all, and I quickly found out that was because I was not using the correct ROM. Then, once I started using the appropriate images, I get a grey window to open for half a second, then shut. I cannot interact with SheepShaver at all during this time. Now just recently, due to some voodoo, SheepShaver started, launched a fullscreen "fade to black", then went back to a desktop view but kept a window-sized black rectangle in the top-left of my screen for about 5-10 seconds, then crashed. When this would happen, I wouldn't be able to do much, no key commands, dock, or menu interaction. However, when this happened, I would get a "SheepShaver has quit unexpectedly" message, which I never did before. While this seemed like progress, it stopped happening and I have not been able to recreate it. I believe it was just from testing fullscreen settings, as the computer behaved as though it was hung in a fullscreen mode (but with a scaled resolution of the "black box").

Now, I'm fairly certain I'm not missing something stupid, but you never know. Here is what I have already tried, troubleshooting-wise
  • Enabled 32-bit only for Sheepshaver.
  • Made sure every ROM was named exactly "Mac OS ROM" with no hidden extensions
  • Configured settings using the external preferences manager
  • Made sure that illegal mem requests and actions were allowed
  • Created a .sheepvm configuration and attempted to launch it from the SheepShaverLauncher, as well as standalone
  • Full system restart
  • Wiping settings and PRAM and starting from scratch
  • Disabling Ubersicht, and Soundflower, and disconnecting external monitor
  • Disabling SIMBL and unchecking QuickDraw Acceleration due to their presence in the console after a failed launch
Here's my current settings file:

Code: Select all

disk /Users/jeff/Desktop/SheepShaver/OS9.dsk
extfs /Users/jeff/Desktop/SheepShaver/Shared
screen win/800/600
windowmodes 0
screenmodes 0
seriala /dev/cu.Bluetooth-Modem
serialb /dev/null
rom /Users/jeff/Desktop/SheepShaver/Mac OS ROM
bootdrive 0
bootdriver 0
ramsize 67108864
frameskip 2
gfxaccel true
nocdrom false
nonet false
nosound false
nogui false
noclipconversion false
ignoresegv true
jit true
jit68k false
keyboardtype 5
ether 
keycodes false
keycodefile 
mousewheelmode 1
mousewheellines 3
dsp /dev/dsp
mixer /dev/mixer
ignoresegv true
idlewait true
Attached are snapshots of the console after different failed attempts
https://imgur.com/a/d2GSD

Also, here are the logs from the Console
https://drive.google.com/drive/folders/ ... sp=sharing

Hope this helps! I've been struggling for a while and combing the forums here for any help, but I'm pretty stuck. Thanks all for any help,

-Jeff

Re: Another Crash-On-Startup: OSX 10.10, Various Configs

Posted: Sat Jun 17, 2017 10:30 am
by Ronald P. Regensburg
- Your prefs settings seem OK.

- I would always start with window mode and try full-screen mode later when everything else is working as it should.

- A RAM setting of 64MB should work, but for running OS9 I would prefer 128MB or 256MB.

- You do not need to worry about the warning that SheepShaver uses the deprecated QuickDraw. That is a 'normal' message to warn developers that QuickDraw will be unavailable in a future OSX/macOS version. (SheepShaver still runs in macOS 10.12 and, according to some, also still in macOS 10.13, so QuickDraw is still available there.)

- Some of the logs seem to indicate that SheepShaver cannot use memory that it wants to use. SheepShaver uses memory in a way it should not. It occupies fixed places in memory instead of looking for memory that is free. Some software that is loaded before SheepShaver may occupy the places SheepShaver wants to use. Or you may use some kind of security software, like anti-malware software, that prevents the way SheepShaver uses memory.

- You have renamed the ROM file correctly to "Mac OS ROM", but you do not mention which ROM file you use and where you got that file.

- You seem to use a pre-installed OS9 system. Which one and where did you get it?

- After several crashes, that OS9 volume may be now corrupted. Use a fresh copy.

- The issue may be related to the retina screen. Does Finder Info for SheepShaver show a "Open in Low Resolution" box. Does it make a difference for launching SheepShaver when that box is checked or not?

Re: Another Crash-On-Startup: OSX 10.10, Various Configs

Posted: Sat Jun 17, 2017 5:38 pm
by jpodolski
I kept prefs where they're at, ran 256MB in windowed, quickdraw enabled, with a freshly downloaded ROM from RedundantRobot and all other applications closed, and I'm still getting the crash. I don't have any antivirus or additional security running in the background either. Oh, and low-res mode is checked by default always. Any ideas? I can attach another console log if you'd like. Thank you for the detailed response, I appreciate it.

Re: Another Crash-On-Startup: OSX 10.10, Various Configs

Posted: Sat Jun 17, 2017 7:21 pm
by Ronald P. Regensburg
jpodolski wrote:with a freshly downloaded ROM from RedundantRobot
Did you also use a fresh copy of the OS9 image? The ROM file will not change when SheepShaver crashes, but a crash may cause the startup volume's file system to get corrupted.

Also delete the NVRAM file after a crash and before you launch SheepShaver again. That file can also get corrupted.
all other applications closed,
Did you close running applications or did you not launch them at or after startup/login? Later OSX versions will often not release memory when applications are closed.
Oh, and low-res mode is checked by default always.
How does SheepShaver behave when that option in unchecked?

BTW 1: Do you use additional monitors connected to your MBP?

BTW 2: Does you MBP have memory installed that was not installed or provided by Apple?

Re: Another Crash-On-Startup: OSX 10.10, Various Configs

Posted: Sat Jun 17, 2017 10:43 pm
by jpodolski
Well I thought I didn't miss anything stupid, but that's usually never the case...

I wasn't using the correct ROM from RedundantRobot, I am now using the New World PPC ROM and am able to get SheepShaver running! Installing OS9 as we speak. Thank you though for all of your help, I appreciate you helping all of us with our roadblocks one by one on the forums :oops: I initally just wanted to get SheepShaver running to play some old games, but this whole process may have sparked an emulation obsession! I'll be around on the forums once I get some more experience, thanks again for all the help

-Jeff