[comp.sys.mac.comm] MacTCP in two places at once OK?

owen@astro.washington.edu (06/26/91)

I have started using VersaTerm, which insists on having MacTCP in the
Control Panels folder (really -- and having an alias there is NOT enough!).
NCSA Telnet and HyperFTP both want it in the System Folder, of course.

So I put a copy in both places, and it actually seems to work, so far.
But...has anybody else tried this? Am I asking for big trouble?

Thanks
-- Russell
owen@astro.washington.edu

P.S. VersaTerm: lock the HOST file. Then VersaTerm won't stupidly archive
the numerical address of everything in the HOST file.

dorner@pequod.cso.uiuc.edu (Steve Dorner) (06/26/91)

>P.S. VersaTerm: lock the HOST file. Then VersaTerm won't stupidly archive
>the numerical address of everything in the HOST file.

Given the current state of the MacTCP resolver, it's not stupid to cache
IP addresses.  I'm not sure it's the right thing to do, but it's not stupid.
The MacTCP resolver is what is stupid (or at least darn unpleasant).

My calendar says it's the end of June; that's when our Apple reps said
MacTCP 1.1 was coming out.  Anybody heard anything lately?
--
Steve Dorner, U of Illinois Computing Services Office
Internet: s-dorner@uiuc.edu  UUCP: uunet!uiucuxc!uiuc.edu!s-dorner

dave@intercon.com (David S Saunders) (06/26/91)

In article <1991Jun25.212948.28527@milton.u.washington.edu>, 
owen@astro.washington.edu writes:

> I have started using VersaTerm, which insists on having MacTCP in the
> Control Panels folder (really -- and having an alias there is NOT enough!).
> NCSA Telnet and HyperFTP both want it in the System Folder, of course.
> 
> So I put a copy in both places, and it actually seems to work, so far.
> But...has anybody else tried this? Am I asking for big trouble?

Being that the DNR stuff doesn't seem to require that you access the active 
copy of MacTCP, it should be OK.


-=Dave

"It takes a lot to get to infinity."