64-bit OS

[Santa]

Can anyone give me a hand with this? I am trying to run the CoEmu server which runs with 32 bit and i have read some threads with people saying you need to rebuild stuff and honestly, i have no freakin clue what im doing. Could you give me some tips?

[StarCurse]

Use the search button man.

[Kiyono]

[Santa]

Originally Posted by StarCurse

Use the search button man.

Oh no ****? What the hell does that do? I didn't know there was one. Your a dumbass you know? All I see is you being a rude cocking ***** to people. I know about the search button dipshit, I've been around here longer than you, I searched and didn't find **** thank you very much.

Originally Posted by Kiyono

Thanks dude.

[StarCurse]

WOW, what a douche, and no, you have not been here longer than I have.

[raidenx123]

Join Date: Sep 2007

Yes he has, and its hard to search things like that because it blocks all words equal to or under 3 letters...

[Santa]

Originally Posted by raidenx123

Yes he has, and its hard to search things like that because it blocks all words equal to or under 3 letters...

Yeah I searched many different things. i did 64-bit first and found nothing

[ApparitionX]

u guys quit fighting who cares who joined first

[_Tequila_]

I love how the person who posted the fix doesn't understand why it fixes the problem. The issue at hand is that when .NET is compiled, it is compiled to a byte code, not an actual "executable". Then, when you run the executable your byte-code is JIT-compiled into actual native code. The code produced actually will depend on whether your running a 64-bit platform, or a 32-bit platform allowing a .net executable to run on either without changes to the executable itself (i.e. recompiling for different platforms). The problem is libeay32.dll (a native dll file) is a 32-bit file, and the person trying to use it is running a 64-bit OS, so naturally .NET will try to run your executable under 64-bit mode, and then when it tries to a load a 32-bit dll, it fails as it doesn't understand the "format" so to speak. You can force-build a .NET executable as 32-bit (meaning it'll always be run at 32-bit, even on a 64-bit platform) which should be the true fix to your problem.

Though I doubt you cared.

[LetterX]

Originally Posted by _Tequila_

You can force-build a .NET executable as 32-bit (meaning it'll always be run at 32-bit, even on a 64-bit platform) which should be the true fix to your problem.

Though I doubt you cared.

That is 100% true. The only problem is people tend to have Visual C# 2008 Express Edition than actual Visual Studios, and the latter has that feature disabled.