Fact-checked by Grok 2 weeks ago

Star Trek project

The Star Trek project was a clandestine initiative by Apple Computer in the early 1990s to port the Macintosh operating system, specifically , to 's x86 architecture, enabling it to run on non-Apple hardware such as PC compatibles. Launched on February 14, 1992, as a collaboration between Apple and , the project aimed to counter the rising dominance of by creating a () shell based on Macintosh that could operate atop 's "Panther" operating system. Key figures included Apple VP of Software Engineering Roger Heinen, Apple CEO , who provided support, VP of Marketing , and CEO Andy Grove, whose endorsement facilitated access to x86 hardware like the 486 processor. Technically, the effort involved rewriting 680x0 assembly code from the Macintosh's processors into x86-compatible code, adapting the Pascal-based Macintosh interface, and implementing functions in software to emulate hardware dependencies. By December 1, 1992, a functional had been achieved, demonstrating core components such as the Finder, GX graphics system, and multimedia support on x86 hardware. The project grew to involve around 50 developers across both companies, with development centered in . Despite its progress, was abruptly canceled in June 1993 under new Apple CEO , who prioritized cost-cutting and shifted resources toward porting to the PowerPC architecture in partnership with and . Factors contributing to the termination included Apple's strategic pivot away from x86 compatibility and constraints from PC manufacturers' exclusive contracts with . The project's legacy influenced Apple's later transition to Intel processors in 2005, following the 1997 acquisition of NeXT, as techniques developed for software-based were reused during Apple's transition to processors in 2005–2006. Although no official releases occurred, the prototype's existence was later confirmed through demonstrations and archival efforts, highlighting an early, unrealized vision for cross-platform Macintosh software.

Background and Motivations

Apple's Strategic Context

In the early 1990s, Apple Computer grappled with intensifying competition from Microsoft Windows running on low-cost Intel x86-based PCs, which captured the majority of the personal computer market. Apple's worldwide PC market share reached 10.7% in 1991, a modest increase from 8.6% in 1990, yet this positioned the Macintosh as a niche player amid the explosive growth of Windows-compatible systems. By 1992, Apple's share hovered around 11%, but the company faced relentless pressure from commoditized hardware that undercut Macintosh pricing and availability. These market dynamics underscored the limitations of Apple's proprietary Motorola 68k architecture, prompting strategic shifts toward greater platform flexibility. Under CEO , Apple pursued ambitious initiatives to counter Microsoft's dominance through development, exemplified by the July 1991 alliance with . This partnership birthed Taligent, a focused on creating an independent of specific hardware, intended to enable seamless application portability across platforms. Sculley described the as one that would "launch a in technological innovation," positioning it as a direct challenge to Windows by fostering an ecosystem beyond Apple's hardware lock-in. Taligent, derived from Apple's earlier Pink project, represented Sculley's vision of Apple evolving into a software powerhouse, though it remained distinct from Macintosh-specific efforts. Internally, Apple wrestled with the tension between its closed hardware ecosystem—which ensured but restricted market reach—and the benefits of openness to third-party manufacturers. These debates intensified as exposed scalability limits, highlighting the risks of over-reliance on architecture. Apple's financial pressures further catalyzed these strategic considerations, with slowing growth despite record 1990 revenues of $5.56 billion. In May 1991, the company announced a 10% reduction—eliminating 1,560 positions—and a $95 million charge, signaling vulnerability amid rising competition and inventory issues. These struggles peaked in late 1991, leading to the approval of the Star Trek project as a covert initiative to port Macintosh to x86 hardware, potentially using Novell's as a foundation to enable compatibility with PCs. This timeline reflected Apple's urgent bid to reclaim momentum before deeper fiscal erosion set in.

Novell's Role and Collaboration

Novell acquired in July 1991 for approximately $80 million, gaining control of and positioning it as a direct competitor to Microsoft's in the burgeoning PC operating system market. offered superior features, including built-in multitasking via the TASKMAX utility in version 6.0, which allowed cooperative execution of multiple DOS programs, and enhanced memory management that outperformed contemporaries. Released in 1991, 6.0 received official endorsement from in September of that year and captured about 10% of new OS shipments by late 1990, with sustained momentum into 1991 despite Microsoft's aggressive pricing and compatibility tactics. The anticipated "" iteration, planned as 7.0, was designed to incorporate 32-bit addressing and preemptive multitasking to further erode Microsoft's dominance, though delays prevented its timely release. In February 1992, and Apple formalized their collaboration on the Star Trek project through a joint agreement signed on , under which committed to enhancing with x86-specific optimizations and providing the underlying kernel, while Apple focused on porting the Macintosh , including elements of System 7.1. The deal included shared funding—estimated in the millions from each party—and stringent nondisclosure clauses to maintain secrecy, with development occurring in a leased Santa Clara facility across from 's headquarters. 's contributions centered on integrating 's multitasking and disk compression features to support the ported , aiming to create a OS capable of running on Intel 486 processors. Key Novell personnel driving the technical aspects included engineering leads with deep expertise in x86 architecture extensions, such as those refined for 's 32-bit disk access and virtual device drivers. VP of strategic marketing spearheaded the partnership outreach to Apple CEO , leveraging 's recent acquisition to propose the . These experts, numbering four initially alongside 14 Apple developers, focused on kernel stability and to ensure seamless operation of Macintosh applications atop the enhanced base. Novell's involvement in Star Trek aligned with its overarching ambition to embed advanced networking into consumer computing devices, extending the reach of its dominant platform—which powered over half of corporate networks by —into desktop environments. By fusing with a polished , Novell sought to preemptively integrate NetWare-compatible protocols for and remote access, positioning the resulting OS as a networked alternative to Microsoft's ecosystem and anticipating future consumer demand for connected PCs.

Development History

Project Initiation

The Star Trek project was formally initiated on February 14, 1992—Valentine's Day—under the direction of Apple's then-CEO , as a collaborative effort between Apple Computer and to explore the Macintosh operating system to non-Apple . The initiative stemmed from Apple's strategic interest in broadening the Macintosh platform's compatibility amid competitive pressures in the personal computing market, though detailed motivations were outlined in prior planning discussions, advocated by Apple's Dan Eilers following 's interest. With the blessing of CEO Andy Grove, the project received early support from , focusing on leveraging x86 architecture to demonstrate feasibility. The team began with a small group of four engineers—two from Apple and two from —headed by Apple's Chris DeRossi, drawn primarily from the company's system software development ranks to handle the core porting challenges. This core expanded to approximately 50 engineers, including those from Apple's Advanced Technology Group, enabling accelerated progress on the prototype. Apple's leadership imposed an aggressive deadline of October 31, 1992 (Halloween), for a functional of System 7.1 running as a shell on 486 processors, incentivizing the team with substantial bonuses ranging from $16,000 to $25,000 per engineer upon meeting milestones. To maintain confidentiality, the project adopted the code name "," inspired by the popular science fiction television series, evoking the idea of taking the Macintosh "where no Mac has gone before" into Intel-compatible territory. Engineers operated under strict non-disclosure agreements (NDAs), with isolated workspaces equipped with Macintosh systems to minimize external interactions and prevent leaks about the experimental x86 port. Initial planning emphasized a proof-of-concept approach, prioritizing booting System 7.1 and basic application compatibility on 486 hardware without delving into full production optimizations.

Key Implementation Phases

The key implementation phases of the Star Trek project unfolded from mid-1992 to early 1993, marking the core technical execution following project initiation. The joint Apple-Novell team focused on porting to x86 hardware, including rewriting 680x0 assembly code, adapting the Pascal-based Macintosh interface, and implementing ROM functions in software to emulate hardware dependencies. This effort involved addressing incompatibilities and driver issues for peripherals, as well as performance bottlenecks on 486 processors, such as lags in graphics and networking. A key milestone occurred in December 1992 with an internal demonstration showcasing System 7.1, including the "Welcome to Macintosh" screen, the Finder, QuickDraw GX graphics, and support, running on x86 hardware. By early 1993, further refinements had progressed to a proof-of-concept stage, though persistent hurdles limited broader functionality.

Cancellation and Dissolution

In June 1993, Apple's newly appointed CEO canceled the Star Trek project, overriding the prior support of his predecessor, , and halting all further development. Spindler prioritized Apple's strategic alliance with for the PowerPC processor transition, viewing the x86 port as a distraction from this direction. The cancellation stemmed from a combination of internal politics at Apple, where the project faced resistance from executives skeptical of its potential amid the rapid adoption of Microsoft's in 1992–1993. Doubts about the long-term viability of an x86-based Mac OS in a Windows-dominated PC market further eroded support. Resources were also diverted to the Taligent with , which aimed to create a next-generation , absorbing engineering talent that might otherwise have sustained . Following the decision, the of approximately 50 engineers was disbanded, and existing was archived without public release. , Apple's collaborator, retained full rights to the enhanced developed during the effort and proceeded to market it independently as Novell DOS 7 in 1994, omitting any Apple-specific integrations. The project incurred significant costs for its prototyping efforts, including high expenses related to code porting and hardware access, which contributed to its termination amid budget constraints and cost-cutting measures. However, the abrupt end represented an opportunity loss, delaying Apple's native x86 strategies by over a decade until the 2005 .

Technical Architecture

Software Porting Approach

The Star Trek project's software porting approach was built around adapting Macintosh System 7.1 to run on x86 hardware by positioning it as a shell atop Novell's "," an enhanced iteration of 6.0 that incorporated 32-bit disk access and multitasking extensions to support the Macintosh environment. This layered allowed the familiar Mac interface and applications to operate within an x86-compatible base, aiming to deliver a cost-effective alternative to proprietary Macintosh hardware while leveraging commodity processors. The design emphasized source-level compatibility, meaning developers could recompile existing Macintosh applications for x86 without fundamental rewrites, though full optimization required targeted adjustments. Central to the porting process was the recompilation of Macintosh components, including the ROM-based routines and application programming (APIs), from Motorola 68k to x86 assembly. Since Macintosh ROMs contained essential low-level code for , input handling, and calls, these were translated into software modules loaded at time rather than embedded hardware, avoiding the expense of custom ROM chips. The Mac GUI operated atop the base, providing Macintosh-specific behaviors. The approach prioritized , with a proof-of-concept demonstrating the Finder desktop, GX , multimedia support, and basic API calls achieved by late 1992. Despite these advances, the effort faced limitations, particularly in blending Macintosh elements with a DOS-derived foundation, ultimately contributing to the project's technical and commercial hurdles.

Hardware and Compatibility Features

The Star Trek project targeted 80486 processors as the core hardware platform for the ported Macintosh , leveraging the then-current leading x86 architecture to enable the OS to run on standard PC configurations. Development and testing occurred on 486-based PC clones, including those donated by and representative of IBM PC compatibles from manufacturers like . To ensure broad compatibility, the project aimed to interface with off-the-shelf PC components, facilitating integration into the existing PC ecosystem. Prototypes underwent extensive testing on and PC-compatible systems, demonstrating the ported OS booting successfully and running core components like the Finder . For recompiled Macintosh applications, most software functioned after source-level adjustments, though hardware-dependent apps required further tweaks. This hardware-focused approach complemented the software porting efforts by prioritizing seamless operation on commodity x86 platforms.

Outcomes and Legacy

Immediate Impacts

Following the cancellation of the Star Trek project in mid-1993, Apple reallocated the majority of its engineering resources to the transition from 68k processors to the PowerPC architecture. This shift, driven by new CEO Michael Spindler's prioritization of the PowerPC initiative, allowed Apple to focus on compatibility efforts for the upcoming Macintosh systems based on the new RISC chips. At , the abrupt end to the collaboration led to the abandonment of plans to integrate a Mac-like into . Instead, the company released DOS 7.0 (codenamed Panther) in January 1994, which incorporated enhancements in , disk handling, and networking but lacked the envisioned layer. This version achieved only limited market penetration, failing to make significant inroads against Microsoft's before discontinued active development of the product line in 1994 and later sold the rights to in 1996. The project's termination resulted in the dispersal of the joint team, consisting of approximately 14 Apple engineers and 4 from Novell. Apple personnel received substantial bonuses ranging from $15,000 to $25,000 each, along with a group vacation to Cancun, Mexico, as recognition of their efforts in achieving a functional prototype. However, the sudden halt contributed to lowered morale among the group, with engineers expressing disappointment over the political infighting that ended the work; project leader Roger Heinen, who had departed Apple in January 1993 to join Microsoft. No widespread layoffs were directly tied to the cancellation, though Apple's broader workforce reductions of 16% in July 1993 affected the company amid financial pressures. Mutual nondisclosure agreements between Apple and remained in effect post-cancellation, effectively preventing public disclosure of project details during the . These restrictions held until late 1997, when key aspects of the initiative were revealed in a San Jose Mercury News investigative article, effectively declassifying much of the previously secret and demonstrations.

Long-term Industry Influence

The Star Trek project's pioneering work in porting to x86 hardware demonstrated the technical feasibility of cross-platform OS compatibility, laying early groundwork for Apple's 2005 transition from PowerPC to processors. By achieving a functional that ran key applications like the Finder and on PCs, the effort underscored the potential for software to operate beyond proprietary hardware architectures, informing strategies to mitigate dependency on specific chip vendors during the Intel shift. This focus on portability and techniques from contributed to the conceptual foundations of , Apple's system introduced in 2006 to enable seamless execution of PowerPC applications on Intel-based Macs, and later extended through 2 for x86 compatibility on during the 2020 architecture change. The project's emphasis on source-level adaptations and addressed core challenges in maintaining software ecosystems across generations, directly paralleling the emulation needs in Apple's M-series transition to ARM-based chips. The initiative's outcomes, once revealed in 1997, highlighted the risks of platform lock-in by demonstrating the complexities and costs of tying an OS to a single hardware ecosystem, influencing broader industry discussions on and encouraging a shift toward more flexible, cross-platform solutions in . By exposing the vulnerabilities of closed architectures, Star Trek's legacy contributed to ongoing developments in and portability. The project's extreme secrecy, conducted in a isolated facility with nondisclosure agreements and limited inter-team communication, has become a staple of technology folklore, exemplifying Apple's culture of guarded that persists in modern product development. This cloak-and-dagger approach, including bonuses for engineers upon prototype completion, fostered legends of internal daring that continue to captivate historians. Several team members advanced efforts post-cancellation; notably, Fred Monroe and Fred Huxham founded Fredlabs, Inc., which in early 1997 announced VirtualMac, an emulator for running Mac OS applications on , though development was canceled later that year without a commercial release. From a 2025 perspective, 's legacy remains pertinent amid the maturation of , where 2 facilitates ARM-x86 emulation on M-series chips without major architectural overhauls since the , though the project itself is primarily referenced in retrospective analyses of Apple's failed ventures and successful pivots to custom silicon. No significant updates or revivals have emerged, but its role in proving OS portability underscores ongoing debates in computing history about balancing with .

Related Projects and Concepts

Within Apple

Following the cancellation of the Star Trek project in the early , Apple revisited cross-platform portability concepts in subsequent internal initiatives, adapting lessons from earlier and efforts to support transitions. One notable successor was Project Marklar, an internal effort from 2002 to 2005 that Mac OS X to x86 architecture for testing purposes, ultimately paving the way for the introduction of Intel-based Macs. This project maintained a feature-complete version of the operating system on x86 , allowing Apple engineers to evaluate performance and compatibility without public disclosure, and it directly informed the decision to shift away from PowerPC processors. Unlike Star Trek's foundation on a DOS-based , Marklar leveraged the underlying Mac OS X, focusing on native compilation rather than heavy . To ensure backward compatibility during the Intel transition, Apple released in 2006 as a , enabling PowerPC applications to run seamlessly on x86-based Macs. dynamically translated PowerPC instructions into x86 code at runtime, minimizing developer overhead while delivering near-native performance for most legacy software; it was bundled with and remained in use until being phased out with the release of Mac OS X Lion in July 2011. This approach echoed Star Trek's exploratory 68k-to-x86 translation ideas but succeeded through tighter integration with Apple's evolving software stack. Apple's shift to its own silicon further extended these portability themes during the 2020–2022 transition from x86 to -based chips, with Rosetta 2 serving as an updated emulator for translating x86_64 binaries to instructions. Introduced alongside in November 2020, Rosetta 2 optimized ahead-of-time translation for many apps, allowing software to run on M-series processors with performance losses typically under 20% for common workloads, and it facilitated a smooth rollout across models by late 2022. In June 2025, Apple announced that Rosetta 2 would be phased out starting with macOS 28 in 2028. This iteration closed the loop on decades of architecture experiments, emphasizing emulation as a bridge without relying on external hardware partnerships. Key differences between these post-Star Trek projects and the original initiative lie in Apple's growing , which enabled control over both hardware and software ecosystems, leading to successful transitions that avoided the challenges and internal conflicts that doomed Star Trek. Marklar, , and Rosetta 2 thrived under unified development, contrasting Star Trek's external dependencies and fragmented approach, ultimately reinforcing Apple's ability to iterate on portability without dissolution.

Within IBM

In parallel to Apple's initiative, IBM pursued its own strategies for enhancing compatibility with Windows applications during the early 1990s, driven by the need to counter Microsoft's growing dominance in the PC market. The Win- project, initiated around 1991 and culminating in 1993, aimed to enable seamless execution of Windows 3.x applications on through API translation and emulation layers. This effort integrated a virtualized Windows environment directly into 2.0, released in March 1992, allowing users to run Windows software without switching operating systems, thereby addressing a key barrier to adoption among enterprise customers reliant on Windows apps. Unlike 's focus on porting Apple's proprietary OS to x86 , Win- emphasized within IBM's ecosystem, prioritizing stability and performance for business workloads over consumer-oriented portability. Complementing these compatibility efforts, IBM collaborated with Apple on the Taligent project from 1992 to 1995, a separate aimed at developing a next-generation, . Taligent sought to create a unified platform leveraging architecture, drawing from Apple's earlier project and IBM's concepts, with the goal of supporting multiple hardware architectures and fostering developer portability across IBM and Apple ecosystems. However, the initiative suffered from , internal disagreements on kernel design—such as migrating from Apple's to IBM's—and escalating development costs, leading to its effective dissolution by 1995 without a commercial release. Taligent's ambitions highlighted IBM's broader push for modular, extensible OS designs during this era, contrasting Star Trek's more targeted porting goals by envisioning a entirely new system rather than incremental adaptations. These projects formed part of IBM's wider response to Windows' market lead, culminating in the September 1994 release of , which incorporated enhanced multi-OS capabilities including improved Win-OS/2 support for applications, native and OS/2 multitasking, and preliminary networking features for heterogeneous environments. emphasized enterprise reliability, with features like voice recognition and built-in connectivity, positioning it as a robust alternative for servers and workstations amid Windows 95's impending consumer launch. Ultimately, while Win-OS/2 and Taligent influenced subsequent developments—such as the integration of microkernel elements into , an ambitious but unrealized multi-personality platform— shifted strategic focus away from proprietary OS enhancements by the late 1990s. Facing persistent market challenges, began supporting in 1998, followed by a $1 billion investment announced in October 2000 as a cost-effective, open alternative, and phased out major updates after Warp 4 in 1996. This pivot marked the end of 's intensive multi-platform OS experiments, redirecting resources toward open-source initiatives that better aligned with industry trends.

Other Initiatives

Microsoft's , released in 1993, exemplified a successful multi-platform operating system designed to support diverse architectures including x86, /R4400, and processors. Unlike projects requiring full ports, NT's architecture emphasized a portable with hardware abstraction layers, enabling deployment across these platforms without extensive rewrites; the initial x86 and versions launched on July 27, 1993, followed by Alpha support in September. This approach, driven by lead developer Dave Cutler's focus on portability, allowed NT to achieve broader adoption in environments by prioritizing kernel-level compatibility over comprehensive user interface migration. BeOS, developed in the 1990s by Be Inc., emerged as a media-oriented operating system initially targeted at PowerPC architecture before being ported to x86 in 1998 with its R3 release. Originally conceived for the company's custom BeBox hardware, BeOS prioritized multimedia capabilities, including real-time audio and video processing, symmetric multiprocessing, and a database-like file system to handle large media files efficiently. The x86 port expanded its accessibility to standard PC hardware, aiming to compete in creative workflows by leveraging hardware acceleration for tasks like digital editing, though it ultimately struggled to gain significant market share due to competition from established systems. The Wine project, initiated in , provides an open-source that enables Windows applications to run on operating systems without a full OS rewrite. By implementing the atop POSIX-compliant environments, Wine translates system calls and libraries in real-time, supporting cross-platform execution on , macOS, BSD, and others while avoiding overhead. Evolving continuously to the present, it has facilitated the porting of thousands of Windows programs, including games and productivity tools, by focusing on API compatibility rather than kernel-level changes. In the 2010s, Android's x86 ports addressed portability needs for non-ARM devices, allowing the mobile OS to run on and processors in PCs and netbooks. Projects like , starting with early builds around 2009-2010, modified the ARM-centric kernel and drivers for x86 compatibility, enabling features such as and support on standard hardware. These efforts highlighted ongoing demands for architectural flexibility in mobile ecosystems, supporting use cases from legacy PC revival to systems without requiring native hardware.

References

  1. [1]
    Star Trek: Apple's First Mac OS on Intel Project
    Apr 27, 2014 · The project to bring the Mac OS to the Intel 486 began on Valentine's Day in 1992 and was named Star Trek.
  2. [2]
    Star Trek - ArchiveOS
    Jun 30, 2025 · Star Trek – a hybrid of Apple's Macintosh operating system, made to run as an operating system GUI shell application upon Novell's next in-development version ...
  3. [3]
    Computer Sales Suffered a Rare Drop Last Year - Los Angeles Times
    Jan 21, 1992 · Apple's share of the worldwide PC market leaped to 10.7% in 1991--from 8.6% in 1990--while IBM's fell to 14.8% from 15.2%. And in an indication ...Missing: Macintosh | Show results with:Macintosh
  4. [4]
    Market share of personal computer vendors - Wikipedia
    The annual worldwide market share of personal computer vendors includes desktop computers, laptop computers, and netbooks but excludes mobile devices.Current top vendors market... · Historical vendors market share · 1990s · Unit sales
  5. [5]
    I.B.M. Now Apple's Main Ally - The New York Times
    Oct 3, 1991 · Not to be outdone, John Sculley, Apple's chief executive, said the alliance would "launch a renaissance in technological innovation."
  6. [6]
    Surrender the Pink! - WIRED
    Feb 1, 1993 · The truth is that while Taligent secretly develops its revolutionary system, software developers have been turning to Windows in record numbers.
  7. [7]
    Apple's Copland Project - Low End Mac
    Nov 8, 2005 · Copland was to be an entirely new operating system. Leveraging its experience with the GUI, Apple designed a brand new theme for the operating system, dubbed ...
  8. [8]
    Apple to Trim 1,560 Positions by End of 1991 - Los Angeles Times
    May 21, 1991 · Apple Computer said Monday that it will cut its 15600-person work force by about 10% this year and take a restructuring charge as part of an ...
  9. [9]
    New life for the old 'Star Trek' project - CNET
    Jun 6, 2005 · Networking giant Novell wanted to provide an alternative to Windows by creating a Mac-like interface for its DR-DOS that ran on Intel-based IBM ...
  10. [10]
    Novell Meets Apple: How MacOS Nearly Went Intel in 1992 - Tedium
    Mar 24, 2021 · The endeavor was, internally, called Star Trek (going boldly where MacOS has never gone before and some such), and it had internal support from ...
  11. [11]
    The History of DR DOS - by Bradford Morgan White - Abort, Retry, Fail
    May 19, 2024 · Kildall chose to be quite a bit more friendly and less competitive while Gates very much chose to be competitive and at times a bit ruthless.Missing: Panther | Show results with:Panther
  12. [12]
    Caldera, Inc. v. Microsoft Corp., 72 F. Supp. 2d 1295 (D. Utah 1999)
    On September 23, 1991, IBM officially endorsed DR DOS 6.0, which was scheduled to be released to the public in September or October of the same year. Plaintiff ...
  13. [13]
    The History of Novell - by Bradford Morgan White - Abort, Retry, Fail
    Mar 20, 2024 · ... Apple's CEO, John Sculley, about porting System 7 to the 486. Sculley agreed, and on the 14th of February in 1992, project Star Trek began ...Missing: collaboration | Show results with:collaboration
  14. [14]
    Apple was cautious when it shifted to Intel, and an ARM Mac ...
    Jun 10, 2020 · ... Apple started to move to Intel on February 14, 1992. At John Sculley's direction, the project was started and it was called "Star Trek." The ...
  15. [15]
    Timeline: Milestones in the Mac's history - Computerworld
    Jan 16, 2009 · 1992. A joint Apple/Novell project known as Star Trek, whose purpose is to port the Mac OS to Intel hardware, succeeds with an initial proof ...
  16. [16]
    Apple's Mac Transitions : 68k to PowerPC to Intel to Apple Silicon
    Oct 22, 2023 · But, the Intel Star Trek project would be shut down in 1993 and the majority of the engineering staff moved to work on the PowerPC project.
  17. [17]
    Novell Founder Noorda Pushes Antitrust Suit Against Microsoft
    Jul 25, 1996 · Novell took DR-DOS off the market after Noorda's retirement in 1994, saying the product had not made significant inroads against MS-DOS.
  18. [18]
    The secret weapon Apple threw away - Michael (Mickey) Sattler
    Nov 1, 1997 · It was internal politics, especially the loss of key backers. Star Trek's biggest supporters were Roger Heinen, an Apple vice president hired ...
  19. [19]
    COMPANY NEWS; Apple Cutting Its Work Force 16% Worldwide
    Jul 7, 1993 · In May 1991, the computer maker cut 10 percent of its work force, and that same quarter it took a $224 million special restructuring charge. But ...
  20. [20]
    https://www.macworld.com/article/2826153/goodbye-intel-the-chips-keep-changing-but-the-mac-remains-the-mac.html
  21. [21]
    How 30 years of chip transitions paved the way for the spectacular ...
    Jun 25, 2025 · That kind of institutional memory was vitally important to Apple's transitions in 2005 and 2020, as it turned out. The original Mac came ...<|control11|><|separator|>
  22. [22]
    Star Trek project - Wikipedia
    Star Trek is the code name that was given to a secret prototype project, running a port of Macintosh System 7 and its applications on Intel-compatible x86 ...
  23. [23]
    A Bit of History Behind the Mac OS X on Intel Project "Marklar"
    Jun 10, 2012 · A post by the wife of a former Apple employee at Q&A site Quora fills in some fascinating details about the Mac OS X on Intel project.
  24. [24]
    Apple Keeps x86 Torch Lit with Marklar - eWeek
    Aug 30, 2002 · Apples current efforts come nearly a decade after the company grounded its “Star Trek” program, a collaboration with Novell to develop the Macs ...
  25. [25]
    Apple's x86 OS named, sized - The Register
    Sep 2, 2002 · But now a report at eWeek confirms its existence, status and staffing levels. Nick de Plume and Matt Rothenberg report that an x86 version of " ...
  26. [26]
    Marklar - x86 OS X - MacRumors
    Aug 30, 2002 · This is not the first time Apple has looked to an x86 port of Mac OS. Project "Star Trek" accomplished the same with an older version of Mac OS.
  27. [27]
    The amazing true story of Project Marklar; how Mac OS X for Intel ...
    Jun 10, 2012 · Intel-based Macs running both Mac OS X and Windows will be good for Apple – June 10, 2005. Related. eWeek adds to Marklar (OS X on x86) rumors ...
  28. [28]
    Notes on Apple's Rosetta Technology - MacRumors
    Jan 13, 2006 · ... Rosetta. Rosetta is the emulator (translator) that allows current Mac (PowerPC) programs to run under the new Intel processors. Apple has ...
  29. [29]
    Bombs Away - Daring Fireball
    Jun 8, 2005 · ... binary. Behind the scenes, Rosetta translates and executes the PowerPC binary code. Rosetta runs in the same thread of control as the ...<|control11|><|separator|>
  30. [30]
    How x86 to arm64 Translation Works in Rosetta 2 - InfoQ
    Nov 30, 2020 · Apple started to use binary translation technology for the first time in 2006, when they began switching from PowerPC CPUs to x86. Based on ...
  31. [31]
    Apple on x86 rumors…yet again - Ars Technica
    Aug 31, 2002 · Aside from the iTablet, this is the Apple rumor that just won't die. eWeek is the latest to print an OS X on x86 story, but unlike previous ...
  32. [32]
    Apple announces Mac transition to Apple silicon
    Jun 22, 2020 · Apple today announced it will transition the Mac to its custom silicon to deliver industry-leading performance and powerful new ...
  33. [33]
    About the Rosetta translation environment - Apple Developer
    Rosetta is a translation process that allows users to run apps that contain x86_64 instructions on Apple silicon. Rosetta is meant to ease the transition to ...
  34. [34]
    Rosetta 2 is Apple's key to making the ARM transition less painful
    Jun 26, 2020 · Rosetta 2 will allow apps built for Intel chips to run on Apple's new processors without any work from the developer.
  35. [35]
    A brief history of architecture transitions - The Eclectic Light Company
    May 17, 2025 · To enable its new Macs to run apps built for Intel x86 processors, Apple returned to code translation in Rosetta 2, bundled in macOS 11 and ...
  36. [36]
    (PDF) Impacts of Apple's M1 SoC on the Technology Industry
    ... In 2020, Apple made a major shift in its computing architecture by transitioning from Intel processors to its customdesigned Apple Silicon chips based on ...
  37. [37]
    When Apple Decided to Stop Relying on Intel Chips - Arthnova
    Discover why Apple stopped relying on Intel and built Apple Silicon ... Apple's shift inspired the tech industry to pursue custom chips and vertical integration.Missing: 2020-2022 | Show results with:2020-2022
  38. [38]
    The Mac's Successful Transition to Apple Silicon: A Five-Year ...
    Jun 27, 2025 · This bold move aimed to enhance performance, improve energy efficiency, and ultimately provide a more seamless integration between hardware and ...<|separator|>
  39. [39]
    OS/2 2.0
    When IBM officially released OS/2 version 2.0 on March 31, 1992, it was not entirely unexpected. In fact, 32-bit OS/2 had been promised since the very beginning ...<|control11|><|separator|>
  40. [40]
    OS/2 Timeline
    OS/2 2.0 was officially released on March 31, 1992, so that IBM could say it was released in the first quarter of 1992. Obviously customers didn't see the ...
  41. [41]
    Half an operating system: The triumph and tragedy of OS/2
    Nov 29, 2019 · This enabled IBM to release OS/2 2.0 in April of 1992, a month after Microsoft launched Windows 3.1. Game on. OS/2 2.0 was a big step forward ...
  42. [42]
    TECHNOLOGY - Dec. 20, 1995 - Los Angeles Times
    Dec 20, 1995 · Taligent was formed in 1992 to develop a new operating system based on “object-oriented” design, in which parts of programs stand on their own ...
  43. [43]
    The Executive Computer; Apple-I.B.M. Venture, With New Leaders ...
    Mar 8, 1992 · Taligent is an independent joint venture of Apple Computer Inc. and the International Business Machines Corporation, with a mandate to develop ...
  44. [44]
    Workplace OS History: IBM's $2 Billion Microkernel of Failure - Tedium
    Feb 28, 2019 · So what about Taligent, Apple's collaboration with IBM? Well, that joint venture faced a lot of challenges, many of which were caused by the ...
  45. [45]
    OS/2 Warp
    In October 1994 IBM released OS/2 Warp, the most popular version of OS/2 and arguably one of the coolest operating systems ever.
  46. [46]
    Thirteen Months That Changed IBM - IBM Newsroom
    Sep 11, 2020 · IBM, though, recognized the operating system's potential and started our Linux initiative in September 1998. The 13 months that followed not ...
  47. [47]
    A strong history and commitment to open source - IBM
    In the late 1990s, IBM supported Linux with patent pledges, a $1 billion investment of technical and other resources, and helped to establish the Linux ...Missing: pivot OS/ 2
  48. [48]
    Windows NT 3.1 - BetaWiki
    Oct 12, 2025 · On 27 July 1993, Windows NT 3.1 was released for x86 and MIPS, followed by the DEC Alpha version in September. The Workstation version was sold ...
  49. [49]
    Microsoft's pivotal Windows NT 3.5 release made it a serious ...
    Sep 21, 2025 · Microsoft offered NT 3.5 builds for MIPS CPUs, DEC's Alpha chips, and even later PowerPC processors, reflecting Cutler's obsession with ...
  50. [50]
    BeOS - BetaWiki
    Mar 16, 2025 · BeOS is a discontinued operating system, first developed by Be Inc. It was originally developed for AT&T Hobbit-based systems but later ported to the PowerPC- ...
  51. [51]
    https://www.winehq.org/about/
  52. [52]
    About Wine - WineHQ
    Wine (originally an acronym for "Wine Is Not an Emulator") is a compatibility layer capable of running Windows applications on several POSIX-compliant operating ...
  53. [53]
    https://www.android-x86.org/changelog.html
  54. [54]
    Porting Android to x86
    2010-09-13: 3G USB dongle support is added to froyo-x86 branch. 2010-09-06: Wifi support in froyo-x86 branch is ready. 2010-08-23: Target 'eeepc' is available ...
  55. [55]
    Breathing New Life into Old PCs and Laptops - Android-x86
    ARM Devices – Android-x86 only supports PCs/laptops with x86 processors from Intel and AMD. ARM-based systems need official Android ports tailored to their ...Missing: portability | Show results with:portability