Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!tcdcs!swift.cs.tcd.ie!brady
From: brady@swift.cs.tcd.ie
Newsgroups: comp.sys.mac.programmer
Subject: Re: MacTCP & System 7.0b4
Message-ID: <1991Mar20.094416.7839@swift.cs.tcd.ie>
Date: 20 Mar 91 09:44:16 GMT
References: <1991Mar15.233537.7831@swift.cs.tcd.ie> <1991Mar18.013625.18058@engin.umich.edu>
Organization: Computer Science Department, Trinity College Dublin
Lines: 24

In article <1991Mar18.013625.18058@engin.umich.edu>, sfalken@caen.engin.umich.edu (Steve Falkenburg) writes:
> In article <1991Mar15.233537.7831@swift.cs.tcd.ie>, brady@swift.cs.tcd.ie writes:
> 
> MacTCP _works_ under seven, and has at least since A9!
> It has to be in the System Folder, not in the Extensions folder or the
> Control Panels folder.  The problem is with end-user applications
> programs that use the Dynamic Name Resolver.  Apple shipped code that
> searches the currently blessed folder for MacTCP (by type and
> creator).  Unfortunately, it does not look in these other folders.
> The only real fix involves re-compiling all programs to work with
> the new folders, and do a PBCatSearch in the extensions folder for
> MacTCP.
> 
Steve is right! What annoys me is that I did experiment with the placement of
MacTCP in different folders for 7.0B1 and it worked fine. But I made the
mistake of believing the warning in Apple's Gift Pack documentation which
says: 'If you are using the current TCP/IP drivers (v 1.0.1 or 1.0.2), do
not upgrade to System 7b4.' It then talks about fixing incompatibilities, with
no hint of a workaround. Hey Apple, is there anyone home?
PS my workaround was to go back to Kermit.
PPS Apple's documentation is normally much better.

Mike
brady@cs.tcd.ie