Mac OS 9 Extensions Conflicting with Classic Environment

When Apple introduced the Classic environment in Mac OS X, it allowed legacy Mac OS 9 applications to run seamlessly alongside modern native software. However, because Mac OS X maintained strict control over memory and physical hardware, several categories of Mac OS 9 system extensions (INITs) and control panels caused fatal freezes, crashes, or launch failures inside Classic, requiring users to disable them using the Extensions Manager.

Video and Hardware Acceleration Extensions

Classic bypassed Mac OS 9's traditional video pipeline, drawing window contents directly through Mac OS X’s Quartz compositing engine. Extensions that attempted direct hardware rendering or video card initialization failed completely.

  • ATI and NVIDIA Graphic Accelerators: Extensions like ATI Resource Manager, ATI Driver Update, NVIDIA Driver, and NVIDIA Engine caused startup crashes because Mac OS X already controlled the GPU. Apple substituted these with Classic RAVE to handle legacy 3D graphics.
  • Glide and 3dfx Drivers: Any legacy 3dfx Glide extensions or third-party Voodoo graphics drivers clashed with the host display server, leading to immediate system hangs.

Low-Level Utilities and Memory Managers

Extensions designed to patch the system kernel, manipulate physical RAM, or alter low-level CPU routines were fundamentally incompatible with the protected memory model of Mac OS X.

  • Speed Doubler: Connectix’s Speed Doubler patched the 68k emulator and disk cache. Inside Classic, this resulted in memory corruption and immediate bombs (system errors).
  • RAM Charger: Because Mac OS X automatically managed virtual memory allocations for the Classic process, memory enhancers like RAM Charger and legacy virtual memory managers caused fatal conflicts.
  • CPU Upgrade Extensions: Control software and cache-enabling extensions from third-party processor upgrade manufacturers (such as Sonnet Technologies, NewerTech, and PowerLogix) failed because Mac OS X directly managed CPU caches and power states.

Appearance and Interface Patches

Software that hooked deeply into the Mac OS 9 Window Manager, QuickDraw, or the Dialog Manager regularly conflicted with Classic’s integration layer.

  • Kaleidoscope: This popular system-wide theming utility caused graphic corruption, invisible windows, or full Classic environment crashes by intercepting low-level QuickDraw calls that Mac OS X was attempting to translate.
  • Default Folder (Versions prior to 3.1.5): Older releases of Default Folder modified standard Open and Save dialog boxes in ways that bypassed the Classic-to-Cocoa/Carbon communication bridge.
  • Action Files and Menu Modifiers: Tools like Action Menus or Now Menus that altered the Mac OS menu bar clashed with the unified menu structure presented by the host operating system.

Networking and Peripheral Drivers

Mac OS X shared its network connection with Classic via an internal bridge, meaning Classic did not need direct access to physical networking hardware.

  • AirPort and Direct Ethernet Drivers: Legacy AirPort Driver and third-party PCI/PCMCIA Ethernet card extensions caused resource contention and network loss because the host OS already claimed the physical interfaces.
  • Serial and Modem Tools: Extensions attempting direct serial port access, including legacy fax software like FAXstf and certain dial-up extensions, failed unless updated specifically with Classic-aware communication plug-ins.

Power Management and System Profilers

  • Energy Saver Extension: The legacy Energy Saver control panel and extension caused lockups by attempting to force sleep and spindown commands directly onto hardware already controlled by Mac OS X’s Darwin kernel.
  • Conflict Catcher: While useful for diagnosing native OS 9 boots, Casady & Greene’s Conflict Catcher often interfered with the automated "Classic Support" extensions that Apple injected dynamically during the Classic environment's startup sequence.