Unofficial Status - md5 mismatches
mbonwick
02 Jan 2010
Hi all,
I've got the "unofficial/Unsupported Release" status. From running MD5 hash comparisions, the following show apup.exe as a mismatch (presumably they haven't been changed when APUP v1.2 came out?)
md5_checksum_for_AutoPatcher_XP_ENU
md5_checksum_for_Extras_Addon_Pack
md5_checksum_for_office2003_ENU
md5_checksum_for_Java_Addon_Pack in addition to a mismatch on apup.exe, also reports win9xnt\vbrun60sp6 as missing.
I don't seem to have hashes for Vista SP2 or Office 2007.
Thanks,
I've got the "unofficial/Unsupported Release" status. From running MD5 hash comparisions, the following show apup.exe as a mismatch (presumably they haven't been changed when APUP v1.2 came out?)
md5_checksum_for_AutoPatcher_XP_ENU
md5_checksum_for_Extras_Addon_Pack
md5_checksum_for_office2003_ENU
md5_checksum_for_Java_Addon_Pack in addition to a mismatch on apup.exe, also reports win9xnt\vbrun60sp6 as missing.
I don't seem to have hashes for Vista SP2 or Office 2007.
Thanks,
_def_x_
02 Jan 2010
You are correct, the md5 files were created before 1.2 was released so no problem here. Also, the "\win9xnt" folder was removed
after the md5 for java was created so again no problem here (in terms of your Unofficial status).
Do you have all the releases in one "\modules" folder, if so, run AutoPatcher Click About - Click Release Info, and look to see
what release is False in the Official status header. I have all the releases you mention except Office 03 and 07, and they are
all Official. You may want to run APUP and update your releases to see if this will help.
Also, I have yet to see dkdk_it put an md5 in the Vista release.
after the md5 for java was created so again no problem here (in terms of your Unofficial status).
Do you have all the releases in one "\modules" folder, if so, run AutoPatcher Click About - Click Release Info, and look to see
what release is False in the Official status header. I have all the releases you mention except Office 03 and 07, and they are
all Official. You may want to run APUP and update your releases to see if this will help.
Also, I have yet to see dkdk_it put an md5 in the Vista release.
mbonwick
02 Jan 2010
All the releases show as Official, so I assume it must just be apup.exe and win9xnt causing the problems?
_def_x_
02 Jan 2010
If the Release Info window shows all the "Titles" in the package as Official (including AutoPatcher Engine) but AutoPatcher is showing
Unofficial/Unsupported Release when you fire it up - you must have some stray files in the "\modules" folder that are not part of any
release (did you wait any prolonged period of time between updates causing you to miss a cleanup routine) therefore causing the
Unofficial warning - you need to find the strays.
You didn't say if all the releases are in the same "\modules" folder? If they are it will be difficult finding the extra files unless someone has
the same releases combined like you, and can generate an md5 of their "\modules" folder, and then you run it against your releases.
To your point about the difference in apup.exe files and the missing "\win9xnt" folder, this won't have an effect on the Official status because
the .rti file that gets generated (that labels a release Official or Unofficial) is created from a scan of the "\modules" folder, except for the .rti
generated for AutoPatcher (apengine.rti) that verifies autopatcher.exe - you did say everything in the Release Info window is "True", right?
BTW, this doesn't really qualify as a bug report so please determine what release is giving you problems and post in the appropriate forum
or in "General Support" if you are unsure - this isn't a problem with AutoPatcher or APUP.
Unofficial/Unsupported Release when you fire it up - you must have some stray files in the "\modules" folder that are not part of any
release (did you wait any prolonged period of time between updates causing you to miss a cleanup routine) therefore causing the
Unofficial warning - you need to find the strays.
You didn't say if all the releases are in the same "\modules" folder? If they are it will be difficult finding the extra files unless someone has
the same releases combined like you, and can generate an md5 of their "\modules" folder, and then you run it against your releases.
To your point about the difference in apup.exe files and the missing "\win9xnt" folder, this won't have an effect on the Official status because
the .rti file that gets generated (that labels a release Official or Unofficial) is created from a scan of the "\modules" folder, except for the .rti
generated for AutoPatcher (apengine.rti) that verifies autopatcher.exe - you did say everything in the Release Info window is "True", right?
BTW, this doesn't really qualify as a bug report so please determine what release is giving you problems and post in the appropriate forum
or in "General Support" if you are unsure - this isn't a problem with AutoPatcher or APUP.
