This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: help setup is not a valid win 32 application
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 28, 2012
11:03 PM
help setup is not a valid win 32 application
ok i did my build and it comes up at the end with this file is not a valid win 32 application 😞 image in attachments
the setup type is installshild script
thank you in advance
the setup type is installshild script
thank you in advance
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Apr 02, 2012
03:57 PM
What is the actual size of this executable? Based on the screenshot the file size listed at the bottom of the Explorer window shows 4.00GB. Note that Windows will not load an executable that exceeds (2^32) -1 byte (which is 4,294,967,295 total bytes) and will consider it invalid. This is a limitation imposed by the memory mapping functions that are responsible for loading executable files both on 32-bit and 64-bit platforms (the Portable Executable format Windows supports is likely the reason for this limitation as the format only supports 32-bit file relative offsets).
The only way around this issue, if a compressed setup.exe is needed, is to reduce the size of the setup until it is less than the size mentioned above.
(For anyone interested, the internal Windows kernel function MiCreateImageFileMap in ntoskrnl.exe is responsible for checking the size of an executable image before loading it.)
The only way around this issue, if a compressed setup.exe is needed, is to reduce the size of the setup until it is less than the size mentioned above.
(For anyone interested, the internal Windows kernel function MiCreateImageFileMap in ntoskrnl.exe is responsible for checking the size of an executable image before loading it.)
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)