Subscribe to Windows IT Pro

 

Get Newsletters

  • Get the Latest News
  • Product Updates
  • Helpful Tricks
  • Productivity Tips

Subscribe Now!

December 01, 1998 12:00 AM

Windows NT and VMS: The Rest of the Story

Windows IT Pro
InstantDoc ID #4494
Rating: (7)
Is NT really new technology?

When Microsoft released the first version of Windows NT in April 1993, the company's marketing and public relations campaign heavily emphasized the NT (i.e., New Technology) in the operating system's (OS's) name. Microsoft promoted NT as a cutting-edge OS that included all the features users expected in an OS for workstations and small to midsized servers. Although NT was a new OS in 1993, with a new API (i.e., Win32) and new user and systems-management tools, the roots of NT's core architecture and implementation extend back to the mid-1970s.

And now...the rest of the story: I'll take you on a short tour of NT's lineage, which leads back to Digital and its VMS OS. Most of NT's lead developers, including VMS's chief architect, came from Digital, and their background heavily influenced NT's development. After I talk about NT's roots, I'll discuss the more-than-coincidental similarities between NT and VMS, and how Digital reacted to NT's release.

A Brief History of NT
NT's history is closely tied to that of David N. Cutler, NT's chief architect. After graduating from Michigan's Olivet College in 1965, Cutler worked for DuPont. Although computers weren't his first interest, he ran simulations on Digital machines as part of his job at DuPont. Before long, Cutler was knowledgeable about software and decided he wanted to develop OSs rather than application software. He joined Digital in 1971 and worked at Digital's famous "Mill" facility in Maynard, Massachusetts, developing OSs for the PDP-11 family. RSX-11M is the first OS in which Cutler incorporated major concepts and design principles that later surfaced in NT. RSX-11M is a PDP-11 OS Digital developed for industrial and manufacturing control.

In 1975, Digital realized that its competitors were developing 32-bit processors and that this technology would lure customers away from PDP's 16-bit architecture. Gordon Bell, a legendary figure in computer history and then vice president of engineering for Digital, drove the development of the 32-bit processor, which Digital eventually named VAX. By this time a star within Digital, Cutler was part of the initial VAX development team. Digital had charged Cutler, along with Dick Hustvedt and Peter Lipman, with designing VAX's OS, VMS. Digital's primary design goals for VAX hardware included backward compatibility with PDP-11 processors and enough flexibility that VAX could be the basis for low-end desktop workstations as well as enterprise-level servers. Digital also made VMS backward compatible with RSX-11M and designed VMS to run on different size machines. Of this development period, Digital states in its company history that it was "betting the business" on VAX and VMS. In an eerie echo of Digital's statement, Bill Gates recently claimed that Microsoft is "betting the business" on NT 5.0.

In 1977, Digital announced VAX-11/780 and VMS 1.0, making the first product shipments in 1978. As the project leader and one of VMS's main architects, Cutler continued work on successive releases of VMS, but he became restless at Digital. In 1981, Cutler threatened to leave Digital. To retain its star developer, Digital gave Cutler about 200 hardware and software engineers. Cutler moved his group to Seattle and started a development center. This elite group's goal was to design a new CPU architecture and OS that would lead Digital into the 1990s. Digital called the Cutler group's hardware project Prism, and its OS Mica.

In 1988, Digital executives cancelled Cutler's project and laid off many of its group members. Cutler decided to leave Digital, but before he could do so, Microsoft executives learned of the development and realized they had an ideal opportunity to hire Cutler. At the time Cutler left Digital, the release of VMS was version 5.0 (today's version is 7.1).

In August 1988, Bill Gates hired Cutler. One of Cutler's conditions for moving to Microsoft was that he could bring around 20 former Digital employees with him, including several Prism hardware engineers. Microsoft readily met this demand­the company knew hiring an OS architect of Cutler's stature was a coup, and few engineers had Cutler's track record. In addition, Gates felt that Microsoft's long-term future depended on the development of a new OS that would rival UNIX.

Microsoft's internal project name for the new OS was OS/2 NT, because Microsoft's intention was for the new OS to succeed OS/2 yet retain the OS/2 API as its primary interface. The success of Windows 3.0 in April 1990 altered Microsoft's thinking and its relationship with IBM. Six weeks after Microsoft released Windows 3.0, Microsoft renamed OS/2 NT as Windows NT, and designated the Win32 API (a 32-bit evolution of Windows 3.0's 16-bit API) NT's official API. Gates decided that compatibility with the 16-bit Windows API and the ability to run Windows 3.x applications unmodified were NT's paramount goals, in addition to support for portions of the DOS, OS/2, and POSIX APIs. From 1990 to NT's public release in August 1993, Cutler's team was in a mad dash to complete NT, and the project grew to involve more than 200 engineers and testers. Figure 1 shows a timeline of the major events in the history of NT.

Related Content:

ARTICLE TOOLS

Comments
  • Rishi
    6 years ago
    Sep 25, 2006

    We enjoyed reading it a lot and we really appreciate the work done by Cutler.

  • Anonymous User
    7 years ago
    Jul 22, 2005

    Linux sucks big time....comparing to NT...



  • Anonymous User
    7 years ago
    Jul 15, 2005

    Everything comes from somewhere. Linux was not written from scratch. The kernel was coded from scratch, but the ideas and philosophy behind Linux can be traced back to the original AT&T UNIX system. Likewise, much of the software for Linux (C compiler, X Windows, filesystem utilities, etc.) was available on the various UNIX systems long before Linux was even a thought.

    The difference, of course, is that Linux *legally* used the ideas and designs already available. Microsoft cannot claim the same thing; by using VMS code in NT, they actually committed copyright infringement. If DEC patented any parts of their system, then MS would also have committed patent infringement.

    All in all, this was an interesting and humorous article. I never knew the history of NT either, but at least MS took the design from a stable and robust OS. The instability is not NT's fault; the stability problems come from third-party drivers and poorly written applications, which Microsoft has no control over. I can write a device driver for Linux that will crash the system (guess how I know :) ) too.

  • Anonymous User
    7 years ago
    Jun 29, 2005

    You missed perhaps the most interersting part - the Digtal lawsuit that followed. MS was going to lose so they settled out of court. But the joke was on DEC because although they settled for $50M, it was all in forms that ultimately benefited MS. One part of the deal included MS subsiding the creation of Digital's MS Services practice and the training of DEC's personnel. But this was a move MS was going to make anyway in order to create a global enterprise-class support org such that MS could claim as many MCSE's were certified on NT and there were Unix support professionals in the market. Thus MS could be positioned as enterprise-ready and as supportable as Unix. Secondly, MS guaranteed they'd outsource a large % of their helpdesk calls to Digital call centers. Again, this was MS's model anyway. In that time period when you made a call to the MS helpdesk, and the person on the other end answerered "Hello. This is Microsoft, can I help you?" you were actaully talking to a Digital, NCR, HP, or Vanstar employee in their respective call centers. And even this arrangement was a joke because MS paid so little to DEC and other support partners on a per-incident basis (I recall the math was $25 per call which meant over 10-15 min's in length and you lost money on that particular call), and MS required so much reporting infrastructure and annual training hours, that the support vendors were left with no margin. In the end most of the big vendors finally got out of the MS desktop support business because it was a money loser.

    All of this came out of the theft of VMS! Even when they get caught they win.

  • Anonymous User
    7 years ago
    Apr 13, 2005

    Fantastic article. I have used both VMS and Win/NT intimately for the last 20 years, and Mark's article is right on the money.

You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

White Papers

Get your Windows 7 deployment off to the right start by implementing PC lockdown. A locked-down environment is easier and cheaper to support since users are less likely to make unnecessary changes to the core system configuration - read more here!

Essential Guides

Is your iSCSI "lossy"? The reality is that most off-the-shelf Ethernet hardware deployed for iSCSI can lose packets, resulting in slow performance or application downtime. Learn how to assess your current iSCSI infrastructure and engineer an advanced iSCSI SAN infrastructure.

Web Seminars

What's the best way to keep your network safe from malware? In this web seminar, security expert Greg Shields suggests an alternative method to the traditional blacklisting approach that is common with anti-virus and anti-malware solutions.

eLearning Series

We bring the experts direct to you to share their real-world perspective and expertise. During each event, three sessions stream in real time, so you can learn, ask questions, and get solutions.
Upcoming event: Getting the Most with Exchange 2010 with Paul Robichaux

Subscribe to Windows IT Pro!

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.