Java Runtime Environment (JRE) Addon Pack
click-click
21 Jul 2010
gUiTaR_mIkE, on 21 July 2010 - 05:34 AM, said:
Just wondering, did anyone ever figure out what the difference is between the file that has the -s and the file that doesn't?
I noticed the new Java file is minus the -s, the old link still has it -> jre-6u21-windows-i586-s.exe
I noticed the new Java file is minus the -s, the old link still has it -> jre-6u21-windows-i586-s.exe
-s version includes online installer of Google Toolbar or suggestions
about downloading OpenOffice (-s = suggest).
download from developer site for non-s version
Edited by click-click, 21 July 2010 - 10:27 PM.
Cristiano
22 Jul 2010
interesting. but when doing an silent install, it doesn't install any toolbar. at least, i never noticed that. the infos about openoffice booth versions has, i'm just not sure about toolbars
[]s
[]s
_def_x_
09 Aug 2010
...speaking of Java, anyone notice this? Go ahead, click the link
http://java.sun.com/
The Sun Java AddOn Pack may need some fixin, at least renamin'.
The Sun Java AddOn Pack may need some fixin, at least renamin'.
Cristiano
09 Aug 2010
to Oracle? if i'm not mistaken, they own Sun. but you are right. the next update will reflect that
[]s
[]s
DesertJerry
12 Oct 2010
Java SE Runtime Environment (JRE) 6 update 22 32-bit and 64-bit available
Cristiano
12 Oct 2010
done. first post updated with the modules and the links, but just in case:
JRE 6u22 x86
JRE 6u22 x64
booth executables shall be saved into modules\AddOns\SunJava_x86_files
modules:
jre_x86 module
jre_x64 module
just don't forget to erase the old versions
[]s
JRE 6u22 x86
JRE 6u22 x64
booth executables shall be saved into modules\AddOns\SunJava_x86_files
modules:
jre_x86 module
jre_x64 module
just don't forget to erase the old versions
[]s
click-click
12 Oct 2010
Hi Cristiano,
would it not be better to make the modules self-extracting in case a user doesn't have 7-zip
installed?
would it not be better to make the modules self-extracting in case a user doesn't have 7-zip
installed?
Cristiano
13 Oct 2010
isn't an bad idea, but the self-extracted version becomes too big to be attached. also, the attachment system gives an idea about the usage of those modules. but as an alternative, attached to this are the same modules, in zip format
[]s
[]s
bizzybody
13 Oct 2010
If you do not want MSN Bing toolbar crammed onto your PC without your permission, do not use the Java updater to download and install JRE 6 Update 22. It just did that on one of my PCs. Use the full installer download.
Grrrrr! Some software packager heads need some cracking together... Never *thunk* push *whack* crap *squash* onto *owwwwww* computers *please stop!* without *we promise we won't!* asking *never! not ever again!* permission!
Grrrrr! Some software packager heads need some cracking together... Never *thunk* push *whack* crap *squash* onto *owwwwww* computers *please stop!* without *we promise we won't!* asking *never! not ever again!* permission!
_def_x_
13 Oct 2010
Quote
If you do not want MSN Bing toolbar crammed onto your PC without your permission, do not use the Java updater to download and install JRE 6 Update 22. It just did that on one of my PCs. Use the full installer download.
Quote
Grrrrr! Some software packager heads need some cracking together... Never *thunk* push *whack* crap *squash* onto *owwwwww* computers *please stop!* without *we promise we won't!* asking *never! not ever again!* permission!
bizzybody
13 Oct 2010
I copied the rti and apm files for the latest Java version to their correct places under my AutoPatcher AddOns folder. I then ran apup and selected the Extras Addon pack.
It did not download the latest JRE. It still has 6 update 18.
It did not download the latest JRE. It still has 6 update 18.
_def_x_
13 Oct 2010
@bizzybody
You need to follow the link given on the first page and download yourself the latest Java and place it in the folder - \modules\AddOns\SunJava_x86_files - this is for x86. You need to delete all older versions of Java in the folder. Also, overwrite the .apm and .rti files with the new files as well. I like to delete the old files by hand personally - the old .exe, .apm, and .rti just in case the new files names are slightly different - in this case they wont get deleted and the release will be unofficial.
Java has made it impossible to grab a reusable link this is why the manual approach is needed - for now anyway. Unless you need to have the latest Java in your AutoPatcher release you could simply download the full installer, install using the switch in the .apm file for a silent install, and reboot when installation finishes.
You need to follow the link given on the first page and download yourself the latest Java and place it in the folder - \modules\AddOns\SunJava_x86_files - this is for x86. You need to delete all older versions of Java in the folder. Also, overwrite the .apm and .rti files with the new files as well. I like to delete the old files by hand personally - the old .exe, .apm, and .rti just in case the new files names are slightly different - in this case they wont get deleted and the release will be unofficial.
Java has made it impossible to grab a reusable link this is why the manual approach is needed - for now anyway. Unless you need to have the latest Java in your AutoPatcher release you could simply download the full installer, install using the switch in the .apm file for a silent install, and reboot when installation finishes.
_def_x_
13 Oct 2010
If I copy the latest Java to my C:\ drive this is the full command using Start - Run
C:\jre-6u22-windows-i586-s.exe /s IEXPLORER=1 MOZILLA=1 REBOOT=ReallySuppress
This will perform a silent install. You want to reboot when the install process is finished, the .apm file waits 120 seconds to complete.
C:\jre-6u22-windows-i586-s.exe /s IEXPLORER=1 MOZILLA=1 REBOOT=ReallySuppress
This will perform a silent install. You want to reboot when the install process is finished, the .apm file waits 120 seconds to complete.
DesertJerry
23 Oct 2010
I noticed on the Sun web site when I downloaded JRE-6u22 they recommended that users of 64-bit operating systems; XP Pro x64 and Win7 64-bit, download and install both the 32-bit and 64-bit versions of the Sun Java runtime. This will then install both versions so that if the user starts either the 32-bit or the 64-bit version of Internet Explorer the updated version of the Java runtime would also be available.
Accepting that recommendation as valid I would now recommend AutoPatcher's APM files be edited so that if the user runs AutoPatcher in a 64-bit environment both versions of the Java runtime are listed as installed or not installed with the option to install both.
Also, this same thinking and procedure applies to the Adobe Flash Players - in a 64-bit OS both the 32-bit and 64-bit versions should be installed - for the same reason given above.
Edited by DesertJerry, 23 October 2010 - 02:44 AM.
Accepting that recommendation as valid I would now recommend AutoPatcher's APM files be edited so that if the user runs AutoPatcher in a 64-bit environment both versions of the Java runtime are listed as installed or not installed with the option to install both.
Also, this same thinking and procedure applies to the Adobe Flash Players - in a 64-bit OS both the 32-bit and 64-bit versions should be installed - for the same reason given above.
Edited by DesertJerry, 23 October 2010 - 02:44 AM.
Cristiano
23 Oct 2010
in fact, the x64 version is only required if the user runs an browser that is x64. so far i know, the default browser under x64 systems is still x86. also, if we deploy both versions in the same module, someone could say that we are deploying things without the knowledge of the user. by me, i never will do that. as for flash player x64, it is still preview release
[]s
[]s
DesertJerry
23 Oct 2010
Cristiano, on 23 October 2010 - 10:43 AM, said:
in fact, the x64 version is only required if the user runs an browser that is x64. so far i know, the default browser under x64 systems is still x86. also, if we deploy both versions in the same module, someone could say that we are deploying things without the knowledge of the user. by me, i never will do that. as for flash player x64, it is still preview release[]s
In a 64-bit system there are two browsers installed: one in \Program Files\Internet Explorer (the 64-bit version) and one in \Program Files (x86)\Internet Explorer (the 32-bit version). Users are capable of selecting either for use. I'm not sure why you say the 32-bit is the default - I have not had it act that way. If the 64-bit version has been invoked and the user selects Microsoft Update - an error nessage appears saying to switch to the 32-bit version - is that what you're assuming is the default?
Anyway, because both versions are available to any user than knows where to look it only makes sense to offer both Java runtimes - just list them as separate items: 32-bit for one and 64-bit for the other.
Same for Adobe Flash if/when it goes final for the 64-bit version.
Cristiano
23 Oct 2010
> I'm not sure why you say the 32-bit is the default
because the one that runs when you hit any link in a software (like msn) is the x86 version. also, the one that has the shortcuts set by default is the x86 version. in fact, x64 systems comes with both versions, but if you wanna run the x64 version, you have to look for it, since the one that is under everyone face is the x86 version
> is that what you're assuming is the default?
that also
> just list them as separate items: 32-bit for one and 64-bit for the other
for sure. that is the way that is being done. the only one thing that happens is that the user has to select it to be installed. so, if the user has an x64 system and doesn't wish deploy the x64 version for certain softwares, he will not. by other hand, if an user that is running x64 and is running an x64 browser wishes deploy both, then all that the user needs to do is check an extra module to be installed
> Same for Adobe Flash if/when it goes final for the 64-bit version
for sure
[]s
because the one that runs when you hit any link in a software (like msn) is the x86 version. also, the one that has the shortcuts set by default is the x86 version. in fact, x64 systems comes with both versions, but if you wanna run the x64 version, you have to look for it, since the one that is under everyone face is the x86 version
> is that what you're assuming is the default?
that also
> just list them as separate items: 32-bit for one and 64-bit for the other
for sure. that is the way that is being done. the only one thing that happens is that the user has to select it to be installed. so, if the user has an x64 system and doesn't wish deploy the x64 version for certain softwares, he will not. by other hand, if an user that is running x64 and is running an x64 browser wishes deploy both, then all that the user needs to do is check an extra module to be installed
> Same for Adobe Flash if/when it goes final for the 64-bit version
for sure
[]s
click-click
01 Dec 2010
Is there an AP download for java6u23?
6u23 has been out for a while now. The final ended up being build 05
Edited by click-click, 01 December 2010 - 11:34 PM.
6u23 has been out for a while now. The final ended up being build 05
Edited by click-click, 01 December 2010 - 11:34 PM.
_def_x_
01 Dec 2010
hmm, I'm still getting v6u22 here - http://java.com/en/download/manual.jsp - are you sure that is a final release and not still beta?
click-click
02 Dec 2010
I guess Sun is taking their time updating the website. I believe B05 is the one that is supposed to be released. I did not realize that Sun had not updated yet. Next time, I hope I can remember to check the official download site.


