--- In protomuck@yahoogroups.com, "R. Fitzgerald" <kalzarius@y...>
wrote:
> Yes, Protomuck always detaches from the console so that it doesn't
tie
> up the console. As for how to run it, if you run it from within
> Cygwin, you won't need to copy cygwin1.dll into the protomuck/game
> directory. However, other than the copy of that DLL file, there are
no
> benefits or drawbacks for either method of running the server.
>
> If Protomuck fails to actually start, there should be a reason for
it
> in the logs/status or logs/protomuck.err. I had similar troubles
> originally when running a recently compiled protomuck, but I was
> unfortunately unable to ever pinpoint what caused it. Out of the
blue
> it started to work.
>
> - Kalzarius

And -that- is the sort of info that is bloody important. ^_^
Now, it may be noted in the install or somesuch else, but if it
isn't.. that's on my list for suggestions of things to put there. Due
to that, now I see the problem is that it's loading on a completely
unexpected port, which didn't show when I was doing netstat or any
other utils I tried. Testing that port.. it works fine. Or so it
seems at the moment. ;) I can finally log into it. More tests
pending, buut..
Thanks. ^_^ For those wondering, it lists the ports it's opening in
the Status file.
Time to start fiddling around an' seeing how I can fix things up
some more.