Earlier quoted context omitted.
Are there specific claims you would dispute?
Because of the low quality, normally no. But since you asked: DOS was not a bootloader for Win3.1. Win 3.1 cannot run without DOS. There were TSRs which were loaded in DOS which interacted with Win3.1. And multitasking: only one program was active at a time (just like in Android today). When you minimized the program, it was suspended.
Myth: Windows 3.1 was just a shell on top of DOS
41–45 of 45 posts
Re: Myth: Windows 3.1 was just a shell on top of DOS
#42Windows 3.x and 9x are "shells on top of DOS" the same way that Linux can be a "shell on top of DOS": https://github.com/haileys/doslinux
Not really. Linux can initialize HW itself. Win3.1 and sometimes 95 relied on DOS to load drivers for some perpherals (Sound cards for example) because there were no Windows drivers available.
Re: Myth: Windows 3.1 was just a shell on top of DOS
#43I wonder if anyone has managed to run windows apps in seperate vms just like the dos apps were (could you even start Windows in standard mode in one somehow)
There are two projects which did that. If you were running Windows NT, when running a 16-bit .EXE file, there was a checkbox in the properties dialogue titled something like "run in separate memory space". That launched this particular binary in its own isolated wow16 runtime. Of course, being an official Microsoft Project slightly reduces how impressive visit. The other one that I am aware of is that Quarterdeck's D…
Re: Myth: Windows 3.1 was just a shell on top of DOS
#44What about Windows running in Real Mode or Standard Mode?
Re: Myth: Windows 3.1 was just a shell on top of DOS
#45Windows 3.x and 9x are "shells on top of DOS" the same way that Linux can be a "shell on top of DOS": https://github.com/haileys/doslinux
Not really. Linux can initialize HW itself. Win3.1 and sometimes 95 relied on DOS to load drivers for some perpherals (Sound cards for example) because there were no Windows drivers available.