The dreaded DataIO ... TILE error has struck

[CrashnBurn]

I'm running Windows XP Home edition and version 1.29f. I've tried Gramphos's multi tool but when I try and open the offending SAV file I get Run-time error '9' Subscript out of range (it works fine on non-corrupt SAV files). When I tried to use his SAVDiag Build4.exe (to locate the offending character string) I get an Invalid Type error. I've tried to bring up the SAV games in a hex editor and search manually but I can't seem to find the offending string of characters.

Does anyone know of another way to find and correct these errors? (Or make the tools work).

Thanks.

 

[ainwood]

Post the save here.

Most likely, this is a corrupt save file, or else its from a different patch version.

 

[CrashnBurn]

But I would like to know it there's a self-service option. This happens on and off and it's more than a tad irritiating.

 

[ainwood]

But I would like to know it there's a self-service option. This happens on and off and it's more than a tad irritiating.

Well, there is no real 'self-service' option, because I am looking at the save direct to see if it is corrupted.

You say you get this reasonably frequently? If so, do you get other problems with programs on your computer? It seems like a simple file corruption problem. Have you checked your hard-drive for errors lately?

 

[CrashnBurn]

Once per month or so. Enough to be annoying but that's about it. ANy ideas on why Gramphos tool won't run? I was thinking that perhaps I had the wrong flavor of VB run times.

 

[ainwood]

Same reason, I suspect. Corrupt TILE section in the save file - subscript 9 error is when you're trying to read in too many values into an array, and I think this is what's causing the problem for Civ as well. I also get the same error with my utility programs.

 

[ainwood]

Might be a bit late, but I found and fixed the error - it has changed "TILE" to "TILM" for some reason.

Had you used Gramphos' multitool to change anything on this save?

 

[CrashnBurn]

I wasn't getting all that far with a hex editor either. How did you find it and fix it?

Thanks, by the way.
I figured I was about to mop up the planet in this one ;-)