Scheduled Startup and Shutdown in Mac OS 9

In Apple's classic Mac OS 9, the Energy Saver control panel included automated power controls that allowed users to schedule specific times for the system to start up, shut down, wake, or sleep. This functionality relied on a combination of software-level preferences written to the system and low-level hardware timers managed by the Mac's Power Management Unit (PMU). By bridging the operating system with the system's underlying power hardware, Mac OS 9 allowed computers to operate unattended for automated backups, office routines, or server tasks.

Accessing the Schedule Settings

To configure automated power events, users navigated to the Apple Menu, selected Control Panels, and opened Energy Saver. Within the control panel, clicking the Schedule tab revealed the interface for automating startup and shutdown routines.

The configuration allowed two primary rules:

  1. Startup or Wake: Checking this box allowed users to instruct the Mac to turn on or wake from sleep at a specified time, on specific days (Every Day, Weekdays, Weekends, or a chosen single day).
  2. Shut Down or Sleep: Checking this box allowed users to set a recurring time and day pattern for the machine to safely shut down or enter low-power sleep mode.

The Underlying Hardware Mechanism

The ability to turn on a fully powered-down computer required low-level hardware communication:

  • The Power Management Unit (PMU) and CUDA Chip: When a user applied a schedule in the control panel, Mac OS 9 sent these parameters to the PMU (or CUDA microcontroller on older hardware) and stored the wake/start time in non-volatile RAM (NVRAM/PRAM).
  • Standby Power and the Real-Time Clock: The PMU continuously ran on low standby power drawn from the wall outlet or the internal logic board battery (PRAM battery). The PMU compared the active Real-Time Clock (RTC) to the programmed alarm time.
  • Hardware Trigger: Once the target timestamp matched the clock, the PMU sent a power-on interrupt to the power supply unit (PSU), turning on the logic board and executing the normal cold boot sequence without requiring physical button engagement.

Software Execution for Shutdown

While startup relied on the hardware-level PMU, scheduled shutdowns were handled via software at the operating system level:

  • The Energy Saver Extension monitored the system clock while Mac OS 9 was running.
  • When the target time was reached, the system generated an alert warning the user that the computer was preparing to shut down. Users were given a brief countdown window to cancel the event.
  • If not canceled, the extension issued a standard Finder-level Shut Down Apple Event. The operating system would then systematically send quit commands to all running applications.

Limitations and Operational Quirks

The scheduling system had a few notable constraints common to classic Mac OS:

  • Unsaved Dialog Hangs: Because the shutdown relied on standard application quit routines, any open document with unsaved changes would prompt a "Save changes?" dialog box. If left unattended, this prompt halted the shutdown process, leaving the computer running indefinitely.
  • Battery Dependency: If a Mac was completely disconnected from AC power, a failing or dead 3.6V PRAM battery would reset the real-time clock and wipe the NVRAM settings, causing scheduled startups to fail.
  • Sleep vs. Power Off: PowerBook laptops treated these commands differently depending on lid state and battery thresholds, often defaulting to sleep rather than a full system shutdown to prevent data loss.