If you register for free, you will be able to post threads, vote on polls and lots more. If you have problems with the registration or logging in, please contact the administrator.
OK, this is an important matter, and I know there are some knowledgeable and helpful llamas, hence why I'm posting it here as well.
Mentioned to Mark on MSN a problem I've got with my 01/02 game crashing every 12th December. It happens in my and my brother's game, we're about ten years apart in game time so it's not a save game issue.
So I've reinstalled the whole game. But now I can't even play it which threatens my participation in the llama online game at the moment...
I've got the problem outlined here from FAQ...
Q23. Getting langlib.cpp and game-config.cpp error when starting CM3.x?
A23. You need to delete the CM3_DATA environment variable, If it is win 95/98/ME then delete it from autoexec.bat, if its WinNT/2k/XP then.. Right click on my computer > properties > advanced tab > environment variables > Find the variable relating to CM3 and delete it.
I've got 3.9.60 at the moment, the problems are langlib..cpp 389 and game_config..cpp 84
Game has been reinstalled, with my massive picture file in My Documents folder waiting to be transferred across.
I'm on windows 98, so how do I delete it from autoexec.bat? Where is autoexec.bat? I'm not very technical with computers so need a walk through guide here!
Autoexec.bat is found on your root directory -"C". Easier to just go into Windows Explorer and delete it from there, but make a backup first just in case.
Just to add, you can open it with notepad, and then delete the offending entry. You can also remove the entry via start > Run > and enter msconfig in the box. Then a tab for your autoexec.bat will appear and you can edit entries from within there.
And don't doubleclick it, but instead right click on the file and select "edit" in the popup menu. Oh, and if you can't see it, maybe you should set your explorer to show hidden and system files.
<BLOCKQUOTE class="ip-ubbcode-quote"><font size="-1">quote:</font><HR>Originally posted by mkus:
Does the problem go if you patch up to .65/68 ?<HR></BLOCKQUOTE>I'm pretty sure I had this problem with 01-02 as well and it did indeed disappear with the last patch.