Page 1 of 1

game.dll - Bad Image

PostPosted: Sat Feb 01, 2014 7:50 pm
by Travynn
Hey there. I used to use Portal for a server about a year ago, I forgot which, and a friend wanted me to join him on the new Origins/Genesis server. That said, I'm running into a new issue here, through following the steps I've seen.

The error reads as follows:

"game.dll - Bad Image

C:\Windows\system23\DINPUT.dll is either not designed to run on windows or it contains an error. Try installing the program afain using the original installation media or contact your system administrator or the software vendor for support."

Thus far, I have done the following-

1. Installed DAoC, patched it fully.
2. Installed the Origins/Genesis patch.
3. Installed the Genesis Launcher (does not work currently for known issues, hence using Portal).
4. Installed DAoC Portal, set directory to C;\Program Files\Electronic Arts\Dark Age of Camelot.
5. Installed .Net 4.5.1, restarted computer.
6. Downloaded all Windows updates (aside from Office updates and other such non-necessary updates). Restarted computer.

And now I'm kind of at a loss. I would dearly love to play this lovely old game from so long ago. Any help would be appreciated.

Re: game.dll - Bad Image

PostPosted: Sat Feb 01, 2014 10:11 pm
by Argo
now you need the game.dll 1.109 and that one you copy over the other one and ready you are

Re: game.dll - Bad Image

PostPosted: Sat Feb 01, 2014 11:32 pm
by Travynn
I tried downloading the 1.109 game.dll manually from this link:
http://www.mediafire.com/download/763i3 ... 109dll.zip

After copying it over my game.dll in my Dark Age of Camelot folder, it still did not run. However, now it appears no error message comes up at all.

Also, I have been running DAoC Portal in Administrator mode as well.

Re: game.dll - Bad Image

PostPosted: Sun Feb 02, 2014 7:28 am
by Travynn
Okay, update on my issue. I know that it's not ideal for anyone else coming into this with the issue, but a reformat fixed my issue. I was able to log in no problem at all. Thanks for the quick response though, I hope this brought to light a possible fix!