Classic Mac - superjamie/lazyweb GitHub Wiki

Classic / Compact Macintosh Notes

This is a crash course in Compact Macintosh (Motorola 68000 CPU family) for people who never had anything to do with them.

I'm writing from the perspective of someone who grew up with DOS and Windows, though now I use Linux and have for almost 20 years.

Warning: I mostly ignored these systems until 2023 and have almost no idea what I'm talking about, so it's very likely I've got something wrong. Comments and corrections are very welcome. Find me at https://fosstodon.org/@suprjami

Hardware

Read the history of these from 128K to Mac II, but focus will be on the Mac Plus and Mac II because those are what Mini vMac emulates by default.

  • Mac Plus: 8MHz 68000, 1 MiB to 4 MiB RAM, 9" 512 x 384 black-and-white CRT, System 3.0 to 7.5.5
  • Mac II: 16 MHz 68020, 1 MiB to 8 MiB RAM, 13" or 14" 640x480 256-color CRT, System 4.1 to 7.5.5
    • In real life, you can use a "32-bit clean" ROM from a different model (IIci?) to get up to 128M RAM - imagine that in 1990!

Software - OS

Operating System 1.0 to 6.0.x

The operating system from 1.0 to 6.0 was called "System Software" and typically was not installed on a hard drive until maybe 6.0.x. The original Mac 128K and 512K didn't even have a hard drive in their original form (but you could get aftermarket ones). Instead, you'd boot the system from the OS floppy and then eject it, inserting another floppy to run an application.

It might seem weird to eject the operating system disk, but the "ROM" of the Mac was not a simple "BIOS" like we think of in a DOS computer. Depending on model, the ROM held a subset of the operating system API like GUI window drawing routines. This would be like Microsoft releasing their own computer and putting half of the Windows API in the BIOS.

Another way programs ran was to boot from their own floppy, which had a subset of the System Software on it. This is probably similar to a DOS boot disk which was prepared with FORMAT /S A: with its own CONFIG.SYS and AUTOEXEC.BAT and a game or application which ran off that bootdisk.

Operating System 7.0 / 7.1 / 7.5

These operating system versions were still called "System Software" and were the last version with support for the original 68k hardware with 7.5.5.

As of 7.6 the name changed to "Mac OS" and required newer "32-bit clean" 68k systems to run.

As far as I can tell, System 7 was always (or almost) installed on hard drives.

This brought several architectural changes to the OS such as virtual memory, "System Extensions" which are like drivers so you could install support for a specific thing, aliases which are like symlinks on Linux, drag-and-drop of documents onto applications.

The install/upgrade paths for these are:

  • 7.0: Install from System 7.0.1 floppies, apply System 7.0.1 Tune-Up 1.1.1
  • 7.1: Install from System 7.1 floppies, apply System 7.1 System Update 3.0
  • 7.5: Install from System 7.1 floppies, apply System 7.5.3 upgrade, apply System 7.5.5 upgrade
    OR Install from System 7.5.3 floppies (16 disks), apply System 7.5.5 upgrade
    OR Install from System 7.5.3 NetInstall using another disk image, apply System 7.5.5 upgrade

Which to Choose?

People seem to have very strong opinions about which is the best OS for which Classic Mac:

My interest is solely in emulators which let us run at unrealistically fast speeds with hardware combinations that didn't even exist in real life. System 7.0 and 7.1 don't support a lot of useful software. I don't really see a compelling reason to use anything except System 7.5.5 in an emulated system.

Where to Get?

You'll also need a ROM image, those are around the place:

How to Use?

The OS gives you a tutorial on first boot, do that to learn some basic usage and keyboard shortcuts.

To "eject" a disk, drag it to the trash can.

The "Command" key ⌘ is Alt in emulators.

The desktop is shared amongst all mounted disks, so if you have multiple disks mounted it's difficult to tell which disk owns which desktop folder. Don't store stuff on the desktop if this is confusing.

Emulators

There are two main emulators for 68k Macs, Mini vMac and Basilisk II.

These two have some similarities and some differences.

Mini vMac

This only emulates older 68k Macs and is available by default in two "variations", one which runs a Mac Plus and one which runs a Mac II:

(there's also Mac 128K but that's so limiting as to be useless to me so I don't consider it)

You'll also want to get the Blank Disk Images. On Linux you can just make a blank disk image with dd if=/dev/zero of=MyDisk.img bs=1M count=80 and vary the count depending on the size of the image.

The old Mac HFS file system can only store a maximum of 65536 files per filesystem, so don't create yourself a 4 GiB image and install everything on it. You're probably best to make a small "OS" image of about 100M and then confine future tinkering to additional hard drive images which you connect to the emulator as needed.

Mini vMac has no commandline options or configuration file. You can change some settings at runtime by holding the Ctrl key. If you want options applied permanently, you need to recompile it:

This is actually very easy if you have a C compiler already setup on Linux. My preferences are:

setup_t -t lx64 -m Plus -magnify 1 -speed a -bg 1 > setup-plus.sh
setup_t -t lx64 -m II -magnify 1 -speed a -bg 1 > setup-ii.sh

To emulate a Mac Plus you will need a Mac Plus ROM called vMac.ROM (case sensitive) in the same directory as the Mini vMac binary.

To emulate a Mac II you will need a Mac II ROM called MacII.ROM (case sensitive) in the same directory as the Mini vMac binary.

To start Mini vMac, launch the binary and the screen will open showing the "Sad Mac" icon, this means the Mac cannot find a disk to boot from. Drag a floppy disk image or hard disk image onto the emulator window. The emulator does some live ROM patching magic to make the disk appear as plugged into the system, and the ROM will boot from the first disk you install.

The OS installation process is to boot from the Install 1.img file, then once the installer is complaining it can't find a valid hard disk, drag your hard disk image onto the emulation window and the installer will find it.

Once you have an OS installed on a disk, you can call that file disk1.dsk and Mini vMac will try to boot from it first any time you start it.

On the Mini vMac Extra Software page you'll find these essentials:

  • ImportFl which is used to get files into the emulated system from the host. As far as I can tell, this hooks the disk mount routine and instead saves the "new imported disk" to a file on the emulated OS.
  • ExportFl which is used to get files out of the emulated system to the host. On Linux this makes a directory out wherever the emulator binary is.
  • binUnpk which is used to unpack software in .bin files, and you'll be thankful any time you find these

Mini vMac is best if you can get disk images, unfortunately those are rare. We'll come back to getting more applications after looking at the next emulator.

Basilisk II

Basilisk definitely seems to emulate a Mac IIci and a Quadra 900 (which can run OS 8.x).

It seems you can select between running "pre-32-bit" Macs with the Mac IIci option, then selecting the appropriate CPU, RAM size, and ROM file, so you could probably emulate a Plus or SE or something else this way.

There's also a lot of confusing advice online about what ROM image works best, including vague statements like "the Performa ROM" (there are 78 models of Performa).

In any case, you can try the advertised Mac IIci ROM and Quadra 900 ROM.

On Linux, you can get Basilisk II either as a Flatpak on Flathub, or as an AppImage as listed at:

If you are using the AppImage and the theming goes all wonky so you can't read button labels due to a clash of light/dark themes, launch the AppImage like:

APP_GTK_THEME=no ./BasiliskII-x86_64.AppImage

I found Basilisk to be less reliable than Mini vMac, it hangs a lot (Use Ctrl+Esc to quit) or just crashes.

There are many hard-to-follow tutorials about using Basilisk:

Create your hard disk image in the Basilisk II interface.

Installing an OS is slightly different from Mini vMac. You need to boot from the Disk Tools.img floppy disk (included in 7.0 and 7.1 downloads) to format your hard drive image before the Install 1.img installer will recognise the disk.

Basilisk doesn't have a way to mount floppy disk images at runtime (at least on Linux it doesn't, apparently you can on Windows) which is mildly annoying, however it does have a Unix Root feature which creates a fake hard disk inside the emulator, the contents of which are a directory on the host filesystem.

This is both very convenient and very inconvenient. It's a great way to get files into the emulated OS because you can just drag and drop them, but it's not a very good way to get files out of the OS. Which brings us to...

File Formats

Most Mac software you'll find is in one (or more) of these file formats:

  • bin - MacBinary
  • hqx - BinHex
  • sea - Self Expanding Archive
  • smi - Self-Mounting Image
  • sit - StuffIt Expander compressed file (the Mac version of zip files)

On DOS and other OSes we're used to associating a file with an application by its extension, like a .txt is a text file to open with the text editor, a .doc is a document to open with a word processor, a .png is an image to open with a graphics program, etc. Mac OS doesn't work that way.

Mac OS has a hidden set of "metadata" about a file, such as its type and what application it should be opened with (it also stores other stuff like icons, graphics, dialog windows, etc). This is called the file's "Resource Fork".

Unfortunately, only Mac's HFS and HFS+ filesystems have support for this metadata. There is no standard way to represent a Resource Fork to non-Mac systems with non-HFS filesystems, such as every other computer in existence.

So if you copy files out of the emulator using Mini vMac's ExportFl or Basilisk's Unix drive, you risk losing that metadata.

The solution is to put a file in one of the above container formats (bin/hqx) and name that container with the appropriate extension. So if you compress a Mac program into a BinHex file, then call the resulting file MyProgram.hqx. The vast majority of Mac software you download from the internet will be in one (or two, or more) of these formats. It's not incommon to download something like program.img.bin.sit which is a disk image, in a MacBinary file, compressed with StuffIt.

StuffIt Expander

This is the standard compression and decompression utility on the Mac, much like DOS and Windows have WinZip, WinRar, 7-Zip, etc.

Version compatiblity is as follows:

  • StuffIt 4.0 works on System 7.0
  • StuffIt 4.5 works on System 7.0 but requires a 640x480 screen, so black-and-white Macs are out (unless you fake the emulator resolution to 640x480)
  • StuffIt 5.5 requires System 7.1.1 or later, 68020 CPU, 8M RAM, and 640x480 screen, so you need a Mac II for this

There is also a common extension DropStuff with Expander Enhancer which helps if you want to make compressed files.

However, there is a problem.

An awful lot of Mac software you download from the internet was made with newer versions of StuffIt (presumably by people on OS8/OS9/OSX) which these older StuffIt Expander versions cannot read. You'll tell StuffIt 5.5 to uncompress something and you'll get either one lone file with no Resource Fork, or you'll get nothing.

As far as I can tell, the only way around this is... to emulate a newer Mac!

The SheepShaver emulator can emulate the PowerPC Macs require for such a thing, but I haven't gone that far down the rabbit hole yet.

Software

For software you can find which usually works, look around these sites:

Essentials

You'll definitely want these:

I also see these listed as essentials but I haven't had the need for them yet:

Once those are setup, can finally get into using the emulated computer and OS to do cool things.

Applications

  • MacWrite - was included by default with the first Mac 128K and was often the first program any Mac user ever tried
  • MacPaint - was also included with the first Mac 128K and if the owner didn't start with MacWrite they started with this instead
  • BBEdit - a very popular text editor, it seems version 4 or 5 are the most popular

Mac-only Games

There was a running joke in the 90s that Mac had no games, and it certainly had less than DOS/Windows (even C64/Amiga/Atari) and not very many good ones, but there were a few:

  • Glider - paper plane action puzzle game, initially a free hobby, grew into a commercial game
  • Dark Castle - platformer, uses WASD and mouse controls in 1986!
  • Systems Twilight - puzzle game by Andrew Plotkin

Mac-superior Games

There are even some games which were released on other platforms but are arguably better on the Mac:

  • ICOM MacVentures - all released on the Mac first
  • The Fool's Errand - puzzle game inspired by real-life treasure hunts like Masquerade, also made on the Mac first, then ported to DOS/Amiga which traded high resolution for more colours
  • The Manhole - famous puzzle game made with HyperCard, by the Millers who would go on to write Myst

Mac-first Games

Some games were later ported elsewhere, but released first on the Mac:

  • Myst - the famous flick-screen puzzle adventure started on the Mac, as a HyperCard stack
  • SimCity - I never expected it to look this great in black-and-white
  • Balance of Power and 1990 Edition - cold war geopolitical simulator by Chris Crawford
  • Exile: Escape from the Pit - fantastic RPG which I later played on Windows, remade (twice) as the modern Avernum series
  • Hidden Agenda - another political strategy, even ported to DOS in black-and-white

Mac-interesting Games

There are games we're probably more used to playing elsewhere which saw release on the Mac:

  • Space Quest 1, 2, 3 - I'm so used to these on DOS EGA, it's a real trip to see them in black-and-white
  • Loom - I always associated this game with being coloruful, again strange to see in black-and-white
  • Starflight - this great open-world sci-fi RPG was everywhere wasn't it?
  • Where in Europe is Carmen Sandiego? - I played a lot of this on DOS in CGA, higher res B&W is arguably better

More Research Required

These caught my eye as possibly interesting:

OS Tinkering

Mac OS is very customisable. If one has the programming skill it seems possible to change almost any aspect.

The components to do this were called "INITs" up to System 6, and "System Extensions" on System 7+.

There are also Control Panel Devices (aka "CDEVs") which add things into the system Control Panel.

You can get lots of ideas of what these are capable of from pre-installed OS images like these:

There were also silly "joke" system extensions, such as Enchanted Menus 88 which just opens the top-bar menus at a random location on the screen.

This and more are detailed in the books:

Developing on/for the Mac

Inside Macintosh

Apple published the Inside Macintosh series of books describing the OS API in detail:

Of particular interest is the Human Interface Guidelines book. Steve Jobs had a vision for how people should interact with computers. To help other developers get into the same mindset and steer all Mac applications to a common set of GUI idioms, this book explains how to lay out an application with fantastic diagrams, and even goes into detail on how to design for different languages, disabilities, to test software, and work with people evaluating your program. It's a fascinating book to flip through.

Macintosh Programmer's Workshop (MPW)

Apple wrote the OS and their programs in 68k assembly and Pascal at first, but later moved to C with the change to 32-bit and the PowerPC platform.

MPW seems to be what Apple used? It seems to have grown over time with their needs and was eventually replaced by CodeWarrior:

HyperCard

Many amateurs at home got a start by tinkering with HyperCard, which is an interesting combination of slideshow, database, hypertext, and scripting language. You'll find many adventure games written in HyperCard. As mentioned above, The Manhole was written in HyperCard which later resulted in Myst!

BASIC

BASIC was also popular around this time. Some of the original Macintosh team members developed MacBASIC, which not only implemented the programming language but allowed a BASIC API to control native system UI like windows and buttons:

Microsoft Basic for Mac was originally criticized for lacking support for the Macintosh Toolbox native UI, but this was resolved by MS Basic 3. That was combined with the compiler into Microsoft QuickBASIC for Mac:

C

Lightspeed C, which became THINK C then Symantec C, seems to have been the most popular at the time. It's definitely not like a traditional UNIX environment with Makefiles, but if you follow the manual you can compile a program linked with the OS libraries easily enough.

C support was later added to MPW (above), and another successful C environment was CodeWarrior:

If you want to write in C for the Mac today, the nicest tools seem to be the Retro68 GCC cross-compiler:

Pascal

I don't know much about Pascal so I'm just going to drop some links:

Go Forth and Mac!

Hopefully that's enough to get you started on emulating Classic Macs and exploring the unique software ecosystem.

Some YouTube channels with good videos about Macs are: