AutoPatcher Forum

FYI...here are the changes needed to update the javajre_x86.apm file:

Title=Java Runtime Environment (JRE) Version 6 Update 24 (x86)
---
Title=Java Runtime Environment (JRE) Version 6 Update 23 (x86)

RegistryPath=HKCR\Installer\Products\4EA42A62D9304AC4784BF238120642FF
---
RegistryPath=HKCR\Installer\Products\4EA42A62D9304AC4784BF238120632FF

KeyValue=Java™ 6 Update 24
---
KeyValue=Java™ 6 Update 23

"Module:\jre-6u24-windows-i586.exe" /s IEXPLORER=1 MOZILLA=1 REBOOT=ReallySuppress
---
"Module:\jre-6u23-windows-i586.exe" /s IEXPLORER=1 MOZILLA=1 REBOOT=ReallySuppress
Edited by click-click, 18 February 2011 - 10:23 PM.

guys, just an hint: mike may be unable to do everything alone. my free time is reduced to basically nothing (except when i'm at my job, but i can't check for detections in there). so, i may help, but i can't help too much. so, this forum really requires someone able to fix at least some script/modules. some are very easy to do and most of them only have an update every month, if so. java, by instance, just requires 2 downloads, change a few fields in the modules and sign it. for the download, it's pretty easy. all that yours have to do is browse to java.com, check free download, all downloads and pick the link for Windows 7/XP/Vista/2000/2003/2008 Off-line. as yours may notice, the default BundleId for this month is 47152, but this downloads the -s version (aka toolbar version). to get the version without it, just add 1 to the BundleId, that will become 47153, that is the x86 version, without the toolbar. for the x64 version, just add 2 to the BundleId for the version without the toolbar (or 3 from the default bundle id). so, the bundle id will become 47155. for that isn't required to work for NASA or something like that. most of the detections are pretty easy to do and most of the detections are already set to be done easily, just changing a few things. just by instance, for the x64 version of java 24, this is the detection:
[DetectionRegistry]
RegistryPath=HKCR\Installer\Products\4EA42A62D9304AC4784BF268140642FF
KeyName=ProductName
KeyValue=Java™ 6 Update 24 (64-bit)

and the install string:
"Module:\jre-6u24-windows-x64.exe" /s IEXPLORER=1 MOZILLA=1 REBOOT=ReallySuppress

not an big deal, isn't? so please, at least give an try to it

thanks in advance

[]s

Update 25 is available. http://www.oracle.co...oad-346243.html
jre-6u25-windows-i586.exe

Changes for javajre_x86.apm:

Title=Java Runtime Environment (JRE) Version 6 Update 24 (x86)
Title=Java Runtime Environment (JRE) Version 6 Update 25 (x86)

RegistryPath=HKCR\Installer\Products\4EA42A62D9304AC4784BF238120642FF
RegistryPath=HKCR\Installer\Products\4EA42A62D9304AC4784BF238120652FF

KeyValue=Java™ 6 Update 24
KeyValue=Java™ 6 Update 25

"Module:\jre-6u24-windows-i586.exe" /s IEXPLORER=1 MOZILLA=1 REBOOT=ReallySuppress
"Module:\jre-6u25-windows-i586.exe" /s IEXPLORER=1 MOZILLA=1 REBOOT=ReallySuppress

isn't required go to oracle to get that. just check those links:
Windows 7, XP Off-line (32 bits)u25
Windows 7, XP Off-line (64 bits)u25

[]s
Edited by Cristiano, 21 May 2011 - 12:41 AM.

Due to a system crash I am in need of the original Java module files as posted by Christiano on 16/10/2010. Unfortunately the Autopatcher links he supplied no longer exist. Can anyone help? Assistance would be greatly appreciated.

that one i don't have anymore, just the current ones. to avoid that, i'm posting it as text. all that you have to do is paste it into notepad and save it with the proper name as follows:
javajre_x64.apm

javajre_x86.apm
to get the detections for the new ones or the old ones, all that you have to do is change the fields pointed by BAM. if you wish, change also ReleaseDate= ModuleAuthor=

[]s

Thanks Christiano. Any idea where I could get the java_jre.rti file?

the .rti files aren't required. those files only work to sign the modules and ensure that they was downloaded ok and avoid the "unofficial" issue. as the current version isn't signed... also, deploy an version from that time isn't an good idea. jre has an auto-update feature. if you deploy that, then shortly you will be downloading the latest version without knowing it

[]s

Just for everyone's information and update: JRE6 update 26 is out. x64 and x86 versions

true. download links:
Windows 7, XP Off-line (x86)
Windows 7, XP Off-line (x64)

required module changes:
x64:

x86:

[]s

I think we may have discussed this before but I have forgotten, did we determine if there is a difference with the java downloads from Java.com versus FileHippo - JavaJRE?

I know the files are named differently - Java.com (jre-6u26-windows-i586-s.exe) and FileHippo (jre-6u26-windows-i586.exe).

The reason is, it would be nice to get Java signed but I cannot download a 64-bit version from Java.com, it detects the browser. If Bam's info is correct it's pretty easy to edit the apm files. Otherwise, I can only sign a 32-bit and ignore the 64-bit.

and they are detecting if you are running x64 even if you aren't running an x64 browser. but with the link that i've posted in my last post, everybody can

as for Java.com versus FileHippo, both are the same version (except that the default version in java.com is the -s version and the user that wishes the version without that has to add an +1 in the download link. also, for the x64, it's just add another +1 in the download link). but states that their version is the SE edition and not the JDK

[]s
Edited by Cristiano, 08 June 2011 - 05:06 PM.

If someone downloads either (hopefully both) versions of Java from post#160 could you supply the md5 and size, I downloaded the x64 file but it may be corrupt??? I'll download the x86 version later.

Once I get a confirmation on the size & hash I'll update the Java page and provide a more detailed explanation on how to add (manually) Java to an AutoPatcher release.

jre-6u26-windows-i586 from Cristiano's link is 15.8 MB (16,619,296 bytes) and the md5 has is 216ca7b04a6898b427643ac683674777
jre-6u26-windows-x64 from Cristiano's link is 16.1 MB (16,920,684 bytes) and the md5 is 169cd52ad4b57e6439171fa411a4b6ef
I checked the md5's against the Java updates I downloaded from filehippo yesterday - and they are the same as these two.

confirmed

[]s

Thanks dfdff3000, that's what I wanted

I will try to get Java done in the next few days, I still have to download Java (x86) on dialup. My first priority is to help get XP SP3 finished, my friend is doing good, almost done, about 15 or so updates added, 8 or so removed, 3 more bulletins left.

I need some clarification, just a bit confused still:

Cristiano said:

This is the download link for x86 - http://javadl.sun.co...?BundleId=49024 - are you saying to change to BundleId=49025, this will download without the -s?

Cristiano said:

I'm not following what you mean exactly? I downloaded the x86 version from java.com, unedited BundleId, one thing I noticed is the executable uses the java coffee cup icon (Java logo), I also downloaded the x64 version using your link, this executable has an ugly dos-like icon (like AutoPatcher), this is why I thought the download was corrupted - it's not, the hash matches. Btw, both files say binary SE!

> are you saying to change to BundleId=49025, this will download without the -s?
yep. it will be the clean version

> I'm not following what you mean exactly?
at oracle site, it's possible download the developer edition (JDK) and the runtime edition (SE). to avoid issues about "hey, i'm looking for the developer edition, not this one", they state the version, just that. as for the link, in here both versions has the same icon. it may be related to the OS (i'm under x64)

[]s

Cristiano said:

OK, makes sense, but this is what still confuses me a bit... your download link for x64 is BundleId=49026, this is to get the x64 version without the -s correct, which means you added +1? What was the original (unedited) BundleId for x64, it couldn't be BundleId=49025, isn't this the edited version for x86 without -s?

> What was the original (unedited) BundleId for x64
that is the original BundleId for x64. that version doesn't have crapware. that way to track the version is just an easy way that i've realized long ago to get the x64 version without change to an x64 browser. now, doesn't matter, their detection is becoming smarter and now it shows both versions to those that run an x64 OS. the interesting thing about that is that if you keep adding +1, you will be getting a lot of versions of java

so:
BundleId=49024 = the x86 version -s
BundleId=49025 = the x86 version
BundleId=49026 = the x64 version
BundleId=49027 = JavaSetup6u26-rv.exe
BundleId=49028 = JavaSetup6u26-sprev.exe

etc

[]s
Edited by Cristiano, 09 June 2011 - 01:19 AM.

OK, can Java(JRE) x64 use both nice and simple registry alternatives for detection (I know one works, do both) - like these for x86:

Note: Is there an HKLM similar to x86 above - simple, easy to read and update - I would like 2 (1 alternative) for each version