All is fine again. So, what are the constraints in changing the Prefs? I feel now that I just cannot mess them at all for fear of causing me to have re-config everything.

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

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.

Quote:

Different matter but perhaps related printing is not working in os8.3

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.

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:

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:

"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?

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.

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.

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?