Ronald, I am trying to move SS V2.4 which is running on my 2010 MacBook Pro running 10.6.8 over to my sons 2009 27" iMac running 10.10.1 I copied all my files over and set the prefs, but SheepShaver blows up with the following messages in the Console Log: 12/20/14 8:38:58.851 PM SheepShaver[136...

better use this in terminal
Terminal might not start in the home directory (depending on it's settings)

Hm, I see. Indeed, I did not understand your description. SheepShaver does not run in 64-bit mode in Yosemite, but then it does not run at all so that is a different issue. Maybe the NVRAM file got corrupted. You can remove it with the "Zap PRAM" script that is ...

Sorry, I guess I didn't word that as clearly as I'd planned. SheepShaver won't launch any further than the blank window when I change the window size in the SheepShaver preferences to anything besides 640x480. So, for example, it wouldn't even get to the flashing disk icon if an operating system was...

The screen resolution setting in Monitors control panel in the installed MacOS may have been reset to 640x480. After choosing a setting in SheepShaver preferences and subsequently quitting and again starting SheepShaver, set the resolution in Monitors control panel accordingly.

... to figure this out for awhile and thought I'd see if anyone here could help. I was using SheepShaver fine under Mavericks, but after updating to Yosemite, the only window size it will open with is 640x480. As soon as I change it from that, it starts to open with the larger window, but then hangs ...

I do not know if the command-button issue and 32-bit vs 64-bit mode could be related. In Yosemite SheepShaver will not run in 64-bit mode, so you need to run the SheepShaver application in 32-bit mode. That does not affect OSX. SheepShaver will open in 32-bit mode by ...

Yes, it works under Yosemite. Just follow the guide slowly and very carefully. Print it out and check off each step as you do it.

SheepShaver Version: 2.4 (2014-02-01) Here are the prefs, if they help at all: Setup: Boot From Any RAM size 1024MB Audio/Video: Video Type Window Refresh Dynamic Width 1280 Height 960 QuickDraw Enabled Misc: Enable JIT Compiler Allow Emulated CPU to Idle Ignore Illegal Memory Accesses (I have tried...

I've looked at the SheepShaver setup and don't really understand much of what is written. It's like reading a foreign language.

Also, will it work on Yosemite? I've seen other posts on here saying that it doesn't work on Yosemite.

Hi, I am a clueless dummy when it comes to computer stuff. All I know is that I want to play Tomb Raider III on my 10.10.1 (Yosemite) Macbook and I found a website that allows me to download it and play it via SheepShaver. All I know about emulators is that they let you run outdated ...

Following your instructions, I built DSumorok's BII under Yosemite. As far as I can tell, it requires XQuartz to be installed and runs XQuartz when it starts up. The version I built under Snow Leopard (following the instructions in the wiki) doesn't seem ...

I should have found those instructions myself - thank you. I'm updating my ports right now and will build under Yosemite.

Is there any hope that we will be able to build SheepShaver the same way?

... with programmer skills have added features and fixed bugs. We will have to wait till (and if) someone will do something about the 64-bit issue in Yosemite.

It's not Yosemite, for certain; I tried with a copy of the same image in Snow Leopard, and no love there either. I guess I'm going to have to reinstall OS 9 and start over.

Hi, Dan Sumorok recently provided a patch to run Basilisk 64 bit in Yosemite. Yesterday I built that code with GCC 4.8 in Yosemite, so no need for Snow Leopard. You need the latest Xcode, Command line tools, XQuartz, and macports for the GNU automake and autogen ...

are you going to retool version so it will run in 64 bit mode? thx again

Make sure you have a compatible rom file, old world rom or new world rom depending on the MacOS version you want to use in SheepShaver. If SheepShaver is set to open in 32-bit mode and if you have a compatible rom file in the same folder with SheepShaver and that rom file is named exactly Mac OS ROM...

no luck everything is as you said started from ground up mac os rom. shared folder on desktop, new copies of os rom and my "new disk" and sheep shaver

Yes, I was just checking. Indeed, this code seems specific to dsumorok builds.
Too bad.

Best,
Cat_7

Cat_7 wrote:The fix is here: https://github.com/dsumorok/macemu/comm ... 2b5b979d31

In the current macemu source there is no such code in BasiliskII/src/Unix/configure.ac nor in SheepShaver/src/Unix/configure.ac. No code to apply this fix to.

In a different topic about issues with SheepShaver in Yosemite is noted that internet access works fine there with slirp networking. So the issue is apparently not related to Yosemite as such. http://www.emaculation.com/forum/viewtopic.php?p=49151#p49151 ...

I'm not having any problems with slirp for Internet, so I'm not sure what's causing the other user's issue. That rules out Yosemite per se as the cause of that issue. I'll post a note in that topic. Unchecked 32 Bit mode. Command button issue still persists in 64 bit mode, You unchecked ...

... might set up a Mavericks system to check for differences. Unchecked 32 Bit mode. Command button issue still persists in 64 bit mode, so no change. Yosemite handles the GUI differently IIRC, so they probably broke something in the way keys work. That's only a guess though. Update: Another discovery ...

How did you upgrade to Yosemite? Did you do the upgrade in place on an existing system? Did you do a clean install and migrated using the Migration Assistant? Or did you manually copy files over from the old system to the new one? If ...