Reputation: 33
I have tried:
I have also went through other stackoverflow similar question, but did not find a solution in my case yet.
Upvotes: 2
Views: 805
Reputation: 15905
If InstallShield Limited Edition is creating a 64-bit package (which matches the symptoms you describe), this is because it believes you are installing resources to a 64-bit location. This could be a file under ProgramFiles64Folder or System64Folder, or a registry key under the 64-bit area. If you can find such, remove them and build again, and the result should be a 32-bit package.
It's also possible that some 64-bit registry keys come from performing COM extraction on your program, but that is unlikely to be the sole cause, as you tried ensuring your program is 32-bit.
If you have other MSI tools, you can search your built MSI for any 64-bit components (Attributes value includes the 256 bit), and try to track back their source. However InstallShield LE doesn't display components, so this may not be as easy to find and edit them if the component's name isn't obvious.
Upvotes: 2