Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
RMX (operating system)
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=={{anchor|I|II|III|86|286}}Variants== Several variations of iRMX have been developed since its original introduction on the Intel 8080: iRMX I, II and III, iRMX-86, iRMX-286, DOS-RMX, iRMX for Windows, and, most recently, INtime. While many of the original variants of iRMX are still in use, only iRMX III, iRMX for Windows, and INtime are currently supported for the development of new real-time applications. Each of these three supported variants of iRMX require an [[Intel 80386]] equivalent or higher processor to run. A significant architectural difference between the [[INtime]] RTOS and all other iRMX variants is the support for address segments (see [[x86 memory segmentation]]). The original 8086 family of processors relied heavily on segment registers to overcome limitations associated with addressing ''large'' amounts of memory via 16-bit registers. The iRMX operating system and the compilers developed for iRMX include features to exploit the segmented addressing features of the original [[x86 architecture]]. The INtime variant of iRMX does not include explicit support for segmentation, opting instead to support only the simpler and more common 32-bit flat addressing scheme. Despite the fact that native processes written for INtime can only operate using unsegmented flat-mode addressing, it is possible to port and run some older iRMX applications that use segmented addressing to the INtime kernel. When Intel introduced the Intel 80386 processor, in addition to expanding the iRMX RTOS to support 32-bit registers, iRMX III also included support for the four distinct protection rings (named rings 0 through 3) which ''describe'' the protected-mode mechanism of the Intel 32-bit architecture. In practice very few systems have ever used more than rings 0 and 3 to implement protection schemes. ===iRMX=== The I, II, III, -286 and -86 variants are intended as standalone real-time operating systems. A number of development utilities and applications were made for iRMX, such as compilers ([[PL/M]], [[Fortran]], [[C (programming language)|C]]), an editor (Aedit), process and data acquisition applications and so on. Cross compilers hosted on the [[VAX/VMS]] system were also made available by Intel. iRMX III is still supported today{{when?|date=June 2018}} and has been used as the core technology for newer real-time virtualization RTOS products including iRMX for Windows and INtime. ==={{anchor|DOS}}DOS-RMX=== DOS-RMX is a variant of the standalone iRMX operating system designed to allow two operating systems to share a single hardware platform. In simplest terms, [[DOS]] and iRMX operate concurrently on a single [[IBM PC compatible]] computer, where iRMX tasks (processes) have scheduling priority over the DOS kernel, interrupts, and applications. iRMX events (e.g., hardware interrupts) pre-empt the DOS kernel to ensure that tasks can respond to real-time events in a time-deterministic manner. In a functional sense, DOS-RMX is the predecessor to iRMX for Windows and INtime. In practice, DOS-RMX appears as a [[Terminate-and-stay-resident]] (TSR) program to the DOS kernel. Once loaded as a TSR, iRMX takes over the CPU, changing to [[protected mode]] and running DOS in a [[virtual machine]] within an RMX task. <!-- A DOS-RMX library is included to facilitate the exchange of data and coordinate activities between tasks running on the iRMX kernel and applications running on the DOS kernel. --> This combination provides RMX real-time functionality as well as full DOS services. ===iRMX for Windows=== Like DOS-RMX, this system provides a hybrid mixture of services and capabilities defined by DOS, Windows, and iRMX. Inter-application communication via an enhanced Windows [[Dynamic Data Exchange|DDE]] capability allows RMX tasks to communicate with Windows processes.<ref>Rajamani K. et al.: "Windows Goes Real Time", pages 121-122. ''BYTE'', April 1992</ref> iRMX for Windows was originally intended for use in combination with the 16-bit version of Windows. In 2002 iRMX for Windows was reintroduced by adding these RMX personalities to the INtime RTOS for Windows, allowing it to be used in conjunction with the 32-bit protected-mode versions of Windows (Windows NT, Windows 2000, etc.).<ref>[http://www.tenasys.com/products/irmx_windows.php Merge the RMX operating system with Windows<!-- Bot generated title -->]</ref> ===INtime=== Like its iRMX predecessors, INtime is a real-time operating system. And, like DOS-RMX and iRMX for Windows, it runs concurrently with a general-purpose operating system on a single hardware platform. INtime 1.0 was originally introduced in 1997 in conjunction with the [[Windows NT]] operating system. Since then it has been upgraded to include support for all subsequent protected-mode Microsoft Windows platforms, including Windows Vista and Windows 7. INtime can also be used as a stand-alone RTOS. INtime binaries are able to run unchanged when running on a ''stand-alone'' node of the INtime RTOS. Unlike Windows, INtime can run on an Intel 80386 or equivalent processor. Current versions of the Windows operating system generally require at least a [[Pentium compatible processor|Pentium]] level processor in order to boot and execute. The introduction of INtime 3.0 included several important enhancements. Among them, support for multi-core processors and the ability to debug real-time processes on the INtime kernel using Microsoft [[Visual Studio]]. INtime is not an [[symmetric multiprocessing|SMP]] operating system, thus support for multi-core processors is restricted to a special form of [[asymmetric multiprocessing]]. When used on a multi-core processor INtime can be configured to run on one CPU core while Windows runs on the remaining processor core(s). ===BOS=== Named BOS (BOS1810, BOS1820), the operating system was cloned by the East-German [[VEB Robotron-Projekt]] in Dresden in the 1980s.<ref name="BOS_1989"/><ref name="Robotron_2021_BOS1810"/>
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)