Filefront 3060 Installer corrupt

[HalfLoaf]

Hi

Just a quick FYI.

The 3060 Installer from Filefront (AIWarSetup3060.exe) is corrupt!

You get a disk1.cab error when installing!

File hashes are:

MD5: bb0ed32bc04e4011b7ab56fcb92050ff
SHA-1: 79769f8e8494311d4f1dad9b92277eb22f78de3f

The one from Mod DB seems fine.

File hashes for that one (2010_03_01_AIWarSetup.exe) are:

MD5: 58e305538ce9c4557fec9c51258f9208
SHA-1: f9b5a59f0e6d9329e15da615ef4fb7f49808a38f

NB The file sizes are identical.

Just a bit error somewhere probably.

HTH?

[x4000]

Dangit... that's the second time they've corrupted an installer I uploaded.  It's been 6 or 7 months since the last time, but that's two times too many.  I just took them off the mirror list.  On the plus side, this time I'm pretty sure that Atomic Gamer, GamersHell, etc, all used the version direct from Amazon S3; last time the corrupt version on Filefront was the primary and went everywhere, which created a much larger problem.

Thanks for the note!

[HellishFiend]

Sad when something as "simple" as file mirroring is buried under so much fluff that they end up being bad at it.

[x4000]

And that "Hey Developers! Host your files with Filefront FTP!" thing?  I've sent them three or so emails over the last few months, going back to last August I believe, and never got any response.  Very frustrating.

[HalfLoaf]

Just as a matter of interest, I fired up a binary file compare on these to see what was what.

There are exactly 32 bytes corrupted from 0xA4029A to 0xA402B9 inclusive. The rest are OK.

The bit corruptions seem random, e.g. 0x20 to 0x25, 0x20 to 0x91 etc.

If it had just been the last or first bit of one byte at the end or the beginning of the file then maybe you could work out some sort of solution to this, but this seems like a random transmission error or subsequent file corruption somehow?

All the CRC checksums for that 32 byte block are different too so, can't offer a solution, sorry.

Creating a Quickpar PAR2 from the good file and using it to repair the corrupted file needs only a small few kB PAR2. In the days of dial-up when a 100MB d/l would have taken hours, that might have been useful, but these days of course it's just another 2 minutes from another file server on broadband! LOL

Anyway, hope this is useful to you in some way.

[x4000]

Thanks for the details! That is very interesting. It is som sort of strange issue with filedront itself, I think, given that I upload a tremendous number of files every week, but only one every few months to them, and two out of those few to them have been corrupted while none to any other site have been. It's very odd.

[RCIX]

Thanks for the details! That is very interesting. It is som sort of strange issue with filedront itself, I think, given that I upload a tremendous number of files every week, but only one every few months to them, and two out of those few to them have been corrupted while none to any other site have been. It's very odd.

Someone's on the iphone again

[x4000]

Thanks for the details! That is very interesting. It is som sort of strange issue with filedront itself, I think, given that I upload a tremendous number of files every week, but only one every few months to them, and two out of those few to them have been corrupted while none to any other site have been. It's very odd.

Someone's on the iphone again

Yeah, you called it.