Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cwjcc!tut.cis.ohio-state.edu!ucbvax!agate!violet.berkeley.edu!edmoy
From: edmoy@violet.berkeley.edu
Newsgroups: comp.sys.mac
Subject: Re: MacTCP
Message-ID: <1989Aug25.165214.6075@agate.berkeley.edu>
Date: 25 Aug 89 16:52:14 GMT
References: <698@eplrx7.UUCP>
Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44)
Organization: University of California, Berkeley
Lines: 31

In article <698@eplrx7.UUCP> leipold@eplrx7.UUCP (Walt Leipold) writes:
>I got a beta copy of MacX (Apple's X Windows implementation for the
>Mac OS) a couple of weeks ago, along with MacTCP.  As expected, it
>doesn't work "out of the box" on our system (LocalTalk, Kinetics
>gateway, and EtherNet).  To check out the network hardware, I tried
>NCSA's TelNet -- it ran flawlessly.  Then I tried the MacTCP version
>of TelNet, thinking I'd sneak up on the problem -- it didn't work.
>So my problem seems to be with MacTCP rather than with MacX.
>
>Does anybody out there have any experience with MacTCP?  Is it
>something simple I'm doing wrong?  

We've been using MacTCP for the last few months, and it works just fine.
The only problem with it is that it is a bit difficult to figure out how
to configure, with all the various options for fixed and dynamic IP addresses,
name servers, etc.  You can send me mail directly and maybe I can help
you set it up.

By the way, how did you get MacX?  It's something that I've been wanting
to test since its announcement.  I was the author of xterm for X10.4, which
is the basis for X11 xterm.  I've been doing mostly Mac stuff since X11
came out, so I haven't really even looked at it.  MacX would be a strong
motivation to get back into X.

Edward Moy				Principal Programmer - Macintosh & Unix
Workstation Support Services		Workstation Software Support Group
University of California
Berkeley, CA  94720

edmoy@violet.Berkeley.EDU
ucbvax!violet!edmoy