Xref: utzoo comp.sys.mac.system:7736 comp.sys.mac.wanted:4192 comp.sys.mac.misc:13447
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!spool.mu.edu!agate!violet.berkeley.edu!steve
From: steve@violet.berkeley.edu (Steve Goldfield;232HMB;3-6292;;MF62)
Newsgroups: comp.sys.mac.system,comp.sys.mac.wanted,comp.sys.mac.misc
Subject: Re: Telnet problems...
Message-ID: <1991Jun25.202522.19787@agate.berkeley.edu>
Date: 25 Jun 91 20:25:22 GMT
Article-I.D.: agate.1991Jun25.202522.19787
References: <1991Jun25.083813.4155@lth.se>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Organization: University of California, Berkeley
Lines: 41

In article <1991Jun25.083813.4155@lth.se> peterm@dna.lth.se (Peter M|ller) writes:
#>Hi out there!
#>
#>I'm looking for a commercial program that does the same thing as NCSA Telnet,
#>but without the disadvantages of Telnet. My main problem with Telnet is that
#>it sometimes quit immediately after start *without telling why* (it must know
#>why, otherwise it would crash, not quit, right?). Having a lot of not-so-
#>technical-users this is a major problem for me. Right now we are having a tough
#>time with what we think is a crazy bridge out there somewhere that makes all
#>our network activities sloooooooooooow (timeout-error upon printing 1 page
#>[non-complex] to a LW IINT). At this time Telnet is among the first things
#>that dies... Second problem: Telnet and System 7 - grrrr.
#>
#>So, does such a program exist?
#>Peter M|ller

Before looking for another program, I'd suggest you consider
whether there are other causes for your problems. I've been
using Telnet for a long time without seeing any of the problems
you cite. The clear implication is that there is something else
in your installation causing the problems. If so, then getting
another program may not help. The only time I've seen NCSA Telnet
quit unexpectedly and without a message is when it couldn't find
a file it needs, such as MacTCP. Usually, it prompts the user
to locate necessary files, but I'm not sure about MacTCP if you
are using a MacTCP version (the non-MacTCP versions are no longer
supported anyway--that's what NCSA told me). I assume you know
that with system 7 you have to move MacTCP to your system folder
from the control panel folder (you can put an alias in the
control panel folder if you want to access MacTCP from there).
That isn't an NCSA Telnet problem; it's a MacTCP problem. Apple
promises a new version eventually.

Also, NCSA Telnet seems to work fine with system 7, especially
version 2.4b11. I installed it on my boss' IIci and he
(definitely not a power user) hasn't had any problems.
Even 2.3 works, except that it disables the Apple menu.

Steve Goldfield
College of Engineering
UC Berkeley