Server requires Unmodified Content??

[ice@BuFu]

Japp - i just talked to someone at ASUS-Support Germany and he also said, that I should check my RAMs with memtest. I should let the test run through next night because it needs several hours to get reliable results, he said. I will do and we´ll see what tomorrow brings...

[KBH33]

hmmmmm interesting the problem for me disappeared after installing a patch 1.2 patch

[Kelloggs]

Hirogen whats a good memory diagnostic programme - let us know and I'll test ram first before removing the additional stick I recently added.

Cheers Kelloggs :|:

Perhaps I'll wait on Ice@BuFu mem test results - let us know Ice@BuFu what your results are :|:

[ice@BuFu]

I was supposed to take memtest from www.memtest.org

[UK.D-Hirogen]

I was supposed to take memtest from www.memtest.org

Yup thats the one, you create a bootable floppy / CDRom. One of the reasons i havent done it yet is the instructions suck and there is no support (freeware).

One thing that is starting to annoy me is EA coded for this error, they know EXACTLY what it means and what causes it, they have offered nothing to help.

As a programmer when i code for errors theres some that i know will arise, a proper try / catch block is coded for this with an appropiate message. When you code for errors you dont expect, you put stuff like 'shouldnt see this'. One BF2 error that reminds me of this is the 'Insane memory error message'. The error we get is a fully coded IN-GAME error message, not a crappy CTD popup warning.

[ice@BuFu]

One thing that is starting to annoy me is EA coded for this error, they know EXACTLY what it means and what causes it, they have offered nothing to help.

...but now we know, what that error-message means: The MD5-Checksums are not equal to those written on the server. It would be nice, if they could say in that message, which files are corrupt but hey - I knew it would be better to ask the community after the first e-mail from EA-Support arrived in my mailbox.

[UK.D-Hirogen]

...but now we know, what that error-message means: The MD5-Checksums are not equal to those written on the server. It would be nice, if they could say in that message, which files are corrupt but hey - I knew it would be better to ask the community after the first e-mail from EA-Support arrived in my mailbox.

No m8 all my md5 checksums pass.

[ODD-BALL]

No m8 all my md5 checksums pass.

Yeah, but you only have problems 5-10% of the time, do a trace route to your favorite server, and see how many devices you pass through to get somewhere, If the game is compairing your files to an md5 sum on the server, then that info has to go out across the net, 1 bad router passes 1 bad packet on your 20 hop journey and it will fail you, and give you the message. Then you reconnect, and try again and it passes. Or the game dosen't figure your sum right and sends faulty info and you fail. Maybe an ant farts and it wiggles a fiber line in China and the whole west coast loses its internet connection. Maybe the game is just buggy. Maybe it will get fixed in the next patch, but don't count on it. After cruising the support forums, we should be estatic when it works at a 90% level.

[ice@BuFu]

aehem - what can I say? I found the source for the error and it´s not EA/DICE! Memtest just started and the whole screen was red - I had to see, that one of my RAM-Modules was f*cked up at ~362 MB. :wall:
i threw it out of the system (will be changed on warranty) and installed/patched and checked: everything was green - even Objects_Client.zip. I tested to join and joined on the first sever I tried. On one side I´m happy but on the other side I´m angry about myself. I really thought my sys would be O.K. and didn´t even think about the sys causing the error. :wall: So if your MD5-Sums are corrupt - check your systems memory first! :)
I will test the other module this night and will exchange the broken RAM-module tomorrow. And m8s let me tell you one thing: BF2 with 512 MB is no fun at all! :rofl:

[UK.D-Hirogen]

aehem - what can I say? I found the source for the error and it´s not EA/DICE! Memtest just started and the whole screen was red - I had to see, that one of my RAM-Modules was f*cked up at ~362 MB. :wall:
i threw it out of the system (will be changed on warranty) and installed/patched and checked: everything was green - even Objects_Client.zip.

What do you mean at 362mb? What was the results of the test, can we get a bit more detail m8? I have 4x256mb RAM chips so it will take an age to test each individual ... how does the test work with dual channel DDR or does it just treat them as individual?

EDIT: Also m8 what was your RAM configuration? Do you have to test one chip at a time? Dual Channel doesnt work properly if theres only one chip present ... any more info would be nice m8 :)

[ice@BuFu]

It´s as easy as binding your shoelaces!
I downloaded "Pre-Compiled package for Floppy (DOS - Win)" LINK and unzipped it on my desktop. There is a readme-file in it so won´t do anything wrong. Just insert a foppy-disk and doubleklick "install.bat". Then you leave the disk in it´s drive and restart your machine (make sure, your floppy-drive is first drive to boot from) and the test will start automatically.
When something get´s red - there is an error. It works with dual-channel RAMs.
After the first test I took one module out of the computer to see which one is broken (asked the motherbord-manual before, where to use only one module) and then I had a good and a broken module.
Then I left the module that had no errors in my system an did the installing/patching.

[ODD-BALL]

yeah, memtest 86 rules! I use it on all my overclocking endevers after I rack up the speed a notch, I let mem test run overnight to make sure it clears 100%

[UK.D-Hirogen]

yeah, memtest 86 rules! I use it on all my overclocking endevers after I rack up the speed a notch, I let mem test run overnight to make sure it clears 100%

Ya but your memory is fine and you still get the error?

[GreatWhiteShark]

Hi buds,
Sorry, but.
Tooooo much to take in tonight, i'll catch up with you all tomorrow.
Ps I asked Gunny Highway to look in, in a PM. He's good, but not always around.

[LOGAN]

EDIT: LOGAN - I moved to BF2 from Nova's Joint Operations, i use to get the old multicoloured textures from time to time in that, i have only had it once in BF2 so far. Nothing i did when i was playing JO fixed it. Very annoying since my squad server and everyone elses who play's matches streams to punk buster, although punk buster will never punt / ban you for it, the ss's would not go down well with other squads. Weird though, because if it can happen and its not your fault, there will be people out there that can make it happen, and punk buster will do nothing about it.

yea i jumped the gun a little bit on that one, when i played later that night on a different server the player models were fine.

and bad RAM sounds like a good theory, my RAM has been givin me a pain the ass lately. first i had a 512 stick but then i bought a 1 gig dual channel kit (512x2) and i was going to sell that extra 512 for a little extra cash but BF2 really benefits from having the extra ram so i decided to keep it. down side is, now that ive kept the "blacksheep" 512 stick (which is infineon, my new sticks are corsair. the timings and speed are the same though), on rare occasions ill get a BSOD and the system will reboot. it doesnt happen a lot but enough to warrant concern on my part, im assuming the random reboots are related to the RAM as ive exhausted all other possible causes for random reboots; that i know of. i tried running memtest to verify my suspision but couldnt understand the (very poor) instructions on their site. ill try what Fubu said tonight or tomorrow and see if i get any errors.

It´s as easy as binding your shoelaces!
I downloaded "Pre-Compiled package for Floppy (DOS - Win)" LINK and unzipped it on my desktop. There is a readme-file in it so won´t do anything wrong. Just insert a foppy-disk and doubleklick "install.bat". Then you leave the disk in it´s drive and restart your machine (make sure, your floppy-drive is first drive to boot from) and the test will start automatically.
When something get´s red - there is an error. It works with dual-channel RAMs.
After the first test I took one module out of the computer to see which one is broken (asked the motherbord-manual before, where to use only one module) and then I had a good and a broken module.
Then I left the module that had no errors in my system an did the installing/patching.