Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!intercon!amanda@mermaid.intercon.com
From: amanda@mermaid.intercon.com (Amanda Walker)
Newsgroups: comp.protocols.appletalk
Subject: Re: NCSA Telnet/Responder problem
Message-ID: <1639@intercon.com>
Date: 19 Dec 89 01:31:11 GMT
References: <215@ss01.pppl.gov@ccc.nmfecc.gov> <525@wcc.oz>
Sender: news@intercon.com
Reply-To: amanda@mermaid.intercon.com (Amanda Walker)
Lines: 18

In article <525@wcc.oz>, tom@wcc.oz (Tom Evans) writes:
> This was followed (Nov 88 - wish I'd kept copies) by the respective
> authors of NCSA Telnet and Responder exchanging postings over
> the net as they went about investigationg the problem.
> 
> Was it ever fixed? After more than a year the suspense is killing me :-)

I was one of the people who was in on that discussion.  We all kind of
scratched our heads and said, "darned if we can find the problem," and went
on to more tractable bugs.  As I remember, it only happened on the Mac Plus,
and only in certain configurations.  My guess was that it was a memory
problem of some sort, but I couldn't find any such problem.  Responder
certainly didn't seem to be eating any resources (it's really pretty
simple as INITs go...).  Until now I had't seen anyone else report it.  Sigh.

Amanda Walker
InterCon Systems Corporation
--