MadBirdCZ

I would not say that anyone is not willing to do this, I think the problem is more burried in the fact that although this problem is known, quite a lot of users is experiencing this sort of crash (which is extremely annoying btw.), yet it is not officialy documented and taken care about by the developpers or mentioned with this workaround in the official support database... Anyway will try the fix after getting home...

Negative, Sir. I'm in the office now and have to 'pretend' some work. However, I did call a friend who is at home and has the same problems and told him to try the above mentioned fix and he said that since renaming the file (exe) the game starts with an error immediately after launching but after the error is clicked away the game starts up and he said that so far it runs with no crashes... Will try it after I get home myself... Best Regards, Zdenek 'MBird' Cizek

Fix MY system? WTF? Well, I'm receiving this error as well and I don't really think the problem is in MY system... For some ocult reason, lockon does not use the local (OLD) version of msvcrt.dll which comes with the installation of the game and is located in the game directory. Although the application should prefer the local version of the dll it links itself tot he current version of the dll which is in the window's system32 directory. However the MS C language runtime has also one more file the msvcp60.dll. And here it becomes interesting because although lomac has both the msvcrt.dll and msvcp60.dll in it's local directory (both old outdated versions), after launching the game the exe links itself to the new msvcrt in the windows system dir but it takes the old msvcp60.dll in the same moment... I don't know why this happens, maybe it is hardcoded in the exe. My "fix" was that i took the new recent version of the msvcp60.dll from windows system32 directory, made backup of the outdated version in lockon's dir and replaced it with the new version. After doing this, lockon is using current versions of both files and the rate of msvcrt errors decreased drasticaly, however they still happen.... So this "fix" is not a wonder "cure it all" medicine but it helps a bit... Yet i strongly disagree that the problem is in MY system... Regards, Zdenek 'MBird' Cizek