3 ms·
It was so bad that even users of Windows [123].x would only fire it up to use specific applications...spending quite a bit of time in DOS (you could try to run
by bane 12y ago
It was so bad that even users of Windows [123].x would only fire it up to use specific applications...spending quite a bit of time in DOS (you could try to run your DOS program from within Windows, but you usually couldn't get enough base memory free to do so). I don't think anybody really considered Windows the "OS" back in those days, just a GUI environment with MS-DOS being the OS.
But if you consider Windows as an OS, then Microsoft basically got everybody to buy two OSs for each computer. Lots of people also had two copies of Word, one for DOS and one for Windows.
I remember also running GEM 2.0 for a couple things as well. In those days you had multiple Windowing systems as well.
It was all kind of funny though with OS/2 you could just put all that mess in a DOS window and even run Windows in them. I think you could run multiple instances and thus have true multitasking for Windows apps (instead of task switching), but it ate up very expensive RAM very quickly.
- yuhong 12y agoYea, there is a reason why the OS/2 2.0 fiasco is one of my favorite topics. My favorite problem with Win9x is how the dependence on DOS allowed Caldera to continue to sue MS, and adding "Microsoft Munchkins" and other attacks on top of that...