Path: utzoo!attcan!uunet!nih-csl!lhc!adm!cmcl2!yale!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!sdd.hp.com!ucsd!ucbvax!ucdavis!csusac!csuchico.edu!robin From: robin@csuchico.edu (Robin Goldstone) Newsgroups: comp.sys.mac.comm Subject: Re: MacIP Message-ID: <1990Sep27.151126.1081@ecst.csuchico.edu> Date: 27 Sep 90 15:11:26 GMT References: <1990Sep3.224339.19176@monu6.cc.monash.edu.au> <1990Sep26.173357.6582@morrow.stanford.edu> <4203@spdcc.SPDCC.COM> Sender: news@ecst.csuchico.edu (USENET) Reply-To: robin@cscihp.UUCP (Robin Goldstone) Organization: California State University, Chico Lines: 21 In article <4203@spdcc.SPDCC.COM> dyer@ursa-major.spdcc.com (Steve Dyer) writes: >In article nf0i+@andrew.cmu.edu (Norman William Franke, III) writes: >>Yes, it is easier to use. I didn't mean to imply NCSA Telnet was better, >>just that it's lest costly in many cases. But, I still think it [MacIP] needs >>work, though I use it anyways... > >Gee, I'm wondering what the matter is with it. I think the point-'n-click >FTP client is just great, especially when using it to retrieve stuff from >sumex-aim. It un-binhexes stuff automatically too! The Telnet client >seems to work OK. Maybe I'm just not picky... > > For me, the main benefit of NCSA Telnet over MacIP is the "Print Selection" option. I frequently need to do a "print screen" during a terminal session. So do most of my users. I can't do this in MacIP. (At least not in the version I have - maybe a newer version does this ?) I agree that MacIP's FTP interface is great, though. Robin Goldstone, Systems Software Specialist California State University, Chico Computing Services robin@csuchico.edu