←back to thread

305 points mooreds | 6 comments | | HN request time: 1.051s | source | bottom
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 #
1. YakBizzarro ◴[] No.42167548[source]
It was Win32s https://en.m.wikipedia.org/wiki/Win32s
replies(2): >>42167616 #>>42189655 #
2. rusk ◴[] No.42167616[source]
Thanks

”Win32s lacked a number of Windows NT functions, including multi-threading, asynchronous I/O, newer serial port functions and many GDI extensions. This generally limited it to "Win32s applications" which were specifically designed for the Win32s platform,[4] although some standard Win32 programs would work correctly”

replies(1): >>42167939 #
3. kjellsbells ◴[] No.42167939[source]
It was a strange time back then for anyone who wanted to get online. Win3.1 had no TCP/IP stack so many folks used a third party download called Trumpet Winsock. IIRC you might have needed win32s in order to use it.

Looking back, Microsoft were clearly in an incredibly complicated transitioning phase, with very little margin for error (no patching over the Internet!)

replies(1): >>42168401 #
4. phire ◴[] No.42168401{3}[source]
Trumpet Winsock works on a 286, but apparently NCSA Mosaic version 2.0 needed Win32s.

So I guess there would have been a time in 1994 where many people were forced to retire their 286es. Though Mosaic was quickly replaced by Netscape Navigator in late 1994 which worked on Win16.

And then Windows 95 came along, and it really needed a 486 with 4MB of ram, ideally 8MB.

replies(1): >>42170574 #
5. dboreham ◴[] No.42170574{4}[source]
1994 wasn't a time where everyone was using a web browser.
6. int_19h ◴[] No.42189655[source]
Much later, the HX DOS Extender (https://www.japheth.de/HX.html) had something vaguely similar called Win32 emulation mode. Meaning that you could load a Win32 PE image, and it could call quite a few Win32 APIs, all while running under plain DOS (in 32-bit flat mode), with HX DOS providing the implementation.

It had just enough parts of the API implemented to be able to run Quake 2 in DOS.