Checking md5 has an error
faceless007
06 May 2010
Hello, this is my first post. First I want to thank the makers of this incredibly useful program, it's saved me many hours and makes the process of reinstalling Windows so much easier.
Anyway, I thought the developers might like to know that I get an error when checking the md5_checksum_for_AutoPatcher_XP_ENU.md5 file after downloading the Autopatcher XP SP3 x86 release, and I've tried re-downloading the pack many, many times over the last few weeks and the same error happens everytime. The problematic file is modules\Components\WindowsUpdateAgent_x86.apm
The version of the file that gets downloaded is 2127 bytes and has a Date Modified of 9/27/2009 5:35pm.
I was curious if I could find the file manually, so I looked at the download script (http://www.autopatch...20100414.script) and manually downloaded the file that was supposed to contain the .apm file (http://www.autopatch...7600.226_new.7z). I don't know if that's actually how AP works so I could be wrong about all this, but anyway, I then unzipped that file, WindowsUpdateAgent_x86.apm inside was 2134 bytes and had a Date Modified of Feb 9 2010 5:35pm. So for some reason, AP ended up downloading an older version of the file. Very odd.
Finally, I compared the 2 files. The only difference I can see is that the Sept 2009 version (which causes an md5 error) has the line:
WindowsVersion=2K,XP_X86,2K3_X86,VISTA_X86,LHSERVER_X86
And the Feb 2010 file (what AP is supposed to download) has the line
WindowsVersion=2K,XP_X86,2K3_X86,VISTA_X86,LHSERVER_X86,SEVEN_X86
I replaced the one AP downloaded with the one I manually downloaded and ran the md5, and total success.
I've tried this multiple times, sometimes with multiple packs selected and sometimes with only the XP SP3 x86 pack selected. That one file always gets an error.
Anyway, the fact that no one else seems to be reporting this leads me to think it's not a widespread problem but I don't have the slightest idea what I'm having it. Could it have something to do with the fact that I'm downloading this on a Vista x86 computer?
If you need any more info to help troubleshoot this I'm happy to provide it.
Anyway, I thought the developers might like to know that I get an error when checking the md5_checksum_for_AutoPatcher_XP_ENU.md5 file after downloading the Autopatcher XP SP3 x86 release, and I've tried re-downloading the pack many, many times over the last few weeks and the same error happens everytime. The problematic file is modules\Components\WindowsUpdateAgent_x86.apm
The version of the file that gets downloaded is 2127 bytes and has a Date Modified of 9/27/2009 5:35pm.
I was curious if I could find the file manually, so I looked at the download script (http://www.autopatch...20100414.script) and manually downloaded the file that was supposed to contain the .apm file (http://www.autopatch...7600.226_new.7z). I don't know if that's actually how AP works so I could be wrong about all this, but anyway, I then unzipped that file, WindowsUpdateAgent_x86.apm inside was 2134 bytes and had a Date Modified of Feb 9 2010 5:35pm. So for some reason, AP ended up downloading an older version of the file. Very odd.
Finally, I compared the 2 files. The only difference I can see is that the Sept 2009 version (which causes an md5 error) has the line:
WindowsVersion=2K,XP_X86,2K3_X86,VISTA_X86,LHSERVER_X86
And the Feb 2010 file (what AP is supposed to download) has the line
WindowsVersion=2K,XP_X86,2K3_X86,VISTA_X86,LHSERVER_X86,SEVEN_X86
I replaced the one AP downloaded with the one I manually downloaded and ran the md5, and total success.
I've tried this multiple times, sometimes with multiple packs selected and sometimes with only the XP SP3 x86 pack selected. That one file always gets an error.
Anyway, the fact that no one else seems to be reporting this leads me to think it's not a widespread problem but I don't have the slightest idea what I'm having it. Could it have something to do with the fact that I'm downloading this on a Vista x86 computer?
If you need any more info to help troubleshoot this I'm happy to provide it.
Cristiano
06 May 2010
> the fact that no one else seems to be reporting
this is one of the worsts things about the project: a lot of people see an problem, but just a few report it. you know, many things change given time. right now, an user has reported an missing file from an script, because ms has removed that file from their servers. without that report, we could take a long time to realize that, because we don't do download tests every single day
> Could it have something to do with the fact that I'm downloading this on a Vista x86 computer?
no. you can download the script to an OS without even run it. checking the script, the downloaded files seems to be fine, but you could be behind an webcache that has the old version. in order to check that, an download test has to be made.
i'm unsure if i will be able to check this issue today (i have an whole year of infos to add into an database in my job right now. this was an fully unexpected work, too hard and, due that, i'm just collapsing after my work). so, can take a few days to check that, but i will, don't worry
thanks
[]s
this is one of the worsts things about the project: a lot of people see an problem, but just a few report it. you know, many things change given time. right now, an user has reported an missing file from an script, because ms has removed that file from their servers. without that report, we could take a long time to realize that, because we don't do download tests every single day
> Could it have something to do with the fact that I'm downloading this on a Vista x86 computer?
no. you can download the script to an OS without even run it. checking the script, the downloaded files seems to be fine, but you could be behind an webcache that has the old version. in order to check that, an download test has to be made.
i'm unsure if i will be able to check this issue today (i have an whole year of infos to add into an database in my job right now. this was an fully unexpected work, too hard and, due that, i'm just collapsing after my work). so, can take a few days to check that, but i will, don't worry
thanks
[]s
Cristiano
07 May 2010
an partial download test was done. no issues with WindowsUpdateAgent_x86.apm, but i didn't an second run of apup to be sure.
[]s
[]s
Poonia
20 Aug 2010
Hello, this is my first post. First of all I want to thank the developers of this incredibly useful program.i am using xp sp3 and i always use apup update software to update windows,but 2-3 days back when i checked md5 sum of following file "md5_checksum_for_AutoPatcher_XP_ENU.md5" it ended with 1 file error.md5 checker software was showing 1 file error of 4KB in size.i don't know why this happened.please suggest me necessary steps to check md5 files validity.
other detais:
OS: XP SP3
Problem with: "md5_checksum_for_AutoPatcher_XP_ENU.md5"
file size:110 KB
Problem: md5 check ends with 1 error.
Edited by Poonia, 20 August 2010 - 04:38 PM.
other detais:
OS: XP SP3
Problem with: "md5_checksum_for_AutoPatcher_XP_ENU.md5"
file size:110 KB
Problem: md5 check ends with 1 error.
Edited by Poonia, 20 August 2010 - 04:38 PM.
_def_x_
20 Aug 2010
@poonia
The .md5 file is a list of files, the failing or missing file should be mentioned by name in the error report, along with the size, this information is helpful
I think the problem here is Cristiano by mistake included his apup.log file when creating the .md5, if this is your issue you can ignore the error. It simply is telling you your log is different (which is to be expected). If your issue is another file, please let us know what the file is.
The .md5 file is a list of files, the failing or missing file should be mentioned by name in the error report, along with the size, this information is helpful
I think the problem here is Cristiano by mistake included his apup.log file when creating the .md5, if this is your issue you can ignore the error. It simply is telling you your log is different (which is to be expected). If your issue is another file, please let us know what the file is.
Cristiano
20 Aug 2010
> Cristiano by mistake included his apup.log file when creating the .md5
true. .md5 file edited to remove that reference
[]s
true. .md5 file edited to remove that reference
[]s
Poonia
28 Aug 2010
gUiTaR_mIkE, on 20 August 2010 - 05:04 PM, said:
@poonia
The .md5 file is a list of files, the failing or missing file should be mentioned by name in the error report, along with the size, this information is helpful
I think the problem here is Cristiano by mistake included his apup.log file when creating the .md5, if this is your issue you can ignore the error. It simply is telling you your log is different (which is to be expected). If your issue is another file, please let us know what the file is.
The .md5 file is a list of files, the failing or missing file should be mentioned by name in the error report, along with the size, this information is helpful
I think the problem here is Cristiano by mistake included his apup.log file when creating the .md5, if this is your issue you can ignore the error. It simply is telling you your log is different (which is to be expected). If your issue is another file, please let us know what the file is.
