/build/static/layout/Breadcrumb_cap_w.png

How to install and customize Java 6 update 31 to keep old version (java6 update29)?

I need to keep old version of java (v.6 update 29) because of an application. I need to install new version on particular path (%root%\Program Files\java\jre6_u31). I extract MSI from EXE and tried to customize with Orca, but no sucess. Java is for IE only and no future updates.


0 Comments   [ + ] Show comments

Answers (6)

Posted by: pjgeutjens 12 years ago
Red Belt
2

you could try to do a static installation of the new JRE adding STATIC=1 as a parameter.

Posted by: GAKIS 12 years ago
Fourth Degree Green Belt
2

I use: 

jre-6u31-windows-i586.exe /qn ADDLOCAL=ALL SYSTRAY=0 EULA=0 IEXPLORER=1 JAVAUPDATE=0 AUTOUPDATECHECK=0 JU=0 REBOOT=ReallySupress [INSTALLDIR=<drive>:\<install_path>] STATIC=1

As said before just use the Static=1 switch to keep old versions.
Posted by: andemats 12 years ago
2nd Degree Black Belt
1

How did you extract the MSI?

You need to run the EXE with the STATIC=1 switch and grab the MSI from %TEMP% (or wherever it is). I had issues with this also untill I realized there were two different MSI's extracted depending on if you run the EXE with or without the STATIC-switch.


Comments:
  • Man, I've been packaging JRE's for ages and I never even noticed that
    It does make sense though to change product/upgrade/component codes if they want to bypass upgrades for future versions

    Nice to learn something new today :D

    P.S. It's the locallow %AppData% in the folder Sun/Java/ where the msi gets placed during install - pjgeutjens 12 years ago
Posted by: ogeccut 12 years ago
Black Belt
1

If you have msi extracted, check upgarde table. If there is a upgrade code for 6.29. create a TRANSFORM and delete upgrade code for that version. TEST.

Posted by: alphabeta 12 years ago
Black Belt
1

does the program that use update 29 not work if you only have update 31 installed? I thought update 31 was backward compatable?

Posted by: anonymous_9363 12 years ago
Red Belt
0

We do all know, don't we, that most Java apps are incredibly dumb? The version relience comes about at "compile" time and actually has little relevance for most apps, unless by some miracle, they have a dependency on a version-specific feature.

The point is, you can fool, 99.999% of apps into believing that v[whatever] is installed by "ghosting the relevant registry entries beneath HKLM\Software\JavaSoft. I generally export the existing registry entry, edit the .REG to reflect the required version details then import the edited .REG. So far, across 3 separate and unconnected clients. I have yet to come across an app which failed to execute.

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ