This will fix Unmodified content Error Also
Ok, here's the deal. I am guessing that the patch fails installation of certain upgrades due to some bad synchronization between its extraction to a temp directory and its installation.
I installed BF2 as usual from my DVD.
To be sure what I did I used md5summer from
and the client 1.0 md5 file. Just copy that entire hash codes from wiki to a text file. Run md5summer, browse to the BF2 install directory and click verify in md5summer. It will ask you for the verification file. Provide the one you created by copying off from wiki.
~100% times your original client installation will be good.
Now onto the patch.
Get 2 copies of it
1] the zip file from http://forum.eagames.co.uk/viewtopic.php?t=3409
direct link -http://www.ea-zone.dk/CS/BF2_v1.02_Patch.zip
2] the official installation file from EA/BF2 homepage.
Now that you have those two, extract out the zip file contents into your BF2 installation folder at its root level.
Run the patch.exe file. (run it via cmd and not directly click it or else you wont see where it fails)
Once it exits (completed or failed) do another checksum, but this time use client 1.02 md5 hashes from wiki (same way as before)
md5summer will tell you whats ****ed up.
If all goes good, you will have the game patched.
if not, keep running the patch.exe file till either md5summer says all good, or patch.exe file says nothing more to modify.
patch.exe will fail 1/2 way through giving the famous patch.rtp failed message. But if you repeat the process 5-6 times, it will finally succeed.
Though its success doesn't mean everything is patched. Only when md5summer says all hash codes are good, then everything is patched.
once the patch.exe says its successful, still keep running it until you see that md5summer is not reporting any reduction in its errors.
Mine initially had 42 files ****ed, but after repeated patch.exe runs it finally reduced to only 3 files not patched. Most likely for everybody its will be the 2 biggest files -
objects_client.zip
common_client.zip
Now that we see applying patch.exe makes no difference to the md5summer's report, switch to the official EA installshield patch.
Run that. That should definitely NOT fail and will pass.
Re run md5summer.
Re-patch using that.
Re run md5summer.
Keep doing it till md5summer gives all GREEN, good to go...I personally had to run this file only 2 times. and that's it.
To summarize it, all you need to do is keep running patch.exe till you see no improvement in md5summer and then keep running installshield patch till success, each time running md5summer and checking after each patching process. Note, you should check the hashes only from client 1.02 file.
Ok, here's the deal. I am guessing that the patch fails installation of certain upgrades due to some bad synchronization between its extraction to a temp directory and its installation.
I installed BF2 as usual from my DVD.
To be sure what I did I used md5summer from
and the client 1.0 md5 file. Just copy that entire hash codes from wiki to a text file. Run md5summer, browse to the BF2 install directory and click verify in md5summer. It will ask you for the verification file. Provide the one you created by copying off from wiki.
~100% times your original client installation will be good.
Now onto the patch.
Get 2 copies of it
1] the zip file from http://forum.eagames.co.uk/viewtopic.php?t=3409
direct link -http://www.ea-zone.dk/CS/BF2_v1.02_Patch.zip
2] the official installation file from EA/BF2 homepage.
Now that you have those two, extract out the zip file contents into your BF2 installation folder at its root level.
Run the patch.exe file. (run it via cmd and not directly click it or else you wont see where it fails)
Once it exits (completed or failed) do another checksum, but this time use client 1.02 md5 hashes from wiki (same way as before)
md5summer will tell you whats ****ed up.
If all goes good, you will have the game patched.
if not, keep running the patch.exe file till either md5summer says all good, or patch.exe file says nothing more to modify.
patch.exe will fail 1/2 way through giving the famous patch.rtp failed message. But if you repeat the process 5-6 times, it will finally succeed.
Though its success doesn't mean everything is patched. Only when md5summer says all hash codes are good, then everything is patched.
once the patch.exe says its successful, still keep running it until you see that md5summer is not reporting any reduction in its errors.
Mine initially had 42 files ****ed, but after repeated patch.exe runs it finally reduced to only 3 files not patched. Most likely for everybody its will be the 2 biggest files -
objects_client.zip
common_client.zip
Now that we see applying patch.exe makes no difference to the md5summer's report, switch to the official EA installshield patch.
Run that. That should definitely NOT fail and will pass.
Re run md5summer.
Re-patch using that.
Re run md5summer.
Keep doing it till md5summer gives all GREEN, good to go...I personally had to run this file only 2 times. and that's it.
To summarize it, all you need to do is keep running patch.exe till you see no improvement in md5summer and then keep running installshield patch till success, each time running md5summer and checking after each patching process. Note, you should check the hashes only from client 1.02 file.
Comment