Mac OS 9 installation options: "Update Apple Hard Disk Drivers" must be unchecked for SheepShaverĪs far as "Customize" is concerned, I pretty much selected everything except Speech-related features. More importantly, the "Update Apple Hard Disk Drivers" checkbox in the "Options" screen accessible via the "Options." button needs to be unchecked (cleared) for successful SheepShaver installation SheepShaver hangs if this button is checked. It appears from the literature around the internet that "Mac OS Extended" is actually a journaling file system with better performance for normal use.
I decided to initialize the two disks with " Mac OS Extended" file system instead of the default "Mac OS Standard". Mac OS 9 Installation CD Boot in SheepShaverĪs expected for new disks, the installer asks to initialize them. It is much easier to directly edit ~/.sheepshaver_prefs instead of having to deal with a GUI. On examining ~/.sheepshaver_prefs I found a time-saving trick - setting "nogui" to "true" does not launch the heavy graphical configuration tool first but boots up the Mac OS 9 virtual machine directly. It then launches the virtual Power Macintosh and boots from the CD image. When the "Start" button is clicked, SheepShaver saves the configuration out to a dotted (hidden) text file called ".sheepshaver_prefs" in the home directory, i.e. SheepShaver Mac OS 9 JIT Compiler configuration I used a port on a VDE (Virtual Distributed Ethernet) switch already configured and used by my DECnet nodes
SheepShaver Mac OS 9 Serial Ports and Network Adapter configuration SheepShaver Mac OS 9 Keyboard and Mouse configuration SheepShaver Mac OS 9 Graphics and Sound configuration SheepShaver Mac OS 9 Disk Volume and Shared Directory configuration
Here is a series of pictures of the options I configured in each tab:
It simplifies transfer of files between Ubuntu host and Mac OS 9 virtual machines guest anything copied into "shared" shows up in the "Unix" drive on Mac OS desktop though they cannot be executed directly from there, requiring me to copy executable installers from "Unix" to a local place on Mac OS first.įinally I fired up SheepShaver, added the boot disk image, created two disk drives of 250 MB each, disabled sound (I do not want audio!), set the network interface and launched the emulated PowerMac G4. This directory is configured to be the "Unix Root" on SheepShaver and shows up as the drive "Unix" on the virtual Mac desktop. I created a subdirectory called "shared" to share files between the Ubuntu host and SheepShaver's Mac desktop. I placed both these items in the same directory as the SheepShaver binary.
There are pointers to where they can be obtained from at " Setting up SheepShaver for Mac OS X". I then looked around the internet to locate a "New World" ROM ( newworld86.rom) and a Mac OS 9 bootable installer image ( Mac OS 9.toast). I created a directory ~/n/ and copied over the SheepShaver binary from the build location ( ~/sheepshaver.build/macemu/SheepShaver/src/Unix/SheepShaver). The following script installs the sheep_net.ko kernel module and creates the /dev/sheep_net network device with the right ownership: Once the main SheepShaver program has been built, the following script builds the sheep_net.ko kernel module.
" Inside Macintosh: Networking" is a great book. Fortunately, there is still enough reading material out on the 'net to get a feel for it. I had zero experience with AppleTalk networking. However, my objective here was to stay away from IP completely, and focus on pure AppleTalk. Interoperability with TCP/IP was introduced as far back as 1988 with MacTCP and later MacIP ( Wikipedia) which basically piggybacked IP over AppleTalk.
Despite phenomenal rise of the Internet Protocol (TCP/IP), AppleTalk was supported all the way to the 2009 release of Mac OS X Snow Leopard.