Here's a tool to help with checksum related problems. If you can't play with someone due to a checksum related error, then run this tool to see a dump of checksums for each file. Comparing checksums of files can help you determine which file caused the error, and possibly who is different among a group of people.
Of course for this to be useful, it helps to know which files have been modded from some original copy. To do this, it would need to know something about the original file. If FileChecksumList.txt is in the folder, then it will be read for a list of original checksums to compare with. For each file in the folder, it will get a single "*" if it is unknown (not found in FileChecksumList.txt), and it will get two "**" if the checksum differs from the original. If no difference is detected, no "*"'s will be printed.
Note: The
FileChecksumList.txt packaged with this tool contains checksums for
1.3.5 Beta 2.
If you all have the same base version, then you only really need to check lines with *'s on them, and compare those checksums. Also, here's a reminder of what files are compared that can lead to this error. Remember that some of this data is stored in Sheets.vol or Maps.vol by default. The error is generated on the final checksum listed in section 4, which is just the checksum of the checksum values in the above sections. Basically, double check the files listed in Sections 1-3, including any .vol files they may be located in.
------- [Part 1: Sheet data]
BUILDING.TXT
MINES.TXT
MORALE.TXT
SPACE.TXT
VEHICLES.TXT
WEAPONS.TXT
edentek.txt
ply_tek.txt
multitek.txt
------- [Part 2: Exe data]
Shell [whatever the loaded shell DLL is called]
Outpost2 [whatever is returned by GetModuleFileName(0)]
------- [Part 3: Script data]
scriptChecksum [the level DLL]
map [referenced by the DLL]
------- [Part 4: Summary]
checksumOfChecksums [checksum of the above checksum table]
-------