[Edit: Deleted message that became irrelevant before I posted it.]

Well, normally there is no need to fear changing preferences settings as long as you do not do something stupid (sorry ) like entering a negative value for ram size.

Apparently you still had a (different) problem after correcting the ram size setting (this time a floppy icon with question mark). Do you know why SheepShaver could not find the system volume then?

If you cannot access preferences settings in SheepShaver itself, like when you are in full-screen mode or when SheepShaver keeps crashing at launch, you can use the stand-alone prefs editor (also mentioned in the setup guide). The stand-alone editor is older, has a slightly different interface, and does not have all the settings that the built-in editor has, but it can help to get out of such situations.
http://www.xs4all.nl/~ronaldpr/sheepsha ... rPrefs.zip

Can someone review this sometimes my unix disk does not show up on mac desktop is something wrong? Will usually show up after couple restarts of sheepshaver. Different matter but perhaps related printing is not working in os8.3

disk New.dsk
disk sheepshared/I386/_DEFAULT.PI_
disk macos9
cdrom /dev/poll/cdrom
extfs /Users/precision/Desktop/
screen win/1024/768
windowmodes 0
screenmodes 0
seriala /dev/cu.Bluetooth-Modem
serialb /dev/null
rom Mac OS ROM
bootdrive 0
bootdriver 0
ramsize 536870912
frameskip 8
gfxaccel true
nocdrom false
nonet false
nosound false
nogui false
noclipconversion false
ignoresegv false
ignoreillegal false
jit true
jit68k false
keyboardtype 5
ether
keycodes false
keycodefile
mousewheelmode 1
mousewheellines 3
dsp /dev/dsp
mixer /dev/mixer
ignoresegv false
idlewait true

From your posts in other topics I understand that you run SheepShaver in OSX 10.8, Mountain Lion, now possibly 10.8.3. Better include such information next time.


Are you referring to OSX 10.8.3? All printing options as described in the printing guide work fine here in OSX 10.8.3, without the issues you describe in the other topic. (To be continued in that other topic.)


Comments on your settings:

- Is macos9 a install disk image and did you install MacOS 9 onto "New.dsk"?

- Weird path and image file name for your second disk, but you may have a reason for that.

- Better do not use your Desktop as shared folder (Unix Root). The setup guide advises to create a separate folder. You can create a folder for that purpose on you desktop if you wish.

- Personally I would set the frame rate to a higher value. On a machine that can run Mountain Lion a refresh rate "Dynamic" would be fine.

- Better enable "Ignore Illegal Memory Accesses".

I just wanted to post some information for compiling SheepShaver and BasiliskII on FreeBSD 10.x with clang. It was driving me nuts but after bouncing some ideas off another bsd junkie I finally got it to compile and run.

For SheepShaver, after you cd to the src/Unix directory and run autogen.sh you need to re-run the configure script like this:

./configure --enable-addressing=direct

This will get rid of the error about mapping global memory invalid argument. I left the rest of the default values. Also you can not do the --disable-vosf option like some of the other guides say, SheepShaver will crash every time it starts the PPC emulation.

Now for BasiliskII, after you run the autogen.sh then you must re-run the configure script as such:

./configure --enable-sdl-video --enable-sdl-audio --enable-jit-compiler

If you get an error after you configure and click 'start', then you should try adding --disable-threads to the configure line. Don't forget to make sure you have the sdl1.2 libs.

And that is that, I hope this information helps someone running FreeBSD. I haven't had many crashes with these configures and I don't have to run the program as root.

Enjoy.

Thanks! This line:
./configure --enable-addressing=direct
should be useful for other OSes when compiling using CLANG too. That's a headache that has been preventing compilation on many platforms.

With this reconfiguration, will SheepShaver compile, for example, on OS X 10.7+?

Hi,

I just got SheepShaver working:) I'm using a 2009 MacBook with OSX 10.9.5. I used a CD disk image instead of the real install CD. I got the boot ROM and the MacOS9 boot image from RandomRobot. I used this YouTube video as a walk through:

https://www.youtube.com/watch?v=Qqgw4z_r2sE

But when I launched SheepShaver, this part didn't happen:

"During startup, the system will encounter the newly created volume and offer to initialize it"

SO I have a volume titled Unix and another titled OS9 but not the third one titled MacOS9HD.

I take it that this is an issue because my system doesn't have a hard drive now:(

My one thought is that I didn't lock the CD disk image (in its "get info" window) before I installed it—the video instructed against following that part of the SheepShaver instructions.

Without having locked the CD disk image, would it mount in OSX? Is that my problem?

Should I just uninstall and start again? Or is there a way I can initialize the volume at this stage?

If what I'm saying makes sense, could someone please help me understand why having the disk image mount in OSX prevented me from getting that prompt—the one asking if I wanted to initialize the newly created volume?

Thanks for your help and for having such an awesome community!

Start over and follow the instructions exactly and in every detail. If you follow the instructions exactly, they will work correctly.

Hi,

You can fix this issue without re-installing. As you have SheepShaver running, you can start the preferences editor.
On the volumes tab, create a new volume of 1000Mb and the desired name.
After it is created, you will see it in the Volumes list. Close the preferences editor, shut down Mac OS and restart SheepShaver. The new volume will appear with the question to initialize it.

Best,
Cat_7

Note that the redundant robot OS9 boot image is a (limited) installed system, not an install CD image. It should not be locked in the Finder as an install CD image should be.

Thank you!

I'm using SheepShaver for my doctoral research on the history of software.

Just got a file from 1999 running after thinking about it for years.

Your help means a lot.

Sincerely,

Will

Let us know if you need any first-hand experts on software history

I just got OS X 10.0.4 working -- ended up getting a Mini G4, which handles the "missing operating systems" we can't emulate under a modern computer. That means I can now run all Apple-related software from 1978 through 2015! I haven't tried the Public Beta or 9.1/9.2 yet, but I've got 10.5.8PPC running too

If I ever get some of that imaginary time to tinker, I'm thinking of running up the same image on SS and the Mini to figure out where some emulation is breaking and what the responses should be. When all else fails, brute force it

[edit] Grr... the Mini won't actually *boot* off of OS 9, nor will it boot off of 10.0 or 10PB. Too new I guess It's a "Mac mini PowerMac10,1 PowerPC G4 (1.2) with boot ROM 4.8.9f1." Someone will have to attempt this with older hardware if we're going to do it at all.

I've attempted to follow the Installation Guide as directed, getting all the way to the point where I am directed to start the SheepShaverGUI. Initially, the GUI did not seem to be able to find the libg****.dll files, so I copied them to the syswow64 and system32 directories. Then I get the following error message:

"The application was unable to start correctly (0xc000007b). Click OK to close the application."

I have had this issue with both SheepShaver and Basilisk II. I am currently on a 64bit Windows 10 system (Toshiba laptop) so I would love some guidance as to where to start fixing the issue.

My suspicion is the installation of the gtk setup. Any thoughts?

Thanks!

James

Very frustrated. Cannot get SheepshaverGUI to start at all. Continue to get error message as mentioned before. I've tried installing and reinstalling the GTK+ 2 a few times, and so far, no luck. Running 64bit Windows 10. Please, any thoughts?

James

I'd recommend doing it without the GUI; just edit the text file manually instead. There are lots of sample files on here to guide in the understanding of how they work.

In the Mac OS X setup guide, the link for QuickTime 4.1.2 is dead.

The oldest version of QuickTime for the Mac on Apple's web site now appears to be 7.6. I've spent the past couple of hours trying to find version 4.1.2 on the web, to no avail.

Can any of you suggest where to find the QuickTime 4.1.2 Installer?

If it is not available online, would some kind soul be willing to post it?

Sigh. It only just occurred to me, after beating my head for an hour or two against useless Google and DuckDuckGo, to check out the splendid Macintosh Garden.

QuickTime 4.1.2 is available at this URL:

http://macintoshgarden.org/apps/quicktime-4

Thanks. I replaced the link in the setup guide.