Windows 3.0 - Revision history

Jnc: /* See also */ +Windows 3.00.55 Beta

2024-01-13T18:45:58Z

‎See also: +Windows 3.00.55 Beta

Jnc: New category

2024-01-13T18:17:08Z

New category

Jnc: +cat

2018-12-15T20:19:17Z

+cat

Neozeed at 17:26, 3 August 2010

2010-08-03T17:26:05Z

Neozeed: /* Advertising */

2010-08-03T17:20:34Z

‎Advertising

Neozeed: /* Advertising */

2010-08-03T17:19:34Z

‎Advertising

Neozeed at 17:18, 3 August 2010

2010-08-03T17:18:38Z

Neozeed: /* Reviews */

2010-05-23T19:40:46Z

‎Reviews

Neozeed at 11:41, 10 May 2010

2010-05-10T11:41:33Z

Neozeed: /* Background */

2009-10-26T01:23:43Z

‎Background

@@ Line 74: / Line 74: @@
 [[Image:Kiss it goodbye Windows 3.0 page 1.jpg|left|thumb|300px|Page 1]]
 [[Image:Kiss it goodbye Windows 3.0 page 2.jpg|center|thumb|300px|Page 2]]
-<p>
 {{Nav Windows}}
 [[Category: Microsoft Operating Environments]]

@@ Line 11: / Line 11: @@
 [[Image:Windows 3.0 on Virtual PC 2007.jpg|200px|thumb|right|Windows 3.0 on Virtual PC 2007]]
-== About ==
+'''Windows 3.0''' was the breakout success that [[Microsoft]] had long hoped for.  At the time they were partnering with [[IBM]] with the [[OS/2]] project.  However they didn't want to have such a large 'break' with their main product of the time, [[MS-DOS]], so they kept on looking for ways to improve on it.  Microsoft had become enamored with the new Intel i386 CPU, and wanted to build a great 32-bit environment.  While IBM had insisted OS/2 support the 16-bit i286 CPU, Microsoft was free to make improvements to its current [[real mode]] 16-bit environment [[Microsoft Windows|Windows]].
-Windows 3.0 was the breakout success that [[Microsoft]] had long hoped for.  At the time they were partnering with [[IBM]] with the [[OS/2]] project.  However they didn't want to have such a large 'break' with their main product of the time [[MS-DOS]] so they kept on looking for ways to improve on it.  Microsoft had become enamored with the new Intel i386 CPU, and wanted to build a great 32bit environment.  While IBM had insisted OS/2 support the 16 bit i286 CPU, Microsoft was free to make improvements to it's current realmode 16bit environment Windows.
+On the way to Windows 3.0 there was work done on the [[kernel]] to support limited multitasking (cooperative) in the 2.0 series, culminating with a 286 version of Windows 2.0 that could run more then one MS-DOS session, although it was very unstable, and a version for the 386 that could run full multiple DOS machines (VDM's) within the 16-bit constraints.  Expanding on this work, the next logical step was to get Windows to execute in protected mode.
 == Background ==
@@ Line 45: / Line 43: @@
 == Modes ==
 Windows 3.0 had three different modes of operation, each tailored for a specific CPU generation.
 === Real Mode ===
 Real mode, operated in the 'real mode' of the 286 & 386 CPUs, and on any 8086/8088 80186 CPU, confined to only 1MB of accessible memory.  This was more so for compatibility with prior versions of Windows, 1.x & 2.x that required the functionality of running in real mode.
@@ Line 79: / Line 78: @@
 {{Nav Windows}}
-[[Category: Microsoft Operating Systems]]
+[[Category: Microsoft Operating Environments]]

← Older revision		Revision as of 20:19, 15 December 2018
Line 78:		Line 78:

	{{Nav Windows}}		{{Nav Windows}}
		+
		+	[[Category: Microsoft Operating Systems]]
	[[Category:Operating Environments]]		[[Category:Operating Environments]]

@@ Line 76: / Line 76: @@
 [[Image:Kiss it goodbye Windows 3.0 page 2.jpg|center|thumb|300px|Page 2]]
 <p>
-{{stub}}
 {{Nav Windows}}
 [[Category:Operating Environments]]

@@ Line 74: / Line 74: @@
 [[Image:Kiss it goodbye Windows 3.0 page 1.jpg|left|thumb|300px|Page 1]]
-[[Image:Kiss it goodbye Windows 3.0 page 2.jpg|right|thumb|300px|Page 2]]
+[[Image:Kiss it goodbye Windows 3.0 page 2.jpg|center|thumb|300px|Page 2]]
+<p>
 {{stub}}
 {{Nav Windows}}
 [[Category:Operating Environments]]

@@ Line 41: / Line 41: @@
 With Windows now running in protected mode, that meant that people would have access to more memory (albeit in 64k chunks as both the 386 & 286 kept the 286's memory model for computability) and errant applications would generate a UAE, and the environment could potentially keep on running.
-Around this time Microsoft then had released QuickC for Windows, which included a version of the Microsoft C Compiler that executed in protected mode, and a copy of the Windows SDK for $149, and allowed other vendors to license and re-sell the Windows SDK.  Borland and Watcom come to mind as two that did.  Compared to the price (and availability) of the OS/2 SDK, more and more developers chose to go with Windows.
+Around this time Microsoft then had released [[QuickC for Windows]], which included a version of the Microsoft C Compiler that executed in protected mode, and a copy of the Windows SDK for $149, and allowed other vendors to license and re-sell the Windows SDK.  Borland and Watcom come to mind as two that did.  Compared to the price (and availability) of the OS/2 SDK, more and more developers chose to go with Windows.
 == Modes ==