www.digitalmars.com         C & C++   DMDScript  

c++.windows - Windows 95, Windows NT, Win32s

reply John Doe <john noreply.com> writes:
Hello,

the IDDE offers a choice under Project Settings -> Target -> Platform. I can
choose between Windows 95, Windows NT,
Win32s (and others, but that's beyond my question). My question is now: What's
the actual difference between them? Which
of them would I pick for maximum compatability to all versions of 32 bit
Windows? And then, when would I need or want to
use the others? Does the compiler actually do something different? Does it
generate better optimized code?
For example, does code compiled for Windows NT work "better" on Windows NT than
code that was compiled for Windows 95 or
Win32s? Does code compiled for Windows NT or Windows 95 still run on Win32s?

Thanks for any answers,
John
Apr 06 2007
parent reply Walter Bright <newshound1 digitalmars.com> writes:
John Doe wrote:
 Hello,
 
 the IDDE offers a choice under Project Settings -> Target -> Platform. I can
choose between Windows 95, Windows NT,
 Win32s (and others, but that's beyond my question). My question is now: What's
the actual difference between them? Which
 of them would I pick for maximum compatability to all versions of 32 bit
Windows? And then, when would I need or want to
 use the others? Does the compiler actually do something different? Does it
generate better optimized code?
 For example, does code compiled for Windows NT work "better" on Windows NT
than code that was compiled for Windows 95 or
 Win32s? Does code compiled for Windows NT or Windows 95 still run on Win32s?
These days, just use Windows NT. Win32s is painfully obsolete, and Win95 isn't worth the bother. All this switch does is mark the executable so that Windows itself knows how to handle it.
Apr 10 2007
parent John Doe <john noreply.com> writes:
== Auszug aus Walter Bright (newshound1 digitalmars.com)'s Artikel

 These days, just use Windows NT. Win32s is painfully obsolete,
and Win95
 isn't worth the bother. All this switch does is mark the
executable so
 that Windows itself knows how to handle it.
Thanks! - John
Apr 11 2007