RISC OS (/rɪsk.ˈɛs/)[4] is a computer operating system originally designed by Acorn Computers Ltd in Cambridge, England. First released in 1987, it was designed to run on the ARM chipset, which Acorn had designed concurrently for use in its new line of Archimedes personal computers. RISC OS takes its name from the reduced instruction set computer (RISC) architecture it supports.

RISC OS
RISC OS cogwheel logo
A screenshot of RISC OS 4
DeveloperAcorn Computers

Open-source (version 5)

Proprietary (versions 4 & 6)

Written inBBC BASIC, C, C++, assembly language
Working stateCurrent
Source modelClosed source; open source for some versions since 2018
Initial release25 September 1987; 36 years ago (1987-09-25)[1]
Latest release
  • 5.30[2] / 27 April 2024; 4 days ago (2024-04-27)
  • 6.20 / 1 December 2009; 14 years ago (2009-12-01)
Latest preview5.31
Marketing targetAcorn personal computers
Available inEnglish
Update methodFlash ROM, OTP ROM, or loadable ROM image
Package managerPackMan, RiscPkg
PlatformsARM
Kernel typeMonolithic
Default
user interface
GUI
License
Preceded byMOS
ARX (discontinued)
Official websiteriscosopen.org RISC OS Open
riscos.com RISCOS

Between 1987 and 1998, RISC OS was included in every ARM-based Acorn computer model, including the Acorn Archimedes line, Acorn's R line (with RISC iX as a dual-boot option), RiscPC, A7000, and prototype models such as the Acorn NewsPad and Phoebe computer. A version of the OS, named NCOS, was used in Oracle Corporation's Network Computer and compatible systems.

After the break-up of Acorn in 1998, development of the OS was forked and continued separately by several companies, including RISCOS Ltd, Pace Micro Technology, and Castle Technology. Since then, it has been bundled with several ARM-based desktop computers such as the Iyonix PC[5] and A9home. As of March 2017, the OS remains forked and is independently developed by RISCOS Ltd and the RISC OS Open community.

Most recent stable versions run on the ARMv3/ARMv4 RiscPC, the ARMv5 Iyonix,[6] ARMv7 Cortex-A8 processors[7][8] (such as that used in the BeagleBoard and Touch Book) and Cortex-A9 processors[9] (such as that used in the PandaBoard) and the low-cost educational Raspberry Pi computer.[10][11][12] SD card images have been released for downloading free of charge to Raspberry Pi 1, 2, 3, & 4 users with a full graphical user interface (GUI) version[13] and a command-line interface only version (RISC OS Pico, at 3.8 MB).[14]

History

The first version of RISC OS was originally released in 1987 as Arthur 1.20. The next version, Arthur 2, became RISC OS 2 and was released in April 1989. RISC OS 3.00 was released with the A5000 in 1991, and contained many new features. By 1996, RISC OS had been shipped on over 500,000 systems.[15]

Acorn officially halted work on the OS in January 1999, renaming themselves Element 14. In March 1999 a new company, RISCOS Ltd, licensed the rights to develop a desktop version of RISC OS from Element 14, and continued the development of RISC OS 3.8, releasing it as RISC OS 4 in July 1999. Meanwhile, Element 14 had also kept a copy of RISC OS 3.8 in house, which they developed into NCOS for use in set-top boxes. In 2000, as part of the acquisition of Acorn Group plc by MSDW Investment, RISC OS was sold to Pace Micro Technology,[16] who later sold it to Castle Technology Ltd.

In May 2001, RISCOS Ltd launched RISC OS Select, a subscription scheme allowing users access to the latest RISC OS 4 updates. These upgrades are released as soft-loadable ROM images, separate to the ROM where the boot OS is stored, and are loaded at boot time. Select 1 was shipped in May 2002, with Select 2 following in November 2002 and the final release of Select 3 in June 2004. In the same month, RISC OS 4.39, dubbed RISC OS Adjust, was released. RISC OS Adjust was a culmination of all the Select Scheme updates to date, released as a physical set of replaceable ROMs for the RiscPC and A7000 series of machines.

Meanwhile, in October 2002, Castle Technology released the Acorn clone Iyonix PC. This ran a 32-bit (in contrast to 26-bit) variant of RISC OS, named RISC OS 5. RISC OS 5 is a separate evolution of RISC OS based upon the NCOS work done by Pace. The following year, Castle Technology bought RISC OS from Pace for an undisclosed sum. In October 2006, Castle announced a shared source license plan, managed by RISC OS Open Limited, for elements of RISC OS 5.

In October 2018, RISC OS 5 was re-licensed under the Apache 2.0 license.[17]

In December 2020, the source code of RISC OS 3.71 was leaked to The Pirate Bay.[citation needed]

Supported hardware

Versions of RISC OS run or have run on the following hardware.

RISC OS compatible hardware
MachineARM architectureIntroducedAcorn versionRISCOS Ltd versionCastle Technology, RISC OS Open version
FirstLastFirstLastFirstLatest
ARM with 26-bit program counter
Acorn ArchimedesARMv21987–19920.203.1x
ARM with 26- & 32-bit program counter
Acorn Risc PCARMv3 / v41994[18]3.50[18]3.714.006.20[19]5.155.30[20]/5.31
Acorn A7000 and A7000+ARMv31995[21] – 1997[22]3.60[21][22]
Acorn Phoebe (cancelled)ARMv419983.80 (Ursula)
MicroDigital Medi[23]ARMv31998[24]3.71[24]4.026.20
MicroDigital Mico1999[25]4.03[25]4.39[19]
RiscStation R75001999[26]4.03[26]4.39[19]
Castle Kinetic RiscPCARMv42000[27]4.036.205.19[28]5.30[20]/5.31
MicroDigital Omega2003[29]4.03[30]4.39[19]
Advantage Six A75ARMv32004[31]4.39[32]
ARM with 32-bit program counter
Iyonix Ltd Iyonix PCARMv5TE20025.015.30[33]/5.31
Advantage Six A9 (Home/RM/Loc)ARMv5TE20054.42[19]
BeagleBoard[7]ARMv7-A20085.155.30[34]/5.31
IGEPv2[35]2009
DevKit8000?
Always Innovating Touch Book2009
OpenPandora's Pandora20105.17[36]
PandaBoard[37]20115.175.30[9]/5.31
Raspberry Pi (1 - 4 and compatible)[11][38][39][40]ARMv6, v7-A, v8-A20125.195.30/5.31
IGEPv5[41]ARMv7-A20145.235.30/5.31
Wandboard Quad[42][43]20155.215.31
Titanium[44]5.235.30/5.31
Pinebook[45]ARMv8-A20175.275.31

RISC OS Open Limited adopted[46] the 'even numbers are stable' version numbering scheme post version 5.14, hence some table entries above include two latest releases – the last stable one and the more recent development one.

A special cut down RISC OS Pico (for 16MiB cards and larger) styled to start up like a BBC Micro was released for BASIC's 50th anniversary.[47]

RISC OS has also been used by both Acorn and Pace Micro Technology in various TV connected set-top boxes, sometimes referred to instead as NCOS.

RISC OS can also run on a range of computer system emulators that emulate the earlier Acorn machines listed above.

RISC OS capable hardware emulators
EmulatorMachines emulatedHost platforms supportedLatest release
!A310Emu[48]ArchimedesRISC OS0.59
Archie[49]DOS, Windows0.9 – 10 February 2001
ArchiEmu[50]RISC OS0.53.3 – 7 December 2014
ArcEm[51]Windows, Linux, macOS, RISC OS1.50.1 – 18 December 2015
Arculator[52]Windows, Linux2.2 – 24 June 2023
Virtual A5000Windows1.4
Red Squirrel[53]Archimedes, Risc PC, A70000.6 – 28 October 2002
RPCEmu[54]Risc PC, A7000, PhoebeWindows, Linux, macOS, OpenBSD0.9.4 – 30 October 2021
VirtualRPCRisc PCWindows, macOS5 September 2014[55]

Features

OS core

The OS is single-user and employs cooperative multitasking (CMT).[56] While most current desktop OSes use preemptive multitasking (PMT) and multithreading, RISC OS remains with a CMT system. By 2003, many users had called for the OS to migrate to PMT.[57] The OS memory protection is not comprehensive.[58][59]

The core of the OS is stored in ROM, giving a fast bootup time and safety from operating system corruption. RISC OS 4 and 5 are stored in 4 MB of flash memory, or as a ROM image on SD Card on single board computers such as the Beagleboard or Raspberry Pi, allowing the operating system to be updated without having to replace the ROM chip. The OS is made up of several modules. These can be added to and replaced, including soft-loading of modules not present in ROM at run time and on-the-fly replacement. This design has led to OS developers releasing rolling updates to their versions of the OS, while third parties are able to write OS replacement modules to add new features. OS modules are accessed via software interrupts (SWIs), similar to system calls in other operating systems.

Most of the OS has defined application binary interfaces (ABIs) to handle filters and vectors. The OS provides many ways in which a program can intercept and modify its operation. This simplifies the task of modifying its behaviour, either in the GUI, or deeper. As a result, there are several third-party programs which allow customising the OS look and feel.

File system

The file system is volume-oriented: the top level of the file hierarchy is a volume (disc, network share) prefixed by the file system type. To determine file type, the OS uses metadata instead of file extensions. Colons are used to separate the file system from the rest of the path; the root is represented by a dollar ($) sign and directories are separated by a full stop (.). Extensions from foreign file systems are shown using a slash (example.txt becomes example/txt).[60] For example, ADFS::HardDisc4.$ is the root of the disc named HardDisc4 using the Advanced Disc Filing System (ADFS) file system. RISC OS filetypes can be preserved on other systems by appending the hexadecimal type as ',xxx' to filenames.[60][61] When using cross-platform software, filetypes can be invoked on other systems by naming appending '/[extension]' to the filename under RISC OS.[62]

A file system can present a file of a given type as a volume of its own, similar to a loop device. The OS refers to this function as an image filing system. This allows transparent handling of archives and similar files, which appear as directories with some special properties. Files inside the image file appear in the hierarchy underneath the parent archive. It is not necessary for the archive to contain the data it refers to: some symbolic link and network share file systems put a reference inside the image file and go elsewhere for the data.

The file system abstraction layer API uses 32-bit file offsets, making the largest single file 4 GiB (minus 1 byte) long. However, prior to RISC OS 5.20 the file system abstraction layer and many RISC OS-native file systems limited support to 31 bits (just under 2 GiB) to avoid dealing with apparently negative file extents when expressed in two's complement notation.[citation needed]

File formats

The OS uses metadata to distinguish file formats. Some common file formats from other systems are mapped to filetypes by the MimeMap module.[63]

Kernel

The RISC OS kernel is single-tasking and controls handling of interrupts, DMA services, memory allocation and the video display; the cooperative multi-tasking is provided by the WindowManager module.[56]

Desktop

The WIMP interface is based on a stacking window manager and incorporates three mouse buttons[64] (named Select, Menu and Adjust), context-sensitive menus, window order control (i.e. send to back) and dynamic window focus (a window can have input focus at any position on the stack). The icon bar (Dock) holds icons which represent mounted disc drives, RAM discs, running applications, system utilities and docked: files, directories or inactive applications. These icons have context-sensitive menus and support drag-and-drop operation. They represent the running application as a whole, irrespective of whether it has open windows.

The GUI functions on the concept of files. The Filer, a spatial file manager, displays the contents of a disc. Applications are run from the Filer view and files can be dragged to the Filer view from applications to perform saves, rather than opening a separate 'Save' dialog box where the user must navigate to a location already visible in the Finder. In addition, files can be directly transferred between applications by dragging a save icon into another application's window.

Application directories are used to store applications. The OS differentiates them from normal directories through the use of an exclamation mark (also called a pling or shriek) prefix. Double-clicking on such a directory launches the application rather than opening the directory. The application's executable files and resources are contained within the directory, but normally they remain hidden from the user. Because applications are self-contained, this allows drag-and-drop installing and removing.

The RISC OS Style Guide encourages a consistent look and feel across applications. This was introduced in RISC OS 3 and specifies application appearance and behaviour. Acorn's own main bundled applications were not updated to comply with the guide until RISCOS Ltd's Select release in 2001.[65]

Font manager

RISC OS was the first operating system to provide scalable anti-aliased fonts.[66][67][68][69] Anti-aliased fonts were already familiar from Arthur, and their presence in RISC OS was confirmed in an early 1989 preview,[70] featuring in the final RISC OS 2 product, launched in April 1989.[71]

A new version of the font manager employing "new-style outline fonts" was made available after the release of RISC OS,[72] offering full support for the printing of scalable fonts, and was provided with Acorn Desktop Publisher.[73] It was also made available separately and bundled with other applications.[74] This outline font manager provides support for the rendering of font outlines to bitmaps for screen and printer use, employing anti-aliasing for on-screen fonts, utilising sub-pixel anti-aliasing and caching for small font sizes.[75] At the time of the introduction of Acorn's outline font manager, the developers of rival desktop systems were either contemplating or promising outline font support for still-unreleased products such as Macintosh System 7 and OS/2 version 2.[76]

Since 1994, in RISC OS 3.5, it has been possible to use an outline anti-aliased font in the WindowManager for UI elements, rather than the bitmap system font from previous versions.[77] RISC OS 4 does not support Unicode but "RISC OS 5 provides a Unicode Font Manager which is able to display Unicode characters and accept text in UTF-8, UTF-16 and UTF-32. Other parts of the RISC OS kernel and core modules support text described in UTF-8."[78]

Support for the characters of RISC OS (and some other historic computers) was added to Unicode 13.0 (in 2020).[79]

Bundled applications

RISC OS is available in several distributions, all of which include a small standard set of desktop applications, but some of which also include a much wider set of useful programs. Some of those richer distributions are freely available, some are paid for.

Backward compatibility

Limited software portability exists with subsequent versions of the OS and hardware. Single-tasking BBC BASIC applications often require only trivial changes, if any.[citation needed] Successive OS upgrades have raised more serious issues of backward compatibility for desktop applications and games.[80] Applications still being maintained by their author(s) or others have sometimes historically been amended to provide compatibility.[citation needed]

The introduction of the RiscPC in 1994 and its later StrongARM upgrade raised issues of incompatible code sequences and proprietary squeezing (data compression). Patching of applications for the StrongARM was facilitated and Acorn's UnsqueezeAIF software unsqueezed images according to their AIF header.[81] The incompatibilities prompted release by The ARM Club of its Game On![82][83] and StrongGuard software.[82][84][85] They allowed some formerly incompatible software to run on new and upgraded systems. The version of the OS for the A9home prevented the running of software without an AIF header (in accord with Application Note 295)[86] to stop "trashing the desktop".[87]

The Iyonix PC (RISC OS 5) and A9home (custom RISC OS 4) saw further software incompatibility because of the deprecated 26-bit addressing modes. Most applications under active development have since been rewritten.[88][89][90] Static code analysis to detect 26-bit-only sequences can be undertaken using ARMalyser.[91] Its output can be helpful in making 32-bit versions of older applications for which the source code is unavailable.[92][91][93] Some older 26-bit software can be run without modification using the Aemulor emulator.[90][94][95]

Additional incompatibilities were introduced with newer ARM cores, such as ARMv7 in the BeagleBoard and ARMv8 in the Raspberry Pi 3. This includes changes to unaligned memory access in ARMv6/v7 and removal of the SWP instructions in ARMv8.[96]

See also

References

External links