Ralph_B
1 March 04, 16:56
Have a little problem and hope, someone has a solution.
Game loads and runs well as long I want, but every time leaving the game an going back to desktop, I get the following error message : "RallyTrophy causes an error in Kernel32.dll". It is only a minor problem, cause everything works on as usual and I can start RT without any problem again - only thing I have to do is to enable the Num-lock funktion again, because this was automatically disabled when running RT. As said not a really serios problem, but what makes me wonder is the fact, that this only happens after the game is patched with the official patch by Bugbear. :confused: Out of box game runs without this annoying message. Did several installs during last time, tried the patch from other downloadlocations - but no changes in the error-message. And I remember, that when I installed RT the very first time and then patched it, this didn't happen (have to say, that I've formated and reinstalled my HD later on).
Anyone else with this bug? Any idea, what's wrong and how to get rid of this?
Greetings,
Ralph.B :wave:
BTW: forgot to say, I am running on Windows ME - without any other problems at all.
Game loads and runs well as long I want, but every time leaving the game an going back to desktop, I get the following error message : "RallyTrophy causes an error in Kernel32.dll". It is only a minor problem, cause everything works on as usual and I can start RT without any problem again - only thing I have to do is to enable the Num-lock funktion again, because this was automatically disabled when running RT. As said not a really serios problem, but what makes me wonder is the fact, that this only happens after the game is patched with the official patch by Bugbear. :confused: Out of box game runs without this annoying message. Did several installs during last time, tried the patch from other downloadlocations - but no changes in the error-message. And I remember, that when I installed RT the very first time and then patched it, this didn't happen (have to say, that I've formated and reinstalled my HD later on).
Anyone else with this bug? Any idea, what's wrong and how to get rid of this?
Greetings,
Ralph.B :wave:
BTW: forgot to say, I am running on Windows ME - without any other problems at all.