How Mac OS 9 Installers Managed System Extensions

During the classic Mac OS era, installing software was fundamentally different from modern operating systems, relying heavily on extensions—small code fragments that modified system behavior at boot. This article explains how third-party software installers in Mac OS 9 automatically placed extensions into the System Folder, highlighting the reliance on specialized installer engines, Mac OS APIs like the Folder Manager, resource fork inspection, and conflict resolution mechanisms.

The Role of Installer Engines

Most software developers in the Mac OS 9 era did not write their own custom deployment tools from scratch. Instead, they relied on standardized commercial installer engines, most notably MindVision’s Installer VISE and Aladdin Systems’ InstallerMaker. These engines abstracted the complexities of Mac OS 9's file system, providing predefined scripts and actions that knew precisely how to handle the fragile environment of the classic System Folder.

Dynamic Pathing via the Folder Manager API

Rather than hardcoding directory paths—such as assuming the boot drive was named "Macintosh HD" or that the extensions folder was simply titled "Extensions"—installers relied on the Mac OS Folder Manager API.

Through the FindFolder routine, an installer queried the system using standardized four-character folder type constants:

  • kExtensionFolderType ('extn'): Returned the exact directory ID and volume reference number for the active Extensions folder.
  • kControlPanelFolderType ('ctrl'): Located the Control Panels directory for accompanying configuration tools.
  • kSystemFolderType ('macs'): Located the blessed System Folder itself.

Using FindFolder ensured that extensions were placed in the correct location regardless of whether the volume was renamed, the operating system was localized in another language (e.g., German or Japanese), or multiple System Folders existed across separate partitions.

The Finder's Native Drop Routing

Installers could also emulate the behavior of the Mac OS 9 Finder. In classic Mac OS, dragging an extension onto a closed System Folder icon triggered an automatic routing mechanism. The Finder inspected the file's Mac OS type and creator metadata. Files with types such as 'INIT' (system extension), 'cdev' (control panel), or shared libraries of type 'shlb' were recognized immediately, prompting the system to ask the user if it could file them away in their proper subfolders. Third-party installers programmatic equivalents mimicked this behavior to ensure consistent placement.

Version Checking via Resource Forks

Overwriting existing system extensions could destabilize Mac OS 9, so installer engines used strict version-control logic before placing files:

  1. 'vers' Resource Inspection: Classic Mac OS files stored metadata in their resource forks. Installers read the standard 'vers' resource (version 1 and version 2) of both the incoming payload and the existing target file.
  2. Conditional Overwriting: Installers evaluated whether the target extension was older, identical, or newer. If an extension with the same name but a higher version number was already present, the installer would skip the file, alert the user, or archive the older version into an installer-created backup folder.

Integration with Extension Manager and Startup Loading

After copying the files into the designated folder, installer scripts often registered the new components with the system's tracking mechanisms. While extensions simply needed to exist in the Extensions directory to execute at next boot, Mac OS 9 used the Extensions Manager control panel to manage startup sets. Advanced installers could append their new files to the "Mac OS 9 All" or current active extension set files to ensure the newly added components were not disabled by default.

Because extensions patched the system trap table and loaded drivers into memory exclusively during system startup, installers concluded the placement process by flagging the operating system for a mandatory restart, ensuring the newly routed extensions could take effect.