Windows Nt 2000
Jan 06, 2008 Licensing in Windows 2000 and in Windows Server 2003 and differences. Because of this and unlike in Windows NT, in Windows 2000 and in Windows. With Windows 2000, the Windows NT driver model was enhanced to become the Windows Driver Model, which was first introduced with Windows 98.
This article needs additional citations for. Unsourced material may be challenged and removed. (August 2008) Windows NT, and Working state Current Source model / Initial release July 27, 1993; 24 years ago ( 1993-07-27) (as ) 1709 (10.0.16299.192) (January 3, 2018; 39 days ago ( 2018-01-03)) RS4 (10.0.17093) (February 7, 2018; 4 days ago ( 2018-02-07)) Update method, Platforms, type Default Depending on version, edition or customer choice:, -only, Official website Windows NT is a family of produced by, the first version of which was released in July 1993. It is a processor-independent, operating system. The first version of Windows NT was and was produced for and.
It was intended to complement consumer versions of that were based on (including through ). Gradually, the Windows NT family was expanded into Microsoft's general-purpose operating system product line for all, deprecating the family. 'NT' formerly expanded to 'New Technology' but no longer carries any specific meaning. Starting with, 'NT' was removed from the product name and is only included in the product version string. NT was the first purely version of Windows, whereas its consumer-oriented counterparts, Windows 3.1x and Windows 9x, were 16-bit/32-bit hybrids. It is a multi-architecture operating system. Initially, it supported several, including, and later.
The latest versions support (more specifically IA-32 and ) and. Major features of the Windows NT family include, and. Contents.
Naming It has been suggested that intended the initialism 'WNT' as a play on,. However, the project was originally intended as a follow-on to and was referred to as 'NT OS/2' before receiving the Windows brand. One of the original NT developers, states that the name was taken from the original target processor—the, code-named N10 ('N-Ten'). A 1998 question-and-answer session with, reveal that the letters were previously to 'New Technology' but no longer carry any specific meaning. The letters were dropped from the names of releases from Windows 2000 and later, though Microsoft described that product as being 'Built on NT Technology'.
Differences Windows Nt And 2000
Major features A main design goal of NT was hardware and software portability. Various versions of NT family operating systems have been released for a variety of processor architectures, initially, and, with, and supported in later releases. The idea was to have a common code base with a custom (HAL) for each platform. However, support for MIPS, Alpha, and PowerPC was later dropped in Windows 2000. Broad software compatibility was achieved with support for several 'personalities', including, and APIs – the latter two were phased out starting with Windows XP. Partial compatibility was achieved via an integrated – although this feature is being phased out in the architecture. NT supported per-object (file, function, and role) allowing a rich set of security permissions to be applied to systems and services.
NT supported Windows network protocols, inheriting the previous OS/2 networking, as well as networking (for which Microsoft would implement a TCP/IP stack derived at first from a -based stack from, then later rewritten in-house). Windows NT 3.1 was the first version of Windows to use 32-bit flat virtual memory addressing on 32-bit processors. Its companion product, Windows 3.1, used segmented addressing and switches from 16-bit to 32-bit addressing in pages.
Windows NT 3.1 featured a core kernel providing a system API, running in (ring 0 in x86; referred to in Windows NT as 'kernel mode' on all platforms), and a set of user-space environments with their own APIs which included the new Win32 environment, an OS/2 1.3 text-mode environment and a POSIX environment. The full kernel could interrupt running tasks to other tasks, without relying on user programs to voluntarily give up control of the CPU, as in Windows 3.1 Windows applications (although MS-DOS applications were preemptively multitasked in Windows starting with Windows 1.0). Notably, in Windows NT 3.x, several I/O driver subsystems, such as video and printing, were subsystems.
In Windows NT 4, the video, server, and printer spooler subsystems were moved into kernel mode. Windows NT's first was strongly influenced by (and programmatically compatible with) that from Windows 3.1; Windows NT 4's interface was redesigned to match that of the brand new, moving from the to the design., a journaled, secure file system, was created for NT. Windows NT also allows for other installable file systems; starting with versions 3.1, NT could be installed on or file systems. Windows NT introduced its own driver model, the Windows NT driver model, and is incompatible with older driver frameworks. With, the Windows NT driver model was enhanced to become the, which was first introduced with, but was based on the NT driver model. Added native support for the, which is also available for, and to an extent,. Development.
Original Windows NT wordmark Microsoft decided to create a portable operating system, compatible with and and supporting, in October 1988. When development started in November 1989, Windows NT was to be known as 3.0, the third version of the operating system developed jointly by Microsoft and. To ensure portability, initial development was targeted at the XR, switching to the in late 1989, and then the in 1990. Microsoft also continued parallel development of the DOS-based and less -demanding Windows environment, resulting in the release of in May 1990.
Windows 3 was eventually so successful that Microsoft decided to change the primary for the still unreleased NT OS/2 (as it was then known) from an extended OS/2 API to an extended. This decision caused tension between Microsoft and IBM and the collaboration ultimately fell apart. IBM continued OS/2 development alone while Microsoft continued work on the newly renamed Windows NT. Though neither operating system would immediately be as popular as Microsoft's MS-DOS or Windows products, Windows NT would eventually be far more successful than OS/2. Microsoft hired a group of developers from led by to build Windows NT, and many elements of the design reflect earlier DEC experience with Cutler's and, but also an unreleased object-based operating system developed by Dave Cutler for.
The operating system was designed to run on multiple and multiple hardware platforms within each architecture. The platform dependencies are largely hidden from the rest of the system by a kernel mode module called the (Hardware Abstraction Layer). Windows NT's kernel mode code further distinguishes between the 'kernel', whose primary purpose is to implement processor- and architecture-dependent functions, and the 'executive'.
This was designed as a modified, as the Windows NT kernel was influenced by the developed at Carnegie Mellon University, but does not meet all of the criteria of a pure microkernel. Both the kernel and the executive are together into the single loaded module; from outside this module there is little distinction between the kernel and the executive. Routines from each are directly accessible, as for example from kernel-mode device drivers. API sets in the Windows NT family are implemented as subsystems atop the publicly undocumented; this allowed the late adoption of the Windows API (into the Win32 subsystem).
Windows NT was one of the earliest operating systems to use internally. Releases. Lextrait, Vincent (January 2010). Retrieved January 4, 2010. ^ (Press release).
October 27, 1998. Retrieved November 10, 2014. Zachary, G Pascal (1994). Show Stopper!: The Breakneck Race to Create Windows NT and the Next Generation at Microsoft. American history. Retrieved March 17, 2017.
Thurrott, Paul. Win super site. Gates, Bill (June 5, 1998). Archived from on May 26, 2001. Retrieved June 26, 2005. October 27, 1998.
Retrieved November 13, 2011. Win super site. Retrieved November 24, 2010. '28 – OS/2 Compatibility', (resource kit), Microsoft, retrieved November 24, 2010.
November 5, 2007. Retrieved November 24, 2010.
Retrieved November 24, 2010. Barr, Adam (June 19, 2001), retrieved February 22, 2013. Retrieved November 24, 2010., 'Preface', in;, Microsoft Windows Internals (fourth ed.), Microsoft Press,. Pollack, Andrew (July 27, 1991), The, retrieved September 2, 2008.
Thurrott, Paul (January 24, 2003). Win super site. Retrieved January 5, 2010. Russinovich, Mark (November 30, 1998). Retrieved January 2, 2018. Neil Rieck. Retrieved August 25, 2015.
Technology network. Prentice Hall.
December 1, 1999. Retrieved August 29, 2011. Retrieved January 14, 2008. Windows Server 2008.
Retrieved May 18, 2009. May 20, 2009.
Retrieved July 6, 2009. LeBlanc, Brandon (February 4, 2009).
Blogging Windows. Retrieved February 5, 2009. Rothman, Wilson (June 2, 2009). Retrieved June 6, 2009. Windows Server 2008. Retrieved May 18, 2009.
'Windows', Microsoft. LeBlanc, Brandon (April 16, 2012). Blogging Windows. Retrieved April 17, 2012. July 18, 2012.
Retrieved July 18, 2012. 'Windows server 8 named Windows server 2012',.
Server cloud. Retrieved July 8, 2012.,. Warren, Tom (August 24, 2013). ^ Thurrott, Paul (November 22, 2014). SuperSite for Windows. Prophet, Tony (May 13, 2015).
Foley, Mary Jo (July 27, 2016). Microsoft Technet. Russinovich, Mark; Solomon, David (December 2001), MSDN mag, Developer network, Microsoft, archived from on April 24, 2003, retrieved December 19, 2006.
Windows Team Blog. October 14, 2008. Retrieved March 30, 2012. Retrieved November 24, 2010. Chen, Raymond (September 28, 2016). Lucovsky, Mark (August 9, 2000). Retrieved November 2, 2006.
The Florida SunFlash. July 7, 1993.
Petreley, Nicholas (September 3, 1999). Warren, Tom (January 5, 2011). Archived from on January 9, 2011. Gandhi, Shaheen. Archived from on December 20, 2008. Thurott, Paul (December 15, 1999).
Retrieved January 2, 2018. Chen, Raymond (August 2008). Technology network. Thurott, Paul (June 21, 2000). Retrieved January 2, 2018.
UPDATE: Compaq has apparently denied that any work is being done on Windows 2000/64 for the Alpha. Retrieved October 14, 2011. Microsoft TechNet. Retrieved October 14, 2011. Windows Server Editions.
Retrieved October 14, 2011. August 15, 2001. Retrieved October 14, 2011. Microsoft Support Center. Retrieved October 14, 2011.
November 1, 2006. Archived from on June 22, 2014.
October 31, 2006. Archived from on March 20, 2014. November 13, 2007. Retrieved September 10, 2017.
September 14, 2007. Retrieved August 10, 2017.
January 21, 2005. Retrieved January 11, 2013.
November 13, 2007. Retrieved September 10, 2017. Retrieved September 10, 2017. Retrieved September 10, 2017. Retrieved September 10, 2017. External links. (official page), Microsoft.
Russinovich, Mark, Win 2000 (discussion of ancestry of NT), archived from on May 3, 2002. (fact sheet), Microsoft PressPass, 1998, archived from on June 10, 2004.
There are a number of issues that must be considered when cloning Windows NT, Windows 2000, Windows XP or Windows Vista:. Ghost versions: Which Ghost version you use to create and restore the image file. Windows versions and service packs: What Windows version is run on the source computer. Cloning Windows NT/2000/XP/2003 Servers: Whether the source computer is a server.
Differences between the source and destination computers: How physical differences between the source computer and destination computers affect the operating system, drivers, and configuration settings, and how encryption on the source computer affects the destination computer. Restoring the uniqueness of a Windows NT/2000/XP/Vista installation after cloning: Configuration settings that must be different on the destination computers than on the source computer. Ghost versions Ghost has improvements in its handling of NTFS partitions in each Ghost version. Update Ghost to the latest version. See the documents and. Norton Ghost 2002 and earlier, and Symantec Ghost 7.5 and earlier cannot save images to local NTFS partitions.
However, some Ghost versions can save images to NTFS partitions that reside on a remote computer. Norton Ghost 2003 and Symantec Ghost 8.x can save image files to local NTFS partitions.
Windows Nt 2000 Startup Sound
See the documents and Windows versions and service packs When working with Windows NT installations, versions of Ghost prior to 2003 require Windows NT 4.0 Service Pack 4, 5, or 6a, but do not support Service Pack 6. Norton Ghost 2003 requires Windows NT 4.0 Service Pack 6a. When working with Windows 2000 installations, Ghost supports Windows 2000 Professional, Server, and Advanced Server with or without Service Pack 1 (also Service Pack 2, 3, or 4 with Symantec Ghost 8.x). See the document.
Windows 2000 Nt Professional
When working with Windows XP installations: Norton Ghost 2002, Norton Ghost 2003, Symantec Ghost 7.5, Symantec Ghost 8.x and Symantec Ghost 11.x support Windows XP. See the document.
Note that Windows XP includes a Product Activation feature that may affect cloning. Product Activation is a Windows XP licensing feature. For information on how Product Activation affects cloning, read the Microsoft article, article number 299840 in the Microsoft Knowledge Base.
Windows Vista is only supported with Symantec Ghost version 11.x. Cloning Windows NT or Windows 2000/2003 Servers Ghost can clone a Windows NT or Windows 2000/2003 Server for backup or migration purposes. However, in most cases, Ghost cannot clone a server for rolling out that server to many computers, and Symantec does not support Ghost when used for this purpose. See the document. Backups When cloning a Windows NT/2000/XP/Vista/2003 computer for backup purposes only, most of the information in the remainder of this document does not affect the cloning process.