Screenshot of RPCEmu

RPCEmu emulates an Acorn Risc PC and A7000 on multiple platforms including Windows, Linux and Mac OS X


RPCEmu allows you to emulate classic Acorn systems, such as the Risc PC and A7000, on multiple platforms including Windows, Linux and Mac OS X

RPCEmu requires a RISC OS ROM image to work, find details of where to find one.

RPCEmu should be considered Alpha Quality code. It has many known and unknown bugs, and all files used with it should be well backed up before using them with RPCEmu.


The following documents are available here.

If you have any questions or need help, there is a RPCEmu Mailing List, however please specify the version number to avoid confusion. Your patches, suggestions and even bug reports are gratefully received.


Binary Packages (Version 0.8.11)

  Format Notes
Windows XP/Vista/7/8 Windows Installer Recommended. Run the provided .msi file. Adds links into you 'Start' menu. Note: upgrading from previous versions may overwrite your cmos.ram and rpc.cfg files.
Zip Archive Install to the location of your choice.

Source Code (Version 0.8.11)

  Format Notes
All Platforms Source Code  

Contributed Builds

  Format Notes
Mac OS X Universal Binary rpcemu-spoon-0.8.9-fjd-beta.zip. A 0.8.9 universal binary for x86 and PowerPC. It should run on Mac OS X 10.7 and other versions, but please test "I've only lightly tested it, so success or failure reports are appreciated, particularly if you're running a different version of OS X from me (I'm on 10.7.2).". (Francis Devereux)
RPCEmu Bootable CD Puppy Binary A 0.8.6 binary to update the Puppy Linux live CD. (Paul Stewart)

Previous Releases

Additional Downloads

Blank Pre-Formatted Hard Discs ADFS E 256MB 1GB
ADFS E+ (long filenames,
RISC OS 3.80 or later only)
256MB 1GB
Blank Pre-Formatted Floppy Discs ADFS E 800KB
All downloads in Zip format, decompress before use. No download is larger that 1MB.

Release Notes

Full Changelog

Not all features are available on all platforms, check the matrix below for details

LinuxSolarisWindowsMac OS X

Version 0.8.11 - 23/10/2013

Changes in this build

Version 0.8.10 - 27/3/2013

Changes in this build

Version 0.8.9 - 1/1/2012

Changes in this build

Version 0.8.8 - 19/9/2010

Changes in this build

Version 0.8.7 - 1/9/2010

Changes in this build

This release contains lots of updates to the networking support; as such a new section to the manual has been written explaining how to setup networking on Linux and Windows:


The support for RISC OS 5 has changed a fair amount since the last release. Please see the updated documentation here:


Version 0.8.6 - 23/12/2009

Changes in this build

Version 0.8.5 - 23/08/2009

Changes in this build

Version 0.8.4 - 05/05/2009

Changes in this build

Version 0.8.3 - 15/04/2009

Changes in this build

Version 0.8.2 - 09/02/2009

Changes in this build

Version 0.8.1 - 16/01/2009

Changes in this build

Version 0.8.0 - 30/12/2008

Changes in this build

Developer Information

We're very happy for RPCEmu to accept code and contributions from third parties, already many people have contributed code and we hope to continue down this route.

The RPCEmu source is stored inside the Mercurial version control system, Mercurial clients are available for many platforms, including (but not limited too) Windows, Linux, Mac OS X, Solaris, BSDs. If you are used to a different version control system, such as CVS or SVN, Mercurial (as a distributed version control system) may seem a little odd, but there are plenty of tutorials and advice for users coming from other systems on the web.

The Mercurial repository is based at


and checking out the code is as simple as

hg clone http://www.home.marutan.net/hg/rpcemu rpcemu

How to get code committed into the repository. Prepare a patch file of the differences between your new code and the current 'HEAD' of the project.

Mercurial provides the 'hg diff' command, which generates diff files suitable for this.

Then post this patch file to the mailing list (or to us directly if you so wish), with an explanation of what it's for, and in the case of bug fixes, the bug it's meant to fix (it's not always obvious from the code)

Generally the smaller the patch, with the most specific function or reason, the easier the patch is to merge in, whereas a "I fixed everything I thought was wrong" would take a very long time to verify and test.

Patches may get edited before being committed, or if the changes required are particularly large an updated patch may be requested of the developer. In some rare cases it might not be possible to commit a patch, and at that point there should be a stated reason (e.g. patch overlaps with another patch that deprecates it, patch is too widespread to verify (suggest breaking into smaller patches), etc).

If you have any questions, once again the mailing list is the best place to ask, also, if you're considering a particulaly large change, that would affect a large functional area or many files, it might well be worth getting some advice from the developers on the mailing list first, incase it overlaps with other development work, or even just a suggestion of how to accomplish it in smaller changes.