RPCEmu and RISC OS 5 on Mac OS X (changes)

Showing changes from revision #16 to #17: Added | Removed | Changed

Introduction

History, RISC OS 5 and software compatibility

Early ARM processors had a combined 26-bit program counter and status register, rather than separate 32-bit program counter and status registers.

For a time processors had both 26-bit and 32-bit modes, with the former being phased out by ARM. In October 2002 RISC OS 5 was released using only the 32-bit mode, required because 26-bit mode processors were no longer available – the last being the StrongARM used in the RiscPC.

Most software written in BBC BASIC has no compatibility issues, and in many cases software written in C merely requires a recompilation of the source code, where available. However, some software is reliant on features specific to 26-bit mode and needs updating before it will work.

A RISC OS 5 ROM upgrade is available to install on real hardware (Risc PC/A7000/A7000+). The following installation notes will allow you to run RISC OS 5 under emulation on an Apple Mac running macOS.

Installing RPCEmu from scratch

A development build of RPCEmu 0.9.3 0.9.4 for 64-bit versions of macOS is now available. This build is known to work on macOS Mojave 13 (10.14), Ventura macOS Catalina (10.15) and macOS Big 14 Sur Sonoma. (11.2).

If you have an older version of RPCEmu already installed, see Upgrading from an older version of RPCEmu below.

Installation

1. Download the zip archive of RPCEmu 0.9.3a 0.9.4a – be sure to get the ZIP archive, not the DMG package.
2. Open the zip archive, and copy the applications “RPCEmu-Interpreter” and “RPCEmu-Recompiler” to the Applications folder (either drag them over the Applications entry in the Finder sidebar, or onto the Applications folder on the dock).
3. Create a data folder within your Documents folder (e.g. Documents/RPCEmu) and copy the contents of the “Data” directory from the RPCEmu distribution archive.
4. Download an IOMD ROM image from the downloads page. The recommended ROM is labelled IOMD 5.28 5.30 stable (softload).
5. Unpack the ROM archive and copy the file “riscos” from /soft/!Boot/Choices/Boot/PreDesk/!!SoftLoad/riscos soft/!Boot/Resources/SoftLoad/riscos into the Documents/RPCEmu/roms directory. The other files aren’t needed and can be discarded.
6. Download a HardDisc4 image from the Miscellaneous downloads page. The recommended version is labelled HardDisc4 (self-extracting) – this should give you a file called “HardDisc4.5.28.util”. “HardDisc4.5.30.util”.
7. Copy this file to Documents/RPCEmu/hostfs as “HardDisc4-util,ffc” – take care to keep add the,ffc (comma ffc) ending which will be translated by RPCEmu to produce the metadata filetype for RISC OS.

Note 1: RISC OS 5 beta versions are updated frequently with nightly builds from the Git repository but may contain bugs, so important data should only be trusted to the stable installs.
Note 2: RPCEmu is deemed alpha quality by its authors, which rather negates any comments about stable installations in note 1. In practice, many people use RPCEmu without issue.
Note 3: If you choose to use a beta ROM it is best to use the matching beta HardDisc4 as changes in the ROM may require specific disc based components.

Configuration

Networking

The explanation over on the RPCEmu web site works reliably on the NAT option, but the bridging option is untested.

Emulator configuration
Run RPCEmu and open the networking configuration (up on title bar)

1. Click Settings
2. Click Networking
3. Select the “Network Address Translation” option and click OK.
   The Emulator will restart.

RISC OS Networking Configuration
When RISC OS has rebooted, click the “Menu” (middle) button on the mouse over the Switcher icon (cog on the right of the icon bar – bottom right of screen) and the select the Configure option in the menu.

1. Click the Network icon in the window that appears.
2. Click the Internet icon in the window that appears.
3. Click Enable TCP/IP Protocol Suite, then click the Interfaces icon.
4. In ‘Interfaces’ make sure EtherRPCEm is selected and click the Configure… button.
5. Choose DHCP; and Click Set. The window closes.
6. Click the close option in the Interfaces window.
7. Click the close option in the Internet window.
8. Click Save in the Network window.
9. Click “Reset now” in the window that appears.

Testing
After the reboot press Ctrl and F12 simultaneously to reach a task window showing a command prompt.

• Type ifconfig -a
  The response should show the rpcem0 interface has an address of 10.10.10.10
• Type ping -c 1 10.10.10.2 to establish that the virtual router created by RPCEmu is working (the -c 1 limits to one ping packet otherwise the action continues until you press Escape). You cannot ping any IP except the virtual router (10.10.10.2) as the current NAT setup does not forward ICMP
• Type gethost www.google.com
  The response gives the IP address of the www server at google.com domain
• Type gethost -t www.google.com
  The response will now include the time it took for your DNS server to respond.
• Type gethost -x -t 8.8.8.8
  The response will give the hostname (it’s dns.google) of the address you typed, and the last line will be the time it took for your DNS server to respond.

Limitations

• The emulator does not support IDE hard discs or CDROM. The OS does, but the emulator has a data loss bug.
• If you do not configure the emulator to use 2MB VRAM, you may get redraw issues in the RISC OS desktop.
• Restarting RISC OS will not work (“Bad PC” error) if you have less than 256MB RAM configured. Workaround: Select 256MB RAM in RPCEmu Preferences.
• As stated at the top: RISC OS 5 uses the processor in 32 bit mode. Legacy 26 bit applications will first need updating, or Aemulor used for any that can’t be updated.

Networking limitations

• Using the NAT option you are hidden from your local network, so sharing of resources between the emulator and other computers on the network does not work.
• The NAT setup uses one specific IP in a /24 subnet (10.10.10.0/24) – if your local network uses this same range this networking setup will not work. Change your router settings to use a different IP range.

Upgrading from an older version of RPCEmu

• Obtain the RPCEmu distribution archive RPCEmu-0.9.3a-Release.zip RPCEmu-0.9.4a-Release.zip as mentioned above.
• Delete (or move elsewhere) your existing versions of “RPCEmu-Interpreter” and “RPCEmu-Recompiler” – they are most likely to be installed in the “Applications” folder.
• Install the updated versions of “RPCEmu-Interpreter” and “RPCEmu-Recompiler” in the Applications folder.
• In your existing Data directory, create a “netroms” folder (alongside “hostfs”, “poduleroms” and “podules”).
• Copy “EtherRPCEm,ffa” from the “netroms” folder of your RPCEmu distribution archive to the “netroms” folder you just created.
• Open the Applications folder, right-click on “RPCEmu-Recompiler” “RPCEmu-Interpreter” and choose “Open”. Acknowledge the warning screen(s) that appear.
• Double-click on “RPCEmu-Recompiler” “RPCEmu-Interpreter” to launch RPCEmu. This should load to theRISC OS desktop.
• You may need to enable networking, as explained above.
• If you are using an Intel-based Mac, repeat the previous 3 steps for RPCEmu-Recompiler.

After starting RPCEmu, you may discover that “mouse capture” mode is not working properly. To fix this, proceed as follows:

• Go to System Preferences > Security & Privacy > Privacy > Accessibility and untick the entry for “RPCEmu-Recompiler”. “RPCEmu-Interpreter”.
• Close the System Preferences window.
• Start RPCEmu-Recompiler RPCEmu-Interpreter and untick “Follow Host Mouse” so that macOS is aware that RPCEmu wants to control the computer.
• Reopen System Preferences > Security & Privacy > Privacy > Accessibility and tick the entry for “RPCEmu-Recompiler”. “RPCEmu-Interpreter”.
• Repeat If you are using an Intel-based Mac, repeat the above process for “RPCEmu-Interpreter”. “RPCEmu-Recompiler”.

Usage notes

Keyboard

Go to Mac “System Preferences > Keyboard > Keyboard” and tick “Use F1, F2 etc. keys as standard function keys”. Also, go to “System Preferences > Keyboard > Shortcuts” and check that you don’t have anything mapped to F12. You may also need to move (or disable) some or all of Ctrl-F1 to Ctrl-F8, as they can prevent the use of the corresponding keyboard shortcuts in RISC OS.

If you have an extended keyboard (with numeric keypad):

• F13 is Print Screen
• F14 is Scroll Lock
• F15 is Break
• The “X in a square” key below F16 is Num Lock.

Also with the extended keyboard, move some of the Mac keyboard shortcuts so that they don’t clash with RISC OS usage. A suggested layout is:

Downloading and transferring software

RISC OS uses a special format of ZIP archive: if these are unpacked under macOS, the individual files will lose their filetypes. The correct process is to copy the ZIP file into the HostFS folder inside the RPCEmu data directory and unpack it from RISC OS.

Tip: Go to Safari preferences and untick “Open safe files after downloading”. This will prevent macOS from unpacking the ZIP file.¹

¹ If you prefer to leave the option ticked, the ZIP file is moved to the Bin after unpacking, so can still be moved to the HostFS folder.

Other notes

• If you want to change Data directories, hold down Shift when starting RPCEmu.
• To exit full-screen mode, use Ctrl-Cmd-downarrow (not Ctrl-End).
• Selecting “2-button mouse” causes the CMD key to behave as MENU.
• Mouse pointer stuck in window? Go to Mission Control (e.g. Fn-F3), move the mouse pointer elsewhere on the screen and click a mouse button.
• UnTarBZ2 will not work if you try to decompress to HostFS. Instead, create a RAM disc large enough to hold the decompressed files and decompress there.