Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!wuarchive!bcm!dimacs.rutgers.edu!aramis.rutgers.edu!paul.rutgers.edu!makmur From: makmur@paul.rutgers.edu (Hanz Makmur) Newsgroups: comp.protocols.appletalk Subject: Re: Need help with MacTCP Keywords: MacTCP Message-ID: Date: 14 Jan 91 20:00:55 GMT References: <1991Jan14.064043.3618@terminator.cc.umich.edu> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 56 To: cmclark@terminator.cc.umich.edu In article <1991Jan14.064043.3618@terminator.cc.umich.edu> cmclark@terminator.cc.umich.edu (Charles Clark) writes: > .... > > But wait! I have found a work-around. I took a floppy, put a min > macplus system on it, NCSA2.3Telnet (macTCP version), and MacTCP > version 1.0.1 (from the distribution floppy, ie never before > configured copy). I went in and clicked server, Class B, 8 bits > of subnet, entered the IP address of a nameserver and clicked OK > after having booted up on a MacPlus with it's LocalTalk connection > physically pulled. IE, there was no zone name for it to save when I > did the configuration. I then booted this floppy on a MacPlus in >two different zones and was able to run and use Telnet. Previously when > I'd done the same thing except I had used the pop-up list under > the LocalTalk icon when configuring MacTCP to choose the current >zone, > it did NOT work when I went to the other zone (as Hanz complained >about). > You are a genius..I got two responds and my question is answered. I would have never guessed of this unless I have seen the code of MacTCP. YOU ARE RIGHT !!!. IT WORKS. Now my MacTCP is zone dependent. I guess Apple hides this feature. FYI: You dont really need an unused copy of MacTCP v1.01. Simply use resedit and open a resource 'ipln' offset 30 and type 00. This will set 'whatever' zone to nozone. > This may stop working as soon as someone uses the control panel to >bring up MacTCP AND uses the zonelist pop-up AND does not click cancel on >the changes dialog when dismissing MacTCP. While AdminTCP lets you >protect the second screen of config parameters, it does not protect the zone >name. Perhaps if MacTCP was changed from type CDEV to INIT it would still >work and no one could accidentally change this; I've already spent enough >time experimenting on this to satisfy my curiosity. > Yap, this is the way to do it. simply change the type from CDEV to INIT and your worry is over. > Hope this work-around helps! > > cmc This is definitely the solution. I am glad to have so many experts or beginners on the net who are willing to help each other. Thank you. Hanz Makmur Rutgers University