IBM TopView

From Infogalactic: the planetary knowledge core
(Redirected from TopView)
Jump to: navigation, search
TopView
250px
An example of a typical TopView session.
Developer IBM Corporation
Written in {{#property:p277}}
Working state Discontinued
Source model Closed source
Latest release 1.12 / 2 April 1987
Marketing target Business
Platforms x86, (DOS 2.0 - 6.0)
Default user interface Text-based (text mode)
License Proprietary
Official website {{#property:P856}}

TopView is a text-mode PC DOS multitasking, object-oriented[citation needed] windowing environment written by IBM, announced in August 1984[1] and shipped in March 1985.[2][3] TopView provided an operating environment that allowed users to run more than one application at the same time on a PC. Many industry leaders and insiders speculated on what was happening in the confidential confines of IBM Boca Raton. IBM demonstrated an early version of the product to key customers before making it generally available, around the time they shipped their new PC AT computer.

Hopeful beginnings

When Microsoft announced Windows in November 1983, International Business Machines (IBM), Microsoft's important partner in popularizing MS-DOS for the IBM PC, notably did not announce support for the forthcoming window environment.[4] IBM determined that the microcomputer market needed a multitasking environment. When it released TopView in 1985, the press speculated that the software was the start of IBM's plan to increase its control over the IBM PC (even though nothing about the IBM PC was proprietary (including the BIOS which was published to the world)) by creating a proprietary operating system for it, similar to what IBM had offered for years on its larger computers.[5] TopView also allowed IBM to serve customers who were surprised that the new IBM AT did not come with an operating system able to use the hardware multitasking and protected mode features of the new 80286 CPU, as DOS and most applications were still running in 8086/8088 real mode.

Even given TopView's virtual memory management capabilities, hardware limitations still held the new environment back—a base AT with 256 KB of RAM only had room for 80 KB of application code and data in RAM once DOS and TopView had loaded up. 512-640 KB was recommended to load up two typical application programs of the time. This was the maximum the earlier IBM XT could have installed. Once loaded, TopView took back much of the memory consumed by DOS, but still not enough to satisfy industry critics. TopView ran in real mode on any x86 processor and could run well behaved DOS programs (i.e. programs that did not write directly to the screen but used BIOS int 10h and DOS int 21h (such as the IBM Assistant Series of productivity programs)) in an arrangement of windows.[6] Well behaved applications would use standard DOS and BIOS function calls to access system services and hardware. Misbehaving programs (i.e. such as programs that did write directly to the screen) such as Lotus 1-2-3, WordStar and dBase III would still run in the TopView environment, however, they would consume the entire screen.[7] Object-oriented applications were written using the TopView API. TopView was not updated to make use of the virtual 8086 mode added in the Intel 80386 processors that allowed better virtualization.[citation needed]

Initially, compatibility with the extended features was limited mainly to IBM applications, along with a few third-party products like WordPerfect and VolksWriter. A chicken-and-egg situation developed where third-party developers were reluctant to add extended feature support (such as block insert and delete to allow users to do cut/copy/paste between applications) when they did not see market demand for them.[6] Most DOS programs did, however, support these functions and did allow the user to perform the cut, copy, and paste operations by using the TopView pop-up menus. Some believed that IBM planned to use TopView to force them to rely on them to comply with the new technical specifications.[3] As later versions of TopView were released, it was able to successfully make more challenging DOS apps run in a multitasking fashion by intercepting direct access to system services and hardware.

TopView first introduced Program Information Files (PIF files), which defined how a given DOS program should be run in a multi-tasking environment, notably to avoid giving it unnecessary resources which could remain available to other programs. TopView's PIF files were inherited and extended by Quarterdeck's DESQview and Microsoft Windows.[8] The concept of Program Information Files was also used under Digital Research operating systems such as Concurrent DOS, Multiuser DOS, System Manager and REAL/32, however, using the PIFED command, the necessary program information got directly embedded into the .EXE or .COM executable file.[9]

Version history

Version 1.1, introduced in June 1986, added support for the IBM PC Network and IBM 3270 terminal emulation. Importantly, support for swapping non-resident programs was added—onto the hard disk on all computers and into the high memory area on machines equipped with a 286 CPU. The initially poor support for DOS batch files was improved.[7]

Version 1.12, introduced in April 1987, added support for the new IBM PS/2 series, their DOS 3.30 operating system, and their new PS/2 mice. It could also now use up to four serial ports.[10]

Decline and discontinuation

TopView sold below expectations from the start, with many potential users already satisfied with cheaper, less memory-intensive TSR task switchers like Ready, Spotlight, and Borland Sidekick which didn't need a multitasking environment.[11] TopView ran in graphics mode (TOPVIEW /G), however, this was rarely used. By mid-1987, IBM began to shift focus away from TopView and was promoting the use of OS/2 to developers and end users alike. OS/2 1.0 was a pre-emptive multitasking, multithreading OS that allowed one real mode and multiple 16-bit protected mode sessions to run at the same time on the PC/AT based 80286 and provided as a DOS alternative announced in April 1987 and made available later that December. A graphical user interface (Presentation Manager) was added with OS/2 1.1 in October 1988. 1.1 could run with or without Presentation Manager as well as an embedded system with no screen, keyboard or mouse interface required. IBM officially stopped marketing the final release of TopView, version 1.12, on 3 July 1990.[3] TopView's concept was carried forward by other DOS multitaskers, most notably Quarterdeck's DESQview, which retained TopView's user interface and many features, plus added more features such as support for the special features of the 80286, 80386 and compatible processors, and, with DESQview/X (released in June 1992), a true GUI interface running on DOS. A variety of similar programs to TopView were also available, including one from Dynamical Systems called Mondrian, which Microsoft bought in 1986 with the stated intention of implementing TopView API compatibility into Windows which never happened.[12] Later in April 1992, IBM introduced OS/2 2.0 which included virtual 8086 mode and full 32-bit support of the Intel 80386 superseding even DESQview and other similar environments. OS/2 2.0 was a priority based preemptive multitasking multithreading OS including 32 levels of priority (from time critical to idle time) for the 386.

TopView requires IBM PC DOS versions 2.0 to 5.0 or MS-DOS 2.0 to 6.0, and will not run with later releases.

Key contributors to TopView included David Morrill (the "father of TopView" code-named "Orion" once the GLASS project was moved to Boca Raton), Dennis McKinley (tasking), Ross Cook (memory management), Bob Hobbs (TopView Toolkit) and Neal Whitten (product manager). Bill Gates, Steve Ballmer, Gordon Letwin and other key Microsoft executives accepted an invitation from IBM executive Don Estridge to IBM Boca Raton to see a special demonstration of TopView. Gates was disturbed that Windows did not have the tasking and windowing capabilities (i.e. overlapping windows, etc.) that TopView had. Gates witnessed TopView running multiple copies of the Microsoft BASIC interpreter running in windows (overlapping and side-by-side) in a multitasking fashion. Even though there was no joint development agreement with Microsoft for the development of TopView, Estridge asked and later told Whitten (against Whitten's and the TopView team's wishes) to turn over all source code and documentation of TopView to Microsoft. Within a short time after the meeting, Estridge's request was granted. This also led to the eventual Microsoft purchase of Mondrian (so that Microsoft could have its own version of TopView that it could further develop), a Windows requirement to do overlapping windows (as later introduced with Windows 2.0) and later the development of Windows NT (to do adequate multitasking on an Intel 80386 processor) and its eventual release in July 1993. Much of the design requirements for Windows NT came out of the original joint development agreement that IBM had with Microsoft for the development of OS/2.

Reception

InfoWorld in 1985 described TopView as "bland, plain vanilla software that hogs far too much memory".[13]

See also

References

  1. IBM. TopView Announcement Letter. 1984-08-14 ([1]).
  2. IBM. TopView Announcement Letter. 1985-02-19 ([2]).
  3. 3.0 3.1 3.2 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. Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 IBM. TopView 1.1 Announcement Letter. 1986-06-25 ([3]).
  8. Dobb's Undocumented Corner- The PIF File Format, or, TopView (sort of) Lives!
  9. Digital Research. Concurrent DOS 386 - Multiuser/Multitasking Operating System - Reference Manual. 1987 ([4]).
  10. IBM. TopView 1.12 Announcement Letter. 1987-04-02 ([5]).
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.

External links