msi errors on Internet Explorer version detect
Hello,
I'm new to packaging and need help.
I use Wise Package Studio 4.6.
I did a setup catpure to create an msi and when trying to install with that new msi, it says: "Internet Explorer 5 or above needed to install"
This version detect must have been built into the original setup of the app, b/c I didn't add it to the msi.
Does anyone know where I need to look in Wise to hack this detection out?
Thanks in advance
I'm new to packaging and need help.
I use Wise Package Studio 4.6.
I did a setup catpure to create an msi and when trying to install with that new msi, it says: "Internet Explorer 5 or above needed to install"
This version detect must have been built into the original setup of the app, b/c I didn't add it to the msi.
Does anyone know where I need to look in Wise to hack this detection out?
Thanks in advance
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
cdorhout
19 years ago
Posted by:
Toupeiro
19 years ago
You may want to make a different copy of your MSI and try this because I'm going by memory [;)]
I packaged an app once that gave me a headache with IE version detection. There wasn't a condition built under system requirements to check for the IE version, it was being handled by custom actions. you can try taking a look under MSI script under all tabs, then, if you see this, remark out the WiseAPI.dll call (GetIeVersion) in any execute phase, then remove any pointers to this function call in your tables (CustomAction; InstallExecuteSequence; InstallUISequence, and any others you may find) That is what worked for me. I hope this helps you out.
I packaged an app once that gave me a headache with IE version detection. There wasn't a condition built under system requirements to check for the IE version, it was being handled by custom actions. you can try taking a look under MSI script under all tabs, then, if you see this, remark out the WiseAPI.dll call (GetIeVersion) in any execute phase, then remove any pointers to this function call in your tables (CustomAction; InstallExecuteSequence; InstallUISequence, and any others you may find) That is what worked for me. I hope this helps you out.
Posted by:
craig16229
19 years ago
Posted by:
dbowe
19 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.