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
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Sorry, I forgot some important info to this post.

The package errors on the Internet Explorer detect even if the version of IE is above 5.0. I'm trying to deploy it to WinXP, which has a newer version, and it still errors.
Thanks
Answered 12/03/2004 by: cdorhout
Senior Yellow Belt

Please log in to comment
0
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.
Answered 12/03/2004 by: Toupeiro
Senior Yellow Belt

Please log in to comment
0
I ran into a similar problem repackaging Dreamweaver. Depending on the specifics of your package, this might be useful to you. Here is the link:

http://www.appdeploy.com/packages/detail.asp?id=241


Craig --<>.
Answered 12/03/2004 by: craig16229
Third Degree Brown Belt

Please log in to comment
0
I had the exact same issue with a product that used IE as it's engine. It had the exact same error as you where getting.
Use "REGMON" to watch what it is trying to do, then give permissions to that specific key as per required to fix.
Answered 12/05/2004 by: dbowe
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity