Civil Rights
Movements, leaders, victories and the continuing fight for equality.
Explore the people, places, events, achievements, struggles and stories that shaped our journey.
Movements, leaders, victories and the continuing fight for equality.
Innovation, patents, science, technology and world-changing contributions.
Pioneers, champions, Negro Leagues, records, activism and excellence.
Meet the people whose lives, choices and achievements shaped the journey.
Black towns, communities, institutions and places where history happened.
Moments that changed communities, movements, institutions and the nation.
Katherine Johnson’s mathematical calculations helped guide some of America’s most important early space missions while she confronted the racial and gender barriers faced by Black women in twentieth-century America.
MORE →Reflects the personal views, recollections, and perspective of the author, Mike Davis.
This is a personal recollection on the Move fire on May 13, 1985
Parts of this article (those related to Windows Setup) need to be updated. (October 2024) |


Windows Setup is an installer that prepares a computer for a Microsoft Windows installation by allowing the user to pick installation settings (modifying partitions if necessary) and copying the files to the drive.
Early versions of Windows required an existing, compatible version of MS-DOS for installation. The Windows NT family, from 3.1 through 5.0 featured text-based installation that prompted users to a GUI wizard in the final steps. The 9x family installer was similar to NT despite it being MS-DOS-based. Additionally, it did not need preinstalled DOS as a requirement. With the release of Windows NT 6.0 (which Windows Vista and Windows Server 2008 are based on), Microsoft introduced a fully graphical setup environment and UEFI support (partial in Windows Vista and 7, full UEFI support on Windows 8 onwards). The new graphical setup environment is based on Windows Preinstallation Environment.
The installation of Windows 1.0, Windows 2.0, Windows 2.1 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.
The installation of Windows 3.0, Windows 3.1 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 95, 98, and Me utilize a similar setup process, which does not require MS-DOS to be already installed. The setup application can be launched from a DOS environment (typically a DOS boot disk, also containing utilities such as fdisk to conduct disk partitioning), or from an existing Windows installation for in-place upgrades. If launched from DOS, a stub application first bootstraps a minimal environment based upon Windows 3.1, which is then used to launch a graphical wizard to begin the first phase of the installation process. In any case, after initial configuration and the copying of files to the selected installation folder, the computer then reboots into the installed OS to conduct the second phase, including hardware detection, driver installation, and post-install housekeeping before installation is complete.[2]

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.
On Windows 2000, Windows XP and Windows Server 2003, the Windows Setup process is first started from setupldr.bin, which is a modified version of NTLDR.
Windows Vista, Windows Server 2008, 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.[5][failed verification]
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.[6][7] Windows Setup is still used when booting from installation media.[7] On Windows 10, a sister program to Upgrade Assistant known as "Media Creation Tool" was introduced, which is used to download the Windows OS files and generate ISO images or USB boot media.[8]
In January 2024, Microsoft began to replace Windows Setup on the Windows 11 boot media with a revamped version based on the UI of Upgrade Assistant. Microsoft stated that the new process would maintain all advanced features available in the existing setup process.[9]
Source: Wikipedia. Article content is retrieved live through the MediaWiki API.
Windows Setup is an installer that prepares a computer for a Microsoft Windows installation by allowing the user to pick installation settings (modifying partitions if necessary) and copying the files to the drive. Early versions of Windows required an existing, compatible version of MS-DOS for installation. The Windows NT family, from 3.1 through 5.0 featured text-based installation that prompted users to a GUI wizard in the final steps. The 9x family installer was similar to NT despite it being MS-DOS-based. Additionally, it did not need preinstalled DOS as a requirement. With the release of Windows NT 6.0 (which Windows Vista and Windows Server 2008 are based on), Microsoft introduced a fully graphical setup environment and UEFI support (partial in Windows Vista and 7, full UEFI support on Windows 8 onwards). The new graphical setup environment is based on Windows Preinstallation Environment.
Windows Installer (msiexec.exe, formerly named Microsoft Installer, codename Darwin) is a software component and application programming interface (API) of Microsoft Windows, used to install, maintain, and remove software. The installing information, and optionally the related files, are packaged in installation packages, loosely relational databases structured as COM Structured Storages and commonly known as "MSI files", from their default filename extensions. The packages with the file extensions mst contain Windows Installer "Transformation Scripts", those with the msm extensions contain "Merge Modules" and the file extension pcp is used for "Patch Creation Properties". Windows Installer contains significant changes from its predecessor, Setup API. New features include a graphical user interface (GUI) framework and automatic generation of the uninstallation sequence. Windows Installer is positioned as an alternative to stand-alone executable installer frameworks such as older versions of InstallShield and Nullsoft Scriptable Install System (NSIS). Before the introduction of Windows Installer, the Windows Setup API can be used in Windows 3.x and Windows 9x. The Setup API can do file copy, as well as INI file or Windows Registry update. Since Windows 2000, use Windows Installer to install application is recommended; Setup API is still used for install device drivers. Before the introduction of Microsoft Store (then named Windows Store), Microsoft encouraged third parties to use Windows Installer as the basis for installation frameworks, so that they synchronize correctly with other installers and keep the internal database of installed products consistent. Important features such as rollback and versioning depend on a consistent internal database for reliable operation. Furthermore, Windows Installer facilitates the principle of least privilege by performing software installations by proxy for unprivileged users.
Windows Vista contains a range of new technologies and features that are intended to help network administrators and power users better manage their systems. Notable changes include a complete replacement of both the Windows Setup and the Windows startup processes, completely rewritten deployment mechanisms, new diagnostic and health monitoring tools such as random access memory diagnostic program, support for per-application Remote Desktop sessions, a completely new Task Scheduler, and a range of new Group Policy settings covering many of the features new to Windows Vista. Subsystem for UNIX Applications, which provides a POSIX-compatible environment is also introduced.
An INF file (setup Information file) is an INI plain-text file used by Microsoft Windows-based operating systems for the installation of software and drivers. INF files are most commonly used for installing device drivers for hardware components. Windows includes the IExpress tool for the creation of INF-based installations. INF files form part of the Windows Setup API and of its successor, Windows Installer. The \windows\inf directory contains several such .inf files. Precompiled setup Information file (*.pnf) is a binary representation of an INF file compiled by the operating system.
Before the 1921 destruction of Tulsa’s Greenwood District, Black residents had created a remarkable center of business and community life. The district included stores, professional offices, entertainment venues and homes owned by Black citizens. Understanding Greenwood means learning what was built—not only what was burned.
MORE →Madam C.J. Walker