alt Hacker NewsI suppose it isn't if you never had it on real hardware. Win32 was well marked as the complete OS takeover for the PC. DOS remained only to boot Windows and as backup OS. If you absolutely needed to jump back to DOS you still could, however you were heavily expected to force your DOS programs to launch and live in their own little DOS environments, much to everyone's chagrin.
Replies
It's the “own little DOS environments” that makes WINSTART.BAT's functionality surprising for people who ain't intimately familiar with the Windows 3.1/9x architecture, because those DOS environments are launched from within Windows but without running anything in WINSTART.BAT. Most people would expect those DOS environments to be running inside the Windows environment, not in parallel with / independent from it.
> I suppose it isn't if you never had it on real hardware. Win32 was well marked as the complete OS takeover for the PC. DOS remained only to boot Windows and as backup OS. If you absolutely needed to jump back to DOS you still could, however you were heavily expected to force your DOS programs to launch and live in their own little DOS environments, much to everyone's chagrin.
I remember that at the time of Windows 95, I very often had to boot back to DOS 7.0 (which was also delivered as part of the Windows installation) to run DOS games, which were still very popular until like the middle of the 00 years.
And yes, when Windows XP came out (2001), people were somewhat disappointed that you couldn't simply boot DOS anymore to play your old beloved games. Over the years, DOSBox got sufficiently stable and PCs got sufficiently powerful that this gap could be closed.