🚀 go-pugleaf

In article <205@smsdpg.uu.net> rht@smsdpg.uu.net (Randy Thompson) writes:
>From article <776@oracle.oracle.com>, by omullarn@oracle.uucp (Oliver Mullarney):
>> 
>> We have been having some problems with NSCA Telnet communications software.
>> Problem is that Telnet seems to be riddled with bugs - crashes the Mac like
>> there was no tomorrow. It also does weird things to the keyboard.
>
>Interesting problem. I have been running NCSA Telnet now for about 3 months
>on a PhoneNET network and over a GatorBox with almost no problems at all.
[only the relevant parts of above are included]

We also are using NCSA Telnet 2.2 thru a GatorBox to get to a Sun (straight
LocalTalk as opposed to PhoneNet, though).  I must agree with Oliver, NCSA
Telnet seems to have some severe bugs.  Most of these seem to happen AFTER
you have closed a connection and re-opened it.  I have one particular set
of events that I can GUARANTEE will cause a System Error ID=01.  The
machines we are using are MacII's w/4+ meg of RAM.  System Software is 5.0.
The bomb occurs both with & without Multifinder and with & without any
'non-standard' INITs or CDEVs.  What I would like to see is a combination
of NCSA Telnet and Kermit, particularly the feature of Kermit that lets you
program your keys to be ANYTHING (we access an IBM mainframe through the Sun,
and need to emulate a 3270 -- when we asked NCSA how we could get the Mac's
F5-F12 keys to generate anything other than the fixed assignment NCSA Telnet
gives them, the response was "How many function keys on a VT102 ?  I count 4.")

Just my $.02 worth.

M. A. Pasek          Switching Software Development          NCR Comten, Inc.
(612) 638-7668              CNG Development                2700 N Snelling Ave.
pasek@c10sd3.StPaul.NCR.COM                                Roseville, MN  55113