[comp.protocols.appletalk] Cant get NCSA Telnet via FTP!!

dlw@hpsmtc1.HP.COM (David Williams) (12/31/87)

Can some one mail me NCSA Telnet 2.1e (the version that supports ethertalk
directly?). I've had a least 2 people inside of Hp who have access to the
outside world attempt to connect to NCSA, but the connection does not last
long enough for them to ftp the files let alone get into the distribution 
directory.  I will be cutting a Purchase order to get everything the 
usual snail way, but in the mean time I would like to be able to actually do
something with that nice card I recently installed into my Mac II here.

Any assistance would be appreciated.

dlw@hpsmtc1.HP.COM (David Williams) (01/01/88)

>Can some one mail me NCSA Telnet 2.1e (the version that supports ethertalk
>directly?). I've had a least 2 people inside of Hp who have access to the

I've got it now! Thanks to gary and it works like a champ.

--------------------------------------------------------------------------
David L. Williams
dlw@hpda
Hewlett Packard, Cupertino Ca
Software Development Technology Laboratory
Distributed Computing Environment Project
Mailstop: 47LR
"Sinanju, buddy -- the real stuff" 

crum@CS.UTAH.EDU (Gary L. Crum) (01/01/88)

David is up and running; I sent him the 2.1e bits.

Now, let's talk about extending NCSA Telnet to support the transfer of
complete Macintosh files without using an encoding program such as binhex,
packit, or stuffit.  Could (and should) "binary" mode of ftp be switchable
to meaning to transfer all three forks of a Macintosh file, say, to and from
"MacBinary" form, instead of meaning only transfer the data fork?  Is this
an appropriate forum to discuss the operation of NCSA Telnet?

Happy New Year,

Gary L. Crum
University of Utah Department of Computer Science
Salt Lake City, UT 84112-1180
Internet: crum@cs.utah.edu
BITnet: gcrum@utahcca
UUCP: utah-cs!crum

krauskpf@uxe.cso.uiuc.edu (01/03/88)

Full Macintosh files should be transferred via MacBinary, the format used
for most Mac BBS's.  An extension to the FTP standard to include 'TYPE M' 
for these types of transfers is one way to do it, the best I know of.

I encourage anyone who has the source code to work on this.
We will distribute it as soon as we can check its reliability.
Contact me if there are any problems.

Tim Krauskopf
National Center for Supercomputing Applications
timk@ncsa.uiuc.edu
(217)244-0638