Not a commercially viable target for most companies. Win32s was a stopgap for Win32 support for lower end machines when only WinNT was around. Once Win95 arrive

Not a commercially viable target for most companies. Win32s was a stopgap for Win32 support for lower end machines when only WinNT was around. Once Win95 arrived, Win32s's days were numbered (along with 16-bit Win 3.x). If you're designing a Win32 app for Windows 95, are you going to stick with the Win3.1 look and feel? No. You're redesigning your UI to look like a native Win95 app. Where are your testing resources targeted? Win32s? Nope. Win95 only. Well maybe if Win95 sales are slow, you'll do more testing on Win32s... Then you read https://finance.yahoo.com/news/microsofts-windows-95-software-turned-192528654.html https://finance.yahoo.com/news/microsofts-windows-95-softwar... People lined up to buy Win95 at midnight on release day? [Before Harry Potter book and iPhone releases] Commercial consumer Win32s support died that day. So running Win95 apps on OS/2 2.1 running Win3.1 running Win32s DLLs wasn't going to be a supported platform for software companies. IBM didn't want Win32 apps. They wanted OS/2 PM apps.