The following is a description of the NCSA/BYU Telnet program... BYU has implemented a very primitive ftp client in the NCSA Telnet application for the Macintosh. This means that you can use this application to do high speed "MacBinary" transfers between Macintosh systems that are connected to the same network. You can also FTP directly from a Mac to any FTP servers (like sumex-aim at Stanford), which you can not do with the original NCSA Telnet application. There is no cost for this application, and the source code is available. Note: NCSA is not responsible for maintenance of this version, so please don't bother them with problem reports. This ftp client is implemented in the non-Mac "command and scroll" style (of older and lower life forms). We're making this version available now for others who need the outgoing ftp capability and aren't fussy about interface elegance. We haven't had time to produce documentation yet, so use the documentation provided by NCSA for now. Some minor improvements are as follows: 1. During a "telnet" session pressing the "shift" key before you press "command" F (to send the "FTP" command) supresses the UNIX "-n" parameter, so you can use it to ftp to non UNIX systems. 2. Under the "Session" menu, when the "Clear Screen Enabled" item is disabled it allows overlaying plots in the graphics window. (Actually, this only disables the "form feed" character). Known problems: 1. Only one outgoing ftp session can be active at one time, but it does work okay with simultaneous Telnet sessions and incoming ftp activity. 2. The "mget" function does not handle directories properly yet. 3. Both the "mget" and "mput" functions will not prompt to verify filenames before sending. The latest version is 2.3.2 which is available for anonymous ftp from... machine ip number username password zaphod.ncsa.uiuc.edu (128.174.20.50) anonymous guest noc.byu.edu (128.187.7.2) anonymous guest On NCSA's "zaphod" system it's in the "NCSA_Telnet/contributions directory. On BYU's "noc" system it's in the "pub" directory. We're open to suggestions and problem reports at the email addresses below. This is not a commitment to provide maintenance support, and since we're busy we might not be able to respond promptly but we try. Regards, Jim Logan bitnet: loganj@byuvax.bitnet internet: loganj@yvax.byu.edu