News for hackers. Stuff that matters.
Re:Switch to Windows 95 by hapless on Saturday February 03, 2018 @01:35PM (#16298825)
Confusingly there was also a windows 95/nt compatibility environment released for win 3.1 -- the win32s subsystem. Many, if not most, applications written for win95 or NT 3.x APIs could run on windows 3.1.

https://en.wikipedia.org/wiki/Win32s

Microsoft has always been laser-focused on forwards- and backwards- compatibility, whether it makes sense to the rest of us or not.

Re:Switch to Windows 95 by wryun on Saturday February 03, 2018 @02:31PM (#16299107)
My (possibly faulty) memory of win32s is that it was came out before Windows 95, and that it would not run most of the programs that were later released for Windows 95. I'd call it a 'Win32 API for Windows 3.1' rather than a compatibility environment for Windows 3.1.
Re:Switch to Windows 95 by ashleyn on Saturday February 03, 2018 @03:07PM (#16299310)
Correct. Win32s was a brief stopgap between home/low-cost user support for 32-bit APIs and the release of Windows 95.
Re:Switch to Windows 95 by stormbrew on Saturday February 03, 2018 @04:56PM (#16299905)
While this was part of it, I think the main reason it existed was more for smaller developers who couldn't use/afford windows NT (at the time really really expensive) a win32 development environment before win95 came out so there'd be more software (of the shareware variety) for it when it came out.
Re:Switch to Windows 95 by digi_owl on Saturday February 03, 2018 @03:57PM (#16299612)
Yep, i recall trying to get a game demo going that required Win32s and WinG installed. Ended up taking up so much of the old HDD that i barely could get the game going, and it crawled.
Re:Switch to Windows 95 by lathiat on Sunday February 04, 2018 @06:46AM (#16302393)
I remember running Win32s with a shell that emulated the look of Windows 95 on 3.11. My 486 has some kind of Boot sector overwrite prompt to protect against viruses but it displayed on screen in text over the graphical UI of the Win95 installer and that froze the machine and I couldn’t continue.
Re:Switch to Windows 95 by muro on Saturday February 03, 2018 @04:13PM (#16299684)
Similar here - I think Battle Isle 3 was annoying being built on that api
Re:Switch to Windows 95 by yuhong on Saturday February 03, 2018 @02:52PM (#16299229)
Yea, old anti-trust exhibits mentioned so-called 32-bit Windows extenders, which had many limitations compared to say OS/2 2.0. For example, I think all Win32s apps ran in a single global address space, not to mention the lack of multi-threading etc.
Re:Switch to Windows 95 by beached_whale on Saturday February 03, 2018 @05:28PM (#16300050)
Windows 3.11 for workgroups had the win32 subsystem
Re:Switch to Windows 95 by dijit on Saturday February 03, 2018 @05:51PM (#16300136)
> Microsoft has always been laser-focused on forwards- and backwards- compatibility, whether it makes sense to the rest of us or not. Microsoft has always been laser-focused on forwards- and backwards- compatibility, whether it makes sense to the rest of us or not.

I, too, made this presumption about Microsoft. However in the switch from 2012 R2 to Server 2016 code that I run asserts often because it seems like the entire process tree model has changed.

So maybe MS is backing off of its forward/backward compatibility strictness.