386 DOS Environments (Part 2)
Windows/386
As the 80's
continued, computers were becoming ever more powerful. The resources to
run GUI environments became much more accessible. This was a good thing
as GUI's tend to be very demanding on their hardware. Graphics demanded
much more computing resources than character-based applications.
Graphical environments such as Windows and GEM didn't catch on during
that decade because the PC's of the 80's were much more limited.
Towards the end of that decade, processors became more powerful. The Intel 386 processor was finding it's way into more computers. The Intel 486 would be released at the very tail-end of the decade. These processors would provide the resources needed to drive such environments.
Don't get me wrong, it was possible to run GUI's on the Intel 8086/8088, 286, and lower-end 386 processors. Just because these CPU's could handle such environments didn't make then ideal though. This was why character-based programs like WordPerfect and Lotus 123 continued to thrive throughout the 80's. They were much more responsive on the same hardware than graphical environments.
OS/2 made a very good case for more powerful machines. OS/2 was very demanding on its hardware. The first incarnation of the OS was designed to run on the 286 processor. Even on the 286, the Presentation Manager tend to be sluggish on several occasions. On the 386 though, it was much more responsive.
It's important to note that 386-based PC's tend to be very expensive (Even 286-based systems at this time weren't exactly cheap if you know what I mean!). They would have been mostly found in the server room or corporate setting. Most home users were still using 8-bit micros like the Commodore 64 or PC-XT clones made by Tandy or Leading Edge. As such, most of the environments used on these (386) systems tend to be geared towards running productivity applications found within the business setting. Those that needed the raw power.
Towards the end of that decade, processors became more powerful. The Intel 386 processor was finding it's way into more computers. The Intel 486 would be released at the very tail-end of the decade. These processors would provide the resources needed to drive such environments.
Don't get me wrong, it was possible to run GUI's on the Intel 8086/8088, 286, and lower-end 386 processors. Just because these CPU's could handle such environments didn't make then ideal though. This was why character-based programs like WordPerfect and Lotus 123 continued to thrive throughout the 80's. They were much more responsive on the same hardware than graphical environments.
OS/2 made a very good case for more powerful machines. OS/2 was very demanding on its hardware. The first incarnation of the OS was designed to run on the 286 processor. Even on the 286, the Presentation Manager tend to be sluggish on several occasions. On the 386 though, it was much more responsive.
It's important to note that 386-based PC's tend to be very expensive (Even 286-based systems at this time weren't exactly cheap if you know what I mean!). They would have been mostly found in the server room or corporate setting. Most home users were still using 8-bit micros like the Commodore 64 or PC-XT clones made by Tandy or Leading Edge. As such, most of the environments used on these (386) systems tend to be geared towards running productivity applications found within the business setting. Those that needed the raw power.
Windows
During this time,
Windows was sitting in the digital equivalent of purgatory. Windows 1.0
was released in 1985 to a audience that showed a general lack of
interest. Windows 2.0, released in 1987, was generally better received,
but it didn't take the computing world by storm as Microsoft hoped.
It's future sat in limbo as it seemed as OS/2 was destined to be the OS
that would be destined successor of both DOS and Windows. However, OS/2
didn't take off in the way that either IBM or Microsoft hoped.
Windows remained as a back-up plan in case OS/2 didn't take-off, and vice-versa (from Microsoft's perspective). This mindset didn't please Big Blue as OS/2 was ordained by succeed both DOS and Windows by decree. This was the natural order of things from IBM's perspective. The development of Windows was essentially Microsoft disrupting the natural order. Again though, OS/2 didn't take off as it was very demanding and the lack of applications didn't help its situation. As such, it still made since for the Redmond giant to continue it development of Windows. Besides, the Presentation Manager, OS/2's GUI, was primarily developed by Microsoft. As such, the Presentation Manager was heavily inspired by Windows.
The Windows/386 kernel loaded in protected mode, creating several 8086 virtual machines for both Windows and DOS applications. These programs ran in protected mode as virtual DOS machines. This did impose limitations though. DOS applications were still restricted to 640KB of RAM, even when running in protected mode, as they were running under the virtual 8086 emulator, which conformed to the memory specs established by IBM in the original PC. Each Windows applications ran in the virtual 8086 mode as well, like DOS programs. However, Windows/386 emulated EMS (Expanded Memory) for Windows programs as well. Applications like Microsoft Word and Excel for Windows made use of it. With expanded memory, it was possible for Windows programs to use more than 640KB of RAM depending on how much memory was in the computer.
The selling point of Windows/386, like Desqview+QEMM, was that it was possible to run and multitask several DOS at the same time. Since the 386 processor could support virtual graphics and serial ports as well, these features were available to the applications as well. Graphical DOS programs could run in a window.
Windows remained as a back-up plan in case OS/2 didn't take-off, and vice-versa (from Microsoft's perspective). This mindset didn't please Big Blue as OS/2 was ordained by succeed both DOS and Windows by decree. This was the natural order of things from IBM's perspective. The development of Windows was essentially Microsoft disrupting the natural order. Again though, OS/2 didn't take off as it was very demanding and the lack of applications didn't help its situation. As such, it still made since for the Redmond giant to continue it development of Windows. Besides, the Presentation Manager, OS/2's GUI, was primarily developed by Microsoft. As such, the Presentation Manager was heavily inspired by Windows.
The Windows/386 kernel loaded in protected mode, creating several 8086 virtual machines for both Windows and DOS applications. These programs ran in protected mode as virtual DOS machines. This did impose limitations though. DOS applications were still restricted to 640KB of RAM, even when running in protected mode, as they were running under the virtual 8086 emulator, which conformed to the memory specs established by IBM in the original PC. Each Windows applications ran in the virtual 8086 mode as well, like DOS programs. However, Windows/386 emulated EMS (Expanded Memory) for Windows programs as well. Applications like Microsoft Word and Excel for Windows made use of it. With expanded memory, it was possible for Windows programs to use more than 640KB of RAM depending on how much memory was in the computer.
The selling point of Windows/386, like Desqview+QEMM, was that it was possible to run and multitask several DOS at the same time. Since the 386 processor could support virtual graphics and serial ports as well, these features were available to the applications as well. Graphical DOS programs could run in a window.
Microsoft Word
running under Windows 386 using expanded memory. The application is
running in protected mode, but as a virtual 8086 virtual process, not as
a true protected-mode application. This means that the application is
still restricted by the memory mappings of the 8086 processor, plus
expanded memory for Windows applications that supported it, like MS-Word
for Windows. After both Windows/386 and Word loads, their is only 22KB
of conventional (640KB) memory left. Their is still a significant amount
of expanded memory free though for Word to use, as the application does
support it.
Here's Microsoft Excel for comparison.
It's a similar
story for Excel. Both Windows/386 and Excel has used the vast majority
of conventional memory in the computer (3MB's allocated to the
emulator). However, most of the expanded memory for Excel to use is
still available to the application to use.
DOS applications multitasking. Windows 386 is using the Trident 8900 SVGA
display drivers, which is running at a resolution of 1024 by 768, 256
colors.
The above
screenshot shows Windows/386 running a DOS 4.01 Session, Lotus 123, and
WordPerfect at the same time. All the programs are running in a window.
The specs of my emulated PCEM computer running Windows 386 is the same
as the DESQview/QEMM setup:
- PC/AT 386 Compatible PC
- Intel 386 processor running at 33MHz
- 3MB's of RAM, and a
- Trident 8900 SVGA Adapter (For the screenshot above. I had another Windows 386 VM, but with the drivers for the Tseng ET4K SVGA adapter installed)
As noted, the 386
supported for virtualized graphics, and this support was rendered in
Windows/386 as well. However, their were certain caveats and restrictions. Windows 386 conforms to the previous generation of video standards. As such, DOS programs running in EGA or VGA mode won't run in a window. Graphical DOS programs running in CGA mode will run in a window. Also, video support also depended on the drivers. The Trident TVGA8900D drivers for Win386 was unable to any graphical DOS programs in a window at all. On the other hand, the standard VGA and Tseng ET4k drivers was able to run graphical DOS programs as long as they were in CGA mode. I was able to run Microsoft's FS 3.0 within a window on Win386.
The first version
of Windows/386 was released about a month earlier than Windows 2
standard in September, 1987. It was released specifically for Compaq
owners using the Deskpro 386 PC. Microsoft continued to develop and
refine it until its general release in March 1989.
Windows/386 was a
very technically innovated product for its time. It allowed the
multitasking of DOS applications that wasn't possible under the 286
versions of OS/2. Windows/386 unlocked many of the powerful features of
the 386 processor, and it rendered the hardware much more useful for its
users. At the same time though, like the previous versions of Windows
before it, it failed to gain mass adaption in the marketplace. Using
Windows/386 out on PCEM revealed why. Even most low-end 386 processors
were not cut out to running such environments. The emulated Intel 386
processor running at 33MHz had no issue running this GUI at all though.
However, such hardware was prohibitively expensive at the time, limiting
its adaption.
Work Cited:
PCEM - https://pcem-emulator.co.uk/
Intel 286 - https://en.wikipedia.org/wiki/Intel_80286
Intel 386 - https://en.wikipedia.org/wiki/Intel_80386
Virtual 8086 Mode - https://en.wikipedia.org/wiki/Virtual_8086_mode
Windows 2.1x - https://en.wikipedia.org/wiki/Windows_2.1x
Expanded Memory - https://en.wikipedia.org/wiki/Expanded_memory
Windows/386 2.01 - http://www.os2museum.com/wp/windows386-2-01/
CEMM (Compaq Expanded Memory Manager) - https://en.wikipedia.org/wiki/CEMM
PCEM - https://pcem-emulator.co.uk/
Intel 286 - https://en.wikipedia.org/wiki/Intel_80286
Intel 386 - https://en.wikipedia.org/wiki/Intel_80386
Virtual 8086 Mode - https://en.wikipedia.org/wiki/Virtual_8086_mode
Windows 2.1x - https://en.wikipedia.org/wiki/Windows_2.1x
Expanded Memory - https://en.wikipedia.org/wiki/Expanded_memory
Windows/386 2.01 - http://www.os2museum.com/wp/windows386-2-01/
CEMM (Compaq Expanded Memory Manager) - https://en.wikipedia.org/wiki/CEMM
Comments
Post a Comment