TurboDOS
| Developer | Software 2000 Inc. |
|---|---|
| OS family | CP/M-like |
| Working state | No longer supported |
| Source model | Closed source |
| Initial release | April 1981 |
| Latest release | 1.43 / 1983 |
| Supported platforms | Zilog Z80, Intel 8086 |
| Kernel type | Monolithic kernel |
| Default user interface | Command-line interface |
| License | Proprietary |
TurboDOS is a multiuser CP/M-like operating system for the Z80 and 8086 CPUs developed by Software 2000 Inc.[1]
The multiprocessor nature of TurboDOS is its most unusual feature. Unlike other operating systems of its time where networking of processors was either an afterthought, or which only support a file transfer protocol, TurboDOS was designed from the ground up as a multiprocessor operating system.[2]
It is modular in construction, with the operating system generation based on a relocating, linking, loader program.[3] This makes the incorporation of different hardware driver modules quite easy, particularly for bus-oriented machines, such as the IEEE-696 (S-100) bus which was commonly used for TurboDOS systems.
Development#edit
Development of TurboDOS began in 1980. It was released in April 1981 for S-100 bus–based systems.[4] One of its most prominent adopters was North Star Computers, who shipped their Horizon microcomputer with TurboDOS as an option starting in 1984.[5] Other large manufacturers whose microcomputers supported TurboDOS included TeleVideo, NCR, Philips, Advanced Digital Corporation, and Ohio Scientific.[6][7]
Architecture#edit
TurboDOS is highly modular, consisting of more than forty separate functional modules distributed in relocatable form.[2][4] These modules are "building blocks" that can be combined in various ways to produce a family of compatible operating systems.[2]
Possible TurboDOS configurations include:[3]
- single-user without spooling
- single-user with spooling
- network server
- simple network user (no local disks)
- complex network user (with local disks)
Numerous subtle variations are possible in each of these categories.[3]
Module hierarchy#edit
The architecture of TurboDOS can be viewed as a three-level hierarchy. The highest level of the hierarchy is the process level. TurboDOS can support many concurrent processes at this level. The intermediate level of the hierarchy is the kernel level. The kernel supports the 93 C-functions and T-functions, and controls the sharing of computer resources such as processor time, memory, peripheral devices, and disk files. Processes make requests of the kernel through the entrypoint module OSNTRY, which decodes each C-function and T-function by number and invokes the appropriate kernel module.[3]
The C functions include the CP/M BDOS functions and selected MP/M functions.[3]
The lowest level of the hierarchy is the driver level, and contains all the device-dependent drivers necessary to interface TurboDOS to the particular hardware being used. Drivers must be provided for all peripherals, including console, printers, disks, communications channels, and network interface.[3]
Drivers are also required for the real-time clock (or other periodic interrupt source), and for bank-switched memory (if applicable).[3]
TurboDOS is designed to interface with almost any kind of peripheral hardware. It operates most efficiently with interrupt-driven, DMA-type interfaces, but can also work fine using polled and programmed-I/O devices.
TurboDOS loader#edit
System generation#edit
The functional modules are distributed in relocatable format (.REL) and the GEN command is a specialized linker which builds an executable version of the system.[3]
Commands#edit
TurboDOS has no "resident" commands. All commands are executable files. The standard commands are:[3]
References#edit
- ^ Davies, Owen, ed. (1984). Omni Complete Catalog of Computer Software. Macmillan. p. 257. ISBN 0025298208 – via the Internet Archive.
- ^ a b c Simon, Michel; William Poole (August 1984). "The Networking Capabilities of TurboDOS". Microsystems. Vol. 5, no. 8. Ziff-Davis. pp. 78–84. Gale A571953. Archived from the original on March 14, 2019 – via the CP/M-86 and CP/M-80 Museum.
- ^ a b c d e f g h i j Fowler, Ron (August 1984). "For Networks and Multiuser Systems—TurboDOS". Microsystems. Vol. 5, no. 8. Ziff-Davis. pp. 58–60. Gale A571952. Archived from the original on March 14, 2019 – via the CP/M-86 and CP/M-80 Museum.
- ^ a b Zarrella, John, ed. (1984). Microprocessor Operating Systems. Vol. 3. Microcomputer Applications. ISBN 0-935230-03-3 – via Google Books.
- ^ Sterne, Karl (August 1984). "TurboDOS Spans the Horizon". Microsystems. Vol. 5, no. 8. Ziff-Davis. p. 114. Gale A571958. Archived from the original on March 14, 2019 – via the CP/M-86 and CP/M-80 Museum.
- ^ Schofield, Jack (July 4, 1985). "How to find a useful alternative in a package deal". The Guardian. p. 15 – via Newspapers.com.
- ^ Bowker's Complete Sourcebook of Personal Computing (1985 ed.). R. R. Booker Company. 1984. pp. 1, 42. ISBN 0835219313 – via the Internet Archive.
- ^ Z80 Implementer's Guide (PDF). Software 2000, Inc. 1983. p. 8 – via Bitsavers.
External links#edit
- The TurboDOS Museum
- TUG Newsletters
- Z80 Implementors Guide (pdf)
- The TurboDOS Operating System at the Wayback Machine (archived March 27, 2022)
- Version 1.30 at the Wayback Machine (archived October 27, 2021)
This article is mirrored from “TurboDOS” on English Wikipedia, revision 1346954685, written by Wikipedia's contributors and licensed CC BY-SA 4.0. Editing it here creates a Quire copy with its own history.
Synced with Wikipedia revision 1346954685 · just now