AutoPatcher Forum

 Erik Ramey, on Dec 12 2007, 03:02 AM, said:

Hi Erik,

problem is with jre hash and also uz unknown header problem - can't extract, see log file below

Download queue status: 2 files waiting.
jre-6u3-windows-i586-p-s.exe: 404 File not found
Download queue status: 1 files waiting.
windows_addons_xp_x86_enu.zip: Download complete.
Download queue status: 0 files waiting.
Attempting to unzip H:\AutoPatcher\XP\modules\windows_addons_xp_x86_enu.zip into H:\AutoPatcher\XP\modules

it stops here, comes up with a uz - unknown error.

and also - could not extract these:

Looking for file H:\AutoPatcher\XP\modules\AddOns\sunjava_x86_enu.apm
File does not exist!!!
Looking for file H:\AutoPatcher\XP\modules\AddOns\SunJava_x86_files\noicon.apf
File does not exist!!!

Starting detection routine for item Java x86 1.6_03
Looking for file H:\AutoPatcher\XP\modules\AddOns\SunJava_x86_files\jre-6u3-windows-i586-p-s.exe
File does not exist!!!

I thought that this could be the culprit. I went ahead and compress Java into addonfiles.zip for now. Everything should be working now.

Hi guys,

Ok, still getting the verification errors!

Here is a copy of the problems from the log file:

Looking for file C:\apup\modules\Critical\KB890830_x86_enu.apm
MD5 Hashes do NOT match. Expecting FD86116D72AF3857E5B5A95D219979EC, but found 54e64122255231fc4c1d41e7367ed886!!!

Looking for file C:\apup\modules\AddOns\sunjava_x86_enu.apm
MD5 Hashes do NOT match. Expecting 59B07B4D48DE608DA21CEC208DE6825E, but found cf7086c528da9bbd645cc56ca44406ed!!!
Looking for file C:\apup\modules\AddOns\SunJava_x86_files\noicon.apf
MD5 Hashes do NOT match. Expecting CF7086C528DA9BBD645CC56CA44406ED, but found 2c3e2c65011f6088d2f86340b8959bd7!!!
Item AutoPatcher AddOns Modules doesn't appear to be here. Adding its downloads to queue...
Adding http://www.autopatcher.com/releases/englis..._xp_x86_enu.zip.

Hopes this helps!

Regards.

I had the same problem, but i have deleted the java files, as the result of a previous problem with this, but is working fine now.

maybe if apup.exe finds a hash problem, delete the problem file and redownload.

Go ahead and try again. Both probably should be corrected. These Verification errors was do to me updating xp first and waiting a day to do 2000. Next month I'll be updating XP and 2000 at the same so this doesn't happen again.

It now downloads the dotnet2.0sp1 fine. But i get another file verification error!

Looking for file C:\apup\modules\Components\__dotnet\dotnet3.5_enu.apm
MD5 Hashes do NOT match. Expecting 89205a7b98b191a1d46c21ca5d20cfc9, but found 19bfd0c211fd85be41bdcab0910c3aae!!!

Thanks!

Already reported by somebody else but no worries... Fixed =)

I've found these hash not matching - don't seems critical, i've deleted them and reloaded without any problems

Maybe a option for apup.exe is to delete apm files when it finds a hash not matching, and re-download again, would solve it.

Looking for file H:\AutoPatcher\XP\modules\Critical\KB942763_xp_x86_enu.apm
MD5 Hashes do NOT match. Expecting E5808519844051A30CF231B9805B0788, but found ba0548a23aa493d9b0ec84aa6733b09e!!!

Looking for file H:\AutoPatcher\XP\modules\NonCritical\KB945007_IE7_x86_enu.apm
MD5 Hashes do NOT match. Expecting 7CA26FBA850993FAD2100E06661B4299, but found c2419a7b465af935d7bb50bc01b7fba3!!!

Looking for file H:\AutoPatcher\XP\modules\NonCritical\KB945007_x86_enu.apm
MD5 Hashes do NOT match. Expecting C5CD535D63D9E55FC4D862714077D93E, but found 501cfdd73bc6cd15d3c4d97a87675c05!!!


Looking for file H:\AutoPatcher\XP\modules\wga\wga_xp_x86_enu.apm
MD5 Hashes do NOT match. Expecting 686C295ED7A187AAA46C9BF80F14A637, but found 48bd84e95bdd5a49f88e14e61eaea3ce!!!

Looking for file H:\AutoPatcher\XP\modules\AddOns\flashplayer_notIE_x86_enu.apm
MD5 Hashes do NOT match. Expecting BA7D74120E5A5DA2632C7E6F0064662C, but found adee9bb1fc74cf82bd79a4981815bd52!!!

 Erik Ramey, on Dec 13 2007, 10:16 AM, said:

Six hours after your post I still get the same checksum error. Is there any chance that you did not update the script on the server?

 Rudy, on Dec 13 2007, 03:41 PM, said:

It already does this if it finds any file which does not match the expected checksum.

 Cyrus, on Dec 14 2007, 09:37 AM, said:

i though so - but it does not seem to work, because it had to delete them manually, before it worked