🚀 go-pugleaf

I can't resist a flame...


/* Written  4:22 pm  Dec 12, 1989 by unocc07@zeus.unl.edu in zaphod:comp.protocols.appletalk */

(** mild flamage ahead **)

I have got to admit at this point that NCSA Telnet for the PC is very very
good (I'm using it now, so yes I know who my gateway and nameserver are :-), 
but their port to the Mac is just that: a PC program running on the Mac.  The
error messages are much less than helpful, the whole thing with the 
"Connections" menu seems counter to the standard Macintosh Interface, and the
thing never puts up a watch cursor when it's "busy" besides. :-)

(** flame (to NCSA at least) off. **)

So... does anyone have any suggestions for getting NCSA Telnet working with
a Kinetics Etherport SE?  I've been playing with various options, etc, for
over a week now, and I'm getting pretty fed up with it.  Maybe I'm doing 
everything fine and the stupid Etherport is just plain bad?  I don't know...
But I just wanted to check to see if anyone else has had these types of 
problems, and if so, how were they resolved?

In fact, I even tried to get MacTCP (and the MacTCP version of NCSA Telnet,
which again, works fine with LocalTalk cabling and the FastPath) to work
with the ethercard, but to no avail.  (And speaking of flames, I can
hardly beleive that Apple put their name on MacTCP!  The setup is VERY 
un-Mac-like.  Just to give my mac an IP number I had to dig out my HP-28S, 
convert numbers to binary, append them, and then convert back to decimal so I 
could type them into the "3 Mystical Class-B Subnet Text Fields".  Argh!)

Thanks very much to anyone that might be able (and willing) to offer some
advice!

-/ Dave Caplinger /---------------------------------------------------------
 Microcomputer Specialist,   Campus Computing,   Univ. of Nebraska at Omaha
 mspecial@zeus.unl.edu       ...!uunet!unocss!dent          MSPECIAL@UNOMA1
/* End of text from zaphod:comp.protocols.appletalk */


My best guess is that the Etherport SE is set for thick Ethernet.  Do
you have any indication that the board is working and is in fact connnected
to a live network?  By the way, it is impossible to tell from the higher
levels whether the network is in fact hooked up.  All we can do is tell
you that we can't get any other computer to respond.

While I admit that the configuration of NCSA Telnet for the Macintosh is
PC-like (too many dialogs to write), the program certainly is not an
example of a PC port.  Just try changing your font to courier and use
a window larger than 50 lines like the window I am typing on right now.

FYI, the slider on the subnet diagram in MacTCP will change the numbers
for you.  They provide the "type-in" boxes for people who want to make
the job harder.

InterCon is working on several of the little Mac-niceties that you 
asked for, so you might want to try TCP/Connect.  I don't think it works
on dead networks though.

Tim Krauskopf
NCSA