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

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
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.
Answered 08/07/2009 by: VBScab
Red Belt

Please log in to comment
0
No, I have the offline installer which is appr. 16MB but the MSI file is only 1,8MB so it really needs the CAB file to complete the installation. It seems like the vendor has started using external CAB files because earlier versions of JRE has only been a MSI that contains all the necessary files.
Answered 08/07/2009 by: RS|Stian
Orange Belt

Please log in to comment
0
That's right, they have switched to external CABs (or the packager forgot to set the media options!). I just re-ran the executable as a sanity check and I definitely get Data1.CAB in my %TEMP% folder.
Answered 08/07/2009 by: VBScab
Red Belt

Please log in to comment
0
Does the CAB file appears at once when you run the executable or after the installation is done? I only get the MSI file and a couple of java install text log files.
Answered 08/07/2009 by: RS|Stian
Orange Belt

Please log in to comment
0
It's alongside the MSI which gets extracted.
Answered 08/07/2009 by: VBScab
Red Belt

Please log in to comment
0
Tried the online installer now and this one extracted an 10MB MSI file under temp folder which obviously worked without asking for the CAB file. So finally it seems like my package it's working [:)]
Answered 08/07/2009 by: RS|Stian
Orange Belt

Please log in to comment
0
Versions 1.0.6.1 through 1.0.6.14 seem to extract under "Application Data", Sun folder. The msi in the "Temp" is the copy of the one underneath Application Data
Answered 08/07/2009 by: revizor
Third Degree Blue Belt

Please log in to comment
0
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?
Answered 08/10/2009 by: RS|Stian
Orange Belt

Please log in to comment
0
That's correct. Java won't uninstall previous version until version 6 update 10. When you try to upgrade to the newest one, the old one will always stay.

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.
Answered 08/10/2009 by: lam2070
Senior Yellow Belt

Please log in to comment
0
JREs are designed to live together in peace and harmony. The last to be installed will update'HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\CurrentVersion' but most apps ignore that.
Answered 08/10/2009 by: VBScab
Red Belt

Please log in to comment
0
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}
Answered 08/11/2009 by: RS|Stian
Orange Belt

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