|This article needs additional citations for verification. (March 2011)|
DOS extenders were initially developed in the 1980s following the introduction of the Intel 80286 processor (and later expanded upon with the Intel 80386), to cope with the memory limitations of MS-DOS and its derivatives.
DOS extender operation
A DOS extender is a program that "extends" DOS so that programs running in protected mode can transparently interface with the underlying MS-DOS API. This was necessary because many of the functions provided by DOS require 16-bit segment and offset addresses pointing to memory locations within the first 640 kilobytes of memory. Protected mode, however, uses an incompatible addressing method where the segment registers (now called selectors) are used to point to an entry in the Global Descriptor Table which describes the characteristics of the segment. The two methods of addressing are mutually exclusive, with the processor having to make costly switches to real (or V86) mode to service non-protected mode requests.
In addition to setting up the environment and loading the actual program to be executed, the DOS extender also provides (amongst other things) a translation layer that maintains buffers allocated below the 1MB real mode memory barrier. These buffers are used to transfer data between the underlying real mode operating system and the protected mode program. Since switching between real/V86 mode and protected mode is a relatively time consuming operation, the extender attempts to minimize the number of switches by duplicating the functionality of many real mode operations within its own protected mode environment. As DOS uses interrupts extensively for communication between the operating system and user level software, DOS extenders intercept many of the common hardware (e.g. the real-time clock and keyboard controller) and software (e.g. DOS itself and the mouse API) interrupts. Some extenders also handle other common interrupt functions, such as video BIOS routines.
Essentially, a DOS extender is like a miniature operating system, handling much of the functionality of the underlying operating system itself.
The DOS extender was arguably invented by Phar Lap, but it was Tenberry Software, Inc.'s (formerly Rational Systems) 386 extender DOS/4GW that brought protected mode DOS programs to the masses. Included with Watcom's C, C++ and Fortran compilers for 386 class processors, it soon became a ubiquitous mainstay of PC applications and games such as id Software's successful DOOM.
While initially it was the memory hungry business applications that drove the development of DOS extenders, it would be PC games that truly brought them into the spotlight. As a result of the development of DOS extenders, two new software interfaces were created to take care of the many potential conflicts that could arise from the varied methods of memory management that already existed, as well as provide a uniform interface for client programs.
The first of these interfaces was the Virtual Control Program Interface (VCPI), but this was rapidly overshadowed by the DOS Protected Mode Interface (DPMI) specification, which grew from the Windows 3.0 development. They provided an API through which an extended program could interface with real mode software, allocate memory, and handle interrupt services. They also provided an easy method for the extender to set up the switch to protected mode, and allowed multiple protected mode programs to coexist peacefully.
- DOS/4G and DOS/4GW and DOS/16M by Tenberry Software, Inc.
- 286|DOS Extender and 386|DOS Extender by Phar Lap
- PROT by Al Williams, a 32-bit DOS extender published in Dr. Dobb's Journal and in two books. This extender had the virtue of running DOS and BIOS calls in emulated mode instead of switching back to real mode.
- PMODE and PMODE/W by Thomas Pytel and Charles Sheffold. The latter was for Watcom C as an alternative to DOS/4GW, and was quite popular with demoscene programmers
- Ergo (formerly Eclipse, formerly A. I. Architects) OS/286 and OS/386 extenders, and DPM16 and DPM32 servers
- all Microsoft Windows versions since 1990, except 64-bit editions, include both a DPMI server and DOS extender.
- HX DOS Extender provides limited Win32 support to allow Windows console applications to run under DOS.
- DosWin32 provides limited Win32 support
- CWSDPMI by Charles W. Sandmann, a DPMI server for use with 32-bit protected mode DOS DJGPP programs
- GO32, used in older (pre-v2) versions of DJGPP, and Free Pascal
- DBOS by Salford Software, a 32-bit protected mode DOS extender used primarily by their FTN77 (Fortran Compiler)
- DOS/32 as an alternative to DOS/4GW by Narech K.
- X32 and X32VM by FlashTek and supported as a target by Digital Mars compilers
Notable DOS extended applications
|This section does not cite any references or sources. (March 2011)|
- Adobe Acrobat Reader 1.0 (uses an early version of DOS/4GW professional)
- AutoCAD 11 (PharLap 386)
- Lotus 1-2-3 Release 3 (Rational Systems DOS/16M)
- Oracle Professional
- IBM Interleaf
- Major BBS, a 1980s BBS software package that utilized the Phar Lap DOS extender.
- Quarterdeck DESQview and DESQview/X multitasking software
- Watcom's C, C++ and Fortran compilers for the x86
- Countless DOS games from the early to mid 1990s, mostly using DOS/4GW, including:
- id Software's DOOM and its sequels, as well as Quake (built with DJGPP)
- Looking Glass Studios' System Shock
- Parallax Software's Descent
- Crack dot com's Abuse
- Blizzard Entertainment's Warcraft: Orcs & Humans and Warcraft II: Tides of Darkness
- 3D Realms' Duke Nukem 3D
- Midway's Mortal Kombat
- Westwood Studios' Command & Conquer and Command & Conquer: Red Alert
- DMA Design (now Rockstar North)'s Grand Theft Auto. Later versions of the game were ported to Windows in order to make it more compatible with modern computers.
- Comanche: Maximum Overkill by NovaLogic used a custom Unreal mode memory manager which required a 80386 processor and was incompatible with memory managers and virtual DOS boxes, requiring a complicated DOS boot menu configuration in CONFIG.SYS. Later revisions included a DOS extender which solved the problem.
- Ultima VII and Ultima VII Part Two: Serpent Isle by Origin Systems also used an custom Unreal mode memory manager called the Voodoo Memory Manager which was incompatible with EMS memory and memory managers such as EMM386.
- Windows 9x, which was based on top of MS-DOS
- Duncan, Ray; Petzold, Charles; Schulman, Andrew; Baker, M. Steven; Nelson, Ross P.; Davis, Stephen R.; Moote, Robert (1992). Extending DOS: A Programmer's Guide to Protected-Mode DOS (2nd ed.). Addison-Wesley Publishing Company, Inc. pp. 433–462. ISBN 0-201-56798-9.
- Williams, Al (October 1990). "Roll your own DOS extender: Part I". Dr. Dobb's Journal (CMP Technology) 15 (10): 16–18, 20, 24. ISSN 1044-789X.
- Williams, Al (November 1990). "Roll Your Own DOS Extender: Part II". Dr. Dobb's Journal (CMP Technology) 15 (11): 74, 76, 80, 81–83, 85, 122–128, 130. ISSN 1044-789X.
- Williams, Al (1991). DOS 5 A Developer's Guide. Markt&Technik. ISBN 1-55851-177-6.
- Williams, Al (1993). DOS 6 A Developer's Guide. Markt&Technik. ISBN 1-55851-309-4.
- Williams, Al (1993). DOS and Windows Protected Mode: Programming with DOS Extenders in C. Addison-Wesley. p. 30. ISBN 0-201-63218-7.