🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.protocols.appletalk
Article #4119

Testing Mac Telnets on a Mac II

#4119
From: dk1z+
Date: Fri, 29 May 1987 20:21
51 lines
2818 bytes
  Having acquired a near-useless Mac II (no hard disk, color monitor, extra
memory, or Ethernet card) I decided to try out the three versions of Telnet
for the Mac that I had around. All three are the very latest releases, as far
as I can tell. Here's what I found:

Stanford:
	Finger: Screen size hardwired to small Mac size.
		   Output appears to right of actual window.

  FTP: Same screen problems. Prompt appears to the right of the screen and in
          a smaller font, but the cursor is positions right for my typing.
          Typed characters are echoed above the banner and are munged.
          Quit is very slow and appears to hang.

  Telnet: Same as before.

  General observation: Useless on a Mac II.  Screen handling is worthless.
Mouse
        does not work at all.
   
CMU:
  Telnet: Screen size hardwired.
   TFTP: Caused a task overflow on the stack.

NCSA:
  Telnet: Hangs once you get the config window up. 
              Due to the nature of our network, no connections are possible
without
                     configuring the software.
              Hardwired window size.

  Stanford's stuff is broken down into two applications, one for Telnet and
one for FTP. This drives me bananas, particularly as the FTP application does
not support the Apple menu and I forgot the name of the file that I wanted to
transfer. It also writes directly to the screen, overwriting everything,
including dialog boxes. Both FTP and Telnet return to the finder on any
error, such as not being able to connect to the foreign host. A new version
that combines the two applications is supposedly in the works.

  NCSA seems to be a lot more robust. Currently it needs a host file or an IP
address, but work is in progress for domain name server support. Gaige has
been quite prompt in his dealing with errors, complaints, and comments. The
only thing that I really have against this version of Telnet is that we'll
never be able to get source code. Into each life a little rain must fall. I
just got a mail message from Gaige explaining why the configuration failed,
so that is basically taken care of.

  Who knows what is going to happen when Michigan gets their drivers out ....

-David Kovar
Technical Details
Message-ID: <wUjSrDy00WA10BU0hn@andrew.cmu.edu>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watmath!clyde!rutgers!ames!ucbcad!ucbvax!ANDREW.CMU.EDU!dk1z+

Show Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watmath!clyde!rutgers!ames!ucbcad!ucbvax!ANDREW.CMU.EDU!dk1z+
From: dk1z+@ANDREW.CMU.EDU.UUCP
Newsgroups: comp.protocols.appletalk
Subject: Testing Mac Telnets on a Mac II
Message-ID: <wUjSrDy00WA10BU0hn@andrew.cmu.edu>
Date: Fri, 29-May-87 16:21:35 EDT
Article-I.D.: andrew.wUjSrDy00WA10BU0hn
Posted: Fri May 29 16:21:35 1987
Date-Received: Sat, 30-May-87 10:59:46 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 51