Xref: utzoo comp.sys.mac.system:5313 comp.sys.mac.comm:3694
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!tut.cis.ohio-state.edu!rutgers!njin!princeton!phoenix.Princeton.EDU
From: bskendig@phoenix.Princeton.EDU (Brian Kendig)
Newsgroups: comp.sys.mac.system,comp.sys.mac.comm
Subject: The `correct' way to use MacTCP with System 7.0
Message-ID: <9549@idunno.Princeton.EDU>
Date: 14 May 91 21:13:11 GMT
Sender: news@idunno.Princeton.EDU
Followup-To: comp.sys.mac.system
Organization: Starfleet Academy: Princeton University
Lines: 22

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?"