{"id":2503,"date":"2006-01-26T15:28:00","date_gmt":"2006-01-26T15:28:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/heaths\/2006\/01\/26\/setup-exe-bootstrap-sample-and-appver\/"},"modified":"2006-01-26T15:28:00","modified_gmt":"2006-01-26T15:28:00","slug":"setup-exe-bootstrap-sample-and-appver","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/setup\/setup-exe-bootstrap-sample-and-appver\/","title":{"rendered":"Setup.exe Bootstrap Sample and APPVER"},"content":{"rendered":"

On an internal alias – which inspires many of my blog entries – someone\nwasn’t able to run the sample bootstrap executable setup.exe<\/i>, found in\nthe Samples\/SysMgmt\/Msi\/Setup.exe<\/i> folder in your\nPlatform SDK<\/a> installation\nroot. The error was "setup.exe is not a valid Win32 application" when run on\nWindows 2000 but the sample worked fine on Windows XP. Right away it would seem\nthat something in the\n\nPE headers<\/a> of the sample something is wrong. Take a look at part of the \ndumpbin.exe<\/i> output:<\/p>\n

OPTIONAL HEADER VALUES\n             10B magic # (PE32)\n            7.10 linker version\n            A800 size of code\n            6200 size of initialized data\n               0 size of uninitialized data\n            5566 entry point (00405566)\n            1000 base of code\n            C000 base of data\n          400000 image base (00400000 to 00414FFF)\n            1000 section alignment\n             200 file alignment\n            4.00 operating system version\n            0.00 image version\n            5.01 subsystem version<\/font>\n               0 Win32 version\n           15000 size of image\n             400 size of headers\n           1EF48 checksum\n               2 subsystem (Windows GUI)<\/pre>\n
Because the subsystem version is 5.01 the executable will run on a minimum\noperating system of Windows XP. So how did this happen?<\/p>\n
If you build the setup.exe<\/i> sample using the build environment consoles\nalso installed with the Platform SDK, the environment variable APPVER<\/code> is set\naccording to which OS you pick in the current options. If you started the\nshortcut "Set Windows XP 32-bit Build Environment (Retail)" then APPVER<\/code> is\ndefined as 5.01. This variable is used many places in the win32.mak<\/i> file\nincluded by Makefile<\/i> in the setup.exe<\/i> sample directory.\nParticularilily this is why the subsystem was set to 5.01:<\/p>\n
# Windows 98 needs subsystem\nversion set to 4.10 for version 5.0 features.
\n!IF ("$(APPVER)" == "5.0") && (("$(TARGETOS)" == "BOTH") || ("$(TARGETOS)" ==\n"WIN95"))
\nEXEVER = 4.10
\n!ELSE
\nEXEVER = $(APPVER)
\n!ENDIF<\/p>\n
\n# ———————————————<\/p>\n
# for Windows applications
\nconlflags = $(lflags) -subsystem:console,$(EXEVER)
\nguilflags = $(lflags) -subsystem:windows,$(EXEVER)<\/p>\n
So when building setup.exe<\/i> make sure you set APPVER<\/code> according to your\nplatform requirements. You can either start the appropriate build environment\nconsole or after starting the console set APPVER<\/code> to 4.0, 5.0, 5.01,\nor 5.02. Future versions of the Platform SDK for future versions of Windows will\nlikely include support for additional values.<\/p>\n","protected":false},"excerpt":{"rendered":"
On an internal alias – which inspires many of my blog entries – someone wasn’t able to run the sample bootstrap executable setup.exe, found in the Samples\/SysMgmt\/Msi\/Setup.exe folder in your Platform SDK installation root. The error was "setup.exe is not a valid Win32 application" when run on Windows 2000 but the sample worked fine on […]<\/p>\n","protected":false},"author":389,"featured_media":3843,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[14,20],"class_list":["post-2503","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-development","tag-installation"],"acf":[],"blog_post_summary":"
On an internal alias – which inspires many of my blog entries – someone wasn’t able to run the sample bootstrap executable setup.exe, found in the Samples\/SysMgmt\/Msi\/Setup.exe folder in your Platform SDK installation root. The error was "setup.exe is not a valid Win32 application" when run on Windows 2000 but the sample worked fine on […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/posts\/2503","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/users\/389"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/comments?post=2503"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/posts\/2503\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/media\/3843"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/media?parent=2503"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/categories?post=2503"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/tags?post=2503"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}