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.

Documentation

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.

Downloads

Binary Packages (Version 0.9.3)

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

Source Code (Version 0.9.3)

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

Easy-Start bundles

Download combination RPCEmu, RISC OS and harddisc Easy-Start bundles, featuring full RISC OS 3.71 and RISC OS Direct (5.27) builds.

Contributed Builds

https://github.com/Septercius/rpcemu-dev/releases
  Format Notes
Mac OS X Binary 0.9.3a. A 0.9.3 binary (Timothy Coltman<)

Previous Releases

Additional Downloads

  Format
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.3 - 7/5/2020

Changes in this build

  • Easy-Start bundles
    • Two ROM/Disc Image sets are now available to make setting up RPCEmu as simple as possible. both are configured with networking by default.
      • RISC OS Direct, a version of the RISC OS 5 based distribution with many extras, ideal for running recent applications
      • RISC OS 3.71, an older '26-bit' version of RISC OS, ideal for running 'classic' applications.
    • Both are pre-setup with a large number of applications, tools, and both ship with !Store and PackMan package managers for installing more.
  • ARM
    • Correct several issues related to the MSR instruction
    • Correct several instruction decoding issues
    • Generate undefined instruction exceptions in the correct places of the instruction set
    • Implement ARMv4 (StrongARM) Load store extensions
    • Make ARMv4 extensions only available when configured as ARMv4
  • Floppy Discs
    • We now support loading of DOS and Atari 360KB (.img) disc images into the floppy drives.
  • Other fixes
    • Settings files and CMOS ram files are saved as changes are made to them, so these settings are retained even if the program is closed abnormally.

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

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

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.