Please, please people, when you post links to OS files, help some of us out and post the md5 of the working file. Downloaded 323 three times yesterday, all of them had different md5 hashes, and no way to tell which was good![]()
Please, please people, when you post links to OS files, help some of us out and post the md5 of the working file. Downloaded 323 three times yesterday, all of them had different md5 hashes, and no way to tell which was good![]()
The problem might have been on my end and not the upload themselves.
Any md5 generated on a file will be the same for another user downloading the file on their end, but if the integrity of the downloaded file is compromised, the md5 will not be the same for both files. Turns out I had one installer corrupted; five of the os files were no good, and of course that's the one I had used first
Edit: I'm sorry if I made it seem like it was a fault of the uploader; there are a number of problems between here and there that can affect the files.
Last edited by AngelDamien; 10-22-2009 at 07:24 AM.
Basically providing a md5 hash with the uploads ensures downloaders can check to make sure the file they downloaded is good. It's especially useful in situations where you could be making yourself a nice paperweight with a bad file :P
ANd, if anyone is interested: 464fb1ac76a6f33b49d0ee570810ad55 *9530AMEA_PBr5_1_.0.0_rel501_PL4.2.0.126_A5.0.0.32 3(2).exe
Valid MD5 for .323
If anyone is interested a good, open-source program: http://www.md5summer.org/download.html
Last edited by AngelDamien; 10-22-2009 at 09:24 AM.
This is exactly the problem why people won't create a checksum of the file. The idea is good, but insuring someone will actually create a checksum is extremely unlikely in my opinion. Also, I could see them getting mixed up or not posted at all when someone posts a link.
Personally, I prefer HashCheck. It integrates itself into the file properties window and calculate multiple hashes type in one file scan.