This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)(Learn how and when to remove this template message)
|Initial release||February 1988|
|Platforms||Macintosh Coprocessor Platform for Apple Macintosh (Motorola 68000)|
A/ROSE (the Apple Real-time Operating System Environment) is a small embedded operating system that runs on Apple Computer's "Macintosh Coprocessor Platform", an expansion card for the Apple Macintosh.
The idea was to offer a single "overdesigned" hardware platform on which third party vendors could build practically any product, reducing the otherwise heavy workload of developing a NuBus-based expansion card. However, the MCP cards were fairly expensive, limiting the appeal of the concept. A/ROSE saw very little use, apparently limited solely to Apple's own networking cards for serial I/O, Ethernet, TokenRing and Twinax. GreenSpring Computers developed the RM1260, which is an IndustryPack (IP) carrier card with a 68000 CPU running A/ROSE and is intended for the data acquisition market.
A/ROSE and the MCP originally came about in August 1987 during the development of the Macintosh II. While working on various networking products for the new system, the developers realized that the existing classic Mac OS would make any "serious" card difficult to create, due to large latencies and the difficulty of writing complex device drivers. Their solution was to make an "intelligent" NuBus card that was essentially an entire computer on a card, containing its own Motorola 68000 processor, working space in RAM mirrored in the main system, and its own basic operating system. The first version of the system was ready for use in February 1988.
A/ROSE was internally called MR-DOS (Multitasking Realtime Distributed Operating System), but Microsoft (developer of MS-DOS) did not appreciate the name and put pressure on Apple to change its name. Eric M. Trehus, a QA engineer on the Token Ring card that ran A/ROSE reportedly said "A/ROSE by any other name is still MR-DOS."
A/ROSE is infamous for its esoteric purpose, which is generally not understood by Mac end users, as well as for causing many Mac emulators, such as Basilisk II, to produce a system error at boot time.
A/ROSE itself is very small, the kernel using only 6 KB, and the operating system as a whole about 28 KB. A/ROSE supports pre-emptive multitasking with round-robin task scheduling with a 110 microsecond context switch time and only 20 microseconds of latency (guaranteed interrupt response time). The system's task is primarily to move data around and start and stop tasks on the cards, and the entire API contains only ten calls.
A/ROSE is a message passing system, and the main calls made by programs running under it are
Receive(). Messages are short, including only 24 bytes of user data, and sent asynchronously. To find the appropriate endpoint, A/ROSE includes a name server that allows the applications to bind their names to their task IDs, allowing them to move in the system and be found dynamically. The OS also supported a number of routines for finding, starting and stopping tasks on other cards, one of those "cards" being the host computer.
To coordinate communications and provide a mechanism for talking with the host's CPU, a cut-down copy of A/ROSE also ran inside the Mac OS in the form of a system extension, or "INIT", known as "Prep" (which should not be confused with the later PReP hardware standard). Device drivers for A/ROSE cards were also written as INITs and started up automatically. After starting, they find the Prep stub and use the normal A/ROSE communications channel it provides to communicate with the cards.
For instance, the Apple TokenTalk NB card installs its driver as an INIT, and optionally installs the Prep stub, assuming it had not been installed before. On startup the driver finds the Prep stub and asks it to enumerate the TokenTalk cards installed in the machine, and optionally uploads code or settings to them. From that point on, Prep handles the communications with the card, handing off the results to the TokenTalk driver.