←back to thread

304 points mooreds | 2 comments | | HN request time: 0.493s | source
Show context
jmclnx ◴[] No.42166830[source]
I never thought of Windows 3.1 as an OS. The other 2 was MS-DOS and Windows 95.
replies(2): >>42167247 #>>42168397 #
rusk ◴[] No.42167247[source]
Agree, the terminology in those days was “shell”.

Though Windows 95 was arguably similar running atop “DOS 7” it actually imposes its own 32-bit environment with its own “protected mode” drivers once booted. Dropping to DOS reverted to “real mode”.

replies(3): >>42167329 #>>42168096 #>>42168667 #
tliltocatl ◴[] No.42167329[source]
So did the lastest Win3.1 for workgroups, just MS spared all the fanfare for Win95. Not sure if the 3.1 version in the installers does.
replies(1): >>42167345 #
rusk ◴[] No.42167345[source]
Windows 3.1 was just a graphical shell. All the drivers and stuff were still managed by DOS. You still needed to configure your system with config.sys

EDIT it’s coming back to me. Windows 3.1 did have a a subsystem for running 32 bit apps called Win32 I think that’s what you mean. This was very much in the application space though.

It still used cooperative multitasking and Win 95 introduced preemptive.

replies(4): >>42167548 #>>42167566 #>>42167659 #>>42167851 #
rbanffy ◴[] No.42167851[source]
I think it’d be fair to call it more than a shell. It was also a set of libraries that implemented the common user interface elements of Windows apps, similar to the Macintosh Toolbox but not in ROM.
replies(1): >>42168502 #
rusk ◴[] No.42168502[source]
Not sufficient on its own to qualify it as an OS though. The VM subsystem described in sibling comment makes a big difference though!
replies(1): >>42171455 #
1. rbanffy ◴[] No.42171455[source]
The line is blurry though.
replies(1): >>42171787 #
2. rusk ◴[] No.42171787[source]
More akin to Window Manager to me. But yes more than a mere “shell” and through my error I have learned oh so much.