Looking for a solution to this DR1 problem...

[sonicintuition]

Hi folks.

I was able to get 0.6.1 DR1 compiled flawlessly - huzzah! All happy and shiznit till I went to run the stupid thing.

World.exe -

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Shawn>cd C:\EQEMU SERVER

C:\EQEMU SERVER>world
Got signal 2
[Status] Starting Log: logs/eqemu_world_3632.log
[Status] CURRENT_WORLD_VERSION:EQEMu 0.6.1-DR1
[Status] Loading opcodes..
[Error] Starting Log: logs/eqemu_error_world_3632.log
[Error] Function Attach Error: Error #127

[Error] LoadEMuShareMemDLL::Load() failed to attach a function.
Unable to load EMuShareMem for opcodes.
[Error] Loading opcodes failed. I cant live like this!

Sure looks like I'm missing a file - but opcodes.conf is in the directory. So what exactly else is needed to get the server running? Devs? Anyone else who's got a working copy? Help please!!

Regards,
SI

[Sarepean]

Send me a zip of the compiled 6.1DR1 and I'll see if I can get it working or figure out why it's not.

It looks like you might be missing the emusharemem.dll or something like that.


EDIT:: Sarepeansky@yahoo.com if you send me a copy of the zip. Thanks.

[sonicintuition]

I have emusharemem.dll in the directory as well ...but sure I'll send you a copy of dr1 anyway.

Regards,
SI

[Sarepean]

Thanks. I was about to head out the door, but I'll get to tinkering with all of this as soon as I get back. =)

[cavedude]

I had that same problem when dynamic opcodes first hit CVS for 6.0DR3. My solution was and still is to use .NET 2003 to compile. For whatever reason VS 6.0 compiles always give me that error. Also, .NET compiles the release source flawlessly out of the box so to say without having to editing the projects. (Perl compile fails with the same errors as VS 6.0)

[RangerDown]

FYI, all official Windows compiles use VS .NET (2k3 I believe) just as you do. If you are still using VS 6.0, you might want to consider compiling with .NET 2k3 -- as of last I heard, this is what the devs consider "official" and they probably won't go out of their way to keep backward compatibility with older Visual Studio versions.