Multiuser DOS

The initial version of CP/M-86 1.0 (with BDOS 2.x) was adapted and became available to the IBM PC in 1982. It was commercially unsuccessful as IBM's PC DOS 1.0 offered much the same facilities for a considerably lower price. Neither PC DOS nor CP/M-86 could fully exploit the power and capabilities of the new 16-bit machine.

It was soon supplemented by an implementation of CP/M's multitasking 'big brother', MP/M-86 2.0, since September 1981. This turned a PC into a multiuser machine capable of supporting multiple concurrent users using dumb terminals attached by serial ports. The environment presented to each user made it seem as if they had the entire computer to themselves. Since terminals cost a fraction of the then-substantial price of a complete PC, this offered considerable cost savings, as well as facilitating multi-user applications such as accounts or stock control in a time when PC networks were rare, very expensive and difficult to implement.

CP/M-86 1.1 (with BDOS 2.2) and MP/M-86 2.1 were merged to create Concurrent CP/M-86 3.0 (also known as CCP/M-86) with BDOS 3.0 in late 1982.^[6] Kathryn Strutynski, the project manager for CP/M-86, was also the project manager for Concurrent CP/M-86. One of its designers was Francis "Frank" R. Holsworth.^[7][8] Initially, this was a single-user operating system supporting true multi-tasking of up to four (in its default configuration) CP/M-86 compatible programs. Like its predecessors it could be configured for multi-processor support (see e.g. Concurrent CP/M-86/80) and also added "virtual screens" letting an operator switch between the interactions of multiple programs.^[6] Later versions supported dumb terminals and so could be deployed as multiuser systems. Concurrent CP/M-86 3.1 (BDOS 3.1) shipped on 21 February 1984.^[9]

In February 1984 Digital Research also offered a version of Concurrent CP/M-86 with windowing capabilities named Concurrent CP/M with Windows for the IBM Personal Computer and Personal Computer XT.^[10]

This was an adaptation of Concurrent CP/M-86 for the LSI-M4, LSI Octopus^[11] and CAL PC computers. These machines had both 16-bit and 8-bit processors, because in the early days of 16-bit personal computing, 8-bit software was more available and often ran faster than the corresponding 16-bit software. Concurrent CP/M-86/80 allowed users to run both CP/M (8-bit) and CP/M-86 (16-bit) applications. When a command was entered, the operating system ran the corresponding application on either the 8-bit or the 16-bit processor, depending on whether the executable file had a .COM or .CMD extension. It emulated a CP/M environment for 8-bit programs by translating CP/M system calls into CP/M-86 system calls, which were then executed by the 16-bit processor.^[6]

In August 1983, Bruce Skidmore, Raymond D. Pedrizetti, Dave Brown and Gordon Edmonds teamed up to create PC-MODE,^[12] an optional module for Concurrent CP/M-86 3.1^[13][14] (with BDOS 3.1) to provide basic compatibility with PC DOS 1.1 (and MS-DOS 1.1).^[14] This was shown publicly at COMDEX in December 1983^[12] and shipped in March 1984 as Concurrent DOS 3.1 (a.k.a. CDOS with BDOS 3.1) to hardware vendors.^[15][16] Simple DOS applications, which did not directly access the screen or other hardware, could be run. For example, although a console program such as PKZIP worked perfectly and offered more facilities than the CP/M-native ARC archiver, applications which performed screen manipulations, such as the WordStar word processor for DOS, would not, and native Concurrent CP/M (or CP/M-86) versions were required.

While Concurrent DOS 3.1 up to 4.1 had been developed in the US, OEM adaptations and localizations were carried out by DR Europe's OEM Support Group in Newbury, UK,^[17] since 1983.

Digital Research positioned Concurrent DOS 4.1 with GEM as alternative for IBM's TopView in 1985.^[18]

Concurrent DOS 3.2 (with BDOS 3.2) in 1984 was compatible with applications for CP/M-86 1.x, Concurrent CP/M-86 3.x and PC DOS 2.0.^[17] It was available for many different hardware platforms. The version with an IBM PC compatible BIOS/XIOS was named Concurrent PC DOS 3.2. Kathryn Strutynski was the product manager for Concurrent PC DOS.

Efforts being part of a cooperation with Motorola since 1984^[19][14] led to the development of Concurrent DOS 68K in Austin, Texas, as a successor to CP/M-68K written in C. One of its main architects was Francis "Frank" R. Holsworth (using siglum FRH).^[7][8] Concurrent DOS 68K 1.0 became available for OEM evaluation in early 1985.^[20][21] The effort received considerable funding worth several million dollars from Motorola^[20] and was designed for their 68000/68010 processors. Like the earlier GEMDOS system for 68000 processors it initially ran on the Motorola VME/10 development system.^[14] Concurrent DOS 68K 1.20/1.21 was available in April 1986,^[22][23][24] offered for about 200000 dollars to OEMs.^[20] This system evolved into FlexOS 68K in late 1986.

Known versions include:

• Concurrent DOS 68K 1.0 (1985)^[20]
• Concurrent DOS 68K 1.1^[23]
• Concurrent DOS 68K 1.20 (April 1986,^[22][23][24] 1986-05-27^[23])
• Concurrent DOS 68K 1.21 (1986)^[22][23][24]

In parallel to the Concurrent DOS 68K effort,^[20] Digital Research also previewed Concurrent DOS 286^[25] in cooperation with Intel in January 1985. This was based on MP/M-286 and Concurrent CP/M-286, on which Digital Research had worked since 1982.^[26][27]

Concurrent DOS 286 was a complete rewrite in the C language based on a new system architecture with dynamically loadable device drivers instead of a static BIOS or XIOS.^[25] One of its main architects was Francis "Frank" R. Holsworth.^[7][8] The operating system would function strictly in 80286 native mode, allowing protected mode multi-user, multitasking operation while running 8086 emulation.^[28][25] While this worked on the B-1 step of prototype chip samples, Digital Research, with evaluation copies of their operating system already shipping in April, discovered problems with the emulation on the production level C-1 step of the processor in May, which would not allow Concurrent DOS 286 to run 8086 software in protected mode. The release of Concurrent DOS 286 had been scheduled for late May, but was delayed until Intel could develop a new version of the chip.^[28] In August, after extensive testing E-1 step samples of the 80286, Digital Research said that Intel had corrected all documented 286 errata, but that there were still undocumented chip performance problems with the prerelease version of Concurrent DOS 286 running on the E-1 step. Intel said that the approach Digital Research wished to take in emulating 8086 software in protected mode differed from the original specifications; nevertheless they incorporated into the E-2 step minor changes in the microcode that allowed Digital Research to run emulation mode much faster (see LOADALL).^[29][23] These same limitations affected FlexOS 286 version 1.x, a reengineered derivation of Concurrent DOS 286,^[30][31] which was developed by Digital Research's new Flexible Automation Business Unit in Monterey, California, since 1986.

Later versions added compatibility with PC DOS 2.x and 3.x.

Known versions include:

• Concurrent DOS 286 1.0 (1985)^[23]
• Concurrent DOS 286 1.1 (1986-01-07)^[23]
• Concurrent DOS 286 1.2 (1986)^[32]
• FlexOS 286 1.3 (November 1986)^[30]
• FlexOS 286 1.31 (May 1987)

The OEM Support Group was relocated into Digital Research's newly created European Development Centre (EDC) in Hungerford, UK in 1986, which started to take over further development of the Concurrent DOS family since Concurrent DOS 4.11, including siblings like DOS Plus and successors.

Developed in Hungerford, UK, versions 5 and 6 (Concurrent DOS XM, with XM standing for Expanded Memory) could bank switch up to 8 MB of EEMS to provide a real-mode environment to run multiple CP/M-86 and DOS programs concurrently and support up to three users (one local and up to two hooked up via serial terminals).

In 1987, Concurrent DOS 86 was rewritten to become Concurrent DOS 386,^[33] still a continuation of the classical XIOS & BDOS architecture. This ran on machines equipped with the Intel 80386 and later processors, using the 386's hardware facilities for virtualizing the hardware, allowing most DOS applications to run unmodified under Concurrent DOS 386, even on terminals. The OS supported concurrent multiuser file access, allowing multiuser applications to run as if they were on individual PCs attached to a network server. Concurrent DOS 386 allowed a single server to support a number of users on dumb terminals or inexpensive low-specification PCs running terminal emulation software, without the need for expensive workstations and then-expensive network cards. It was a true multiuser system; several users could use a single database with record locking to prevent mutual interference.

Concurrent DOS 6.0 represented also the starting point for the DR DOS family, which was carved out of it.

Known versions include:

• DR Concurrent PC DOS XM 5.0 (BDOS 5.0)
• DR Concurrent DOS XM 5.0 (BDOS 5.0, October 1986)
• DR Concurrent DOS XM 5.1 (BDOS 5.1?, January 1987)
• DR Concurrent DOS XM 5.2 (BDOS 5.2?, September 1987)^[34][35][36]
• DR Concurrent DOS XM 6.0 (BDOS 6.0, 1987-11-18),^[37][38] 6.01 (1987)
• DR Concurrent DOS XM 6.2 (BDOS 6.2),^[39] 6.21

• DR Concurrent DOS 386 1.0 (BDOS 5.0?, 1987)
• DR Concurrent DOS 386 1.1 (BDOS 5.2?, September 1987)^[34]
• DR Concurrent DOS 386 2.0 (BDOS 6.0, 1987-11-18),^[37] 2.01^[40]
• DR Concurrent DOS 386 3.0 (BDOS 6.2, December 1988, January 1989),^[39] 3.01 (1989-05-19), 3.02 (1989)

Concurrent PC DOS XM 5.0 emulated IBM PC DOS 2.10,^[41] whereas Concurrent DOS XM 6.0 and Concurrent DOS 386 2.0 were compatible with IBM PC DOS 3.30.^[42]

Known CCI Concurrent DOS adaptations by Concurrent Controls, Inc. include:

• CCI Concurrent DOS 386 1.12 (BDOS 5.0?, October 1987)
• CCI Concurrent DOS 386 2.01 (BDOS 6.0?, May 1988)
• CCI Concurrent DOS 386 3.01 (BDOS 6.2?, March 1989)
• CCI Concurrent DOS 386 3.02 (April 1990)
• CCI Concurrent DOS 386 3.03 (March 1991)
• CCI Concurrent DOS 386 3.04 (July 1991)^[43] aka "CCI Concurrent DOS 4.0"^[44]
• CCI Concurrent DOS 3.05 R1 (1992-02), R2 (1992), R3+R4 (1992), R5+R6 (1992), R7+R8 (1993), R9+R10 (1993), R11 (August 1993)
• CCI Concurrent DOS 3.06 R1 (December 1993), R2+R3 (1994), R4+R5+R6 (1994), R7 (July 1994)
• CCI Concurrent DOS 3.07 R1 (March 1995), R2 (1995), R3 (1996), R4 (1996), R5 (1997), R6 (1997), R7 (June 1998)^[45]
• CCI Concurrent DOS 3.08
• CCI Concurrent DOS 3.10 R1 (2003-10-05)^[46]

Other adaptations include:

• Apricot Concurrent DOS 386 2.01 (1987) for Apricot Quad Version Level 4.3^[47]

Later versions of Concurrent DOS 386 incorporated some of the enhanced functionality of DR's later single-user PC DOS clone DR DOS 5.0, after which the product was given the more explanatory name "Multiuser DOS" (a.k.a. MDOS), starting with version 5.0 (with BDOS 6.5) in 1991.^[48]

Multiuser DOS suffered from several technical limitations that restricted its ability to compete with LANs based on PC DOS. It required its own special device drivers for much common hardware, as PC DOS drivers were not multiuser or multi-tasking aware. Driver installation was more complex than the simple PC DOS method of copying the files onto the boot disk and modifying CONFIG.SYS appropriately – it was necessary to relink the Multiuser DOS kernel (known as a nucleus) using the SYSGEN command.

Multiuser DOS was also unable to use many common PC DOS additions such as network stacks, and it was limited in its ability to support later developments in the PC-compatible world, such as graphics adaptors, sound cards, CD-ROM drives and mice. Although many of these were soon rectified – for example, graphical terminals were developed, allowing users to use CGA, EGA and VGA software – it was less flexible in this regard than a network of individual PCs, and as the prices of these fell, it became less and less competitive, although it still offered benefits in terms of management and lower total cost of ownership. As a multi-user operating system its price was higher than a single-user system, of course, and it required special device drivers, unlike single-user multitasking DOS add-ons such as Quarterdeck's DESQview. Unlike MP/M, it never became popular for single-user but multitasking use.

When Novell acquired Digital Research in 1991^[1][2][3] and abandoned Multiuser DOS in 1992, the three Master VARs DataPac Australasia, Concurrent Controls^[4] and Intelligent Micro Software^[5] were allowed to license the source code of the system to take over and continue independent development of their derivations in 1994.

Known versions include:

• DR Multiuser DOS 5.00 (1991),^[49] 5.01
• Novell DR Multiuser DOS 5.10 (1992-04-13),^[50] 5.11^[51]
• Novell DR Multiuser DOS 5.13 (BDOS 6.6, 1992)

All versions of Digital Research and Novell DR Multiuser DOS reported themselves as "IBM PC DOS" version 3.31.

Known versions by DataPac Australasia Pty Limited include:

• Datapac Multiuser DOS 5.0
• Datapac Multiuser DOS 5.1 (BDOS 6.6)
• Datapac System Manager 7.0 (1996-08-22)

In 1997, Datapac was bought by Citrix Systems, Inc.,^[52][53][54] and System Manager was abandoned soon after. In 2002 the Sydney-based unit was spun out into Citrix' Advanced Products Group.^[55]

Known CCI Multiuser DOS versions by Concurrent Controls, Inc. (CCI) include:

• CCI Multiuser DOS 7.00
• CCI Multiuser DOS 7.10
• CCI Multiuser DOS 7.21^[56]
• CCI Multiuser DOS 7.22^[56] R1 (September 1996), R2 (1996), R3 (1997), R4 GOLD/PLUS/LITE (BDOS 6.6, 1997-02-10), R5 GOLD (1997), R6 GOLD (1997), R7 GOLD (June 1998), R8 GOLD, R9 GOLD, R10 GOLD, R11 GOLD (2000-09-25), R12 GOLD (2002-05-15), R13 GOLD (2002-07-15), R14 GOLD (2002-09-13), R15 GOLD, R16 GOLD (2003-10-10), R17 GOLD (2004-02-09), R18 GOLD (2005-04-21)

All versions of CCI Multiuser DOS report themselves as "IBM PC DOS" version 3.31.^[56] Similar to SETVER under DOS, this can be changed using the Multiuser DOS DOSVER x.y utility.^[56]

In 1999, CCI changed its name to Applica, Inc.^[57] In 2002 Applica Technology became Aplycon Technologies, Inc.^[58]

Known adaptations of IMS Multiuser DOS include:

• IMS Multiuser DOS Enhanced Release 5.1 (1992)
• IMS Multiuser DOS 5.11
• IMS Multiuser DOS 5.14
• IMS Multiuser DOS 7.0
• IMS Multiuser DOS 7.1 (BDOS 6.7, 1994)

All versions of IMS Multiuser DOS report themselves as "IBM PC DOS" version 3.31.

Intelligent Micro Software Ltd. (IMS) of Thatcham, UK, acquired a license to further develop Multiuser DOS from Novell in 1994 and renamed their product REAL/32 in 1995.^[5]

Similar to FlexOS/4690 OS before, IBM in 1995 licensed REAL/32 7.50 to bundle it with their 4695 POS terminals.^{[5][clarification needed]}

IMS REAL/32 versions:

• IMS REAL/32 7.50 (BDOS 6.8, 1995-07-01), 7.51 (BDOS 6.8), 7.52 (BDOS 6.9), 7.53 (BDOS 6.9, 1996-04-01), 7.54 (BDOS 6.9, 1996-08-01)^[59]
• IMS REAL/32 7.60 (BDOS 6.9, February 1997),^[60] 7.61, 7.62, 7.63
• IMS REAL/32 7.70 (November 1997), 7.71, 7.72, 7.73, 7.74 (1998)^[61]
• IMS REAL/32 7.80, 7.81 (February 1999), 7.82, 7.83 (BDOS 6.10)
• IMS REAL/32 7.90 (1999),^[62] 7.91, 7.92
• ITERA IMS REAL/32 7.93 (June 2002),^[63] 7.94 (BDOS 6.13, 2003-01-31)^[64]
• Integrated Solutions IMS REAL/32 7.95^[65]

REAL/32 7.50 to 7.74 report themselves as "IBM PC DOS" version 3.31, whereas 7.80 and higher report a version of 6.20. LBA and FAT32 support was added with REAL/32 7.90 in 1999.^[62] On 19 April 2002, Intelligent Micro Software Ltd. filed for insolvency and was taken over by one of its major customers, Barry Quittenton's Itera Ltd.^[66][67][68] This company was dissolved on 2006-03-28.^[69][70] As of 2010 REAL/32 was supplied by Integrated Solutions of Thatcham, UK, but the company, at the same address, was later listed as builders.^[65]

REAL/NG was IMS' attempt to create the "Next Generation" of REAL/32, also named "REAL/32 for the internet age". REAL/NG promised "increased range of hardware from PCs to x86 multi-processor server systems".^[71]

Advertised feature list, as of 2003:^[72]

• Runs with Red Hat 7.3 or later version of Linux
• Backward compatible with DOS and REAL/32
• Max 65535 virtual consoles; each of these can be a user
• No Linux expertise required
• Administration/setup/upgrade by web browser (local and remote)
• Supplied with TCP/IP Linux-/Windows-based terminal emulator for the number of users purchased
• Print and file sharing built in
• Drive mapping between Linux and REAL/NG servers built in
• User hardware support
• Increased performance
• Vastly increased TPA
• Multi-processor support
• Improved hardware support
• Built-in firewall support
• Very low cost per seat
• Low total cost of ownership
• Supplied on CD
• Supplied with a set of Red Hat CDs

By 10 December 2003, IMS made "REALNG V1.60-V1.19-V1.12" available,^[73] which, based on the Internet Archive, seems to be the latest release.

By 2005, the realng.com website was mirroring the IMS main website, and had no mention of REAL/NG, only REAL/32.^[74]

While the various releases of this operating system had increasing ability to run DOS programs, software written for the platform could take advantage of its features by using function calls specifically suitable for multiuser operation. It used pre-emptive multitasking, preventing badly-written applications from delaying other processes by retaining control of the processor. To this day, Multiuser DOS is supported by popular SSL/TLS libraries such as wolfSSL.

The API provided support for blocking and non-blocking message queues, mutual-exclusion queues, the ability to create sub-process threads which executed independently from the parent, and a method of pausing execution which did not waste processor cycles, unlike idle loops used by single-user operating systems. Applications were started as "attached" to a console. However, if an application did not need user interaction it could "detach" from the console and run as a background process, later reattaching to a console if needed.

Another key feature was that the memory management supported a "shared" memory model for processes (in addition to the usual models available to normal DOS programs). In the shared memory model the "code" and "data" sections of a program were isolated from each other. Because the "code" contained no modifiable data, code sections in memory could be shared by several processes running the same program, thereby reducing memory requirements.

Programs written, or adapted, for any multitasking platform need to avoid the technique used by single-tasking systems of going into endless loops until interrupted when, for example, waiting for a user to press a key; this wasted processor time that could be used by other processes. Instead, Concurrent DOS provided an API call which a process could call to "sleep" for a period of time. Later versions of the Concurrent DOS kernel included Idle Detection, which monitored DOS API calls to determine whether the application was doing useful work or in fact idle, in which case the process was suspended allowing other processes to run. Idle Detection was the catalyst for the patented DR-DOS Dynamic Idle Detection power management feature invented in 1989 by Roger Alan Gross and John P. Constant and marketed as BatteryMAX.^[75]

• CP/M
• MP/M
• Concurrent DOS V60
• FlexOS
• DR DOS
• PC DOS – IBM's OEM version of (single-user) MS-DOS
• MS-DOS 4.0 (multitasking)
• PC-MOS/386 – unrelated multitasking DOS clone
• VM/386 – unrelated multitasking DOS environment
• Virtual DOS machine
• Multiuser DOS Federation
• Timeline of operating systems
• List of mergers and acquisitions by Citrix

• Novell Desktop Systems Group (1993-01-07) [1992]. "DRTIPS.ZIP". Digital Research / Novell. Archived from the original on 2018-09-12. Retrieved 2018-04-03.

• former Intelligent Micro Software (IMS) website (vendors of IMS Multiuser DOS, IMS REAL/32, and REAL/NG)
• former Logan Industries (LLI) website (IMS REAL/32 US distributor up to 2002-05-01)
• former Concurrent Controls website (CCI Multiuser DOS)
• Applica, Inc. website
• former Aplycon Technologies, Inc. website