Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!uunet!brunix!ajb
From: ajb@cs.brown.edu (Atul Butte)
Newsgroups: comp.sys.mac.comm
Subject: Re: New XferIt Mac FTP Client Available
Message-ID: <74187@brunix.UUCP>
Date: 1 May 91 21:12:46 GMT
References: <1991Apr30.121736.10695@ux1.cso.uiuc.edu> <1991Apr30.172718.11744@dartvax.dartmouth.edu>
Sender: news@brunix.UUCP
Reply-To: ajb@cs.brown.edu (Atul Butte)
Organization: Brown University Department of Computer Science
Lines: 27

If people are using their own dnr code, I would also like to suggest not
just looking in the System Folder for MacTCP... it would be great to also
search the application's own directory for it as well.

This way, schools blessed with having Macintoshes with only a single floppy
drive can also use MacTCP applications (i.e. use InitShare to load the
drvr code at INIT time, then put another MacTCP in the app's directory
to get the dnr resource).  Flexibility in the placement of the MacTCP
is key here: if developers can find ways around having to fit MacTCP
on a 800K startup disk, they are going to have better luck in university
clusters...

It would also be great if MacTCP developers could, if the TCP driver itself
could not be found, to load it and open it from a MacTCP file in the app's
directory... this would eliminate the need to have to put MacTCP on
startup disks or deal with InitShare...

While we're making a wish list, it would be great to have MacTCP set itself
to the current LocalTalk zone instead of having to set it and reboot
every time one moves to another LocalTalk zone.


Atul Butte
Brown University

atul@brownvm.brown.edu
ajb@cs.brown.edu