DESQview

From Infogalactic: the planetary knowledge core
(Redirected from DESQview/X)
Jump to: navigation, search
DESQview
DESQview 2.8 screenshot.png
DESQview 2.8 running on top of MS-DOS 6.22 in VirtualBox
Developer(s) Quarterdeck Office Systems
Last release DESQview/2.70[1]
Development status Historic
Platform DOS
License Proprietary commercial software
Website {{#property:P856}}

DESQview (DV) was a text mode multitasking operating environment developed by Quarterdeck Office Systems which enjoyed modest popularity in the late 1980s and early 1990s. Running on top of DOS, it allowed users to run multiple DOS programs concurrently in multiple windows, and was a direct precursor to the graphical user interface of the Microsoft Windows line which was introduced in 1985.

Desq

Quarterdeck's predecessor to DESQview was a task switching product called Desq (shipped late April[2] or May 1984[3]) which allowed users to switch between running programs. Quarterdeck revamped its package, bringing multitasking in, and adding TopView compatibility.

DESQview was released in July 1985, four months before Microsoft introduced the first version of Windows. It was widely thought to be the first program to bring multitasking and windowing capabilities to DOS, but in fact there was a predecessor, IBM's TopView, shipped March 1985,[4] from which DESQview inherited the pop-up menu.[citation needed]

Under DESQview, well-behaved DOS programs could be run concurrently in resizable, overlapping windows (something the first version of MS Windows could not do). A simple hidable menu allowed cutting and pasting between programs. DESQview provided support for simple editable macros as well. Quarterdeck also developed a set of optional utilities for DESQview, including a notepad and dialer. Later versions allowed graphics mode programs to be loaded as well, but only run in full screen mode.[5]

DESQview was not a GUI (Graphical User Interface) operating system. Rather, it was a non-graphical, windowed shell that ran in real mode on top of DOS, although it could run on any Intel 8086- or Intel 80286-based PC. It could also use expanded memory add-ons to work around the 640 kB RAM limit of conventional memory on early PCs. DESQview really came into its own on Intel 80386 machines, which were better at utilizing memory above DOS's limit. However, in either case, it ran in real mode rather than protected mode, meaning that a misbehaving program could still crash the system.

DESQview and QEMM

To make maximum use of extended memory on Intel 80386 processors, by transforming it into expanded memory and upper memory blocks (UMBs) accessible to DESQview and other real-mode programs, Quarterdeck developed a sophisticated memory manager. Owing to the foresight of its marketing manager, Quarterdeck marketed it as a separate product, QEMM-386 (Quarterdeck Expanded Memory Manager 386). It became more popular than DESQview itself, and sold steadily for many years, generating over US$150 million in sales from 1987 through 1994. After the release of the Intel Pentium processor, the 386 in QEMM was dropped. The combination package of DESQview and QEMM-386 was called DESQview 386 (DV386).

With the introduction of the 80386, the memory management features were enhanced to allow the system to be shifted into protected mode but also allowing the addresses to be configured in a virtual 8086 mode so that the extended memory could be mapped into addressing frames and accessible to real-mode programs such as MS-DOS. This allowed a 386 to implement the LIM (Lotus, Intel, Microsoft) EMS (expanded memory specification).[6] The memory manager was easily controlled by the user with DOS program QEMM.COM.

DESQview was able to use QEMM's features far beyond just the LIM EMS API, mapping most of the "conventional" address space (below 640 kB) into multiple extended memory blocks such that each could execute transparently during its context. The main copy of DOS and any device and networking drivers had to be loaded before DESQview. The resulting space was the largest single program that could run, but DESQview under QEMM could run as many instances of those programs as the EMS would allow. So an 8  MB system could generally have a dozen full-sized MS-DOS programs running concurrently; a 16  MB system could run over twenty, and so on.

DESQview usage

DESQview was noteworthy in that it supported all common DOS-compatible programs and achieved a degree of performance and stability that was remarkable, given the constraints of its host operating system. It also had a clever interface that was generally unobtrusive while being quickly available and very easy to learn.

All normal PCs include a keyboard with three "shift" or "modifier" keys: Control, Alt, and the normal Shift keys. These keys are normally held down in combination with other keys. DESQview, by default, monitored the Alt key for isolated presses (not in combination). Pressing the Alt key by itself would bring up the DESQview menu allowing access to the program's features: start new tasks, switch among them, mark text on the screen, paste text as input into the current task, resize or move the text windows, configure new menu items, etc. In addition a Shift+Alt combination would cause DESQview to learn a set of keys as a macro. This allowed DESQview to run other programs without interfering with any of the "keybindings" they might be using.[7]

DESQview was critically acclaimed and won many fans, but it never met with mass appeal, despite Quarterdeck's sustained efforts to win people over. Reportedly it intrigued many people at Microsoft, including Bill Gates, who by some accounts[which?] based his first version of Windows on DESQview and two other early GUIs, Visi On and GEM.

In one area, however, DESQview was a lasting success: many multiuser bulletin board systems were based on it, thanks to its modest hardware requirements, robust multitasking, and superlative handling of multiple communication ports. Most free or inexpensive BBS software of the time ran as a single-node, single-tasking DOS program. Normally, only one copy of the BBS software could run at once, limiting the host PC to running one node. DESQview allowed multiple copies of these single-task programs to run at once on the same computer, allowing anyone with even unimpressive hardware to run a large, powerful, multiuser BBS out of their home.

Decline of DESQview

DESQview did not provide a graphical user interface (GUI). While Quarterdeck did provide suites of programming libraries and utilities to support the development of software to use its features these never became widely popular. DESQview's ability to run most software with no modification and the cost of "run-time" licenses, combined with the costs of the development suites themselves made this an unreasonable combination for commercial shrink-wrapped software publishers and vendors.

Microsoft released MS Windows version 3.0 with its own memory management and multitasking features. While DESQview was far faster, smaller, and more stable, it was more expensive and didn't include support for the graphical features of MS Windows.

The decline of QEMM started with the bundling of a memory manager in Digital Research's DR DOS 5.0,[lower-alpha 1] released in 1990. To catch on, Microsoft included its own EMM386 in MS-DOS 5.0, while previously the memory management functionality was only available with Windows. QEMM could still be used instead, notably with Windows 3.1x, but it only provided incremental benefits. Sales of QEMM declined. In August 1994, after three quarters of losses, the company laid off 25% of their employees and the CEO, president, and founder Terry Myers resigned.

As users moved from DESQview to other platforms, notably Windows 3.x and OS/2, third party utility authors wrote utility programs that emulated some DESQview API functions to allow suitably equipped DOS programs to co-operate with these OS. The most notable were TAME (for Windows) and OS/2SPEED (for OS/2).

DESQview/X

Quarterdeck eventually also released a product named DESQview/X (DVX), which was an X Window System server running under MS-DOS and DESQview and thus provided a GUI to which X software (mostly Unix) could be ported.

DESQview/X had three window managers that it launched with, X/Motif, OPEN LOOK, and twm. The default package contained only twm, the others were costly optional extras, as was the ability to interact on TCP/IP networks.[8] Mosaic was ported to DVX.

DVX itself could serve MS-DOS programs and the 16-bit Windows environment across the network as X programs, which made it useful for those who wished to run MS-DOS and MS Windows programs from their Unix workstations.[8] The same functionality was once available with NCD Wincenter.

NetWare Access Server

Internetworking company Novell developed a product called NetWare Access Server incorporating features of DESQview 386 and pcAnywhere.[9] The DESQview multitasking support was used to create an environment into which up to 16 PC and Macintosh clients could login remotely to access NetWare services and run DOS applications.[10]

DESQview after X

DESQview development continued in parallel with DESQview/X. After ceasing development on DESQview/X, another version of DESQview was released. QEMM was still developed after the discontinuation of DESQview, and a version compatible with Windows 98 was released.

In the mid 1990s, Quarterdeck tried to recast itself as an Internet company, releasing a version of the Mosaic web browser. Eventually, the company was acquired by Symantec.

Reception

BYTE in 1984 stated that DesQ's application compatibility was the highest of the five window managers tested.[11]

Notes

  1. Prior to version 7.02, the product name was written without a hyphen.

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found..
  3. Lua error in package.lua at line 80: module 'strict' not found..
  4. Lua error in package.lua at line 80: module 'strict' not found..
  5. Perry 1991, p. 2.
  6. Perry 1991, pp. 67–101.
  7. Perry 1991, pp. 30–34.
  8. 8.0 8.1 Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.

External links and further reading

  • Screenshots of DESQview/X
  • Lua error in package.lua at line 80: module 'strict' not found. (link down – Project seems to be no longer available)
  • Lua error in package.lua at line 80: module 'strict' not found.