Retry on checksum errors
BritTim
18 Jul 2008
As a long term lurker, I would just first like to take the opportunity of thanking those who bring us this invaluable tool.
One very irritating issue (at least for me) is that, periodically, a message will appear that "one or more files have checksum errors". These errors seem to disappear if I try again with a restored AutoPatcher folder.
I am wondering how difficult it would be to check files immediately on download and retry at least once if a checksum error is found.
One very irritating issue (at least for me) is that, periodically, a message will appear that "one or more files have checksum errors". These errors seem to disappear if I try again with a restored AutoPatcher folder.
I am wondering how difficult it would be to check files immediately on download and retry at least once if a checksum error is found.
chubbycheese
14 Apr 2009
I agree. this feature would help out even though the problem doesn't happen often it would still be nice to have.
Cristiano
14 Apr 2009
> periodically, a message will appear that "one or more files have checksum errors"
pal, periodically, ms replace their updates with files that have the exact same name. given so, apup will download the file anyway, but will point that isn't downloading the same file. due that message, we always investigate the reason for that and, if required, the script is updated to match with the new file. you may also notice that when this happen, the detection for the installed module will not work for the new one.
> These errors seem to disappear if I try again with a restored AutoPatcher folder.
of course. because apup will look if you have the version that was expected to, doesn't matter if there's an new version for the file or not. due that, you only will download the new version when we realize that there's an new update and fix the script. you may also notice that this issue happens more often each 2nd Tuesday of each month, that is know also Patch Tuesday (today, to be exact)
[]s
pal, periodically, ms replace their updates with files that have the exact same name. given so, apup will download the file anyway, but will point that isn't downloading the same file. due that message, we always investigate the reason for that and, if required, the script is updated to match with the new file. you may also notice that when this happen, the detection for the installed module will not work for the new one.
> These errors seem to disappear if I try again with a restored AutoPatcher folder.
of course. because apup will look if you have the version that was expected to, doesn't matter if there's an new version for the file or not. due that, you only will download the new version when we realize that there's an new update and fix the script. you may also notice that this issue happens more often each 2nd Tuesday of each month, that is know also Patch Tuesday (today, to be exact)
[]s
_def_x_
15 Apr 2009
Hi BritTim & chubbycheese...
If AutoPatcher actually hosted the files that comprise the release this would make sense, but probably 99% of every release is download from another site, and not much more than a few small 7z files are downloaded from autopatcher.com. This is why the failed verification errors will always be a part of the process - it is unavoidable at this point.
The upside, despite a few small aggravations, when all is said and done the release is available to use on another computer or use again without having to redownload, versus the options available when using MU/WU.
Mike
Quote
I am wondering how difficult it would be to check files immediately on download and retry at least once if a checksum error is found.
The upside, despite a few small aggravations, when all is said and done the release is available to use on another computer or use again without having to redownload, versus the options available when using MU/WU.
Mike
