0
Originally, Windows NT was to be known as OS/2 3.0; the connection is actually quite intimate. Windows NT resulted from the fact that IBM and Microsoft decided to go their own ways with OS/2 after the success of Windows 3.0. Microsoft added a Windows-like API to "their" OS/2, on top of the OS/2 API, and christened the result "Windows NT" (mid 1993; there were a number of other differences between early Windows NT and OS/2, but the API was the principal one). IBM continued development of OS/2, with a more-or-less "native" API. Windows NT and OS/2 continued to diverge over the next few years. For more, see this excellent article on Windows NT: http://en.wikipedia.org/wiki/Windows_NT
Still curious? Ask our experts.
Chat with our AI personalities
Judy
Devin
BlakeAdd your answer:
Earn +20 pts
How is os2 loosly connected to Windows NT?
OS/2 was developed by Microsoft and IBM before NT was developed. No doubt discoveries made by the Microsoft side while OS/2 was under development went into NT when Microsoft developed it. I've seen programs state compatibility between OS/2 and the Win 9x line of operating systems along with NT4.
What is the purpose of the network command in configuring RIP?
to identify the directly connected networks that will be announced in RIP updates
What is the win32 subsystem?
The Win32 subsystem is the native environment of Windows 2000. It processes all 32-bit applications. It provides text window support, shutdown, and hard-error handling for all subsystems. Applications created for Windows NT, Windows 95, and Windows 98 are also run on the Win32 subsystem.
How do you fix a NT DETECT failed error message?
http://support.microsoft.com/kb/555304 Looks like your NTLOADER.COM is messed up. You running XP?
What are the disadvantages of Novell NetWare?
As an application server its fails as Windows NT beats it on this case. Poor at printing data/information network status and management. It has build in network management tools that are not powerful
