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: Remove platform-specificity from x86-targeted MSI
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
‎Sep 30, 2011
05:37 PM
Remove platform-specificity from x86-targeted MSI
I have a Basic MSI installer that was targeted to x86 platforms (with a companion installer targeted to x64). We have removed the 64-bit components and would like to have a single installer that works on both platforms. However, the x86 installer refuses to run on x64 platforms.
The Platforms value on the x86 installer reads "Intel;1033" which according to what I've read should work for both. The Platforms value in the Release view is blank.
Where else can I look to remove the platform specificity and allow the single installer to work on x86 and x64?
The Platforms value on the x86 installer reads "Intel;1033" which according to what I've read should work for both. The Platforms value in the Release view is blank.
Where else can I look to remove the platform specificity and allow the single installer to work on x86 and x64?
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 03, 2011
11:59 AM
The three places platforms can interrupt the install are:
- Template summary, as you describe. If it said x64 it would refuse to run on an x86 machine.
- Launch Conditions. If a launch condition of the format NOT VersionNT64 is present, the package would exit on 64-bit machines.
- Custom actions, including the type 19 error custom action. If a type 19 action with the condition VersionNT64 existed, it would exit on a 64-bit machine. Similarly scripted or C++ code custom actions can abort as they see fit by returning an error code.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 03, 2011
04:50 PM
MichaelU wrote:
- Launch Conditions. If a launch condition of the format NOT VersionNT64 is present, the package would exit on 64-bit machines.
It was a Launch Condition. Thank you for your help!
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)