deltablues
Chieftain
- Joined
- May 5, 2002
- Messages
- 4
I struggled with this one for a couple days before I figured it out....
When I originally loaded Civ3 up, I installed the main civilization directory onto my desktop.
This wasn't a problem because prior to loading up 1.21f, I used to be able to manually move the civilization main directory wherever I wanted it without any ill effects.
At the time of trying to load up the 1.21f patch my civilization directory was located in c:\program files, but I noticed that when I installed 1.21f that it came up by default asking if I wanted to load the patch to my old "desktop" location. I just pointed the 1.21f installation to my c:\program files location and the install appeared to go fine.
But I noticed after the installation that I kept getting abnormal termination errors everytime I tried to start up civ3edit.exe , which wasn't happening before.
I went round and round loading up and trying all the cracked, fixed, patched, and original versions of civ3edit.exe only to get the same error over and over again.
Just when I was about to give up and just reload the original non-1.21f version, I tried moving the civilization directory back to my desktop and Miraculously civ3edit.exe started working again !!! I tried moving it back to the c:\program files directory and it gave me the same abnormal termination error, so I knew that's what fixed it.
I haven't investigated this any further, but I'm guessing that whoever wrote this latest 1.21f patch rememberd to give you the option to change the installation directory, but they didn't make the installation script smart enough to correct registry entries and such for the new installation location.
This could also probably be solved if the developers just made their install scripts smart enough to search for your civ3 installation directory on its own and then do all the proper clean up automatically.
It's a fun game, but I agree with the rest of the posters here about the fact that firaxis developers code in a very amaturish way which doesn't appear to include any error checking. This is the kind of BS you might expect in an alpha or early beta program, but not in a final release that you're turning loose on the entire world...
When I originally loaded Civ3 up, I installed the main civilization directory onto my desktop.
This wasn't a problem because prior to loading up 1.21f, I used to be able to manually move the civilization main directory wherever I wanted it without any ill effects.
At the time of trying to load up the 1.21f patch my civilization directory was located in c:\program files, but I noticed that when I installed 1.21f that it came up by default asking if I wanted to load the patch to my old "desktop" location. I just pointed the 1.21f installation to my c:\program files location and the install appeared to go fine.
But I noticed after the installation that I kept getting abnormal termination errors everytime I tried to start up civ3edit.exe , which wasn't happening before.
I went round and round loading up and trying all the cracked, fixed, patched, and original versions of civ3edit.exe only to get the same error over and over again.
Just when I was about to give up and just reload the original non-1.21f version, I tried moving the civilization directory back to my desktop and Miraculously civ3edit.exe started working again !!! I tried moving it back to the c:\program files directory and it gave me the same abnormal termination error, so I knew that's what fixed it.
I haven't investigated this any further, but I'm guessing that whoever wrote this latest 1.21f patch rememberd to give you the option to change the installation directory, but they didn't make the installation script smart enough to correct registry entries and such for the new installation location.
This could also probably be solved if the developers just made their install scripts smart enough to search for your civ3 installation directory on its own and then do all the proper clean up automatically.
It's a fun game, but I agree with the rest of the posters here about the fact that firaxis developers code in a very amaturish way which doesn't appear to include any error checking. This is the kind of BS you might expect in an alpha or early beta program, but not in a final release that you're turning loose on the entire world...
