https://gunkies.org/index.php?action=history&feed=atom&title=Talk%3AMicrosoft_Windows 2026-06-06T14:27:39Z Revision history for this page on the wiki MediaWiki 1.30.1 https://gunkies.org/w/index.php?title=Talk:Microsoft_Windows&diff=20985&oldid=prev 2019-04-11T07:09:12Z

<p>‎<span dir="auto"><span class="autocomment">VMMs in DOS history, and memory...</span></span></p> <p><b>New page</b></p><div>Hmm..<br /> <br /> &quot;Windows 386 v2.0..x itself was still a 16-bit real mode program, even running on the 386 VMM.&quot;<br /> <br /> VMM is virtual machine mode, which allowed a computer running Windows, to run multiple 8086 real mode<br /> applications simultaneously. so.... Windows v2 running in 16-bit real mode could run multiple<br /> VMMs, but could not run itself. ( It actually would complain that it could not run itself... )<br /> Quardecks DeskView could run AutoCAD in one window, and Windows another window, and could run two copies of AutoCAD, but not two copies of Windows v2.<br /> <br /> 8086 real mode is limited to &gt;1Mb of memory, using segmented ( unprotected memory ) memory addresses,<br /> or up to 15Mb more of data memory using the LIM 4.2 spec memory boards and appropriate software.<br /> Command.com could run in multiple windows, but could easily crash the Windows program.<br /> <br /> 80286 real mode is limited to &gt;16Mb of memory, using 16-bit unsegmented addresses, however requiring a processor reset to move between<br /> 16-bit mode and 8086 real mode.<br /> Command.com could run in multiple windows, but it was not command.com that could crash the program, the program ( Windows 2.0 ) could easily crash itself.<br /> <br /> 80386 real mode again limited to &gt;16MB of memory, could use 32-bit addresses, did not need to reset the processor to move from<br /> 16-bit mode to 8086 segmented mode, and included a VMM, Virtual Machine Mode capable of running 8086 processors in a protected memory space.<br /> Command.com could run in multiple windows, but with the 3.1 update, could only crash its own task, and not effect other programs.<br /> ( Windows 3.x had a generous helping of GPFs ( General Program Faults ) from poor drivers, which need constant attention.. )<br /> <br /> But out of all of this, Windows 2.0 should have been able to run a copy of itself under VMM, ( unsegmented memory hypervisor, running a segmented memory application ), but the program itself would not allow it to operate in this fashion.<br /> <br /> How could you easily describe this in a picture? A multi-deminensional view with details? [[User:ForOldHack|ForOldHack]] ([[User talk:ForOldHack|talk]]) 09:08, 11 April 2019 (CEST)</div>

ForOldHack