Screenshot of RPCEmu

RPCEmu is an emulator of classic Acorn computer systems, such as the Risc PC and A7000. It runs 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.

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.9.1)

  Format Notes
XP Vista 7 8 10
(32/64 bit)
Zip Archive Install to the location of your choice.

Source Code (Version 0.9.1)

  Format Notes
All Platforms Source Code Use this to compile up a version for Linux or OpenBSD, also for Windows.

Contributed Builds

  Format Notes
Mac OS X Binary A 0.8.14 binary (Theo Markettos)

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

Version 0.9.1 - 24/10/2018

Changes in this build

  • User Interface
    • A screenshot can be saved of the current display, by choosing 'Take Screenshot...' from the File menu.
    • Entering full-screen mode displays a reminder of how to leave this mode. The message can be hidden by ticking the checkbox.
    • Choosing 'Reset' or 'Exit' from the File menu will request confirmation before taking the action.
    • The CD-ROM sub-menu has moved to the Disc menu.
  • Networking
    • The EtherRPCEm driver module now works with RISC OS Select 3 or later (4.39 - 6.20).
    • Networking configuration now requires fewer steps to be performed in RISC OS as a result of the following changes. The documentation has been updated to reflect this.
    • The driver module is now provided directly by the networking podule. This means there is no need to install the driver in the Boot sequence.
    • The driver module is now 26/32-bit neutral. This means that there is no need to install an updated SharedCLibrary for the network driver. Note, you may well still need this update for application compatibility.
    • The driver module now auto-installs AutoSense file in Boot sequence.
  • HostFS
    • The Create-Dir, Rename and Save entry points now return an error if part of the path is invalid, instead of saving the file to a wrong location.
  • Keyboard
    • Keys can no longer get 'stuck' if held down when interacting with GUI menus.
  • Other fixes
    • Some potential crash scenarios when resetting/exiting have been fixed.
  • Windows
    • Shift-F10 keypresses are now passed through to the emulated machine, instead of invoking the Windows context menu handler.
    • If you are using a keyboard layout with 'dead keys' (e.g. US-International) these keypresses are now passed through. Dead keys are used to compose accented characters, and are not found on the UK keyboard layout.
    • The Windows executable has Data Execution Prevention (DEP) enabled.

All the keyboard fixes and the enabling of DEP are based on contributions by J. Percival.

Older Release Notes

Full Changelog

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 to) 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 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.