Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!agate!violet.berkeley.edu!steve
From: steve@violet.berkeley.edu (Steve Goldfield;232HMB;3-6292;;MF62)
Newsgroups: comp.sys.mac.system
Subject: Re: The `correct' way to use MacTCP with System 7.0
Message-ID: <1991May14.232949.16950@agate.berkeley.edu>
Date: 14 May 91 23:29:49 GMT
References: <9549@idunno.Princeton.EDU>
Sender: root@agate.berkeley.edu (Charlie Root)
Organization: University of California, Berkeley
Lines: 42

In article <9549@idunno.Princeton.EDU> bskendig@phoenix.Princeton.EDU (Brian Kendig) writes:
#>I've seen a lot of confusion around here lately from people who can't
#>seem to get MacTCP to work under System 7, so here's the way I've
#>gotten it to work:
#>
#>- Put the MacTCP cdev in the System Folder proper, not in any
#>subfolder of the System Folder.  (TCP applications look in the main
#>level of the System Folder for the MacTCP cdev, so if the cdev is in
#>the Control Panels folder, they won't find it.)
#>
#>- Make an alias of the MacTCP cdev, and put the alias in the Control
#>Panels folder.  (This is so you can get to it like any normal control
#>panel.)
#>
#>Until a new release of MacTCP is, um, released, this is the only way I
#>know of to get it to work, and I've had no problems with it so far.
#>
#>     << Brian >>
#>
#>| Brian S. Kendig      \ Macintosh |   Engineering,   | bskendig             |
#>| Computer Engineering |\ Thought  |  USS Enterprise  | @phoenix.Princeton.EDU
#>| Princeton University |_\ Police  | -= NCC-1701-D =- | @PUCC.BITNET         |
#>"You gave your life to become the person you are right now.  Was it worth it?"

Your method is what NCSA recommends. However, other problems with
MacTCP are reported. Apparently, while it is running, your Apple
menu does not work properly; if you try to launch something it
just beeps. (This problem may only occur with NCSA Telnet 2.3,
and may be OK with 2.4. If so, then it is a Telnet problem and
not a MacTCP problem.) Apple (as of a demo I went to today)
is promising a new version of MacTCP in June or July. MacTCP
also does not work with virtual memory.

So, yes, it will work, but no it doesn't work perfectly.

CAVEAT!

Everything I've just written is hearsay which I get directly
from either NCSA, Apple, or the workstation support people
at UC Berkeley.

Steve Goldfield