Can someone help with the code?

[Zafar]

Anyone who would be willing to tell me exactly where and what files need to be modified to make EQEmu 0.3.10 look in to a specific directory without relying being restricted to one directory? The reason why I am asking this, is for two reasons.

1) I would like to run EQEmu as a XP Service (I am now, but it is still very unstable, unpredictible and goofy.) And having it know where the files are, would make my life easier rather than having it acting the way it is.

2) Should I ever wish to execute from the command line, no matter where -- it would automatically say, ok, he's running it from here, we know to look at c:\eqemusrc, etc..

I just need to, or should only need to know what files contain this information and I should be OK there. Thank you in advance for your help. (God, after being up for over 30+ hours, you'd think all would be good by now. NOT!) :-p

[Zafar]

After being up all that time and trying to figure that out, only to not be lucky should have said, "Go to bed." Well, been up for a few hours already, after successfully making the changes that I needed -- which did make life easier, but to get it to run as a NT server (XP Service technically, since I am using Windows XP Professional.), is not going very well. It loads, and gives some sort of a timed out failure, shrug. Perhaps I will see if I can find some code here or there, to implement a NT Service.

And yes, I am aware that this is a very ugly task as well. I seen some code, and heard many people saying that it is extremely rough, to get something implemented as a "NT Service", which I have a couple of programs here that can also help loading a program as a service, and code snips here that allow you to do the same thing. But the code itself, is .NET based. Sigh. This is something that would probably be nice, or a GUI version of EQEmu -- or perhaps, a NT Service based EQEmu with a GUI login to do what you could do, see, etc. that you can now.

[alkrun]

I actually did some work with this a while ago. A short description of what I did...

Switch all of the server projects from Executables to DLLs. I added some exported functions to initialize and cleanup each respective server.

I then wrote a master service that used a config file of its' own to figure out what DLLs to load and initialized them, how many zone servers to run etc...


It was working fairly well, but at the time the server sourcecode was at a fairly unstable state and when a new release came out I just tossed the changes with the intention of adding them again at a later date.

I wasn't using .NET but a good old Win32 ServiceMain etc... in theory you could go with the convert-them-to-dlls option and load them in a C# Windows Service with calls to the unmanaged DLLs... that could be interesting. You could also get some nifty features with the Service-oriented features of the .NET Framework, easy access to the event logs etc...