Matrix Games Forums

Hi,
I have the following problem.

I've been playing FitE PBEM with someone; we're playing turn 42 at the moment. We use the same versions of the game (3.4.0.202) and there was no problem with this for most of the time we've been playing. However, when we were playing turn 37 and I sent it over to my opponent, he informed me that he can't load it and that there is some version compatibility problem. Apparently, TOAW displayed the following message:



We couldn't solve it, so I had to play the turn again, and sent him a new save. The same happened when we were playing turn 42.

Do you have any idea what may cause this? Could it be something with TOAW screwing up the save? Or perhaps file corrupting in email? Any ideas? Again, we checked and we have the same version.

Regards

Hi, Marjur........

First, it's only your puter thats having a problem, right? The reason I ask is that this wouldn't be a 'normal' result of ToaW in any fashion.

We'd need to know what your puter IS in order to work on this, but meanwhile I'd suggest that you save your turns better, eh?

Any chance you could load "Game Booster 3" and get a diagnostic done? This is a program by Iobit that does a good job of figuring out everything on your puter. Link: http://www.iobit.com/gamebooster.html


Kurt

http://forums.gamesquad.com/showthread. ... s-scenario

That set of posts is from an earlier version, but I assume it covers your problem??? Still need to know what your running for a puter, guy, as it looks like everything worked after Ralph's post, and I'm sure you've tried all their remedies.

Whatever, eh?

No, actually, archiving didn't solve it. I thought it did as the problem didn't appear for a while, but it soon started to reappear.

I didn't reply for a while as I needed to test a few things.

Believe it or not, it seems that the culprit is Microsoft's hotmail, which I used to send my save files. I'm not an expert on these things but something (Microsoft's servers? or perhaps little gnomes) must have changed the files somehow now and then. Anyway, this is the only explanation as I changed my account to Google some time ago and the problem hasn't reappeared ever since.

Of course, it will need some further testing.