go to www.cygwin.com and download cygwin, make sure you get autoconf, make, gcc, and tcsh, then copy the protomuck dir into the home directory created when running cygwin and follow the instructions in the install file, it should woirk as instructed, if need anymore help I can send you a tar file of an already compiled muck for cygwin
shirra_whitefur <shirra_whitefur@...> wrote:
shirra_whitefur <shirra_whitefur@...> wrote:
Yep, yet another one of us poor Windows users is at it again.
Notably, the last time I tried to get this running was several
years back, and at the time, the binary was compiled for me by a
friend.. who's helpful talents I don't have access to anymore.
Anyways..
The 'short' problem.. I can't get it working.
The 'long' problem.. I can't really get it to accept incoming
connections, and I'm darned unsure if it's actually working in the
first place. Now, I've been messing with this for about the past two
days, and have finally exhausted all the ideas I can think of.. so
I'll outline my results an' general notes on testing work...
One constant, no matter what, is that as long as I've passed any
information at all, right or wrong, about the db locations, the
response I'll get is:
'ProtoMUCK-Cygwin 2.0b7.07 now detaching from console.'
This also is all I'll get, no matter if verboseloading is specified
or not on the command line. The only differancet that I've noticed
between giving it the right information for db's and the wrong, is
that if I give it the right information.. it stays and lurks in
memory. As far as I can tell, it's not opening / attempting to
listen
to the port specified to it.. nor the default port listed by the
program / 'install' documentation.. nor the default port in the
config.h from the source code.
I've tried it on two different machines, with two different
firewalls.. and removed those firewalls completely even and tried.
I've had a friend run it on their machine.. and the only difference
was that theirs actually noticed it attempting to listen to the
ports.
It still wouldn't -notice- any connections or do anything with them,
wether or not their firewall was in place.
I've even gone as far as downloading cygwin, setting that up,
getting the sources laid out, compiling it (And kudo's, it compiles
nicely, might I add. ^_^), and running that version both under cygwin
and from windows.. same results.
For referance, all this has been done on WinXP Pro, running with
service pack 1.. and any firewall stuffs is a moot point since I
tried
this with them completely uninstalled from the system even. I've
tried connecting with raw telnet, as well as a few different muck/mud
clients, just to be sure, on each test attempt.
This would be all done using the 2.0b7.07 windows binary without
SSL
support, and the 2.0b7.07 sources. And as said, I'm really out of
ideas to try at this point. I don't have any computers to spare to
shove linux onto, and the only person I can have hosting a muck for
me
runs only windows (but isn't against installing cygwin at least), so
my last option, of trying it under linux, is not exactly really a
viable option.
Any thoughts.. suggestions.. take-you-by-the-hand-step-by-step
walkthroughs...?
- Shirra