Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • It's faq says win32; which isn't surprising. There were major architecture changes going from Win16 to Win32; it's not like the more recent 32-64bit transition which (for well written) code required little more than flipping a compiler switch. kmeleon.sourceforge.net/wiki/FAQ#platforms Commented May 18, 2012 at 12:43
  • 1
    @Dan - as others have mentioned, 32 bit code can be run on Windows 3.1 using win32s. As far as I remember, a pretty big subset of the win32 API was supported.
    – user31438
    Commented Jun 15, 2012 at 15:48
  • @Steve314 many of the APIs being capable of being grafted onto win16 isn't surprising, since in many cases the only changes needed would be changing the default int from 16 to 32 bits in length. At deeper levels the change from win16 applications cooperatively sharing a single process/thread among the OS and all applications and win32 using process isolation and preemptive scheduling is a massive shift for complex applications. As they steadily race towards doing everything that an OS does, browsers have become among the most complex applications in existence. Commented Jun 16, 2012 at 11:02