Repackaging a NSIS installer with JRE inside?!
Hi...
I have a NSIS installer exe that I want to turn into a MSI package for deployment with SCE2010...
The application it self is mostly Java, and therefore the vendor installer installs Java Runtime Enviroment without giving me the choice to leave it out...
Since this program is not shipped with the latest JRE I really don't want to capture a setup with an older version, and also because out client-computers all ready have the lastest JRE deployed...
So... When I do a repackage with Wise I want to leave out the JRE part of the installation, as I think it will cause some trouble putting an older version into my repackaged MSI?! But when I do so, the App is not working after install...
The real question is: Do I have to worry about this JRE in my repacking or will it automatically detect that there is a newer version installed already?!
I'm quite of a newbie, so sorry if this is a stupid question, but the application is not mainstream so google is not really my friend here... :D
Cheers
Bo Urskov, Denmark
I have a NSIS installer exe that I want to turn into a MSI package for deployment with SCE2010...
The application it self is mostly Java, and therefore the vendor installer installs Java Runtime Enviroment without giving me the choice to leave it out...
Since this program is not shipped with the latest JRE I really don't want to capture a setup with an older version, and also because out client-computers all ready have the lastest JRE deployed...
So... When I do a repackage with Wise I want to leave out the JRE part of the installation, as I think it will cause some trouble putting an older version into my repackaged MSI?! But when I do so, the App is not working after install...
The real question is: Do I have to worry about this JRE in my repacking or will it automatically detect that there is a newer version installed already?!
I'm quite of a newbie, so sorry if this is a stupid question, but the application is not mainstream so google is not really my friend here... :D
Cheers
Bo Urskov, Denmark
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
Some idiot vendors will insist on installing their flavour, no matter what's installed. In a word, cheat. You can "ghost" the flavour of JRE that the installer wants using your flavour.
What I mean by that is, say you have 1.6_23 but the installer wants to put down 1.4_12. You export the registry data for JRE (from memory, HKLM\Software\JavaSoft) and copy the 1.6_23 entries to almost identical new ones named 1.4_12 and save as a new .REG. Import that new .REG and start the installer. Hopefully it will see that its preferred JRE is installed and carry on its merry way.
Having said that, JREs are easy to spot in a capture, since they use (mostly) discrete registry entries and folders so they can be removed from the package if they should slip through.
What I mean by that is, say you have 1.6_23 but the installer wants to put down 1.4_12. You export the registry data for JRE (from memory, HKLM\Software\JavaSoft) and copy the 1.6_23 entries to almost identical new ones named 1.4_12 and save as a new .REG. Import that new .REG and start the installer. Hopefully it will see that its preferred JRE is installed and carry on its merry way.
Having said that, JREs are easy to spot in a capture, since they use (mostly) discrete registry entries and folders so they can be removed from the package if they should slip through.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
