MOO-cows Mailing List Archive

[Prev][Next][Index][Thread]

[mercere@netcom.ca: Re: PANIC: Caught signal 11]



------- Start of forwarded message -------
Return-Path: nop@ccs.neu.edu
X-Sender: mercere@popd.netcruiser
X-Mailer: Windows Eudora Pro Version 3.0.1 (32)
Date: Fri, 21 Mar 1997 15:24:07 PST
To: "Dr. Rob Higgins" <rhiggins@cybercorp.net>
From: Eric Mercer <mercere@netcom.ca>
Subject: Re: PANIC: Caught signal 11
Cc: moo-cows@parc.xerox.com
In-Reply-To: <Pine.LNX.3.91.970321064438.5748A-100000@cybercorp.net>
References: <Pine.LNX.3.96.970320212457.8210B-100000@avatar.worldone.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: MOO-Cows-Errors@parc.xerox.com
Precedence: bulk
X-Filter: mailagent [version 3.0 PL44] for fox@ares.mars.org
Resent-From: clue-cows <nop@nop.com>
Errors-To: clue-cows <nop@nop.com>

You might try installing the pAS9 patch, which makes the MOO a bit more
forgiving when it comes to telnet programs.  The telnet included with
Windows is notoriously sucky.  What that says about "standard Windows"
programs, is a question left to the student.   :-)

You can find that server patch at Alex Stewart's Patch Repository (he's
also the "AS" in the patch name, since he wrote it).  Try: 

  ftp://ftp.crl.com/users/ro/riche/MOO/patches/MOO-1.8.0/moo-1.8.0-pAS9.patch

At Diversity University MOO we find it especially useful for fixing
backspace problems people with lousy telnet clients typically report.
Incidentally, the 1.8.0p6 version of the server makes some changes that
were supplied by the 1.7.9 version of the pAS9 patch, and were therefore
left out of the 1.8.0 version of the pAS9 patch.  It might be that
upgrading to 1.8.0p6, which you should do anyway, will fix the particular
problem you are reporting.

Eric

At 04:39 AM 3/21/97 PST, Dr. Rob Higgins wrote:
>Another ongoing problem, when it is accepting connections,
>is that it seems to give problems to users of standard
>Windows telnet programs. It seems that the same user
>can connect ok with any MUD/MOO client, but when using
>telnet from Windows the first screen appears but the 
>connect command doesn't work. Sometimes it is a matter
>having the users turn on local echo, because they are
>just not seeing what they are typing, but in other cases
>the connection can't be made.

 ---------------------------------------------------------------
   Eric Mercer <mercere@netcom.ca>   (416) 929-7920  fax -5793
   DU Services, Manager              http://www.du.org/duSvcs
   Diversity University, Inc.	       http://www.du.org
 ---------------------------------------------------------------
=  DU is a non-profit company that develops, disseminates, and  =
=  provides training in educational internet tools, emphasizing =
=  interactive, multiuser, virtual reality worlds for schools.  = 
 ---------------------------------------------------------------
------- End of forwarded message -------


Home | Subject Index | Thread Index