Sun Java (JRE) Update v1.6.0_15
Working on package JRE 1.6.0_u15 and I need to make an AIP but when using the MSI file that is wrapped inside the vendor's EXE file it's requesting a data1.cab file that obviously contains all the system files. When extracting the EXE file I only get the MSI file (under temp directory) and no CAB file. Is there any possibility to get the CAB file out of the EXE? If not, how to resolve this? I'm using Wise to package...
0 Comments
[ + ] Show comments
Answers (11)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
What I *think* you may have done is downloaded the web installer, which pulls files from sun.com. It's not immediately obvious at the d/l stage. Go to this page http://www.java.com/en/download/manual.jsp and select 'Windows XP/Vista/2000/2003/2008 Offline instead of the 'Online' link.
Posted by:
RS|Stian
14 years ago
Posted by:
anonymous_9363
14 years ago
Posted by:
RS|Stian
14 years ago
Posted by:
RS|Stian
14 years ago
Posted by:
revizor
14 years ago
Posted by:
RS|Stian
14 years ago
I thought I was finished with customizing the transform file but there is one issue regarding uninstall of previous versions of Java I can't figure out how to resolve. The last version that are deployed to the PC's in our environment is 6 update 2 so this is the one I want to be uninstalled before the new one gets installed. I use Wise Package Studio to create the packages and have added the following row into the Upgrade table:
UpgradeCode: {3248F0A7-6813-11D6-A77B-00B0D0160030}
Attributes: 769
ActionProperty: UNINST_JRE1.6.02
I've also edited 'SecureCustomProperties' in the Property table to contain the following:
INSTALLINTL;UNINST_JRE1.6.0.02
But still, after testing the installation and transform, the previous version is on the PC and both old and new Java appears under Add or Remove Programs. I guess I've missed out something here?
UpgradeCode: {3248F0A7-6813-11D6-A77B-00B0D0160030}
Attributes: 769
ActionProperty: UNINST_JRE1.6.02
I've also edited 'SecureCustomProperties' in the Property table to contain the following:
INSTALLINTL;UNINST_JRE1.6.0.02
But still, after testing the installation and transform, the previous version is on the PC and both old and new Java appears under Add or Remove Programs. I guess I've missed out something here?
Posted by:
lam2070
14 years ago
Posted by:
anonymous_9363
14 years ago
Posted by:
RS|Stian
14 years ago
I know this is not the best approach, however I normally simply run a msiexec /x to uninstall the old one before installing the new one.
Ended up using this method to get rid of old versions before installing the latest one myself. Found this list with product codes for a lot of Java versions:
msiexec.exe /qn /x {7148F0A8-6813-11D6-A77B-00B0D0142000}
msiexec.exe /qn /x {7148F0A8-6813-11D6-A77B-00B0D0142010}
msiexec.exe /qn /x {7148F0A8-6813-11D6-A77B-00B0D0142020}
msiexec.exe /qn /x {7148F0A8-6813-11D6-A77B-00B0D0142030}
msiexec.exe /qn /x {7148F0A8-6813-11D6-A77B-00B0D0142040}
msiexec.exe /qn /x {7148F0A8-6813-11D6-A77B-00B0D0142050}
msiexec.exe /qn /x {7148F0A8-6813-11D6-A77B-00B0D0142060}
msiexec.exe /qn /x {7148F0A8-6813-11D6-A77B-00B0D0142070}
msiexec.exe /qn /x {7148F0A8-6813-11D6-A77B-00B0D0142080}
msiexec.exe /qn /x {7148F0A8-6813-11D6-A77B-00B0D0142090}
msiexec.exe /qn /x {7148F0A8-6813-11D6-A77B-00B0D0142100}
msiexec.exe /qn /x {7148F0A8-6813-11D6-A77B-00B0D0142110}
msiexec.exe /qn /x {7148F0A8-6813-11D6-A77B-00B0D0142120}
msiexec.exe /qn /x {7148F0A8-6813-11D6-A77B-00B0D0142130}
msiexec.exe /qn /x {7148F0A8-6813-11D6-A77B-00B0D0142140}
msiexec.exe /qn /x {7148F0A8-6813-11D6-A77B-00B0D0142150}
msiexec.exe /qn /x {7148F0A8-6813-11D6-A77B-00B0D0142160}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0150000}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0150010}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0150020}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0150030}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0150040}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0150050}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0150060}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0150070}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0150080}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0150090}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0150100}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0150110}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0150120}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0150130}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0150140}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0160000}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0160010}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0160020}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0160030}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0160040}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0160050}
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.