... with my old 9600 and "G4" for many years) Only left me get a virtual machine to mount the greatest Apple MacOS: 10.4.11 -tiger- within Yosemite. I was working many years (9) with 10.4.11 in my "G4 Dual"... and was the best OS of Apple... of course... sure. There are many mac ...

Well... then.... when.. do you believe that could be possible work (64 bits) with yosemite and SheepShaver Classic 9.2.2 ? I was working several years (1997-2002) with my old PowerPC 9600/G4 and classic 9.2.2. I have many files and docs in classic apps like Freehand ...

Well... then.... when.. do you believe that could be possible work (64 bits) with yosemite and SheepShaver Classic 9.2.2 ? I was working several years (1997-2002) with my old PowerPC 9600/G4 and classic 9.2.2. I have many files and docs in classic apps like Freehand ...

... only can run 9.0.4 version and this version is very limited for many apps, less icons, etc. Would be pleasant/genial if we could run 9.2.2 with Yosemite (10.10.3). So we could open we old files, docs, images .... and games. I believe that there are many people expert in C++ to improve the SheepShaver ...

... only can run 9.0.4 version and this version is very limited for many apps, less icons, etc. Would be pleasant/genial if we could run 9.2.2 with Yosemite (10.10.3). So we could open we old files, docs, images .... and games. I believe that there are many people expert in C++ to improve the SheepShaver ...

... know. Where would we be without your helpful responses?! By the way, for any remaining hesitating Mavericks users out there, I can only say the Yosemite upgrade has been - for me at least - one of the least disruptive (in terms of incompatible software) I have ever done. Most of my older apps ...

Strange. I cannot imagine the issue has anything to do with SheepShaver itself. Did you try to log-out and log-in again (which will restart the Dock)?

I upgraded to Yosemite today, and my initial experience with Sheepshaver is that it will NOT run from the Dock, even when removed from the Dock and replaced there, but it runs when directly started from its folder in Apps. It will ...

... partly from inertia, having started out with it, and having been used to OS 9, but mostly because the mouse cursor works better for me under Yosemite than it does with Basilisk II. The Basilisk cursor is actually okay on my Mid 2011 Mac mini, but not so much on my Late 2013 Retina 15" ...

I'd like to run M68k software in SheepShaver under OS X Yosemite that uses floating point instructions. When I run a little assembly language program that tests for the fpu, it reports that no coprocessor is present, and indeed floating point instructions ...

SheepShaver should launch if a compatible ROM file is in the same folder as the SheepShaver application and if that file is named exactly "Mac OS ROM". It does not need to be added in prefs to start with. Better start over after deleting the prefs file (script in the SheepShaver download) ...

I have exactly this problem – yet I have a (supposedly?) working New World ROM. Tried renaming the file and pointing directly to its path via SheepShaverPrefs, yet still not working.

I have OS X 10.10.3, Intel 64 bits (with 32 bits mode enabled for SheepShaver)

I increased the memory in the preferences to 2048 and saved and restarted Sheepsaver...Nothing happens. I messed up and I can't seem top recover. I had it working under Yosemite, but ClarisCad wanted more ram to save a file...

... BasiliskII reacts as if normal left-clicking was used and without the delay. This weird behavior of BasiliskII seems to exist in OSX 10.10 (Yosemite) only. What other lag issues do you notice, with which BasiliskII build and with which software? As I wrote above, performance depends on the ...

There should not be any speed issues related to screen size when in window mode. Running SheepShaver full screen will have some effect on cursor movements.

... builds by me, by Cat_7, and by vasi) and they all have the same problem here. You tried SheepShaver first without success. It still works fine in Yosemite. Maybe you could try again and start a topic in SheepShaver forum for help if needed. BTW: This is not "our" software. No regular ...

Ok, this was because I didn't add the ROM file inside the folder. A message in the terminal would have been nice because I just assumed something was broken. SheepShaver isn't having the same laggy cursor issue that I'm having in Basilisk II unless I increase the screen size to 800x600 then there ar...

Did you set up SheepShaver with needed additional files as described in our setup manual? SheepShaver will not run on its own. Specifically, when no compatible rom file with the prescribed file name is available, SheepShaver wil quit on launch. Link to the guide is in the download. Indeed, SheepShav...

Title says it all. Downloaded the link provided in the form for the latest version and get a crash before anything loads. Running the binary in the terminal just returns "Killed: 9" and I get the following output in the console which I don't think is related. The bundle wasn't code signed ...

The latest OSX configuration on which SheepShaver can be built is OSX 10.6.8 with Xcode 3.2.6. The resulting application will run in OSX 10.10 Yosemite, though only in 32-bit mode.

See also: http://www.emaculation.com/doku.php/com ... r_basilisk

I see sheepshaver won't run in 64-bit mode, but how does one build under Yosemite ? It's been a couple of OS X revs since I last built sheepshaver. The following leads to failure: ./configure --enable-sdl-vido --enable-sdl-audo --with-bincue --disable-jit --enable-sdl-framework ...

As of Yosemite, the full screen plist value is slightly different IIRC; I can't recall the change off-hand, but someone must have written about it by now. The full-screen plist value is still 4 in Yosemite; it hasn't changed; ...

As of Yosemite, the full screen plist value is slightly different IIRC; I can't recall the change off-hand, but someone must have written about it by now.

This no longer works, as of Yosemite, or at least I can't get it to. The menu bar is hidden, and an Applescript can tell System Events to tell SheepShaver to move the window, but the OS moves it right back.

... and TCP/IP control panels are set correctly for my network (these settings worked fine when Basilisk was running on my other Mac mini running Yosemite): http://i61.tinypic.com/xmv7yb.png http://i60.tinypic.com/1zzno21.png http://i61.tinypic.com/23w1e35.png http://i61.tinypic.com/555oas.png ...