Oberon Computing Systems
This book is about the Oberon family of computing systems, with a focus on technicalities. For an overview, refer to the Wikipedia article. For other uses of the name Oberon, refer to the disambiguation page.
- 1 Audience
- 2 System Characteristics
- 3 This Book
- 4 Historical Perspective
- 5 System Variants
- 6 Use Cases
- 7 Installing
- 8 Getting Started
- 9 Reading this Book
- 10 Oberon Text
- 11 Dataflow of a Text
- 12 Compilation
- 13 Contributing a Module or Tool Not in the Book
- 14 Editing this Book
- 15 Comparing Versions and Pages
- 16 Contemporary Hardware
- 17 FAQ
- 18 Glossary
- 19 Support
- 20 Developing
- 21 Licenses
- 22 References
- 23 Footnotes
A novice interested to learn computing from the foundations will appreciate the freedom from overwhelming and unnecessary complexity imposed by other systems. The more advanced user will find an efficient tool with complete sources allowing study in depth. The system engineer might adapt Oberon to intensive computation, to data I/O and manipulation or to automation.
Typical usage progresses through these stages.
- Bug repair
- Customization and development
The reader should install and use at least one Oberon system. As preparation, an introductory course covering programming basics is advantageous but not essential.
Oberon was developed as a stand-alone personal workstation and remains viable in that capacity. The system was designed to attain compactness, comprehensibility, efficiency, reliability, responsiveness, security and simplicity. The extreme compactness is immediately evident to a novice installing Oberon S3 (System 3) on a bare PC. The complete system including applications, documentation, graphical interface, fonts and source texts was installed from ten HD diskettes.
An Oberon system comprises a collection of modules and this book presents one module per page. An example is Sort.Mod from S3. Additionally there are Tool pages, each of which is a template of executable commands. An example is Sort.Tool. A system building Tool is a template for rebuilding the entire system, including system installer and module packages.
Following development of the programming languages Euler, Algol W, Pascal, Modula and Modula-2, Niklaus Wirth proceeded to create the Oberon language with original release occurring in 1986. The language design was driven by the wish to design an operating system similar to the OS of the Alto and the insight that Modula-2 did not have the required language construct, which we would now call type inheritance. Wirth chose the other viewpoint and called it type extension. Beside other syntactic differences, which were mainly simplifications, type extension is the major difference between Modula-2 and Oberon . Having met at Xerox PARC Wirth collaborated with Jürg Gutknecht to build a complete operating system written in the Oberon language. This system was also named Oberon. The distinction between language and system is usually obvious from the context where the term appears.
In subsequent developments, small syntactical changes created various dialects of the language (Oberon-2, Component Pascal, Active Oberon, and Oberon-07), with compatibilities and incompatibilities. Variants of the operating system have also evolved, again entailing small incompatibilities. The four most prominent of these OS flavors are
- ETH Oberon (aka System 3, S3) written mostly in Oberon with some parts in Oberon-2,
- V4 Oberon (aka Linz-Oberon) basically written in Oberon but with many extensions in Oberon-2
- AOS (aka Bluebottle and A2) written in Active Oberon, and
- Oberon V5, described in Wirth's Project Oberon, 2013 Edition and written in Oberon-07.
With reasonable effort, incompatibilities can always be resolved to allow shift of source text from one system to another.
Beside being a stand-alone operating system, Oberon has been implemented as an emulated operating system atop other systems, decades before virtualization became a buzz-word. The most prominent of these emulated Oberon Systems was Oberon V4, which was implemented on top of SunOS 1 & 2, Ultrix, Irix, AIX, MacOS 7,8,9 (both 68K and Power PC), AmigaOS, TOS (Atari), OS/2, Microsoft Windows, HPUX, and (of course) Linux. Oberon V4 was sometimes also called Linz-Oberon, due to the fact that it was maintained by the group around Hanspeter Mössenböck, who joined the faculty at JKU Linz in 1994. But also System 3 was implemented on top of another operating system for MacOS (68K and PowerPC), SunOS (SPARC and x86), and Microsft Windows. A2 is running as an emulated OS on Microsoft Windows, Linux, and Solaris (x86). In 2015 Peter Matthias revitalized System 3 under the name "Oberon Linux Revival" (OLR) as a multi-platform proof of concept running both in framebuffer-mode and in the X-Window System on X86, Mips, and ARM hardware under Linux.
The Oberon system runs directly on several machine architectures and as a subsystem in several host operating systems. To see pages specific to a variant, click on the hyperlink in the identifier (3rd) column. Order of rows is approximately chronological.
||The Oberon System||V1, V2|
|Bare X86 PC||ETH Oberon
= PC-Native Oberon
= System 3
|S3||SourceForge||ETHZ, actual diskettes|
|X86, ARM, ARMv7,
RISC-V or MIPS with Linux
|Oberon Linux Revival; sources following S3 closely.||OLR||P. Matthias|
|X86 PC with Linux||Linz-Oberon||V4||JKU Linz and
|X86 PC with MS Windows||Linz-Oberon||V4||JKU Linz and
|X86 PC with Windows or with *nix and Wine||BlackBox Component Builder, an IDE for Component Pascal||BB||BB Community download area|
|.NET and CLI||Gardens Point Component Pascal application for .NET and CLI||GPCP||Current project at github |
Original site from Archive.org
|JVM||Gardens Point Component Pascal application for JVM||GPCP||Current project at github |
Original site from Archive.org
|Bare X86 PC||Bluebottle
|X86 PC with Solaris,
Linux or MacOSX (Darwin).
|X86 PC with A2 or UnixA2 or WinA2||Oberon subsystem||A2O||Included in A2, UnixA2 and WinA2|
|FPGA RISC||Oberon V5||V5||N. Wirth|
||Emulator written in C.||V5||P. De Wachter|
|Unix command line||Norebo, a software allowing
execution of an Oberon
command without the Oberon
system and interface.
|V5||P. De Wachter|
|Oberon RISC processor or emulation of it||Experimental Oberon||EO||A. Pirklbauer|
|Web browser||Emulator written in Java.||V5||Michael Schierl|
|Linux or Mac OS||Integrated Oberon written
in the Go programming language.
or MIPS running Linux
|Project Oberon Linux, POL;
installed on Linux.
In A2, identifiers "A2" and "Oberon" in the name or text of a source module denote context  where necessary. This is the syntax in ActiveOberon.
Module := "MODULE" Identifier "IN" Identifier ";" ...
Where context is not formally recognized, an identifier in a comment is possible.
Module := "MODULE" Identifier "(* IN " Identifier "*);" ...
An identifier can also be prefixed to the module identifier.
Module := "MODULE" Identifier Identifier ";" ...
As the Oberon filesystem does not support folders, name conflict can be avoided by prefixing a file name.
NameOfModuleFile := Identifier Identifier ".Mod"
Of all Oberon systems, PC Native (S3) and A2 have the broadest range of application level development for a personal workstation. Nevertheless their capabilities are limited in comparison to familiar commercial systems, Unix and Unix-like systems. By using an Oberon subsystem in one of these familiar systems, benefits are combined. The subsystem can be installed as an application such as UnixA2. Alternatively the subsystem can be a guest of a hypervisor as when S3 is hosted by QEMU. The subsystem can also be emulated; the Oberon RISC emulator being a prime example. Refer to the table of system variants.
Currently a strong interest in Oberon development is in embedded systems with Astrobe the leading commercial effort. It provides a MS Windows based integrated development environment for producing Oberon source text and executables.
In the table above, a system is chosen and an installation archive is retrieved. Instructions for installation and configuration are linked in the last column of the table. For some systems, instructions are also available in the system specific page linked in the third column.
S3 may be run on a bare PC and is similar to the Oberon subsystem of A2. In comparison to V5, S3 has relatively advanced application level capabilities including the Gadgets GUI. Discarded desktop and laptop PCs capable of running S3 are widely available, typically at no cost.
A2 may be run on a bare PC and as an emulated OS on various platforms. Refer to the A2 page. A2 contains an Oberon subsystem very similar to S3. The compactness and speed of user level tasks such as email, makes a striking comparison to analogues in the host system. A2 also works well on many desktop and laptop machines considered obsolete for commercial operating systems.
Archives are available from JKU Linz and from Sourceforge. Specific installation instructions are available for Linux and for MS Windows. The instructions should also help with Amiga, HPUX, Macintosh, MIPS, PowerMac, Sparc and UV4.
For installation on FPGA machines, refer to the documentation of N. Wirth and of Paul Reed. Oberon RISC Emulators work on contemporary MS Windows, Linux and Unix systems. Refer to instructions of author Peter De Wachter. Additional notes are available for Android. On some machines the size of block random access memory (BRAM) is a noticeable constraint.
The user interface of the Oberon System is quite surprising on the first sight. It is a so called text user interface (TUI) and combines the point-and-click convenience of a graphical user interface (GUI) with the linguistic strength of a command line interface (CLI). It is closely tied to the naming conventions of the Oberon language. Any text appearing (almost) anywhere on the screen can be edited and can therefore be used as command input. Commands are activated by a mouse-middle, MM, click on a text fragment of the form Module.Command (optionally followed by Parameters, which are terminated by ~). A command is defined by a procedure, which has an empty argument list. Parameters to the command have to be defined before executing the middle click and must be explicitly scanned and retrieved by the procedure. There are no checks nor any questions asked during command execution. This is sometimes called a "non-modal" user interface (UI). Nothing like a command prompt is required. Although radically different from a command line, the TUI is very efficient and powerful. Active elements can be embedded in Oberon texts: a clock showing the current time, push buttons, or graphical elements visualizing data. Most user interface elements are realized with the help of documents. A steep ascent in the early learning curve makes it a little bit difficult in the beginning. No questions are asked: this is a deliberate design decision, which needs getting used to. Most editors ask the user when closing a modified text: this is not the case in the Oberon System. The usage of the TUI and programming interface is fully documented in Martin Reiser's book "The Oberon System". A short introduction to the user interface can be found on Niklaus Wirth's home page. The later Versions of System Oberon, Oberon V4 (or V4 in short, sometimes also referred to as Linz-Oberon) and Oberon System 3 (or S3, sometimes also called ETH-Oberon or Spirit of Oberon), enhanced the basic interface with different but incompatible implementations for buttons, drop down menus, and other active elements. V4 used for that purpose a dedicated control character embedded in normal text in contrast to System 3, which extended the kernel by introducing persistent objects. Both extensions include a large set of user interface elements.
Mastering the Oberon user interface, both the purely textual and also the so called Gadgets System (under S3), is absolutely non-trivial. Therefore it is recommended to proceed after a successful installation of Oberon System 3 to André Fischer's Oberon System 3 Tutorial. An expanded version of this tutorial is published as a book, which is now out of print. Although the book has a standard copyright, it is available in electronic form under a single user license in every installed version of System 3 (Windows, Linux or Native, i.e. also with the Gadgets toolkit of OLR). If you try to read it in System 3, you are confronted with the classical chicken and egg problem: You have to master the user interface to have access to the documentation of the user interface. Therefore some detailed instructions for reading "The Oberon Companion" – after a successful installation of the Oberon System can be found by opening the file Book.Tool with the command Desktops.OpenDoc. If this command is not present in any of the windows/viewers, which are opened by default when you start the Oberon System, you can click anywhere with the left-mouse button (ML) in any viewer and type the command Desktops.OpenDoc Book.Tool ~. Then move the mouse over Desktops.OpenDoc and do a middle-mouse button (MM) click. This will open an new viewer with a table of contents of "The Oberon Companion". All lines with blue text are hyperlinks to the chapters of the book, which in turn can be clicked with the MM button so that the chapter will open in a new viewer. The license in Book.Tool gives the user the right to print a single copy for personal use. I had good results in print with a GhostScript based free PDF converter. If you want to print an open document in Oberon, i.e., the contents of a window (or viewer in Oberon terminology), you have to set the star shaped mark by hitting the F1 key (see Tutorial) and then issue the command Desktops.PrintDoc Default * ~ by a MM click on Desktops.PrintDoc. In an Oberon command the * is not a wildcard, but symbolizes the marked viewer.
Reading this Book
At 2018-02-06 the WebBrowser in A2 fails to open a page. Hypothetically, follow the system menu, Apps > WebBrowser and specify a URL. Alternatively, Mouse middle, MM, click on WebBrowser.Open in an A2 window (not in the Oberon subsystem).
WebBrowser.Open https://en.wikibooks.org/wiki/Oberon ~
In S3 and in the Oberon Subsystem of A2
MM click on Desktops.OpenDoc.
Desktops.OpenDoc "http://www.loband.org/loband/filter/org/wikibooks/en/%20/wiki/Oberon" Desktops.OpenDoc "http://www.loband.org/loband/filter/org/wikibooks/en/%20/wiki/Oberon/Oberon.Sort.Mod"
Desktops and Webrowser are not implemented.
In Any Desktop, Laptop or Smartphone
Use any browser.
firefox https://en.wikibooks.org/wiki/Oberon firefox https://en.wikibooks.org/wiki/Oberon/Oberon.Sort.Mod
To see the list of sources available here for a given system, click on the identifier in the third column of the table. Most of the wiki text extraneous to a module Text is eliminated with a click on the "Mobile view" link at the foot of a page.
An Oberon Text can appear to be no more than a plain text comprising a sequence of ASCII characters. Nevertheless Text in Oberon is a type defined in the Text module. A character can have attributes including typeface, size and color. Furthermore a Text can include non-character objects; an image or a hyperlink for example. Consequently two documents, one an Oberon Text and the other an HTML text, can have the same appearance and the same behavior of links.
Editing a Text
Various editors are available. Each Oberon system has an Edit module. If Edit.Open Example.Text appears almost anywhere on the screen, a MM click on Edit.Open will open a viewer. If a file named Example.Text exists, it's content will appear in the viewer. If no file with the name exists, the viewer will be empty. The caret can be set by ML and characters can be inserted using a keyboard. In S3, edit is extended by ET and by the Gadgets subsystem. Try commands ET.Open <aFile> and Desktops.OpenDoc <aFile>. S3 also has the Hex module providing a hexadecimal editor. Try Hex.Open <aFile>.
A dedicated page addresses Programmatical access to Text and the type structure on which Text is based.
Dataflow of a Text
From an Oberon system to the Wikibook and to the Oberon system again.
Ideally the three Texts in the upper row are identical; but currently Text color and style are not preserved by Desktops.OpenDoc nor by transport of browser text into Oberon. Variations of Text color and style are harmless to compilation.
If a module name matches an extant object file, compilation can overwrite it. To avoid that, the name of the newer or test module can be altered. Prefixed with an identifier for example; "MODULE Sort" could become "MODULE V4Sort". Overwriting is also avoided when the new and old object files are in different volumes or directories. Object files of S3 are installed to the SYS volume whereas the new file would typically be written to a USR or HOME volume. Object files of UnixA2 are installed to /usr/aos/obj/ and a new file would typically be written to a working directory such as /home/me/aos/.
In A2 and Oberon
Compile A2 and Oberon modules in A2; not in the Oberon subsystem. The compiler in A2 is Flexible Oberon Cross Compiler or Fox. Invoke it with the Compile button in the PET editor or MM on a Compiler command in an A2 window, in accord to Fox.Tool. Builder.Tool from S3 is not relevant to A2.
Compiler commands are defined in Compiler.Mod and summarized there following "END Compiler". If a module is opened with Desktops.OpenDoc as described under Reading, it can be compiled directly from the viewer. Select any characters beginning with M in MODULE and MM click on Compiler.Compile @ . Otherwise import to the S3 system and use a command according to Compiler.Tool.
Use an ORP.Compile command in System.Tool.
Contributing a Module or Tool Not in the Book
- Initialize a Module or Tool page from a published release. Preferably the latest. Oberon.Sort.Mod, for example, is taken from the Oberon subsystem in UnixA2. Indicate the source in the wiki edit subject line.
- Use Oberon naming conventions.
- Avoid page duplication. If two systems share a source module, a page redirect might be preferable to duplicate pages.
Addition of a Text is the first two steps of the dataflow diagram above. The first step is performed by the contributor. The second is performed automatically by the MediaWiki server. Retrieve the MediaWiki module (S3, A2O) to your Oberon system and compile it. Open a viewer with the module to be contributed and * mark the Text. Translate to MediaWiki markup with "MediaWiki.Markup * " and save the <Module>.Mod.mw with Edit.StoreAscii or ET.StoreAscii.
To add the page to the book, a browser capable of HTTPS is necessary; the current Desktops.OpenDoc is inadequate. Being logged in to a Wikimedia account is advisable. In the table above, click on an identifier to open the system specific page. There add the name of the intended module and "Publish change". The new entry will be colored red. Click on it to open the page for the new module. Copy and paste the text from <Module>.Mod.mw and "Publish change".
Editing this Book
All progress is welcome. Correct errors in grammar and in algorithms. Present unrefined ideas in the talk pages.
Editing a Module Source Text
A source can be edited directly using a browser capable of HTTPS. Alternatively it can be edited on your Oberon system, translated using MediaWiki.Markup and applied to replace the existing version, as when adding a new module. If replacing, take care to avoid over-writing a previous edit. The latest version of the page should be retrieved to a working Oberon system and compared using Diff.Do. Alternatively, a registered user can put a new version in the user sandbox and compare as in the following section. Be aware that the non-zero time interval between retrieval from the book and installation of the new version allows an edit conflict.
- If an edit conflict is inadvertently created, fix it, please.
- Avoid breaking compilation.
- Avoid breaking interfaces. If an interface is changed, adjust all modules which connect to it. An idea clearly expressed in a discussion page is preferable to broken interfaces.
- Avoid breaking functionality.
- Avoid introducing a bug. If a bug is introduced, the change might be reverted, however brilliant the intended improvement.
- Prefer more recent syntax over older syntax. Remove LOOP. Where possible remove RETURN.
- Optionally, color changed text, green; text disabled by commenting, red.
Formatting a Source Text
Various formatting conventions and preferences exist. Refer to the Oberon Mailing List, 2017-07-22 through 2017-07-26, and search for "indentation?". No particular format is essential here. Any reasonable format preferred by a contributor is welcome.
Styling a Source Text
Various stylistic conventions also exist. Refer to the Oberon Mailing List, 2017-07-29 through 2017-07-30, and search for "Italicization". Editors such as PET in A2 and the "pretty printers" mentioned in the list automatically style a source Text to highlight syntax. Therefore direct syntax styling can be unnecessary. Color to distinguish a revision is optional and relatively harmless.
Comparing Versions and Pages
Oberon has module Diff. For example, two pages can be retrieved to files TextFile1 and TextFile2. Then MM on Diff.Do TextFile1 TextFile2 .
To compare versions of a page within the book, open the history using the button at the top of the page. Choose two versions and "Compare selected versions".
To compare distinct pages, ID numbers are specified in a URL. In the page history of S3.HTML.Mod, when the mouse pointer is hovered over the date in the entry for the original version, ID 3205558 is reported by the browser. The original version of Oberon.HTML.Mod is ID 3205420. The URL
produces a side by side comparison. "Compare" works well where a fraction of lines differ. When most or all lines in the compared pages differ, comparison has little or no value.
|Model Name||Image||Processor||Boot Memory||Memory||Approximate
|Pepino LX9||Xilinx Spartan-6 FPGA||1 MB SRAM||128 MB SPI||100|
|OberonStation||Xilinx XC3S700AN FPGA||1 MB SRAM||microSD||Website unreachable September 2018.|
|RiskFive||Xilinx Artix-7 FPGA||16-32 MB SPI Flash||4 MB ZBT, microSD||"expensive"||Motherboard plus FPGA module.|
|Radiona ULX3S||Lattice ECP5 LFE5U-85F-6BG381C (85K LUT) FPGA||4–16 MB Quad-SPI Flash||32 MB SDRAM 166 MHz, microSD||60-140||Boards with 12K LUT also available.|
- Why do some Oberon systems have a flat file system? Isn't a tree structured file system indispensable in highly productive contemporary environments?
- The tree structured file system came into prominence during the 1950s and '60s when computer memories were miniscule in comparison to memories now available. The tree structure of those early file systems helped with organization of the operating system. Typical memory access is far faster than file access. With current hardware, a data structure can be composed and used in memory with much faster performance than a data structure in a file system. With some focus on choice of meaningful names for files, most users will find the flat file system entirely adequate. Also, most Oberon subsystems have access to a tree structured file system of the host. Additionally, S3 running on a bare PC supports the FAT16, FAT32 and ISO 9660:1988 file systems, all of which are tree structured. In reality, a flat file system in Oberon is a benefit rather than detriment.
- In S3 (or A2O) MM+MR opens a viewer with the Edit menu whereas I prefer ET. How can that be fixed?
- Open TextFrames.Mod in S3
or in the Oberon sub-system of A2.
OpenCmd = "Edit.Open"
OpenCmd = "ET.Open"
recompile and reboot. TextFrames and all modules which import it could be reloaded but rebooting is simpler.
Also refer to the glossary in the Wikipedia article.
BRAM, Block Addressable Random Access Memory, as used in the FPGA machine.
Columbus, a software tool in S3 used to inspect and modify gadget attributes and to add a new attribute to a gadget. Usage described in the tutorial
Definition ( or Module Definition), a summary of a module presenting constant declarations, type declarations, variable declarations and procedure headings.
Gadgets, software infrastructure in S3 providing a graphical user interface. Usage described in the tutorial
INTEGER, an integer type in every Oberon system.
Interclick, a click of a mouse button while holding another button. MM+MR below is an example. The mouse tutorial has additional details.
Lola-2, a hardware description language developed by Niklaus Wirth.
LONGINT, an integer type in S3. Synonymized to INTEGER in the current V5.
LUT, look up table of FPGA. Referenced when quantifying the size of the device.
ML, a click of the left button of the mouse. Ref. Mouse support
MM, a click of the middle button or the wheel of the mouse.
MM+MR, a click of the right button while holding the middle button or the wheel of the mouse. MR here is termed an "interclick".
ML+MM+MR, Nullification of unwanted mouse click.
native, modifies the name of an Oberon system to indicate that it is installed on bare hardware; distinguishing from a subsystem such as UnixA2 installed atop a host system.
(** any comment *), appears in some module sources. It means that any comment is an exported comment. A tool named Def produces a module interface file with this comment included, thus enhancing internal documentation.
(** portable *), this comment in S3 marked a module where OMI/Slim binary code was portable across platforms. More generally, it means there were no SYSTEM dependencies or machine specificities. This exported comment appears in the documentation created by the above mentioned browser, Def, which was integrated into a tool called Watson in S3.
SHORTINT, an integer type in S3. Not in V5.
Watson, a tool capable of extracting a module definition from a definition file, module file, module Text or object file. Usage described in the tutorial
- The Oberon mailing list https://lists.inf.ethz.ch/mailman/listinfo/oberon
- The Oberon Community Platform http://www.ocp.inf.ethz.ch/wiki/OCP/Home
A few potential projects.
- For any system, compile a fresh release, with bug fixes and improvements, and post on a public server.
- Make a TUI for A2.
- With the cryptography modules in S3 and in A2 as a base, build an SSL implementation for S3.
- Using HTTPS, automate the download and upload processes. Allowing MediaWiki.Get Oberon.Sort.Mod ... ~ and MediaWiki.Put Oberon.Sort.Mod ... ~ for example.
- Improve support of Unicode.
- Improve HTMLDocs in S3 and in A2O. Add support for styling and tables, for example.
For compatibility of the ETH License with Wikibooks open the
Project Oberon, Revised Edition 2013
Approximate chronological order. Also refer to the Oberon Bibliography at the ETHZ.
- N. Wirth, J. Gutknecht, Project Oberon, 1992.
- P.J. Muller, The Active Object System - Design and Multiprocessor Implementation(PDF), PhD thesis, Institute of Computer Systems, ETH Zurich, 2002. Containing the original description of A2.
- Oberon System 3 - Main Tutorial.
- N. Wirth, Project Oberon, 2013 Edition. Originally published with co-author J. Gutknecht, 1992.
- Reviving a Computer System of 25 Years Ago, 2014 lecture by Prof. N. Wirth
- P. Reed, Project Oberon, 2015-present.
- In the preface of The Oberon System (Pub. Addison-Wesley, 1991) Martin Reiser commented "It is the most responsive system by far known to the author. This responsiveness substantially improves user productivity;"
- With contemporary facilities, the base system is easily installed using the Oberon0.Dsk image and a hypervisor such as QEMU. The additional packages can be retrieved via a network connection and installed. Refer to the installation instructions for S3.
- These systems comprise hundreds of modules. At present fewer than twenty modules are available here. Nevertheless even one insight can advance understanding and one small bug fix can be essential to success in a task.
- Sources of Oberon V4 at SourceForge
- Matthias, Peter. "Oberon Linux Revival". http://oberon.wikidot.com/.
- In some cases the host environment is a bare machine. Otherwise it is a machine running another system.
- The compiler in A2 recognizes context identifiers "A2" and "Oberon". Other identifiers here are merely hyperlinks to system specific pages. See also "Identifiers" in the discussion page.
- Including the Transmeta Crusoe 5400 and the StrongARM SA 110 and SA 1110.
- V4 can also execute on obsolete systems 680x0 MacIntosh and PowerMac with MacOS to version 9 inclusive, Amiga, Atari ST, DECstation, HP-UX, IBM RS/6000, SGI IRIS and SPARC with Solaris. Refer to ftp://ftp.ethoberon.ethz.ch/Oberon/OberonV4/ and ftp://ftp.ssw.uni-linz.ac.at/pub/Oberon/. A native version has not been produced.
- GPCP provides a compiler for Component Pascal; not a full Oberon subsystem.
- During the summer of 2019 work is underway at the ETHZ to improve portability and other aspects. Until the work is completed, the user may encounter difficulties with the native variant of A2. The Oberon subsystem remains available in UnixA2 and WinA2. A notice is in the mailing list archive at 2019-07-03. Patience is advised.
- The SDL2 library and a C99 capable C compiler are required. GCC or Clang suffice for compiling the emulator.
- The Oberon compiler, for example, can be executed at the Unix command line.
- EO does not modify the RISC processor; it modifies only the Oberon system which runs on it.
- Friedrich, F., Negele, F., "Proposal for Modules Contexts"
- Using the mouse and the keyboard http://www.ethoberon.ethz.ch/ethoberon/tutorial/Mouse.contents.html
- Franz, Michael (2000). "Oberon - The Overlooked Jewel". in Böszörmény, Lászlo; Gutknecht, Jürg; Pomberger, Gustav. The School Niklaus Wirth - The Art of Simplicity. Morgan Kaufmann Publishers. pp. 41–53. ISBN 1-55860-723-4. https://pdfs.semanticscholar.org/d48b/ecdaf5c3d962e2778f804e8c64d292de408b.pdf. Retrieved 2017-12-14.
- Reiser, Martin: "The Oberon System - User Guide and Programmer's Manual" - Out-of-print - Addison-Wesley/ACM Press (1991) ISBN 0-201-54422-9
- Wirth, Niklaus (2015). "How to use the Oberon System". https://www.inf.ethz.ch/personal/wirth/ProjectOberon/UsingOberon.pdf.
- André Fischer & Hannes Marais: The Oberon Companion. A Guide to Using and Programming Oberon System 3. vdf Hochschulverlag AG (1997). ISBN 978-3728124937, out of print, for a personal copy, see notes in text
- With an older HTMLDocs module some characters appear as empty boxes. To correct this, install and compile a revised Oberon.HTMLDocs.Mod.
- The loband filter allows Oberon to use HTTP while the Wikimedia server provides HTTPS.
- With Text being a fundamental type in an Oberon system, "Oberon Text" is considered a proper name. Hence the capitalization "Text".
- Explained further in the Oberon mailing list at 2019-02-09.