Copland (operating system)
Copland (operating system)
Main page
C

Copland (operating system)

logo
Community Hub0 subscribers
Read side by side
Copland (operating system)
View on Wikipedia
from Wikipedia
Copland
DeveloperApple Computer, Inc.
OS familyMacintosh
Working stateDiscontinued
Source modelClosed source
Marketing targetMacintosh users
Available inEnglish
Supported platformsPower Macintosh
Kernel typeMicrokernel
Preceded bySystem 7
Succeeded byMac OS 8
Articles in the series
Taligent, A/UX
Part of a series on
macOS
History and architecture
Versions
Applications
Utilities
Related operating systems

Copland is an operating system developed by Apple for Macintosh computers between 1994 and 1996 but never commercially released. It was intended to be released with the name System 8, and later after changing their naming style, Mac OS 8.[1] Planned as a modern successor to the aging System 7, Copland introduced protected memory, preemptive multitasking, and several new underlying operating system features, while retaining compatibility with existing Mac applications. Copland's tentatively planned successor, codenamed Gershwin, was intended to add more advanced features such as application-level multithreading.

Development officially began in March 1994. Over the next several years, previews of Copland garnered much press, introducing the Mac audience to operating system concepts such as object orientation, crash-proofing, and multitasking. In August 1995, David Nagel, a senior vice president, announced at Macworld Expo that Copland would be released in mid-1996. The following May, Gil Amelio stated that Copland was the primary focus of the company, aiming for a late-year release. Internally, however, the development effort was beset with problems due to dysfunctional corporate personnel and project management. Development milestones and developer release dates were missed repeatedly.

Ellen Hancock was hired to get the project back on track, but quickly concluded it could never ship. In August 1996, it was announced that Copland was canceled and Apple would look outside the company for a new operating system. Among many choices, they selected NeXTSTEP and purchased NeXT in 1997 to obtain it. In the interim period, while NeXTSTEP was ported to the Mac, Apple released the much more legacy-oriented Mac OS 8 in 1997 based upon adding components from Copland, and Mac OS 9 in 1999 to transition forward. Mac OS X became Apple's next-generation operating system in 2001.

The Copland development effort has been described as an example of feature creep. In 2008, PC World included Copland on a list of the biggest project failures in information technology history.

Design

[edit]

Mac OS legacy

[edit]

Launched in 1984, the Macintosh and its operating system were designed from the start as a single-user, single-tasking system, which allowed the hardware development to be greatly simplified.[2]

The Macintosh lacks multitasking but tries to fake it, and it insists on a complicated user interface but leaves much of the work up to the application. These are serious drawbacks, and it is difficult to imagine elegant repairs for them.

— Adam Brooks Webber, Byte (September 1986)[3]

These limits meant that supporting the multitasking of more than one program at a time would be difficult, without rewriting all of this operating system and application code. Yet doing so would mean the system would run unacceptably slow on existing hardware. Instead, Apple adopted a system known as MultiFinder in 1987, which keeps the running application in control of the computer, as before, but allows an application to be rapidly switched to another, normally simply by clicking on its window. Programs that are not in the foreground are periodically given short bits of time to run, but as before, the entire process is controlled by the applications, not the operating system.

Because the operating system and applications all share one memory space, it is possible for a bug in any one of them to corrupt the entire operating system, and crash the machine. Under MultiFinder, any crash anywhere will crash all running programs. Running multiple applications potentially increases the chances of a crash, making the system potentially more fragile.

Adding greatly to the severity of the problem is the patching mechanism used to add functions to the operating system, known as CDEVs and INITs or Control Panels and Extensions. Third party developers also make use of this mechanism to add features, including screensavers and a hierarchical Apple menu. Some of these third-party control panels became almost universal, like the popular After Dark screensaver package.[4] Because there was no standard for use of these patches, it is not uncommon for several of these add-ons — including Apple's own additions to the OS — to use the same patches, and interfere with each other, leading to more crashing.

Copland design

[edit]

Copland was designed to consist of the Mac OS on top of a microkernel named Nukernel, which would handle basic tasks such as application startup and memory management, leaving all other tasks to a series of semi-special programs known as servers. For instance, networking and file services would not be provided by the kernel itself, but by servers that would be sending requests through interapplication communications.[5] The Copland system as a whole consists of the combination of Nukernel, various servers, and a suite of application support libraries to provide implementations of the well-known classic Macintosh programming interface.[6]

Application services are offered through a single program known officially as the Cooperative Program Address Space.[7] Mac programs run much as they do under System 7, as cooperative tasks that use the non-reentrant Toolbox calls. Copland provided much improved stability for applications running compared to System 7 – "the system won’t crash as it can in System 7. Instead, because the Copland microkernel tracks all resources (such as, tasks, timers, and areas), it can reclaim them when it terminates the process associated with your application.".[8] A worst-case scenario is that an application in the CPAS environment crashes, taking down the entire environment with it. This does not result in the system as a whole going down, however, and the Cooperative Program Address Space environment is automatically restarted.[9][page needed] In addition, Copland provides pre-emptive scheduling of tasks where "the Process Manager gives each primary task the opportunity to be preemptively scheduled by the microkernel."[8]

The Copland runtime architecture includes purple boxes showing threads of control, and the heavy lines show different memory partitions. In the upper left the blue boxes are running several System 7 applications, and the toolbox code supporting them (green). Two headless applications are running in their own spaces, providing file and web services. At the bottom are the OS servers in the same memory space as the kernel, indicating colocation.

New applications, written with Copland in mind, are able to directly communicate with the system servers and thereby gain many advantages in terms of performance and scalability. They can also communicate with the kernel to launch separate applications or threads, which run as separate processes in protected memory, as in most modern operating systems.[10] These separate applications cannot use non-reentrant calls like QuickDraw, however, and thus could have no user interface. Apple suggested that larger programs could place their user interface in a normal Macintosh application, which then start worker threads externally.[6]

Copland is fully PowerPC (PPC) native. System 7 had been ported to the PowerPC with great success; some parts of the system run as PPC code. There is enough 68k code left in the system to be run in emulation, and especially user applications, however that the operating system must map some data between the two environments. In particular, every call into the Mac OS requires a mapping between the interrupt systems of the 68k and PPC. Removing these mappings would greatly improve general system performance. At WWDC 1996, engineers claimed that system calls would execute as much as 50% faster.[11]

Copland is also based on the then-recently defined Common Hardware Reference Platform, or CHRP, which standardized the Mac hardware to the point where it could be built by different companies and can run other operating systems (Solaris and AIX were two of many mentioned). This was a common theme at the time; many companies were forming groups to define standardized platforms to offer an alternative to the "Wintel" platform that was rapidly becoming dominant — examples include 88open, Advanced Computing Environment, and the AIM alliance.[12]

The fundamental challenge of Copland's development and adoption was getting all of these functions to fit into an ordinary Mac. System 7.5 already uses up about 2.5 megabytes (MB) of RAM, which is a significant portion of the total RAM in most contemporaneous machines. Copland is a hybrid of two systems, as its native foundation also hosts the Cooperative Program Address Space application environment as well as Copland native Server tasks. Copland thus uses a Mach-inspired memory management system and relies extensively on shared libraries,[13] with the goal of being about 50% larger than 7.5.

History

[edit]

Pink and Blue

[edit]
See also: Taligent § History

In March 1988,[a] technical middle managers at Apple held an offsite meeting to plan the future course of Mac OS development.[14] Ideas were written on index cards; features that seemed simple enough to implement in the short term (like adding color to the user interface) were written on blue cards; longer-term goals—such as preemptive multitasking—were on pink cards; and long-range ideas like an object-oriented file system were on red cards.[15][16][b] Development of the ideas contained on the blue and pink cards was to proceed in parallel, and at first, the two projects were known simply as "blue" and "pink".[17] Apple intended to have the Blue team [18] release an updated version of the existing Macintosh operating system in the 1990–1991 timeframe, and the Pink team to release an all-new OS around 1993.

The Blue team, who came to call themselves the "Blue Meanies" after characters in the film Yellow Submarine, delivered what became known as System 7 on May 13, 1991, but the Pink team's efforts suffered from second-system effect and its release date continued to slip into the indefinite future. Some of the reason for this can be traced to problems that would become widespread at Apple as time went on; as Pink became delayed, its engineers moved to Blue instead.[19] This left the Pink team constantly struggling for staffing, and suffering from the problems associated with high employee turnover. Management ignored these sorts of technical development issues, leading to continual problems delivering working products.

At this same time, the recently released NeXTSTEP was generating intense interest in the developer world. Features that were originally part of Red were folded into Pink, and the Red project (also known as "Raptor")[20] was eventually canceled. This problem was also common at Apple during this period; to chase the "next big thing", middle managers added new features to their projects with little oversight, leading to enormous problems with feature creep. In the case of Pink, development eventually slowed to the point that the project appeared moribund.

Taligent

[edit]
Main article: Taligent

On April 12, 1991, Apple CEO John Sculley performed a secret demonstration of Pink running on a PS/2 Model 70 to a delegation from IBM. Though the system was not fully functional, it resembled System 7 running on a PC. IBM was extremely interested, and over the next few months, the two companies formed an alliance to further development of the system. These efforts became public in early 1992, under the new name "Taligent".[21] At the time, Sculley summed up his concerns with Apple's own ability to ship Pink when he stated "We want to be a major player in the computer industry, not a niche player. The only way to do that is to work with another major player."[22]

Infighting at the new joint company was legendary, and the problems with Pink within Apple soon appeared to be minor in comparison.[23] Apple employees made T-shirts graphically displaying their prediction that the result would be an IBM-only project.[24] On December 19, 1995, Apple officially pulled out of the project.[25] IBM continued working alone with Taligent, and eventually released its application development portions under the new name "CommonPoint". This saw little interest and the project disappeared from IBM's catalogs within months.

Business as usual

[edit]

While Taligent efforts continued, very little work addressing the structure of the original OS was carried out. Several new projects started during this time, such as the Star Trek project, a port of System 7 and its basic applications to Intel-compatible x86 machines, which reached internal demo status. But as Taligent was still a concern, it was difficult for new OS projects to gain any traction.

Instead, Apple's Blue team continued adding new features to the same basic OS. During the early 1990s, Apple released a series of major new packages to the system; among them are QuickDraw GX, Open Transport, OpenDoc, PowerTalk, and many others. Most of these were larger than the original operating system. Problems with stability, which had existed even with small patches, grew along with the size and requirements of these packages, and by the mid-1990s the Mac had a reputation for instability and constant crashing.[6]

As the stability of the operating system collapsed, the ready answer was that Taligent would fix this with all its modern foundation of full reentrance, preemptive multitasking, and protected memory. When the Taligent efforts also collapsed, Apple was left with an aging OS and no designated solutions. By 1994, the press buzz surrounding the upcoming release of Windows 95 started to crescendo, often questioning Apple's ability to respond to the challenge it presented.[16] The press turned on the company, often introducing Apple's new projects as failures in the making.[26]

Another try

[edit]

Given this pressure, the collapse of Taligent, the growing problems with the existing operating system, after the release of System 7.5 in late 1994, Apple management decided that the decade-old operating system had run its course. A new system that did not have these problems was needed, and soon. Since so much of the existing system would be difficult to rewrite, Apple developed a two-stage approach to the problem.

In the first stage, the existing system would be moved on top of a new kernel-based OS with built-in support for multitasking[27] and protected memory. The existing libraries, like QuickDraw, would take too long to be rewritten for the new system and would not be converted to be reentrant. Instead, the CPAS keeps applications and legacy code such as QuickDraw in a single memory block so they continue to run as they had in the past. CPAS runs in a distinct Copland memory space, so crashing legacy applications or extensions within CPAS cannot crash the entire machine.

In the next stage of the plan, once the new kernel was in place and this basic upgrade was released, development would move on to rewriting the older libraries into new forms that could run directly on the new kernel.[28][29][30] At that point, applications would gain some added modern features.

In the musical code-naming pattern where System 7.5 is code-named "Mozart", this intended successor is named "Copland" after composer Aaron Copland. In turn, its proposed successor system, Gershwin, would complete the process of moving the entire system to the modern platform, but work on Gershwin would never officially begin.[31]

Development

[edit]

The Copland project was first announced by David Nagel in May 1994.[32][33] Parts of Copland, such as an early version of the new file system, were demonstrated at Apple's Worldwide Developers Conference in May 1995. Apple promised that a beta release of Copland would be ready by the end of the year, for final commercial release in early 1996.[33][34] Gershwin would follow the next year.[35] Throughout the year, Apple released several mock-ups to various magazines showing what the new system would look like, and commented continually that the company was fully committed to this project. By the end of the year, however, no Developer Release had been produced.[34]

Copland's open file dialog box has a preview area on the right. The stacked folders area on the left is intended to provide a visual path to the current selection, but this was later abandoned as being too complex. The user is currently using a favorite location shortcut.

As had happened during the development of Pink, developers within Apple soon started abandoning their own projects in order to work on the new system. Middle management and project leaders fought back by claiming that their project was vital to the success of the system, and moving it into the Copland development stream. Thus, it could not be canceled along with their employees being removed to work on some other part of Copland anyway.[36] This process took on momentum across the next year.

"Anytime they saw something sexy it had to go into the OS." said Jeffrey Tarter, publisher of the software industry newsletter Softletter. "There were little groups all over Apple doing fun things that had no earthly application to Apple's product line." What resulted was a vicious cycle: As the addition of features pushed back deadlines, Apple was compelled to promise still more functions to justify the costly delays. Moreover, this Sisyphean pattern persisted at a time when the company could scarcely afford to miss a step.[33]

Soon the project looked less like a new operating system and more like a huge collection of new technologies; QuickDraw GX, System Object Model (SOM), and OpenDoc became core components of the system,[37] while completely unrelated technologies like a new file management dialog box (the open dialog) and themes support appeared also. The feature list grew much faster than the features could be completed, a classic case of creeping featuritis.[33] An industry executive noted that "The game is to cut it down to the three or four most compelling features as opposed to having hundreds of nice-to-haves, I'm not sure that's happening."[38]

As the "package" grew, testing it became increasingly difficult and engineers were commenting as early as 1995 that Apple's announced 1996 release date was hopelessly optimistic: "There's no way in hell Copland ships next year. I just hope it ships in 1997."[38]

In mid-1996, information was leaked that Copland would have the ability to run applications written for other operating systems, including Windows NT. Simultaneously allegedly being confirmed by Copland engineers while being authoritatively denied by Copland project management, this feature had supposedly been in development for more than three years. One user claimed to have been told about these plans by members of the Copland development team. Some analysts projected that this ability would increase Apple's penetration into the enterprise market, others said it was "game over" and was only a sign of the Mac platform's irrelevancy.[39]

Developer Release

[edit]

At WWDC 1996, Apple's new CEO, Gil Amelio, used the keynote to talk almost exclusively about Copland, now known as System 8.[40] He repeatedly stated that it was the only focus of Apple engineering and that it would ship to developers in a few months, with a full release planned for late 1996. Very few, if any, demos of the running system were shown at the conference. Instead, various pieces of the technology and user interface that would go into the package (such as a new file management dialog) were demonstrated. Little of the core system's technology was demonstrated and the new file system that had been shown a year earlier was absent.

There was one way to actually use the new operating system – by signing up for time in the developer labs. This did not go well:

There was a hands-on demo of the current state of OS 8. There were tantalizing glimpses of the goodies to come, but the overall experience was awful. It does not yet support text editing, so you couldn’t actually do anything except open and view documents (any dialog field that needed something typed into it was blank and dead). Also, it was incredibly fragile and crashed repeatedly, often corrupting system files on the disk in the process. The demo staff reformatted and rebuilt the hard disks at regular intervals. It was incredible that they even let us see the beast.[41]

Several people at the show complained about the microkernel's lack of sophistication, notably the lack of symmetric multiprocessing, a feature that would be exceedingly difficult to add to a system due to ship in a few months. After that, Amelio came back on stage and announced that they would be adding that to the feature list.

In August 1996, "Developer Release 0" was sent to a small number of selected partners.[33] Far from demonstrating improved stability, it often crashed after doing nothing at all, and was completely unusable for development. In October, Apple moved the target delivery date to "sometime", hinting that it might be 1997. One of the groups most surprised by the announcement was Apple's own hardware team, who had been waiting for Copland to allow the PowerPC to be natively represented, unburdened of software legacy. Members of Apple's software QA team joked that, given current resources and the number of bugs in the system, they could clear the program for shipping sometime around 2030.

Cancellation

[edit]

Later in August 1996, the situation was no better. Amelio complained that Copland was "just a collection of separate pieces, each being worked on by a different team ... that were expected to magically come together somehow."[42] Hoping to salvage the situation, Amelio hired Ellen Hancock away from National Semiconductor to take over engineering from Ike Nassi[43] and get Copland development back on track.[44]

After a few months on the job, Hancock came to the conclusion that the situation was hopeless; given current development and engineering, she believed Copland would never ship. Instead, she suggested that the various user-facing technologies in Copland be rolled out in a series of staged releases, instead of a single big release. Apple officially canceled Copland in August 1996,[35] The CD envelopes for the developer's release had been printed, but the discs had not been mastered.

To address the aging infrastructure underneath these technologies, Amelio suggested looking outside the company for an unrelated new operating system. Candidates considered were Sun's Solaris and Windows NT. Hancock reportedly was in favor of going with Solaris, while Amelio preferred Windows. Amelio even reportedly called Bill Gates to discuss the idea, and Gates promised to put Microsoft engineers to work porting QuickDraw to NT.[45]

After lengthy discussions with Be and rumors of a merger with Sun Microsystems, many were surprised at Apple's December 1996 announcement that they were purchasing NeXT and bringing Steve Jobs on in an advisory role.[46] Amelio quipped that they "choose Plan A instead of Plan Be."[47] The project to port NeXTSTEP to the Macintosh platform was named Rhapsody and was to be the core of Apple's cross-platform operating system strategy. This would inherit OpenStep's existing support for PowerPC, Intel x86, and DEC Alpha CPU architectures, and an implementation of the OpenStep libraries running on Windows NT. This would in effect open the Windows application market to Macintosh developers as they could license the library from Apple for distribution with their product, or depend on an existing installation.

Legacy

[edit]

Following Hancock's plan, development continued with System 7.5 receiving integration of several elements of Copland. System 7 was renamed to Mac OS 7 with the release of 7.6, wherein stability and performance were improved.[48] Many Copland features, including the new multithreaded Finder and support for themes (defaulting to Platinum) were integrated into the unreleased beta of Mac OS 7.7, which was instead rebranded and launched as Mac OS 8.[49]

With the return of Jobs, this rebranding to version 8 also allowed Apple to exploit a legal loophole to terminate third-party manufacturers' licenses to System 7 and effectively shut down the Macintosh clone market.[50] Later, Mac OS 8.1 finally added the new file system and Mac OS 8.6 updated the nanokernel to handle limited support for preemptive tasks. Its interface is Multiprocessing Services 2.x and later, but there is no process separation and the system still uses cooperative multitasking between processes. Even a process that is Multiprocessing Services-aware still has a part that also runs all single-threaded programs and the only task that can run 68k code.

The Rhapsody project was canceled after several Developer Preview releases, support for running on non-Macintosh platforms was dropped, and it was eventually released as Mac OS X Server 1.0. In 2001 this foundation was coupled to the Carbon library and Aqua user interface to form the modern Mac OS X product.[51] Several features originally seen in Copland demos, including its advanced Find command, built-in web browser, piles of folders, and support for video-conferencing, have reappeared in subsequent releases of Mac OS X as Spotlight, Safari, Stacks, and iChat AV, respectively, although the implementation and user interface for each feature is very different.

Hardware requirements

[edit]

According to the documentation included in the Developer Release, Copland supports the following hardware configurations:[52]

  • NuBus-based Macintoshes: 6100/60, 6100/60AV (no AV functions), 6100/66, 6100/66 AV (no AV functions), 6100/66 DOS (no DOS functions), 7100/66, 7100/66 AV (no AV functions), 7100/80, 7100/80 AV (no AV functions), 8100/80/ 8100/100/ 8100/100 AV (no AV functions), 8100/110
  • NuBus-based Performas: 6110CD, 6112CD, 6115CD, 6117CD, 6118CD
  • PCI-based Macintoshes: 7200/75, 7200/90, 7500/100, 8500/120, 9500/120, 9500/132
  • Drives formatted with Drive Setup
  • For DR1 and earlier, the installer requires System 7.5 or later on a hard disk of 250MB or greater capacity.
  • Display set to 256 colors (8-bit) or Thousands (16-bit).

See also

[edit]

Notes

[edit]

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Copland (operating system)

View on Grokipedia
from Grokipedia
Copland was an ambitious, unreleased operating system project undertaken by Apple Computer in the mid-1990s to create the next major version of the Mac OS, featuring a microkernel architecture designed to introduce modern capabilities such as preemptive multitasking, protected memory, and enhanced user productivity tools.[1][2] Development of Copland began in earnest in March 1994, with the goal of releasing it as System 8 by mid-1996 to leverage the PowerPC processor and address the limitations of the classic Mac OS, including its cooperative multitasking and lack of memory protection.[3] Key features planned for Copland included the Appearance Manager for customizable 3D interfaces and themes, the Assistance Manager for task automation and active user support, Navigation Services for improved file handling, integration with OpenDoc for component-based software, and Open Transport for advanced networking.[1][2] A beta version was distributed to approximately 50 developers on November 17, 1995, but the project faced significant challenges, including technical instability, feature creep, and escalating development costs of around $250 million per year involving 500 engineers.[4] Ultimately, Copland was canceled in August 1996 by CEO Gil Amelio due to its unreadiness for release and Apple's mounting financial losses exceeding $740 million that year, prompting the company to acquire NeXT Software and adopt its NeXTSTEP foundation for what became Mac OS X.[3][4][5]

Background

Origins in Pink and Blue

In March 1988, Apple engineers and managers convened at an off-site meeting to brainstorm the future direction of the Macintosh operating system, which had been in existence for four years. Participants documented their ideas on index cards, categorizing short-term enhancements feasible for an incremental update on blue cards and ambitious long-term innovations requiring a ground-up redesign on pink cards. This exercise formalized the division of development efforts, with the Blue project focusing on evolving the existing System 6 into its successor, System 7.[6] The Pink project, initiated that same month, aimed to create a next-generation object-oriented operating system as a complete replacement for the classic Mac OS, incorporating advanced capabilities such as protected memory and preemptive multitasking. Starting with a core team of about 20 engineers, Pink was envisioned to address fundamental limitations in the aging system while retaining compatibility where possible. Meanwhile, the Blue project progressed more rapidly, culminating in the release of System 7 on May 13, 1991, which introduced features like virtual memory and improved multitasking but remained constrained by the original architecture.[7][8][9] Pink's development faced significant hurdles, including initial staffing shortages that arose from the need to retain key talent frustrated by stalled progress on Mac OS innovations; to prevent defections, Apple assembled the project around these experienced engineers. As the scope expanded, feature creep set in, with developers adding increasingly complex elements without sufficient oversight, exacerbating delays. The initiative also exemplified the second-system effect, where the desire to incorporate every sidelined idea from prior systems led to over-design and indefinite postponement, as articulated in software engineering literature. These challenges ultimately prompted Apple to transition Pink into the Taligent joint venture with IBM in 1992.[8][7]

Taligent project

Taligent was established in early 1992 as a joint venture between Apple Computer and International Business Machines (IBM) to commercialize the object-oriented operating system concepts originating from Apple's Pink project.[10][11] The company, named Taligent Inc., began operations in March 1992 with approximately 170 employees and significant venture backing, aiming to create a next-generation operating system that could serve as a foundation for business computing in the mid-1990s and beyond.[11] Under the leadership of IBM veteran Joseph M. Guglielmi as chairman and CEO, Taligent sought to challenge Microsoft's dominance by developing open standards-based software.[11] The primary goals of Taligent centered on building a platform-independent operating system leveraging advanced object-oriented models, particularly for enterprise applications.[10] This involved creating C++-based frameworks, such as those for compound documents, user interfaces, and file systems, to enable reusable, extensible software components across hardware platforms.[12] Taligent's approach emphasized portability, allowing the OS to run on diverse architectures like PowerPC, Intel, and others, while integrating IBM's contributions such as the Mach 3.0 microkernel for its Workplace OS initiative.[13] However, the project faced significant internal conflicts stemming from differing corporate priorities—Apple's focus on consumer Macintosh users versus IBM's enterprise-oriented customer base shifting toward Windows—leading to goal-shifting delays and scope changes.[13] These tensions diverted substantial resources from Apple's internal OS efforts, as engineers and intellectual property were committed to the joint venture.[13] By late 1995, escalating delays and strategic misalignments prompted Apple's withdrawal from the partnership on December 19, 1995.[14] The dissolution was announced the following day, with IBM absorbing Taligent as a wholly owned subsidiary in Cupertino, California, resulting in job losses for some of its 375 employees.[14] IBM proceeded independently, releasing CommonPoint—a runtime environment based on Taligent's object frameworks—in mid-1995 for platforms including AIX, OS/2, HP-UX, and Windows NT.[10] Despite critical acclaim for its innovative C++ frameworks comprising over 100 components and 1,000 classes, CommonPoint achieved only minimal market success, failing to attract widespread adoption amid competition from established systems like Windows 95.[10]

Interim Mac OS updates

Amid delays in ambitious projects such as Pink and Taligent, Apple focused on incremental enhancements to its existing operating system to maintain user satisfaction and market relevance in the early 1990s.[8] Apple released System 7 on May 13, 1991, marking a significant upgrade from System 6 with improvements in multitasking via MultiFinder, better memory management, and the introduction of TrueType fonts for scalable typography.[9][15] Subsequent versions built on this foundation; System 7.1 arrived in August 1992, incorporating a revised Sound Manager for enhanced audio handling. System 7.1.1, released in October 1993 and marketed as System 7 Pro, introduced AppleScript for scripting and automation to enable users and developers to create custom workflows without deep programming knowledge.[16][17] By September 12, 1994, System 7.5 was unveiled as a comprehensive update, integrating QuickDraw GX for advanced vector-based graphics and improved printing capabilities, which allowed for more sophisticated layout and color management in applications.[18] However, the accumulation of system extensions known as INITs (initialization files) and CDEVs (control device extensions) in these versions often led to software conflicts, resulting in frequent crashes and system instability that frustrated users.[19][20] Third-party utilities like Conflict Catcher emerged to address this by allowing users to selectively load or disable extensions during startup, thereby isolating problematic combinations and restoring reliability.[20] Market dynamics intensified these challenges, as the release of Microsoft Windows 3.1 in April 1992 introduced a more affordable and expandable graphical interface for PCs, eroding Apple's dominance in creative markets.[21] The anticipation surrounding Windows 95, launched in August 1995 with preemptive multitasking and a modernized interface, further compelled Apple to emphasize stability and minor feature additions in System 7 updates rather than pursuing radical overhauls.[21][22] System 7.5 stood as the final major incremental update in this era, providing a stable platform with enhanced networking and better file sharing, just as planning for more transformative changes began to accelerate.[18]

Design and Architecture

Legacy Mac OS constraints

The classic Mac OS, introduced in 1984, operated as a single-user system with cooperative multitasking, where applications were required to voluntarily yield control of the CPU to allow task switching. This model was initially supported by the Switcher utility but gained broader adoption with MultiFinder, an extension released in 1987 as part of System Software 5.0, which enabled multiple applications to run concurrently while maintaining the illusion of simultaneous execution through event-driven yielding via routines like WaitNextEvent.[23][24] Key limitations stemmed from the absence of protected memory, as all applications shared a single address space without isolation, allowing one program's errors—such as buffer overflows or invalid pointers—to corrupt others and crash the entire system. This shared memory architecture, combined with no preemptive multitasking, meant that a misbehaving application could monopolize the CPU indefinitely, freezing the interface until manual intervention, while rogue extensions or drivers exacerbated vulnerabilities by directly accessing hardware without safeguards.[25][26] As the system evolved into System 7 in 1991, reliance on extensions and control panels for functionality introduced patch-like dependencies similar to "DLL hell," where incompatible versions led to frequent conflicts; for instance, duplicate fonts in the System Folder could cause rendering errors or application failures in tools like the Font/DA Mover, and mismatched printer or SCSI drivers often resulted in boot failures or data corruption during I/O operations. By the mid-1990s, these issues compounded with memory fragmentation and leaks from poorly managed heaps, necessitating frequent reboots—sometimes multiple times daily—to restore stability and clear accumulated errors.[27][28] These pervasive constraints in the legacy Mac OS architecture underscored the imperative for a comprehensive redesign in Copland to achieve modern reliability.

Copland's core innovations

Copland represented a fundamental shift in Apple's operating system design, aiming to address the limitations of the classic Mac OS through a modern, modular architecture centered on a microkernel known as the NuKernel.[29] This microkernel was engineered to handle essential low-level functions such as process management, memory allocation, and interprocess communication (IPC), while delegating higher-level services—like file systems, networking, and display management—to separate, modular servers running outside the kernel space. By minimizing the kernel's footprint to only critical operations, Copland sought to enhance system stability and reduce the risk of widespread crashes, as a failure in one server would not compromise the entire system.[30][1] A key innovation was the introduction of protected memory and preemptive multitasking specifically for new applications developed under Copland. Protected memory ensured that applications operated in isolated address spaces, preventing one program from corrupting another's data or the kernel itself, thereby improving overall reliability and enabling more robust multitasking environments. Preemptive multitasking allowed the microkernel to interrupt and reschedule tasks based on priority, contrasting with the cooperative model of prior Mac OS versions and promising greater responsiveness, especially for resource-intensive operations like I/O and networking. These features were optimized through efficient IPC mechanisms, which facilitated faster communication between kernel and user-space components compared to traditional trap-based calls.[31][1] Copland's hybrid architecture balanced radical change with backward compatibility, fully replacing the core OS while incorporating advanced layers to run legacy Mac applications seamlessly. It was designed as a native implementation for PowerPC processors, adhering to the Common Hardware Reference Platform (CHRP) standards to ensure broad hardware support and interoperability with other operating systems on compatible machines. Additionally, the system emphasized object-oriented principles through frameworks like the System Object Model (SOM), promoting reusable, extensible components that could streamline development and integration across applications. This approach not only aimed to minimize kernel bloat but also to foster a more scalable and crash-resistant foundation for future Macintosh software.[31][32][33]

System components and compatibility

Copland's core system components revolved around the NuKernel microkernel, which managed essential functions including preemptive task scheduling, memory protection, and resource allocation to improve overall stability and performance.[1][31] The NuKernel enabled higher-priority tasks to execute promptly and reclaimed resources upon process termination, forming the foundation for a modular OS design.[31] A pivotal component was the Collaborative Program Address Space (CPAS), which allowed legacy System 7 applications to run in a shared address space with cooperative multitasking, while isolating them from newer, preemptively multitasked processes to prevent crashes from affecting the entire system.[1][31] CPAS maintained compatibility with System 7 APIs like the Process Manager and Memory Manager, enabling older apps to operate without modification, though they retained their cooperative scheduling model via mechanisms such as WaitNextEvent.[31] Dedicated servers complemented this architecture, running in separate address spaces for enhanced reliability; for instance, the Display Server handled graphics operations, leveraging QuickDraw GX for unified text, imaging, and printing capabilities.[1][31] Other servers included the File Share Server and Events Server, each managing specific system services independently.[31] The compatibility strategy adopted a transitional, two-phase approach to bridge legacy and modern software: the first phase relied on CPAS to support existing System 7 applications without requiring immediate rewrites, while the second phase encouraged developers to adopt updated Copland APIs for native performance gains and future-proofing.[31] This rollout integrated OpenDoc for component-based document handling, promoting modularity and cross-platform potential, alongside QuickDraw GX to extend graphics features across the system.[1] On the hardware side, Copland included a hardware abstraction layer to facilitate transitions from NuBus to PCI buses, supporting dynamic driver loading via the Name Registry for broader device compatibility.[1][31] Optimizations targeted PowerPC processors through native code implementations for the OS and Toolbox, boosting efficiency in areas like multimedia and I/O without initial support for symmetric multiprocessing, though SMP was planned for future multiprocessor systems aligned with standards like CHRP.[1][31][34]

Development

Project initiation and planning

Following delays in the Taligent joint venture with IBM, Apple shifted focus to an internal project to modernize the Macintosh operating system.[3] Development of Copland officially began in March 1994, building directly on the foundation of System 7.5 to address the limitations of the aging Mac OS while ensuring backward compatibility.[35] The project was first discussed publicly in March 1994. In August 1995, Senior Vice President David Nagel announced at Macworld Expo that Copland, positioned as the successor to System 7 and codenamed System 8, would have a beta release to developers by the end of 1995 and a full commercial launch in mid-1996.[36] By 1996, amid Apple's escalating financial struggles—including plunging earnings and shrinking market share—newly appointed Chief Technology Officer Ellen Hancock assumed leadership of Copland in July 1996 to streamline efforts and reallocate resources.[37] Hancock prioritized stabilizing the project within constrained budgets, emphasizing core OS improvements over expansive features to mitigate the company's broader economic pressures.[38]

Key milestones and challenges

Development of Copland commenced in March 1994 as Apple's effort to create a next-generation operating system, initially targeted for release as Mac OS 8 in mid-to-late 1996.[3] Early internal alpha versions emerged in 1995, incorporating foundational elements like preemptive multitasking and a new object-oriented file system, though these builds were primarily for engineering use and not yet stable for broader testing.[3] The first beta release to approximately 50 developers occurred on November 17, 1995, allowing limited external feedback but revealing significant instability due to ongoing integration of core components.[39][4] A major challenge arose from scope expansion, as feature creep introduced ambitious additions such as advanced dynamic theming (including Platinum, Z, and P themes) and a complete Finder redesign, which bloated the project and exacerbated instability from the cooperative multitasking remnants of legacy Mac OS.[3] This was compounded by external pressure from Microsoft's Windows 95 launch in August 1995, which delivered preemptive multitasking and improved memory management, highlighting Copland's delays and eroding Apple's competitive edge in the market.[3] Initially promised for mid-1996 availability during a Macworld Expo announcement in August 1995, the beta program extended into 1996 without a viable consumer release, fostering a "vaporware" perception that diminished developer confidence and third-party investment in Mac software.[39] Under CEO Gil Amelio, who assumed leadership in February 1996, staffing challenges intensified as Apple implemented major layoffs—totaling around 5,600 jobs by mid-1997—to address financial woes, disrupting the Copland team and further slowing progress on stabilizing the system.[40] At the Worldwide Developers Conference (WWDC) in May 1996, Amelio demonstrated partial Copland functionality, such as live search and tabbed interfaces, but the showcase underscored persistent crashes and incomplete features, underscoring the project's mounting technical hurdles.[3] These milestones and obstacles ultimately highlighted the difficulties of overhauling a legacy OS amid rapid industry shifts and internal turmoil.[39]

Developer releases and testing

In August 1996, Apple distributed Developer Release 0 (DR0) of Copland to a limited group of select developers and partners, marking the final pre-cancellation build of the operating system. This release primarily featured a basic microkernel implementation but suffered from severe instability, with frequent crashes occurring multiple times per minute even in idle states, and lacked a complete user interface, relying instead on rudimentary tools for evaluation. Hardware requirements for testing DR0 included a minimum of 16 MB of RAM on PowerPC-based Macintosh systems. Developer feedback on DR0 highlighted profound shortcomings, including inadequate stability that rendered the system unusable for practical development, incomplete multiprocessing support that failed to deliver reliable concurrent operations, and significant usability issues stemming from the absence of polished interface elements and essential features like full memory protection. These reports underscored scalability flaws in Copland's architecture, such as resource bloat and integration challenges, prompting an internal reassessment of the project's viability just weeks after the release. Despite these evident problems, at the Worldwide Developers Conference (WWDC) in May 1996, CEO Gil Amelio publicly promised a ship date for Copland in late 1996, framing it as a phased rollout to restore confidence amid ongoing delays partly attributable to feature creep. This optimistic projection, however, clashed with the harsh realities exposed by DR0 testing, accelerating the decision to halt further investment.

Cancellation and Aftermath

Reasons for cancellation

The cancellation of Copland was officially announced in August 1996 by Apple's Chief Technology Officer Ellen Hancock, who determined that the operating system was in an unshippable state owing to severe instability and a lack of essential features.[41] This decision came shortly after the release of Developer Release 0 (DR0) in November 1995 and just prior to the Macworld Expo in January 1997, highlighting the project's inability to stabilize even in late-stage testing.[3] Several interconnected factors contributed to this outcome, beginning with the project's overambition, which led to protracted delays as Apple attempted to overhaul the legacy Mac OS with a new microkernel architecture, protected memory, and preemptive multitasking while maintaining backward compatibility.[3] These technical aspirations, initiated in 1994, ballooned development costs and timelines, with the system failing to meet its targeted release as Mac OS 8 in mid-1996. Compounding this were Apple's dire financial straits, including a net loss of $816 million for fiscal year 1996, which intensified pressure to cut unviable investments amid shrinking market share and competition from Windows.[42] Furthermore, Copland's instability in developer previews alienated third-party developers, who increasingly turned to alternatives like BeOS for its speed and modern design, or NeXT's operating system for its robustness.[3] In response, under CEO Gil Amelio, Apple shifted strategy toward acquiring an external solution, evaluating options including BeOS before ultimately purchasing NeXT in December 1996 for approximately $400 million, paving the way for the Rhapsody project and eventual Mac OS X.[43] This pivot marked a recognition that internal efforts could not deliver a competitive OS in time to stem Apple's losses.[41]

Immediate consequences

Following the cancellation of Copland in August 1996, Apple engineers salvaged key components for integration into the classic Mac OS, prioritizing elements that could be adapted without the project's full protected memory architecture. The multi-threaded Finder, featuring spring-loaded folders and improved window management, along with the Platinum visual theme incorporating 3D shading and customizable appearances, were ported to Mac OS 8, which Apple released in July 1997. QuickDraw GX, Copland's advanced graphics and printing engine, was also incorporated into Mac OS 8 to enhance imaging capabilities and support for scalable typography.[3] The decision rippled through Apple's developer community and business model, prompting immediate strategic shifts to address instability. In September 1997, Apple terminated its Macintosh cloning licensing program, acquiring major licensee Power Computing for $100 million to halt sales that were cannibalizing its own revenue and market share.[44][45] As an interim solution, Apple pivoted to Rhapsody, a developer preview of a new operating system based on NeXTSTEP and incorporating some Copland interface elements, with the first release distributed in October 1997.[44][45] Copland's failure accelerated Apple's acquisition of NeXT Software for $400 million, announced in December 1996, which brought Steve Jobs back as an advisor and positioned NeXTSTEP as the foundation for future OS development. Jobs assumed the role of interim CEO in September 1997, steering the company toward incremental enhancements to the classic Mac OS, including Mac OS 8 and the subsequent Mac OS 9 in 1999, amid severe financial pressures that saw Apple post a $708 million quarterly loss in Q2 FY1997.[46][43][47]

Hardware specifications

Copland targeted PowerPC-based Macintosh computers, requiring a PowerPC processor for native operation. The operating system was optimized for these systems, with all core components written in native PowerPC code to maximize performance on the architecture introduced in 1994. Legacy 68k applications were supported through emulation via a compatibility layer, allowing existing software to run without immediate recompilation.[31][3] Minimum system requirements specified installation over System 7.5 or later on a hard disk with at least 250 MB of free space. A minimum of 16 MB RAM was needed, though 32 MB was recommended to handle multitasking and debugging features effectively. Copland required a color display capable of at least 256 colors, aligning with the graphical standards of mid-1990s Macintosh hardware. No support for Intel x86 processors was included, as the project focused exclusively on Apple's PowerPC transition.[48][49] Supported hardware encompassed NuBus-based Power Macintosh models such as the 6100/60, 7100/80, and 8100/100, along with early PCI-based systems like the Power Macintosh 7200/75 and 7500/100. These mid-1990s machines, primarily featuring the PowerPC 601 processor, formed the core testing and deployment platforms. Older 680x0-based Macintosh models were excluded unless upgraded with a PowerPC processor card.[50][51] The design incorporated planned compatibility with the Common Hardware Reference Platform (CHRP), a standard aimed at enabling third-party vendors to produce Mac OS-compatible hardware without proprietary ROMs, potentially broadening support beyond Apple's initial models. In developer release 0 (DR0) testing, emphasis was placed on these mid-1990s Power Macintosh configurations to validate core functionality on representative production hardware.[52]

Legacy

Integration into later Mac OS versions

Following the cancellation of Copland in 1996, several of its prototyped features were salvaged and integrated into subsequent versions of the classic Mac OS, providing incremental improvements while maintaining backward compatibility for existing Macintosh applications.[53] Mac OS 8, released in 1997, incorporated key visual and usability elements originally developed for Copland. The Platinum appearance, featuring three-dimensional shading and metallic color schemes, was directly adapted from Copland prototypes to modernize the user interface without requiring a full system overhaul.[3] This theme became the default look for Mac OS 8, implemented through the new Appearance Manager, which allowed for customizable themes and enhanced graphical controls.[53] Additionally, the multi-threaded Finder, enabling operations like file copying to run in separate threads without freezing the interface, drew from Copland's multitasking prototypes, improving responsiveness for everyday tasks.[54] File synchronization capabilities, such as background threading for data transfers, were also prototyped in Copland and refined for Mac OS 8's file handling.[55] Building on these foundations, Mac OS 9 in 1999 further extended Copland-inspired concepts in search and resource handling. The Sherlock search tool, introduced in Mac OS 8.5 and enhanced in Mac OS 9, evolved from Copland's indexing prototypes by enabling disk-wide file content searches and internet queries through a unified interface.[3] OS 9 introduced better virtual memory partitioning and cooperative multitasking tweaks to reduce fragmentation, though full protected memory from Copland's CPAS was deferred.[3] HFS+ file system enhancements, including journaled support in later updates, aligned with scalability concepts from Copland's server-oriented prototypes to handle larger volumes more efficiently.[3] These integrations stabilized the classic Mac OS architecture, extending its viability for PowerPC-based systems and allowing Apple to focus resources on the next-generation platform without immediate disruption for users.[53]

Influence on Mac OS X and beyond

Following the cancellation of Copland in 1996, Apple pursued Rhapsody as an interim operating system in 1997, incorporating some visual and usability elements salvaged from Copland alongside NeXTSTEP technology acquired through the purchase of NeXT that year. Rhapsody served as a bridge, leveraging NeXTSTEP's mature foundation, and evolved into the Mac OS X Public Beta in 2000 and the full Mac OS X release in 2001. This hybrid approach addressed Copland's unfinished goals by providing a stable platform for further development.[56][57][58] Copland's core concepts of protected memory and preemptive multitasking, intended to overcome the limitations of the classic Mac OS, were ultimately realized in Mac OS X through the XNU kernel. XNU, a hybrid kernel derived from NeXTSTEP's Mach microkernel combined with BSD components, delivered the stability and efficiency Copland had aimed for with its NuKernel microkernel design, enabling robust multi-user support and application isolation. These features marked a revolutionary shift, ensuring Mac OS X could handle demanding workloads without the crashes plaguing earlier systems.[57][3] In terms of user interface, Copland's prototypes for dynamic, task-oriented elements influenced the modernization seen in Mac OS X, particularly through integrations like the Dock, which evolved from Copland's drag-windows-to-bottom minimization feature for quick access and multitasking visualization, though refined via NeXTSTEP's shelf metaphor.[4] Long-term, Copland's envisioned advanced search capabilities foreshadowed features in later macOS releases, such as Spotlight introduced in Mac OS X 10.4 Tiger in 2005, which built on Copland's "live search" toolbar integration for rapid, system-wide information retrieval. Similarly, the component-based modularity Copland promoted—enabling reusable software parts—echoed in the extensible frameworks supporting applications like Safari, debuted in 2003, allowing seamless OS-browser interactions. Retrospectives in the 2020s, including analyses of macOS Big Sur's redesigned, modular interface, highlight how Copland's failure underscored the value of hybrid kernel designs in Apple's enduring OS architecture, balancing performance with flexibility.[59][3]

Broader impacts on Apple

The failure of the Copland project intensified Apple's existential crisis in the mid-1990s, directly contributing to severe financial strain that prompted major layoffs, including the elimination of over 1,300 positions announced in January 1996 as part of a broader restructuring to address mounting losses. Additional job cuts followed in April 1996, totaling around 2,800 for the year and representing about 16% of the workforce, as the company grappled with quarterly deficits exceeding $740 million. By 1996, Apple's personal computer market share had declined to approximately 5%, down from double digits in the early 1990s, underscoring its diminished competitive standing amid the rise of Windows dominance. The project's August 1996 cancellation, after consuming an estimated $250 million annually and involving 500 engineers, accelerated Apple's pivot to external operating system solutions, most notably the December 1996 acquisition of NeXT for $429 million. This deal facilitated Steve Jobs' return as interim CEO in July 1997 and set the stage for the iMac's August 1998 debut, whose colorful, all-in-one design sold over 800,000 units in its first five months and helped restore profitability by emphasizing user-friendly hardware innovation. Copland's protracted delays and ultimate abandonment deeply undermined confidence in Apple's software ecosystem, leaving developers in limbo after years of anticipation for a protected-memory, multitasking foundation to modernize Macintosh applications. Third-party developers, facing an outdated System 7, increasingly explored alternatives like BeOS, whose multithreaded architecture and media-handling strengths drew significant interest as a potential Mac OS successor during Apple's 1996 vendor evaluations. This erosion of trust manifested in reduced investment in Mac-specific tools and a temporary exodus of talent, exacerbating Apple's isolation in the developer community. Under Jobs' leadership post-acquisition, Apple rebuilt this loyalty by integrating NeXT's developer frameworks into Mac OS X, introducing APIs like Carbon for legacy compatibility and Cocoa for native apps, which by the early 2000s had stabilized the ecosystem and attracted renewed third-party support. On an industry level, Copland exemplified the perils of overly ambitious operating system redesigns, where feature creep—adding advanced elements like dynamic linking and object-oriented subsystems without sufficient testing—inflated scope and timelines, ultimately dooming the effort to internal instability. This high-profile collapse served as a cautionary example for software engineering practices, reinforcing the value of phased releases and modular architectures over wholesale rewrites, lessons that helped contemporaries like Microsoft refine Windows NT's hybrid kernel for reliability without Apple's level of disruption. The project's fallout also spotlighted the vulnerabilities of closed, proprietary development in a competitive landscape, indirectly bolstering momentum for more agile, collaborative models that gained traction in the late 1990s. Retrospective examinations, such as Michael S. Malone's 1999 book Infinite Loop: How Apple, the World's Most Insanely Great Computer Company Went Insane, attribute Copland's downfall to a pivotal realignment at Apple, compelling the company to prioritize synergistic hardware-software integration—a philosophy epitomized in products like the iMac and later iPod—that underpinned its resurgence as a trillion-dollar enterprise.

References

  1. None
  2. Copland: The Mac OS Moves Into the Future - MacTech
  3. Apple's Copland Project - Low End Mac
  4. Copland OS ships to Mac devs: Today in Apple history | Cult of Mac
  5. Copland 2010 revisited: Apple's language and API future
  6. Section 1.1. Apple s Quest for the Operating System | Mac OS X ...
  7. 32 and 16 Years Ago - IEEE Computer Society
  8. Pink: Apple's First Stab at a Modern Operating System - Low End Mac
  9. System 7 transformed the Mac on May 13, 1991 - AppleInsider
  10. Taligent Company History
  11. The Executive Computer; Apple-I.B.M. Venture, With New Leaders ...
  12. SP 94: The Architecture of the Taligent System
  13. The Secrets of Pink, Taligent and Copland - RoughlyDrafted
  14. TECHNOLOGY - Dec. 20, 1995 - Los Angeles Times
  15. System 7 debuts; new OS shakes up Mac | Today in Apple history
  16. System 7: Bigger, Better, More Expandable, and a Bit Slower than ...
  17. System 7.5 and Mac OS 7.6: The Beginning and End of an Era
  18. Troubleshooting Classic Macs and the Classic Mac OS - Low End Mac
  19. Conflict Catcher 3 - TidBITS
  20. Windows 95: One of the Greatest Operating Systems Ever?
  21. Mac at 40: The eras tour - Six Colors
  22. The Cooperative Multitasking Environment (IM: Pr) - Inside Macintosh
  23. Today in Apple history: MultiFinder brings multitasking to Mac
  24. [PDF] M: Introduction to Memory Management - Apple Developer
  25. The Challenges of Integrating the Unix and Mac OS Environments
  26. System Crashes in the Classic Mac OS
  27. A brief history of Mac memory and its management
  28. Copland - ArchiveOS
  29. None
  30. Copland: The Abstract Mac OS (07/1995)
  31. [PDF] Apple Plans Open Licensing for PPC Platform: 12/5/94 - CECS
  32. A Look at Macintosh Multiprocessing - MacTech
  33. Mac's new OS: Seven years in the making - CNET
  34. [PDF] Apple Confidential 2.0 - No Starch Press
  35. COMPANY REPORTS; Apple's Earnings Plungs as Revenues Rise
  36. Unlikely Apple Exec Behind Jobs' Return - Los Angeles Times
  37. Another Delay at Microsoft - The New York Times
  38. Mac's new OS: Seven years in the making - CNET
  39. Gil Amelio gets the boot after terrible quarter: Today in Apple history
  40. 15 years of OS X: How Apple's big gamble paid off - Computerworld
  41. APPLE POSTS 4TH-QUARTER PROFIT - The Washington Post
  42. Steven Jobs Making Move Back to Apple - The New York Times
  43. Apple Kills Clone Market - WIRED
  44. The rap on Apple's Rhapsody system - Variety
  45. [PDF] Apple Computer, Inc. Agrees to Acquire NeXT Software Inc.
  46. Mac OS Copland suffers fatal blow: Today in Apple history
  47. Mac OS 8.0 Copland (Beta Builds) - Macintosh Repository
  48. Apple Copland - Higher Intellect Vintage Wiki
  49. Copland - The Long View
  50. Was Apple's Developer Release DR1 of Copland ever distributed?
  51. ANOTHER CHRP TRANSITION: MAC ROMS SET TO DISAPPEAR ...
  52. Programmer's Introduction to Mac OS 8.5 - MacTech
  53. OS 8 Adds New Life to Mac Platform - The New York Times
  54. Mac OS 8 Copland - WinWorld
  55. Searching for Information About Sherlock - The Vintage Mac Museum
  56. Mac OS 9 - MacTech | The journal of Apple technology.
  57. Mac OS X: An act of desperation that formed the foundation for the ...
  58. Here's to the crazy ones: a decade of Mac OS X reviews - Ars Technica
User Avatar
No comments yet.