TopView

IBM's DOS-based multitasking and windowing shell that arrived just early enough to matter and just late enough to be overtaken by everything that came after it.

TopView was IBM's answer to the obvious problem with PC-DOS: it ran one program at a time, and by the early 1980s that felt increasingly inadequate. Rather than replace DOS, IBM built TopView on top of it. The result was, technically speaking, not an operating system at all (IBM said so explicitly in its own FAQ literature) but an extension that ran on top of DOS version 2.00 and higher, adding multitasking, windowed display, and data transfer between co-resident applications.⁴ Whether that distinction comforted the users who paid for it is another matter.

What TopView Was, Precisely

IBM's own documentation is careful about the label. The product FAQ states flatly: "TopView is not an operating system. It works in conjunction with DOS version 2.00 and higher to provide a multitasking and windowing operating environment."⁴ Under DOS 3.00 and 3.10, TopView supported only the subset of functions available under DOS 2.00 or 2.10, a meaningful constraint that the documentation acknowledges without apology.⁴ The environment was strictly single-user.⁵

When you ran TopView, you could load as many applications as physical memory permitted, switch between them, view their screens in separate windows, and copy text from one to another.⁵ Paste was not universally available; it depended on how cooperative the underlying application was.¹ Background execution worked the same way: available in principle, contingent on application behavior in practice. The constraint was architectural. Because TopView needed to control the hardware directly to arbitrate multitasking, applications that wrote directly to hardware interrupt vectors or grabbed video buffers without going through TopView's interfaces could not be fully managed. Program switching was the one feature that always worked, regardless of how an application behaved.³

TopView was sold as two separately priced packages. The first was TopView itself, the runtime environment. The second was the TopView Programmer's ToolKit, which contained the application programming interface documentation, language interface tools, and programming guidelines for developers who wanted their software to take full advantage of the environment.⁵ The ToolKit was the means of reaching the deeper features; without it, developers were largely guessing.

Hardware Requirements

The minimum hardware list was modest by the standards of what TopView was trying to do. IBM specified an IBM Personal Computer, XT, Portable Personal Computer, or AT; at least 256KB of RAM; and either two double-sided diskette drives or one diskette drive plus a fixed disk.⁴ Display support covered the IBM Monochrome Display, IBM Color Display, and IBM Enhanced Color Display running in emulation mode.⁴ TopView would not run on the PCjr.⁴

IBM recommended 512KB of RAM for practical use, along with an XT or AT with a fixed disk.³ The 256KB minimum was technically honest but operationally stingy: on a 256KB PC running DOS 2.00 or 2.10, approximately 80KB remained available for actual application programs after DOS and TopView claimed their share. Under DOS 3.00 or 3.10 that number dropped to roughly 68KB.⁴ Multitasking several large programs on 256KB was possible in the same sense that crossing the Atlantic in a rowboat is possible.

For the IBM 3270 PC specifically, the recommended minimum rose to 384KB, and only the 3852, 5152, and 5182 printers were supported in that configuration.¹ TopView runs on the 3270 PC with Control Program version 1.20.⁴ IBM PC 3270 Emulation compatibility considerations for IBM TopView 1.1 are documented in IBM's PC 3270 Emulation Program Version 2.00 User's Guide.¹¹

A mouse was optional. TopView supported the Microsoft Mouse (both parallel model 037-099 and serial model 039-099), the PC Mouse by Mouse Systems (part number 900120-214, serial), and the VisiOn Mouse by VisiCorp (part number 69910-1011, serial).⁶ The keyboard could substitute as the pointing device throughout, and applications were not required to support a mouse to run under TopView.⁶ When using the IBM Professional Graphics Adapter, TopView had to be configured for the keyboard or a parallel mouse, as the PGA path was constrained.³

Application Compatibility & the API

TopView sorted applications into three tiers, a classification scheme that captures the product's central tension neatly. A plain DOS application got program switching at minimum, and possibly copy if it followed certain behavioral guidelines, with no guarantees beyond that. A TopView Aware application used two TopView-provided Interrupt 10 BIOS calls to write to the screen instead of going directly to the video buffer, gaining multitasking and windowing support while remaining usable in a plain DOS environment. A TopView Specific application was written against the full API and had access to everything, including paste without a filter table.⁷

This hierarchy mattered because most software in 1984 and 1985 fell into the first category. Applications that wrote directly to the hardware video buffer (which was most of the commercially important PC software of the era) created conflicts that TopView could not fully resolve. The product documentation is candid about this: existing applications "in general, may not be able to use every TopView feature."³

Each application required a Program Information File supplying TopView with its title, executable path, default data directory, minimum and maximum memory requirements, screen type, the range of software interrupt vectors it modified, window size and offset, and behavioral flags.⁶ Maximum memory for a single application was capped at 512KB.⁸ The system memory overhead per application (for TopView's own control blocks and video buffer) was a minimum of 7KB, rising by 16KB for any application using graphics.⁸

Batch files were not supported. IBM's Application Guide acknowledges this directly while noting that many programs launched via batch files could still be made to run under TopView with appropriate configuration.¹

The Programmer's ToolKit & Third-Party Development

The Programmer's ToolKit documented the TopView API and provided language interface tools and sample code for developers targeting the environment.⁵ Third parties moved quickly to wrap it in more accessible form. Lattice, Inc. produced the Lattice TopView Toolbasket, developed for them by Strawberry Software, which added window, cursor, and pointer functions, printer controls, cut-and-paste utilities, a debugging layer, an assembler interface, and master file and data definition headers, along with sample programs with source code.⁹ It ran on the IBM PC, XT, AT, and compatibles with 256KB minimum (512KB and the IBM ToolKit recommended), and sold for $250; binary plus source code was available for $500.⁹

The TopView API was open: any developer could obtain the ToolKit documentation and write applications against it.⁴ IBM distributed and updated a compatibility list through authorized dealers and marketing representatives.³

Specifications

Reception & Legacy

TopView's timing was awkward in a way that no amount of IBM backing could fix. It appeared in a market that was already being reshaped by the prospect of graphical environments; Microsoft Windows 1.0 shipped in 1985, and the Macintosh had arrived in 1984. TopView was text-mode and keyboard-driven at its core, with mouse support bolted on and optional. Its windowing was functional, not visual in any inspiring sense.

The deeper problem was the compatibility tier structure. A product whose headline feature (multitasking) worked fully only for software specifically written to its API, while the existing installed base of software got little more than program switching, was selling a promise more than a capability. IBM's own Application Guide table showing which features were available for which IBM programs, with columns of Y and N for Window, Copy, Paste, and Background, makes the gap concrete.¹ Paste, in particular, showed up as N frequently enough to be telling.

TopView's lasting contribution may have been forcing the conversation about what a multitasking PC environment needed to look like, and providing a published, open API against which third-party developers could write. The ToolKit documentation, the Programmer's ToolKit ecosystem, and IBM's compatibility classification scheme gave developers a vocabulary for thinking about well-behaved PC software that influenced how the platform evolved. That is a real legacy, even if TopView itself did not survive long enough to benefit from it. By the 1988 IBM product reference, TopView appears only as a line item under network software, a considerable demotion.¹²

References

1. 6481060 TopView Application Guide jan85
2. 1502480 TopView Nov84
3. PC Seminar V02 N06-1 198503 (1985)
4. G320-0845-0 198509 (1985)
5. PC Seminar V02 N06 198409 (1984)
6. G320-0846-00 198510 (1985)
7. PC Seminar V04 N02 198604 (1986)
8. G320-0843-0 198507 (1985)
9. 1985 07 BYTE 10-07 Computers and Space (1985)
10. 59X8423 PC 3270 Emulation Program Version 2.00 Users Guide Mar1986 (1986)
11. IBM Personal System 2 and IBM Personal Computer Product Reference Ver 4.0 Sep88