AutoPatcher Forum

Autopatcher file verification of latest Shockwave version 11.5.8.612 fails. Downloaded Shockwave file seems OK. This was on a completely fresh installation of Autopatcher. Problem is persistent.

On an existing installation of Autopatcher, when an older Shockwave version 11.5.7.609 is already present, the new version is ignored.
Edited by hake, 26 August 2010 - 11:52 AM.

It looks like shockwave has been updated, this is common (Cristiano may already know), it should be fixed soon...

Shockwave 11.5.8.612 (sw_lic_slim_installer.exe)
size=2025336
md5=416F25A0ED72498B96F4AD41539AFE52

Also, this is an 'Extras' script issue so the forum for this post is 'Extras', the forum description mentions Shockwave by name - for next time.

hake said:

In terms of the downloaded file the old version will be deleted from the folder and the new version will now be present in your release. The fact you have the previous version installed it should still show up in AutoPatcher as installed, at this point the .apm file hasn't changed. Btw, don't update Shockwave until the .apm file is fixed, you could install the new version (it should work) but it will appear uninstalled (black, not blue) which will only create another problem.

Start using APUP's logging feature, there will be times when the APUP screen wont provide the information needed regarding failing files. 2 easy ways to do this, run Cristiano's 'hit_this...cmd' file or, create a shortcut to APUP adding the /log switch -> apup.exe /log

You will want to put the text of the log file (unedited) in Spoiler code - [spoiler ] log file here [ /spoiler] - bringing the brackets together creates this... It may be helpful to read Log Files..., the only thing changed is we no longer use 'codebox', instead Spoiler code which I mentioned above.

in fact, i already knew that, but i really was busy trying to avoid an word that starts with the same letter than this cartoon. and that was really unpleasant

[]s

Thanks for sorting that out. It now works perfectly.