To view parent comment, click here.
To read all comments associated with this story, please click here.
OS/2 will integrate this windows copy into itself.
(OS/2 2.x had windows support out of the box)
As OS/2 Warp 3+ (and so, eCS since it's based upon OS/2 4.51) requires a copy of windows 3.x, it would be more logical to run that on top of a (MS)-DOS.
OS/2 Warp 3 was available in four flavors back in the day:
OS/2 Warp 3 - red spined box - required Windows 3.1 if you wanted to run Windows. It would integrate with an existing installation, or you could install Windows later on, even on an HPFS partition.
OS/2 Warp 3 "Fullpack" - blue spined box - came with its own copy of Windows 3.x called WinOS2.
OS/2 Warp 3 Connect - red and blue versions as above plus peer to peer networking, TCP/IP, etc.
The first two just had SLIP and PPP dial-up networking, which wasn't a big deal because very few home users had access to anything requiring ethernet (or other) drivers and hardware.
OS/2 Warp 4 removed all of those variations, and was only available as a fullpack client with full networking support.
In other words, you might've been correct depending on which version of Warp 3 you were talking about. :-)





Member since:
2005-07-06
I suppose FreeDOS is a better option in this case. At least, when your DOS software requires direct hardware access, it's not advisable to run it within a multitasking enviorement.
The Windows enviorement within OS/2 requires, starting from OS/2 Warp 3.0 a copy of Microsoft Windows 3.x.
OS/2 will integrate this windows copy into itself.
(OS/2 2.x had windows support out of the box)
As OS/2 Warp 3+ (and so, eCS since it's based upon OS/2 4.51) requires a copy of windows 3.x, it would be more logical to run that on top of a (MS)-DOS.