DOS Ain't Done Til Lotus Won't Run? (2005)

Re:DOS Ain't Done Til Lotus Won't Run? (2005) by untog on Thursday October 22, 2015 @11:55AM (#10432925)

I don't see how those two things are in any way connected. The point they were making is that you might even be able take a Windows 3.1 app (but definitely a Windows 95 one) and run it on Windows 8.

[ Parent | on HN ]

Re:DOS Ain't Done Til Lotus Won't Run? (2005) by jcranmer on Thursday October 22, 2015 @12:21PM (#10433080)

Actually, you can't do Windows 3.1: Microsoft ripped out the Win16 subsystem in Windows 7.

[ Parent | on HN ]

Re:DOS Ain't Done Til Lotus Won't Run? (2005) by yuhong on Thursday October 22, 2015 @12:27PM (#10433122)

They didn't. You can still enable it in 32-bit Win10 I think.

[ Parent | on HN ]

Re:DOS Ain't Done Til Lotus Won't Run? (2005) by apaprocki on Thursday October 22, 2015 @12:35PM (#10433169)

I wonder if Solaris ABI compat is actually older than the Windows stuff. Solaris to this day maintains binary compat with older releases and, for example, a 32-bit fopen() will fail once you open 255 streams because that was the limit in the ancient ABI. Everyone using Solaris at one point or another has probably hit this and it caused some issue, but Sun^H^H^HOracle refuses to make modern operation the default, all in the name of ancient binary compat. That's a bit more hardcore than optional support you can enable.

[ Parent | on HN ]

Re:DOS Ain't Done Til Lotus Won't Run? (2005) by creshal on Thursday October 22, 2015 @12:34PM (#10433160)

16-bit compatibility only exists in the 32-bit version, no longer in the 64-bit one. Same as every x64 version since XP64.

[ Parent | on HN ]

Re:DOS Ain't Done Til Lotus Won't Run? (2005) by wvenable on Thursday October 22, 2015 @01:20PM (#10433462)

This is because in 64-bit mode the CPU can no longer handle 16-bit code. It's all AMD's fault...

[ Parent | on HN ]