A new BeOS workstation could be exciting and inconvenient at the same time. Christian Bauer had moved from his Amiga 4000 to a BeBox, a machine whose two processors and new operating system appealed to him. That did not make the Mac applications people wanted to use disappear.
SheepShaver put a Mac environment inside that other desktop. Its original PowerPC-hosted form could execute guest code on the real processor. After Be’s decline, its source code and later CPU emulation carried it far beyond the commercial product sold in 1998.
In our interview with Bauer, he explains the difficult interrupts behind the familiar Mac screen and the IRC joke behind a very unfamiliar name.

Explore the history
From ShapeShifter to a PowerPC Mac
ShapeShifter had already let an Amiga run Macintosh software. Both machines used Motorola’s 68k family, allowing Bauer to adapt the guest system’s input and output rather than simulate every part of a Mac.
The name of the next project began as somebody else’s joke. A friend in a German Amiga IRC channel suggested SheepShaver as a pun on ShapeShifter. Bauer thought it was funny enough to keep. The original ShapeShifter and Basilisk names had come from characters in Archon, one of his favorite games.
The PowerPC Mac brought a different problem. It still had to support existing 68k Mac software, and its early nanokernel handled the transition between pieces of that environment. Interrupts passed through that layer. Getting them to work reliably became Bauer’s particular headache.
A Mac desktop that appeared on screen was not enough. Software had to keep receiving the events and timing behavior that made it usable. A window that stopped responding would rather quickly spoil the pleasure of seeing it open.
1998: a commercial product for BeOS
SheepShaver first appeared commercially for BeOS in 1998, initially as shareware and later through BeDepot, according to the official FAQ. Bauer’s January 26 news entry already linked it. Christian Bauer and Marc Hellwig are credited together in the project’s historical change record.
The program’s original audience wanted useful Mac software inside a BeOS machine. On a PowerPC host, the guest’s instructions did not need a software PowerPC CPU. Bauer preferred the description “runtime environment,” partly because “emulator” made many people expect something painfully slow.
People who has used hardware-level emulators for home computers and consoles were used to needing a machine several times more powerful than the original to get it running smoothly.
Christian Bauer, Retro Replay interview.
His terminology describes the original approach. Modern SheepShaver can also include CPU emulation when the host is not a PowerPC machine. Those two phases should not be collapsed into the claim that every version always ran natively.
The host and guest could share a screen while remaining different operating environments. Running an old application beside a BeOS program was the attraction. The work beneath that convenience involved patching the guest system and supplying the services it expected.

2001–2002: freeware first, source code afterward
On March 31, 2001, Bauer announced SheepShaver 2.1 for BeOS as freeware. The price had changed. The subsequent release of the source was a separate event, not another name for the same announcement.
The preserved history file dates version 2.2 to February 4, 2002, recording the GPL source release and integrated code from Basilisk II. The official FAQ connects that reopening to Be’s demise.
The commercial home for the original program was disappearing. Available source gave other developers the opportunity to change its future, including the large task of serving machines that did not share the guest’s CPU architecture.
Basilisk II remained a close relative in the code. The projects targeted different generations of Mac software, but could share support work. Their later repositories preserve that relationship rather than treating the programs as completely isolated inventions.
2003–2006: the processor becomes software too
The historical change record dates a first public test release with a PowerPC CPU emulator to November 25, 2003. That milestone comes well after the original 1998 commercial version. It opened a different route through the program for non-PowerPC hosts.
The following years brought ports as well as fixes. The same record lists Mac OS X work in 2004, a Windows port in 2005, and an Intel Mac port with JIT support in 2006. These were distinct steps, carried out after the source release, rather than capabilities that should be credited to the first BeOS build.
Gwenolé Beauchesne helped drive the later development and porting, as the E-Maculation project history records. Other contributors continued the work. The improvements included the sorts of problems a user notices immediately: installation failures, display behavior, networking, and copying text between environments.
A working copy of an application could depend on any of those details. A program that launched but could not reliably receive input, read its files, or exchange a document was still a frustrating machine to use.
Mac OS 9.0.4 is a boundary, not Mac OS X
SheepShaver’s official page lists support through Mac OS 9.0.4 and explicitly excludes Mac OS X as a guest. A modern host running SheepShaver is not a route to every operating system that Apple ever released.
That limit helps explain its relationship to Basilisk II. The latter reconstructs a 68k Mac environment. SheepShaver reaches into the PowerPC era. Choosing between them starts with what a particular application needs, not which project has the more recent download.
The guest system and ROM remain separate from the emulator code. The official project documentation explains those requirements. The ability to download source freely does not mean that a complete installed Mac environment is included with it.
Bauer’s original technical explanation is useful here. The familiar desktop can hide very different arrangements underneath: native guest instructions on one host, software CPU emulation on another, and a patched operating system in both cases.
The later community keeps the window opening
E-Maculation’s history records Beauchesne suspending his work in 2008, followed by continued volunteer fixes and features. Its forums and guides became an important place to find builds and compare setup problems.
The kanjitalk755 macemu fork documents newer hosts and SDL2-based build requirements for both SheepShaver and Basilisk II. The shared repository also makes the relationship between the programs visible to somebody exploring the code today.
For a new user, the official project page is a useful signpost into that community. Its old BeOS references remain part of the record, even when the program is now being started inside a very different computer.
Bauer still has his BeBox running, he told Retro Replay. SheepShaver’s later users no longer need to share his original workstation to meet the project, though its name still carries the joke from an Amiga IRC conversation.
More from Retro Replay
- Christian Bauer interview
- Christian Bauer’s biography and timeline entries
- Frodo: from SID music to the portable C64
- Basilisk II: the classic Mac leaves its original hardware
- The history of UAE
- The complete emulation history
Sources and further reading
- Christian Bauer’s Retro Replay interview: firsthand recollections, October 2026.
- Bauer’s dated news archive: release notices, ports, and project milestones.
- Official SheepShaver page and FAQ: 1998 commercial origin, the later GPL release, and guest limits.
- Preserved SheepShaver change history: dated GPL, CPU-emulation, and platform-port milestones; credits Bauer and Hellwig.
- E-Maculation history and guides: later development and community support.
- Later macemu fork: newer build arrangements for SheepShaver and Basilisk II.
Retro Replay Retro Gaming History, Reviews & Emulation
