Windows NT 3.1

This article is about the NT operating system released in 1993. For the similar home operating system released in 1992, see Windows 3.1x.
Windows NT 3.1
A version of the Windows NT operating system

Screenshot of Windows NT 3.1
Developer Microsoft
Source model Closed-source
July 27, 1993 (1993-07-27)[1]
Latest release Service Pack 3 (3.1.528) / October 29, 1994 (1994-10-29)[2]
Platforms IA-32, Alpha, MIPS
Kernel type Hybrid
License Commercial software
Succeeded by Windows NT 3.5 (1994)
Support status
Unsupported as of December 31, 2000[3][4]

Windows NT 3.1 is a 32-bit operating system developed by Microsoft. It constitutes the first operating system of the Windows NT family and was released on July 27, 1993. Although it is the first version in the NT line, the name was chosen as a brand extension of the similar Windows 3.1.

The architecture of Windows NT 3.1 was designed from scratch, and was originally intended to be a rewrite of the OS/2 operating system that Microsoft had co-developed with IBM; however, the popularity of Windows 3.0 resulted in a change to a more Windows-like architecture, a change which subsequently resulted in IBM discontinuing its partnership with Microsoft. The central design goals were portability to multiple processor architectures, as well as higher security and stability than the previous DOS-based operating systems. Windows NT 3.1 was released in a workstation variant, called just Windows NT 3.1, and a server variant called Windows NT 3.1 Advanced Server.

The operating system's success on the market was only limited, mostly due to the high system requirements for its time and the lack of 32-bit applications which used the capabilities of Windows NT 3.1. Nevertheless, the operating system laid the foundation for all future releases of the Windows NT line.


As NT OS/2

While Microsoft had a major foothold on the personal computer market due to the use of its MS-DOS as the de facto operating system of IBM PC compatibles, Nathan Myhrvold (who had joined Microsoft after its acquisition of Dynamical Systems Research) identified two major threats to Microsoft's monopoly—the RISC architecture, which proved to be more powerful than the equivalent Intel processors that MS-DOS ran on, and Unix, a family of cross-platform multitasking operating systems with support for multiprocessing and networking. While the widespread use of Unix was hindered by the need to adapt programs for each individual variant, Bill Gates believed that the combination of a Unix-like operating system with RISC processors could be a market threat, prompting the need for Microsoft to develop a "Unix killer" that could run on multiple architectures.[5]

Gates hired David N. Cutler from Digital Equipment Corporation to assist in developing the new operating system; Cutler had left the company after a series of conflicts surrounding its work on the Prism architecture and its microkernel operating system Mica, and agreed to join Microsoft on the condition that he be able to bring a number of staff members from his team at DEC with him.[6][7][8][9][10] Cutler arrived at Microsoft on October 31, 1988,[11] and work on the future operating system started in November.[12]

The operating system was first developed as a revised version of OS/2, an operating system Microsoft had jointly developed with IBM.[13] While OS/2 was originally intended to succeed MS-DOS, it had yet to be commercially successful. The OS was to be designed so it could be ported to different processor platforms, and support multiprocessor systems, which few operating systems did at that time.[14][15][16] To target the enterprise market, the OS was also to support networking, the POSIX standard, and a security platform compliant with the "Orange Book" standards; which would require the OS to be a multi-user system with a permission framework and the ability to audit security-related events.[17]

To ensure that the use of x86-specific code was avoided, the team first targeted development of the OS to a non-x86 processor—an emulated version of Intel's i860. Alluding to the chip's codename, "N10", the operating system was codenamed NT OS/2.[18] When DEC preemptively sued Microsoft for allegedly stealing code from Mica for use on the new operating system, Microsoft agreed to support DEC's Alpha processor in an out-of-court settlement.[12] By April 1989, the kernel could run inside the emulator; the development team originally estimated that development would be completed within 18 months. After determining that the i860 would be unsuitable for the project, development of NT OS/2 was shifted in December to a MIPS R3000 chip, with the port completed within three months.[18] Uncertainties developed over how soon the NT project would be completed; Paul Maritz suggested in February 1990 that the new OS be previewed at COMDEX later that year to quell speculation from competitors that the OS wouldn't be completed until 1994 (Maritz estimated that it would be completed in 1992).[19]

As Windows NT

In May 1990, Microsoft would release Windows 3.0, the next version of its own MS-DOS-based Windows operating system. The commercial success of Windows 3.0 had negative effects on the OS/2 partnership; IBM wanted Microsoft to concentrate solely on developing OS/2 as its primary platform as opposed to building their future business around Windows,[20] users and developers were unsure of whether to adopt Windows or OS/2 due to these uncertainties (a situation magnified by the fact that the operating systems were incompatible with each other at the API level), while Microsoft's resources were also being drained by the simultaneous development of multiple operating systems.[21][22] In August 1990, as a response to the popularity of Windows 3.0, the NT OS/2 team decided to re-work the operating system to use an extended 32-bit port of the Windows API known as Win32. Win32 maintained the familiar structure of the 16-bit APIs used by Windows, which would allow developers to easily adapt their software for the new platform while maintaining a level of compatibility with existing software for Windows.[23] With the shift to a Windows-like architecture, the operating system's shell was also changed from OS/2's Presentation Manager to Windows' Program Manager.[24][25][26]

Due to these changes, NT would not be presented at COMDEX 1990 as was originally planned.[24] Neither the general public nor IBM knew about the transformation of NT OS/2 into Windows NT at the time.[27] Although the companies did agree to a revised partnership where IBM and Microsoft would alternate developing major versions of OS/2 instead of collaborating on each version,[28] IBM eventually learned of Microsoft's Windows NT plans in January 1991, and immediately ended the OS/2 partnership. As had been originally planned, IBM would solely develop OS/2 2.0, along with future versions, without any further involvement from Microsoft.[23][29]

In October 1991, Windows NT received its first public demonstration at COMDEX; in an effort to ensure software taking advantage of Windows NT was available upon its release (scheduled for late-1992), Microsoft also distributed a 32-bit software development kit to selected developers in attendance.[30][31] The demonstration was positively received; PC Magazine called Windows NT “the modern reinvention of the operating system”, but at the same time claimed that it was unlikely that the promised backward compatibility would be kept for the final release.[32][33] In March 1992, Microsoft also released Win32s, which would allow Windows 3.1 to have partial compatibility with Windows NT programs for the purposes of developing software optimized for the platform.[34]

At Microsoft's Win32 Professional Developers Conference in June 1992, Windows NT was demonstrated running on x86 and MIPS processors, while a beta version of Windows NT and an updated development kit were also made available.[35] Concurrently, Microsoft announced a new version of its SQL Server product for Windows NT; Unix vendors feared that the software could be a killer app that would affect the market share of Unix systems.[36][37] Concerns were also raised over NT's memory usage; while most computers of the era shipped with 4 megabytes of RAM, 16 MB was recommended for NTs. Due to the high cost of RAM at the time, critics thought that its high system requirements could affect the sales and adoption of Windows NT. Steps were taken to reduce its memory usage through methods such as paging.[38][39][40][41]

Microsoft began releasing public beta builds of NT in October 1992, and a month later at COMDEX, a presentation focusing on third-party software for Windows NT was held.[42][43][44] The final pre-release version of NT was released in March 1993, alongside the unveiling of the server version, Windows NT with LAN Manager. Although its stability and performance had improved, there were still fears that the OS could be released in an unfinished state or delayed further into 1993.[45][46]


Windows NT 3.1 and Windows NT 3.1 Advanced Server (named to associate them with Windows 3.1) were released on July 26, 1993.[47] At first, only the x86 and MIPS versions shipped, the DEC Alpha version followed in September.[18][48] The workstation version cost $495; the server version was planned to be sold for $2,995 and be available in the first six months only for $1,495,[49] but in the end this discount was kept until the release of the successor.[50] 250 programmers[51] wrote 5.6 million lines of code,[52] the development cost $150 million.[53] In the last year of development, over 30,000 bugs were fixed.[47]

To fix errors in the operating system, three service packs were published subsequently: Service Pack 1 was released on October 8, 1993,[54] Service Pack 2 followed on January 24, 1994[55] and Service Pack 3's release came on October 29, 1994.[56] The Service Packs were rolled not only on CD and floppies,[57] but also via bulletin board systems, CompuServe and the Internet.[58] Support for the operating system ended on December 31, 2000.[3]

Windows NT 3.1 was localized into various languages, besides English, it was available in Dutch, French, German, Japanese, Spanish and Swedish. Only the workstation, but not the server was available in Danish, Finnish, Italian, Norwegian and Portuguese.[59]

Operating system goals

Cutler set three main goals for Windows NT. The first goal was portability: in contrast to previous operating systems, which were strongly tied to one architecture, Windows NT should be able to operate on multiple architectures.[60] To meet this goal, most of the operating systems, including the operating system core, had to be written in the C programming language.[61] During the planning phase it was clear that this would cause Windows NT to have higher memory consumption than all previous operating systems.[62] Besides the graphics system and parts of the networking system, which were written in C++, only parts of the operating systems which required direct hardware access and performance critical functions were written in assembly language. These parts were isolated so that they could easily be rewritten when porting the operating system to a new architecture.[63]

The second goal was reliability: The system should no longer crash due to a faulty application or faulty hardware.[64] This way, the operating system should be made attractive for critical applications.[26] To meet this goal, the architecture of Windows NT was designed so that the operating system core was isolated and applications could not access it directly.[65] The kernel was designed as a microkernel and components of the core were to run atop the kernel in a modular fashion; Cutler knew this principle from his work at Digital.[66] Reliability also includes security, and the operating system should be able to resist external attacks.[64] Mainframes already had a system where every user had their own account which was assigned specific rights by the administrator, this way, users could be prevented access to confidential documents.[67] A virtual memory management was designed to thwart attacks by malware and prevent users from accessing foreign areas of memory.[68]

The third goal was called personality: The operating system should be able to run applications designed for various operating systems, such as Windows, MS-DOS and OS/2 applications.[26] The Mach kernel followed a similar concept by moving the APIs to components which operated in user mode as applications, these could be changed and new ones could be added. This principle was applied to Windows NT.[69]

Despite all these goals, the performance of the operating system was optimized where possible, by adapting critical sections of the code to fast execution speed. To improve networking performance, large parts of the networking system were moved to the operating system core.[70]

Windows NT was designed as a networking operating system. In this branch, Novell had a lead with its product NetWare, mostly because of a lack of competition, and Microsoft failed to develop a product which could challenge NetWare's lead. Cutler hoped to gain additional customers with a reliable networking operating system.[71] Bill Gates already dominated the market of desktop operating systems with MS-DOS and Windows and hoped to do the same in the networking market with Windows NT.[72] He especially hoped to find a market in the emerging amount of servers, while at the same time he did not expect a success in the desktop market until 1995.[73]

Therefore, Windows NT was positioned as a high-end operating system in an interview with the product manager David Thacher. It was not designed to replace Windows 3.1 completely, but it should rather supplement Microsoft's product palette with an operating system for critical applications. The expectations were 10% to 20% among all Windows sales[51] and a market share of 10% in the high end market, which amounted to one million copies.[74]



While Windows NT 3.1 uses the same graphical user interface as Windows 3.1, it was developed anew. The operating system is not DOS-based, but an independent 32-bit operating system; many concepts were taken from Cutler's previous operating system, VMS.[61] The architecture of Windows NT takes some ideas of the client-server model, like the modular structure and the communication between the modules.[75] System resources like memory, files or devices are viewed as objects by the operating system, which are all accessed in the same way through handles and which can in this way be secured against unauthorized access.[76]

The operating system was designed for multiprocessor systems; it supports preemptive multitasking[77] and can make use of threads to run multiple processes in parallel.[78] Using symmetric multiprocessing, the processing usage is evenly distributed among all available processors.[79] The inter-process communication in Windows NT 3.1 is designed around networks; two newly introduced functions, Remote Procedure Call (RPC) and Network DDE, an extension of Dynamic Data Exchange (DDE), facilitate the access and data exchange between processes running on different computers inside a network.[80]

The operating system is designed to combine certain elements of a monolithic kernel and a microkernel;[75] nowadays this is most often referred to as a hybrid kernel.[81] The hardware abstraction layer represents the lowermost layer and isolates the operating system from the underlying hardware to make it easy to port the operating system to other platforms.[82] The kernel running atop only has very basic functions like interrupt management and processor synchronization. All other functions of the operating system core are handled by modules[75] which operate independently from one another and can be swapped without affecting the rest of the operating system.[83]

Positioned above the operating system core are the subsystems. There are two types of subsystems: one are the integral subsystems, which perform important operating system functions. One such subsystem is the security subsystem, which handles the logon process and monitors the security of the system. The other type of subsystem is the environment subsystem, which exposes the operating system functions to applications via application programming interfaces.[84] The base subsystem is the 32-bit subsystem which runs 32-bit applications written for Windows NT. Windows NT applications can only run on one platform, and must be recompiled for every platform. The 32-bit subsystem also contains all output functions, including the Graphics Device Interface (GDI),[85] so all other subsystems have to call the 32-bit subsystem to be able to output text or graphics.[86] Other subsystems contained in Windows NT 3.1 are the POSIX subsystem, which supports POSIX-compatible applications built for Windows NT, and, in the x86 version only, the OS/2 subsystem, which allows command-line based OS/2 1.x applications to run.[85]

The Virtual DOS Machine (VDM) is sometimes also viewed as a subsystem, but is, strictly speaking, a normal 32-bit Windows application.[87] It manages applications originally built for DOS. Built on top is Windows on Windows (WoW), which allows applications built for 16-bit Windows operating systems like Windows 3.1 to run.[88] On x86 computers, the virtual DOS machine uses the virtual 8086 mode to run DOS applications directly,[85] on RISC computers, an emulator licensed from Insignia Solutions is used which emulates a 80286 processor.[89] However, not all DOS and 16-bit Windows applications can be run on Windows NT 3.1 due to various limitations,[90] one of them being the inability of applications to directly access the hardware. As well, VxD files sometimes needed by applications cannot be used with Windows NT 3.1.[91] While pure DOS applications are run in separate memory spaces, 16-bit Windows applications have to share one memory space. While this is done due to compatibility reasons with applications which depend on this ability, like Schedule+ and Microsoft Mail,[87] it also means that 16-bit Windows applications only run in cooperative multitasking. A faulty 16-bit Windows application is in this way able to cause all other 16-bit Windows applications (but not Windows NT itself) to crash.[85]

Graphical view of the architecture of Windows NT 3.1. Shown are the following components of the operating system core: I/O Manager, Object Manager, Security Reference Monitor, Process Manager, Local Procedure Call Facility, Virtual Memory Manager.[86][92]


Windows NT 3.1 provides a boot manager called NTLDR which is loaded during the startup process of the operating system on x86-based computers.[93] It allows a multiboot setup of multiple instances of Windows NT 3.1, as well as MS-DOS and OS/2 1.x.[94] NTLDR is not used for the RISC versions because the RISC computers' firmware provides their own boot manager.[95]

Every user has to log on to the computer after Windows NT 3.1 is booted up by pressing the key combination Ctrl+Alt+Del and entering the user name and password. All users have their own user account, and user-specific settings like the Program Manager groups are stored separately for every user. Users can be assigned specific rights, like the right to change the system time or the right to shut down the computer. To facilitate management of user accounts, it is also possible to group multiple user accounts and assign rights to groups of users.[85]

Windows NT 3.1 introduced the new NTFS file system. This new file system is more robust against hardware failures[68] and allows assignment of read and write rights to users or groups on the file system level.[85] NTFS supports long file names[85] and has features to accommodate POSIX applications like hard links.[96] For compatibility reasons, Windows NT 3.1 also supports FAT16 as well as OS/2's file system HPFS.[85]

Designed as a networking operating system, Windows NT 3.1 supports multiple network protocols. Besides IPX/SPX and NetBEUI, the TCP/IP protocol is supported allowing access to the Internet.[85] Similar to Windows for Workgroups, files and printers can be shared and the access rights and configuration of these resources can be edited over the network. When a network printer is installed, the required drivers are automatically transferred over the network, removing the need to manually install the drivers for every computer.[85] The Remote Access Service (RAS) allows a client from outside the network to connect to the network using a modem, ISDN or X.25 and access its resources. While the workstation allows one RAS connection at a time, the server supports 64.[85]

Windows NT 3.1 supports the then-new Unicode standard, a character set which allows multiple languages to be displayed. This facilitates localization of the operating system.[97] All strings, as well as file and folder names, are internally processed in Unicode,[98] but the included programs, like the File Manager, are not Unicode aware, so folders containing Unicode characters cannot be accessed.[99] For demonstration purposes, a Unicode typeface called Lucida Sans Unicode is shipped with Windows NT 3.1[100] even though it is not installed by default.[101] The previous code pages are still supported for compatibility purposes.[97]

The Windows registry, introduced with Windows NT 3.1, is a central, hierarchical configuration database[85] designed to allow configuration of computers over the network[102] and to replace the commonly-used text-based configuration files, like INI files, AUTOEXEC.BAT and CONFIG.SYS.[103] Using the undocumented registry editor, the Windows registry can be viewed and edited by the user.[85]

The Advanced Server is designed to manage the workstation computers.[85] It can function as a Domain controller, where all users and groups as well as their rights are stored. This way, a user can log on from any computer in the network, and users can be managed centrally on the server. Trust relationships can be built to other domains to be able to exchange data cross-domain.[85] Using the replication service, files like logon scripts can be synchronized across all computers on the network.[104] The Advanced Server supports the AppleTalk protocol to allow connections to Macintosh computers.[85] Hard drives can be combined to RAIDs in Windows NT 3.1 Advanced Server, the supported configurations are RAID 0, RAID 1 and RAID 5.[105]

Included programs

Windows NT 3.1, for the most part, comes with 32-bit versions of the components featured in Windows 3.1 and Windows for Workgroups. However, it also included applications specifically aimed at the needs of Windows NT, like the User Manager, the Performance Monitor, the Disk Administrator, the Event Viewer and the Backup application. The Advanced Server contained further, server-specific administration tools. Because Windows NT 3.1 is not DOS-based, a new 32-bit command-line processor, called CMD.EXE was included which was compatible with MS-DOS 5.0.[85] For compatibility reasons, Windows NT 3.1 shipped with a few 16-bit applications, like Microsoft Write or EDLIN.[106]

Windows NT 3.1, being an all-new operating system for which no previous drivers could be used, includes a wealth of drivers for various common components and peripherals.[90] This includes common SCSI devices like hard drives, CD-ROM drives, tape drives and image scanners,[107] as well as ISA devices like graphics cards, sound cards and network cards. The PCI bus, however, is expressly not supported.[108] Windows NT 3.1 supports an uninterruptible power supply.[109]

Windows NT 3.1 could be installed either by using the CD-ROM and a provided boot disk, or by utilizing a set of 22 3.5" floppies[110] (23 floppies for Advanced Server[111]). Windows NT 3.1 could also be installed over the network.[85] A coupon was included that made it possible to order a set of 27 5.25" floppies[112] (or 28 floppies for Advanced Server[113]).[114] Compared to the floppies, the CD-ROM contained additional drivers[115] and applications.

System requirements

Windows NT 3.1 supports multiple platforms: Aside from the x86 architecture, it runs on computers with DEC Alpha or MIPS (R4000 and R4400) processors.[116]

Minimum system requirements on x86 systems include a 25 MHz 80386 processor, at least 12 megabytes of memory, 75 megabytes of hard drive space, and a VGA graphics card.[117] RISC systems require 16 megabytes of memory, 92 megabytes of hard drive space, and a CD-ROM drive.[118] The Advanced Server edition requires an 80386 processor with 16 megabytes of memory and 90 megabytes of hard drive space. On RISC systems, 110 megabytes of hard drive space is needed.[119]

Windows NT 3.1 supports dual processor systems, while the Advanced Server edition supports up to four processors.[117] Due to an error in the processor detection routine, Windows NT 3.1 cannot be installed on Pentium II or newer processors. Microsoft never fixed the problem, but unofficial patches are available.[118]


Windows NT 3.1 sold about 300,000 copies in its first year.[120] The hardware requirements were deemed to be very high at that time; the recommended system requirements of a 486 processor with 16 megabytes of memory were well above the average computer's configuration,[90] and the operating system turned out to be too slow to use.[121] 32-bit applications which could have used the capabilities of Windows NT 3.1 were scarce, so users had to resort to the old 16-bit applications; however, these ran slower than on Windows 3.1. Estimates in November 1993 counted only 150 Windows NT applications,[122] common software, like an office suite, was not available at all for Windows NT 3.1.[90] During the development of the operating system, the API calls were changed so 32-bit applications built on the pre-release version of Windows NT 3.1 could not be run on the final version. This affected even commercial software like Microsoft Visual C++.[123]

RISC systems with Windows NT 3.1 had an even bigger disadvantage: even though they were more powerful than x86 systems,[80] almost no 32-bit applications or drivers were ported to these platforms.[120] 16-bit applications ran much slower under RISC systems because of the 80286 emulation compared to x86 systems which could run 16-bit applications natively,[80] and DOS and 16-bit applications which depended on 386 calls could not be run at all on RISC systems.[89]

However, not all reception was negative; the multitasking capabilities of the operating system were rated positively, especially compared to Windows 3.1.[85] Compared to the size of the operating system, the installation turned out to be very easy, even though installing from floppies was a very time-consuming task.[124] The Advanced Server, intended to be the successor to the unsuccessful LAN Manager product, was technically much superior to its predecessor, and only failed to gain success because it shared the same problems with its workstation pendant, such as the low performance running 16-bit applications.[125] The Advanced Server provided a financial advantage for large networks because its price was not dependent on the amount of clients, unlike its competitor Novell NetWare.[119]

With Windows NT, Microsoft entered a market it could not previously address and which was mostly dominated by Unix, Novell NetWare and OS/2.[126] A test performed by the InfoWorld magazine in November 1993, where the networking capabilities of several operating systems were tested, showed that Windows NT 3.1 was seriously lacking in inter-client communication: it could only connect to its own server via NetBEUI; attempts to connect to Unix, NetWare and OS/2 all failed because no client software was available. For the Advanced Server, only their own client, the Macintosh and, if only limited, OS/2 were able to connect to the server.[127]

Even though the operating system's actual success was only moderate, it had a huge lasting impact. Developers of Unix derivations for the first time strived to standardize their operating systems, and Novell was so concerned about its market share that it bought a Unix vendor.[128] Manufacturers of microprocessors hoped to use the portability of the new operating system to increase their own sales,[128] and thus ports of Windows NT were announced for various platforms, like the Sun SPARC architecture[129] and the Clipper architecture.[130] It was recognized that Windows NT would dominate the desktop market as soon as the hardware became powerful enough to run the operating system at an acceptable speed.[131] Eight years later, Microsoft would unify the consumer-oriented Windows line (which had remained MS-DOS based) with the NT line with the October 2001 release of Windows XP—the first consumer-oriented version of Windows to use the NT architecture.[132]

Notes and references


  1. Paul Adams (August 4, 2009). "Windows NT History".
  3. 1 2 "Microsoft Support Lifecycle - Windows NT Workstation 3.1". Retrieved 2012-06-08.
  4. "Microsoft Support Lifecycle - Windows NT Advanced Server 3.1". Retrieved 2012-10-06.
  5. Zachary 2009, p. 35
  6. Zachary 2009, p. 24
  7. Zachary 2009, p. 17
  8. Zachary 2009, p. 37
  9. Zachary 2009, p. 25
  10. Zachary 2009, p. 36
  11. Zachary 2009, p. 38
  12. 1 2 Smith, Mark (1999-08-27). "The Death of Alpha on NT". Retrieved 2012-05-19.
  13. Custer 1993, pp. 43–44
  14. Custer 1993, p. 2
  15. Zachary 2009, p. 33
  16. "National Museum of American History | Microsoft Windows NT OS/2 Design Workbook". Retrieved 2012-06-09.
  17. "Department of Defense - Trusted Computer System Evaluation Criteria" (PDF; 0,4 MB). Retrieved 2012-09-19.
  18. 1 2 3 Thurrott, Paul (2003-01-24). "Windows Server 2003: The Road To Gold - Part One: The Early Years". Archived from the original on 2005-01-01. Retrieved 2012-05-28.
  19. Custer 1993, pp. 84–85
  20. Zachary 2009, p. 100
  21. Custer 1993, pp. 98–99
  22. Glass, Brett (1991-05-27). "Windows, OS/2 debate is still a hot topic: Software vendors with limited resources are still forced to choose between Windows and OS/2 development". InfoWorld. 13 (21): 66.
  23. 1 2 Johnston, Stuart J. (1991-07-08). "Microsoft drops OS/2 2.0 API, revamps 32-bit Windows plan: Users face choice between OS/2 and Windows NT". InfoWorld. 13 (27): 1, 103.
  24. 1 2 Zachary 2009, p. 102
  25. Zachary 2009, p. 105
  26. 1 2 3 Zachary 2009, p. 54
  27. Zachary 2009, p. 108
  28. Parker, Rachel (1990-12-24). "Two giants with own views: IBM needs OS/2; Microsoft does Windows". InfoWorld. 12 (52): 8.
  29. Custer 1993, pp. 108–109
  30. Zachary 2009, p. 165
  31. Johnston, Stuart J. (1991-10-28). "NT looks real at Comdex: Microsoft declares it will start beta tests in early 1992". InfoWorld. 13 (43): 1, 8.
  32. Machrone, Bill (1991-11-26). "Are NT Promises MT Promises?". PC Magazine. 10 (20): 85f. ISSN 0888-8507.
  33. Custer 1993, pp. 175–176
  34. Johnston, Stuart J. (1992-03-02). "Microsoft reveals 32-bit strategy: Win32s lets NT applications run on Windows 3.1". InfoWorld. 14 (9): 1, 107.
  35. Strehlo, Kevin (1992-07-13). "Microsoft makes its move with Windows NT SDK". InfoWorld. 14 (28): 1, 92.
  36. Johnston, Stuart J. (1992-07-20). "SDK readied for SQL Server for NT: Will speed writing of 32-bit code". InfoWorld. 14 (29): 8.
  37. Hammett, Jim; McCarthy, Vance (1992-12-14). "Unix vendors strike out at Microsoft: Campaign seeks to steal thunder of Windows NT". InfoWorld. 14 (50): 8.
  38. Zachary 2009, p. 227
  39. Zachary 2009, p. 229
  40. Zachary 2009, p. 230
  41. Custer 1993, pp. 248–249
  42. Willett, Shawn (1992-10-12). "NT's delays mean a second look and respect for OS/2". InfoWorld. 14 (41): 17.
  43. Johnston, Stuart J. (1992-10-26). "Microsoft rolls out Windows NT beta". InfoWorld. 14 (43): 3.
  44. Johnston, Stuart J. (1992-11-23). "Vendors throw support behind Windows NT". InfoWorld. 14 (47): 3.
  45. Johnston, Stuart J. (1993-04-05). "NT is shaping up, say latest beta users: But they want a bug-free final version, even if it's late". InfoWorld. 15 (14): 3.
  46. Willett, Shawn; Borzo, Jeanette (1993-05-31). "Users praise NT's graphics support at Comdex". InfoWorld. 15 (22): 13.
  47. 1 2 Zachary 2009, p. 300
  48. Johnston, Stuart J.; Barney, Doug (1993-09-20). "NT version for Alpha chip poised to ship to users". InfoWorld. 15 (38): 3.
  49. Mace, Scott (1993-05-31). "NT keeps client/server apps waiting: Database servers will be ready as soon as Microsoft ships delayed OS". InfoWorld. 15 (22): 1.
  50. Barney, Doug (1994-09-19). "Microsoft set to ship Windows NT 3.5: Will bolster push into enterprise with SMS release". InfoWorld. 16 (38): 5.
  51. 1 2 Hixson, Amanda (1993-05-24). "Aiming for the high end: An Interview with Paul Thatcher, Microsoft's Windows NT product manager". InfoWorld. 15 (21): 92.
  52. Zachary 2009, p. 290
  53. Zachary 2009, p. 307
  54. Dave Macdonald (1993-10-08). "First update for Windows NT 3.1 is available!". Newsgroup: Usenet:
  55. Steve Heaney (1994-01-24). "US Service Pack 2 Now Available". Newsgroup: Usenet:
  56. "moderator" (1994-11-07). "61 New Uploads to CICA [11/07/94]". Newsgroup: Usenet:
  57. Microsoft Knowledge Base - README.TXT: U.S. Service Pack for Windows NT (no longer available online)
  58. Microsoft Knowledge Base - How To Obtain U.S. Service Pack for Windows NT (no longer available online, the Knowledge Base number 104597 now refers to a different article)
  59. "Microsoft - List of Localized MS Operating Systems - Older Versions of Windows". Retrieved 2012-06-04.
  60. Zachary 2009, p. 53
  61. 1 2 Russinovich, Mark (1998-12-01). "Windows NT and VMS: The Rest of the Story". Retrieved 2012-05-19.
  62. Zachary 2009, p. 55
  63. Custer 1993, pp. 8–9
  64. 1 2 Custer 1993, p. 9
  65. Zachary 2009, p. 56
  66. Zachary 2009, p. 57
  67. Custer 1993, pp. 157–158
  68. 1 2 Custer 1993, p. 10
  69. Custer 1993, p. 6
  70. Custer 1993, p. 12
  71. Zachary 2009, p. 65
  72. Zachary 2009, p. 3
  73. Zachary 2009, p. 151
  74. Hixson, Amanda (1993-05-24). "Building an infrastructure: Microsoft recognizes that it needs solid partnerships to give it credibility at the high end". InfoWorld. 15 (21): 85.
  75. 1 2 3 Custer 1993, p. 20
  76. Custer 1993, pp. 22–23
  77. Custer 1993, p. 92
  78. Custer 1993, p. 94
  79. Custer 1993, p. 24
  80. 1 2 3 Ayre, Rick; Raskin, Robin (1993-09-28). "Windows NT: See how it runs". PC Magazine. 12 (16): 211–231. ISSN 0888-8507.
  81. "MS Windows NT Kernel-mode User and GDI White Paper". Retrieved 2012-06-07.
  82. Custer 1993, p. 30
  83. Custer 1993, p. 28
  84. Custer 1993, p. 27
  85. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 Siering, Peter (1993). "Paarige Premiere: Microsoft Windows NT 3.1 und Advanced Server". c't (11): 142 ff.
  86. 1 2 Custer 1993, p. 33
  87. 1 2 "Microsoft Knowledge Base - Why 16-Bit Windows Applications Run in Single VDM". Retrieved 2012-07-17.
  88. "Microsoft Knowledge Base - Unable to Start Win 16 WOW Applications". Retrieved 2012-07-18.
  89. 1 2 "Microsoft Knowledge Base - Windows NT Only Supports Standard Mode Windows on RISC". Retrieved 2012-09-04.
  90. 1 2 3 4 Siering, Peter (1994). "Lizenz-Rezepte: Windows NT 3.5 Workstation und Server". c't (12): 266 ff.
  91. "Microsoft Knowledge Base - Virtual Device Drivers (VXDs) Do Not Work in Windows NT". Retrieved 2012-06-11.
  92. Custer 1993, p. 26
  93. "Microsoft Knowledge Base - Intel x86-basierte Systemstartsequenz und -dateien". Retrieved 2012-06-08.
  94. "Microsoft Knowledge Base - Windows NT Multi-Boot Support Limitations". Retrieved 2012-06-08.
  95. "Windows NT Resource Kit - Chapter 19 - What Happens When You Start Your Computer". Retrieved 2012-06-08.
  96. Custer 1993, p. 39
  97. 1 2 "Microsoft Knowledge Base - Unicode and Microsoft Windows NT". Retrieved 2012-06-07.
  98. Custer 1993, p. 43
  99. "Microsoft Knowledge Base - Windows NT File Manager: Services for Macintosh Concerns". Retrieved 2012-06-08.
  100. Bigelow, Charles; Holmes, Kris (1993-09-00). "The design of a Unicode font" (PDF; 0,5 MB). Electronic Publishing. 6 (3): 289–305. ISSN 0894-3982. Check date values in: |date= (help)
  101. "Microsoft Knowledge Base - Keys Produce "?" with Russian Language Settings". Retrieved 2012-06-08.
  102. Zachary 2009, p. 251
  103. Custer 1993, p. 327
  104. "Microsoft Knowledge Base - Windows NT AS Features Not Included in Windows NT". Retrieved 2012-06-10.
  105. "Microsoft Knowledge Base - Überblick über RAIDs (Redundant Arrays of Inexpensive Disks)". Retrieved 2012-06-07.
  106. "Microsoft Knowledge Base - 16-Bit Applications Included with Windows NT". Retrieved 2012-07-26.
  107. "Microsoft Knowledge Base - Contents of Windows NT SETUP.TXT, Part 1". Retrieved 2012-07-09.
  108. "Microsoft Knowledge Base - Support for PCI Computers and Peripherals in Windows NT 3.1". Retrieved 2012-07-09.
  109. Custer 1993, p. 328
  110. "Microsoft Knowledge Base - Windows NT 3.5 Inch Disk Contents (511)". Retrieved 2012-07-12.
  111. "Microsoft Knowledge Base - Windows NT Advanced Server 3.5 Inch Disk Contents (511)". Retrieved 2012-07-12.
  112. "Microsoft Knowledge Base - Windows NT 5.25 Inch Disk Contents (511)". Retrieved 2012-09-06.
  113. "Microsoft Knowledge Base - Windows NT Advanced Server 5.25 Inch Disk Contents (511)". Retrieved 2012-09-06.
  114. "Microsoft Windows NT version 3.1 - Computing History". Retrieved 2012-09-06.
  115. "Microsoft Knowledge Base - Extra Drivers Included on Windows NT and NTAS CD-ROM". Retrieved 2012-09-04.
  116. "Microsoft-Werbung". InfoWorld. 15 (49): 15. 1993-12-06.
  117. 1 2 "Microsoft Knowledge Base - Recommended Hardware Configs. for Workstations and Servers". Retrieved 2012-06-08.
  118. 1 2 "Windows NT 3.1 bei". Archived from the original on January 19, 2008. Retrieved 2012-09-05.
  119. 1 2 Strom, David; Capen, Tracey; Crawford, Tim; Gallie, Rodney; Chapin, Rod (1993-11-15). "A bumper crop of network operating systems brings centralized management, application services, and more capable clients to the enterprise". InfoWorld. 15 (46): 138–150.
  120. 1 2 "c't - Zehn Jahre Windows NT -- ein Rückblick". 2003-07-27. Retrieved 2012-06-09.
  121. Strehlo, Kevin; Gallie, Rodney (1993-08-16). "Windows NT: a robust server but a poor OS". InfoWorld. 15 (33): 1, 100.
  122. Korzeniowski, Paul (1993-11-15). "More than just a print and file server". InfoWorld. 15 (46): 84.
  123. "Microsoft Knowledge Base - Running Visual C++ for Windows with Windows NT". Retrieved 2012-06-14.
  124. Howell, Dave (1993-11-15). "Diary of an NT install: With a small amount of preparation and the right hardware, installing NT is a no-brainer". InfoWorld. 15 (46): 96–98.
  125. Korzeniowski, Paul (1993-11-15). "Windows NT Advanced Server: The new network OS seems to be on a slow climb toward acceptance". InfoWorld. 15 (46): 81.
  126. Korzeniowski, Paul; Barney, Doug (1993-11-15). "Which Windows when, where and why? Do you need to know the way to Cairo and Chicago? And how long will it take to get there?". InfoWorld. 15 (46): 77 f.
  127. Perele, Nicholas; Durlester, Nancy; Wonnacott, Laura; Sommer, Dan (1993-11-15). "The interoperability headache: linking disparate clients and servers: The mission: to give each of eight client operating systems simultaneous access to the leading networks and printers in our testing enterprise". InfoWorld. 15 (46): 124–134.
  128. 1 2 Zachary 2009, p. 303
  129. Johnston, Stuart J.; Wilson, Jayne (1993-07-12). "Sun, Intergraph to port Windows NT to RISC-based Sparc systems". InfoWorld. 15 (28): 8.
  130. Johnston, Stuart J. (1992-11-23). "Intergraph to port its Unix-based engineering apps to Windows NT". InfoWorld. 14 (47): 16.
  131. Kent, Les; Armstrong, James; Nash, Siobhan (1993-11-22). "32-bit desktop operating systems: Finding the right operating system to suit your needs". InfoWorld. 15 (47): 66–83.
  132. "Windows XP review". CNET. Retrieved 24 May 2013.


  • Zachary, G. Pascal (2009). Showstopper!: The breakneck race to create Windows NT and the next generation at Microsoft. New York: E-Rights/E-Reads. ISBN 0-7592-8578-0. 
  • Custer, Helen (1993). Inside Windows NT. Redmond: Microsoft Press. ISBN 1-55615-481-X. 
This article is issued from Wikipedia - version of the 11/10/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.