StarDestroyer.Net BBS

I bought The Battle for Middle Earth 2 when it came out, and it's been running without any problems - until yesterday. For absolutely no reason, when I went to start the game, it wouldn't load. When I go into the task manager, I of course see that the game/program is not responding, and when I go into processes to see if I can spot the proble, I clearly see that game.dat is the corrupted file: it uses 38,000K memory, +/- 500, every time. That's obviously not right. When the game finally shuts down, the error reports says that game.dat is what's causing the game not to load, confirming my original hypothesis.

I completely un-installed the game, and erased everything related to it today, twice, and each time I went to re-install it and start it, I got the game.dat error. I REALLY need help on this one. I spent 60 friggin bucks for the collectors edition, and not I can't even use it. ANY help would be greatly appreciated.

Have a trawl through the cess-pit that is the official forums. I'm very much sure I saw something saying that there is a game.dat issue.

You have patched it right?

Acidburns wrote:Have a trawl through the cess-pit that is the official forums. I'm very much sure I saw something saying that there is a game.dat issue.

You have patched it right?

I already had the 1.01 patch, and the problem occured immediately after I downloaded the 1.02 patch. What exactly is the cess-pit?

The cess-pit that is the official forums.

The 1.02 patch is out, though I believe that it may or may not patch with the problems you've got.

Official Forum page on Game.dat errors

I don't have time to read much of this, but it may help.

Acidburns wrote:The cess-pit that is the official forums.

The 1.02 patch is out, though I believe that it may or may not patch with the problems you've got.

Official Forum page on Game.dat errors

I don't have time to read much of this, but it may help.

Thanks. I'll read it when I get home from school. The odd thing is that the first time I got the game.dat error, was when I installed the 1.02 patch! Very odd indeed...