eddie wrote:To fix just reinstall BF2 and PR. Fixed all my problems but the handshaking, which is easily sorted by joining another server, then quitting and joining the original server.
Is that the one you mean Kilroy? couldn't find any other.... Won't work for me, lost my bf2 CD and am running off bf2 SF CD
"Where to mate- "Visit me on an Aussie Pr server (GSA BigD, Game Arena)- im [COLOR="DarkRed"]0.CHUGGA.CHUGGA.0[/COLOR]
I did not see this error in the 1st post, but lots of people have been getting it. It seems to be coming from the only DLs availible.
I went to Moddb, filefront and TGF. All DLs are same and consistant with 'MD5TOOL MISMATCH' (mine is) "...\levels\7gates\client.zip (len=2048 )". This is the one of the errors similar to the others that has come up on my machine.
I know that this is not an error coming out of my machine. This PC has been tested for months, 99.9% of bugs are gone. My PC was having the greatest time with .85, never had one error. Now I can only play four maps. I get random kick on MD5TOOL MISMATCH and C2D on level changes effected by 'corrupted file' from ALL DL Locations
[not tried GB as it was going to take two hours to DL]
This comp was error checked over a period of a month, way before PR ever had this problem on my PC. I've ran many error check test and bench suites, so I know my PC is cool. It plays GTA4 very well
E8400/CO-6~1.196Vcore, GA-EP45-UD3R Mainboard
HyperX 1066/3:4~5-5-5-14-7-2T,2.2V
-Liquid cooled- eVGA 9600GT OC'd @ 2000MHz
300GB WD SATA-XP32
1Tb Seagate SATA storage
The problem is with Punkbuster, AGAIN! If this is going to be the reoccurring issue with Punkbuster I'll just have to ditch PB games. I don't like having to go through these complications just for updating cheat detection systems that does not inform the pubilc of its serves very well and adds more issues than it fixes! I'm understanding most of these errors are occuring from Servers not updating properly, as I the client have the updates. However, this has no connection to the reason the Level install is corrupted! /rant
Last edited by pdxmark on 2009-07-27 22:26, edited 2 times in total.
I have reasons to complain, is it PB or is it EA, I do not know...but someone have to get his behind toasted.
Why are we consumers, who pay money for our games, supposed to take our computers apart and reprogram others errors?
Only to play?
Games that we have bought?
i was getting the md5 tool mismatch error ever sinse the patch came out i finally uninstalled everything BF2 related then reinstalled bf2,bf2 patch 1.41,pr core,pr levels, pr patch 0860 then retro pack. Seems to have fixed it all i havent received the error again so far only been in couple maps but never got the error thank god
I still have yet to see an answer to why one server kicks for MD5 mismatch and all other servers work fine. I am suddenly getting MD5 mismatch on CHICAGO INS server only and nothing is helping.
So I jumped onto Google and did some Thread hunting and found many players that have had the same issue. Unfortunately, there didn't seem to be any standardised resolution to the problem from any source, including the PR site.
I took this troubleshooting approach using a different computer (#2):
1) Installed BF2 + 1.41 patch
2) Installed pr_0856_core_setup.exe + pr_0856_levels_setup.exe
3) Installed pr_0860_patch_setup.exe + pr_0860_retro_mappack1_final_setup.exe
4) Downloaded pbsetup.exe and used it to bring PB up-to-date
5) Now the #2 should be the same as the problem system (#1)
6) Joined several random servers and played without any issues using #2
7) Started to compare file sizes and versions in the "C:\Program Files\EA GAMES\Battlefield 2\mods\bf2" folders
8 ) #1 'Shaders_client.zip' = 188,781 bytes and #2 'Shaders_client.zip' = 223,590 bytes - hmmmmmmm, I thought....
9) noticed #1 has an extra file called 'Shaders_client.zip-vanilla' = 223,590 bytes - could it be this easy?
10) #1 re-named suspect 'shaders_client.zip' to 'shaders_client.zip-problem'
11) #1 re-named 'Shaders_client.zip-vanilla' to "Shaders_client.zip'
12) #1 - started PR and played un-interupted for 3+ GLORIOUS hours on Kashan
PROBLEM SOLVED - hope this may actually help someone else...
SpaceTuna wrote:I just installed PR 87, got into a game and got this.
I've never had this problem before.
I'm running Win 7RC 64bit, 4gigs RAM, 8800 GT
After about 15 minutes in a server, I got the same error. WHYYYY. Why couldn't Dice just leave the game alone and forget about it? Now we have to suffer from alt-tab problems, md5sum mismatches, and other weird issues.
Chances are the server you are trying to join didn't update their md5 files. Though, you could confirm that you actually have that file in your root battlefield 2 folder.
[R-DEV]AncientMan wrote:Chances are the server you are trying to join didn't update their md5 files. Though, you could confirm that you actually have that file in your root battlefield 2 folder.
Well what do you know. It wasn't! I went to the 1.41 folder and copied it over...maybe it will work now
Also, it doesn't make sense if your 1.41 folder has the file but 1.5 does not. How did you install everything?
I actually did a full, fresh install, and in my efforts to try and fix my alt-tab problem, I patched BF2 1.0 straight to 1.5. That didn't work so I went and installed the 1.41 patch, then installed the 1.5 patch again. Everything is working fine now, although the alt-tab problem still remains.
I get MD5Tool Mismatch something about kozelsk/client.zip
Figured out that the problem for me is caused by Skype. Whenever Skype is running i keep getting this error every 20 min or so.
Infact today i was playing, and i opened Skype and the second Skype opened it gave me that error.
I did some testing turning off skype, i ran smoothly all day yesterday. Then i opened skype and in 20 min i was kicked.
Hope this helps, if noone has not noticed this yet...
Last edited by malo on 2009-09-05 17:57, edited 1 time in total.
I get booted with an MD5 mismatch continually, always on coredll.dll. I definitely haven't tampered with it before, and this only happens after BF2's 1.5 patch. Has anyone else experienced this?
Feels like the best option is to install BF2 on a different machine and then copy over the DLL. (It'll save me installing at least 1.5 again, although I still need to patch it to 1.41. *Sigh*). Since that will waste a lot of time, maybe someone could (if it's legal, of course) share their own pristine 1.5 coredll.dll?
Last edited by Picklesworth on 2009-09-10 03:48, edited 1 time in total.
