Planned Windows 2000 successor (minor update, NT 5.50), merged into Whistler
Windows 2000 Service Pack 4 Update Rollup Win64 (early codename for Windows 2000 64-bit)Ī collection of networking updates for Windows 2000 Very early codename for Windows 2000 (around 1995/96) Microsoft BackOffice Small Business Server 4.5 Microsoft BackOffice Small Business Server 4.0 Planned successor of Daytona, Windows NT 4.0 Windows 98 OEM/Corporate image cloning utility OLE-2 Based Shell and environment on top of Chicago (became Memphis later) Windows 96, Merge Internet and Desktop together Project, Active DesktopĮarly codename for Windows 98, when Memphis NT was still planned as a successor of Cairo Planned successor of Chicago, became Nashville Very early codename for Windows 95 (around 1992), became Chicago Very early codename for Windows 95 (around 1990)
Windows for Mobile Computing: a direct derivative of the Cougar and Panther projects outlined above with Windows API support, never released Subsystem which provides API support for 16 and 32-bit Windows applications “Stop-ship” type bug fix release of Windows 3.1 (planned about rc1-rc3), became Windows 3.11ģ2-bit protected-mode kernel which runs on top of Jaguar Non-Upgrade combined DOS/Windows setup (Setup installs MS-DOS 6.0 first and then Windows 3.1) Improved version of DOS 4.0, became MS-DOS 5.0Ī feature upgrade to MS-DOS 5.0a, became MS-DOS 6.0Ĭombined DOS 5.0 and Windows 3.1 install, became JanusĬombined DOS 5.0a and Windows 3.1 install, became Jastro Improved version of DOS 4.0, never finished Microsoft generally does not announce a final name until shortly before the product is finished, although it is usually possible to speculate (“Memphis”, for instance, was expected to be “Windows 97”, but was delayed). Since many of these products, particularly new versions of Windows, are of major significance to the IT community, codenames are often widely used in discussions prior to the official release. Codenames are used to refer to products before their final release.