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.
- User Manual - All platforms.
- Networking Guide - Windows/Linux.
- Using ROOL RISC OS 5 - All platforms.
- Tutorial - Installing RPCEmu and RISC OS 3.71 on Windows - on 4corn.
- How to compile from source - Windows
- How to compile from source - Linux
- How to compile from source - OpenBSD
- (Advanced) Tutorial - Running RPCEmu as the Phoebe Risc PC 2 - on 4corn.
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.15)
XP Vista 7 8 10
|Windows Installer||Run the provided .msi file, installs to Program Files. 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.15)
|All Platforms||Source Code||Use this to compile up a version for Linux.|
|Mac OS X||Binary||0.8.13-caliston-dev1.zip. A 0.8.13 binary (Theo Markettos)|
|Blank Pre-Formatted Hard Discs||ADFS E||256MB||1GB|
|ADFS E+ (long filenames,
RISC OS 3.80 or later only)
|Blank Pre-Formatted Floppy Discs||ADFS E||800KB|
|All downloads in Zip format, decompress before use. No download is larger that 1MB.|
Not all features are available on all platforms, check the matrix below for details
|Linux||Solaris||Windows||Mac OS X|
Version 0.8.15 - 26/10/2016
Changes in this build
- All Platforms
- Issue with 8MB VRAM being less stable has been resolved, code is now correctly allowed in the 2-8MB area.
- ARM SWP instruction correctly handles unaligned access.
- Enhancements to TLB to correctly flush caches on more operations.
- The window maximise button has been disabled, as the size of the window is determined by the mode in RISC OS.
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 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.