Windows Setup

Not to be confused with Windows Installer.
Windows Setup installing Windows Server 2008 R2

The process in which retail versions of Microsoft Windows are installed onto a computer is referred to as Windows Setup. This process has changed significantly with the introduction of Windows NT 3.1, and again with the advent of Windows Vista.

Windows 1.x and Windows 2.x

The installation of Windows 1.x, Windows 2.0, Windows 2.1x requires that a compatible version of MS-DOS is installed. The user must specify any hardware such as mice or printers during installation. After the installation, Windows was to be started either manually by typing "WIN.COM" at the command prompt, or configured for automatic startup by adding WIN.COM to the end of AUTOEXEC.BAT.

Windows 3.x

The installation of Windows 3.0, Windows 3.1x and Windows 3.2 requires that a compatible DOS operating system is already installed. The installer attempts to detect network cards, mice, and other hardware on its own but will rely on the user to specify hardware if it cannot find them. After the installation, Windows was to be started either manually by typing "WIN.COM" at the command prompt, or configured for automatic startup by adding WIN.COM to the end of AUTOEXEC.BAT. [1]

Windows 9x

Windows 95, Windows 98 and Windows Me do not require MS-DOS. The first phase of setup prepares the hard disk partition for use by Windows by formatting it to a compatible file system, then runs scandisk, and, if the hard disk appears to be ready for installation in terms of free space and disk integrity, then it will copy files to the selected installation folder (typically C:\WINDOWS). The first phase of setup resembles the interface of Windows 3.x. Once this phase is finished, the computer reboots and setup resumes from the hard disk, but still requires the installation media to continue copying files and drivers. At this point the user will be asked to provide a product key.

Windows NT

Before Windows Vista

The setup process introduced with Windows NT 3.1 remained in effect until the release of Windows Vista. The general process is:

All versions of Windows NT up to Windows Server 2003, except for Windows XP Home Edition, prompt the user to enter an Administrator password.

On Windows 2000, Windows XP and Windows Server 2003, the Recovery Console is included to repair damaged installations. It allows the user to repair disk and boot record errors, and copy missing or corrupted files to the destination folders.

After Windows Vista

Windows Vista and subsequent operating systems all utilize Windows Preinstallation Environment (Windows PE) as the installation environment. Windows PE features a graphical user interface with mouse support from the beginning, rather than requiring a text-only phase as in previous versions. The concept of F6 disks has been improved to provide support for computers without floppy drives; the loading of drivers from CD-ROMs and USB flash drives is now supported. Support for installing Windows onto FAT partitions has been dropped; Windows must be installed onto an NTFS partition.[3]

Windows 8

Windows 8 introduces a new secondary installer known as the Upgrade Assistant, replacing Windows Setup for upgrade installations. Designed to be simpler and faster than previous installation methods, it analyses the system's hardware and software for compatibility with Windows 8, allows the user to purchase, download, and install the operating system, and migrate files and settings from the previous Windows installation in the case of a clean install.[4][5] Windows Setup is still used when booting from installation media.[5]

References

  1. http://support.microsoft.com/kb/82731
  2. http://support.microsoft.com/kb/103939
  3. http://support.microsoft.com/kb/926069
  4. Paul McDougall (July 3, 2012). "Microsoft Reveals Windows 8 Upgrade Price". InformationWeek. Retrieved July 4, 2012.
  5. 1 2 "Improving the setup experience". Building Windows 8. Microsoft. Retrieved 18 September 2012.
This article is issued from Wikipedia - version of the 3/6/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.