Newsgroups: comp.sys.mac.comm
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!m.cs.uiuc.edu!roundup.crhc.uiuc.edu!ux1.cso.uiuc.edu!klefstad
From: klefstad@ux1.cso.uiuc.edu (Sue Klefstad)
Subject: Re: Having Localtalk and Ethernet too
Message-ID: <1991Apr29.182834.23310@ux1.cso.uiuc.edu>
Keywords: localtalk local ethernet
Organization: University of Illinois at Urbana
References: <1991Apr26.204034.27688@hubcap.clemson.edu> <2491@pdxgate.UUCP>
Date: Mon, 29 Apr 1991 18:28:34 GMT
Lines: 25

gerry@eecs.cs.pdx.edu (Gerry Recktenwald) writes:

>In article <1991Apr26.204034.27688@hubcap.clemson.edu> philip@hubcap.clemson.edu (Philip L Harshman) writes:
>>We have a Mac IIci here that is tied into the campus Ethernet with an Ethertalk
>>card.  ... stuff deleted ... 
>>           However, since you have to decide between Ethertalk and
>>localtalk with the "Network" control panel, this precludes us from using our
>>local LaserWriter.  ... rest of post deleted

>....  All our Ethernet communication is with NCSA Telnet, I
>have no idea how this works with other TCP/IP communication packages.

MacTCP is a wonderfully independent beast.  But if you have to
work with EtherTalk (or one of its variants) and Localtalk,
then you'll have to flip flop the network cdevs between one and 
the other.

The EtherTalk network cdev has to be selected on startup, but after
that the Built-in (localtalk) cdev can be selected.  (Just remember
to reselect the EtherTalk cdev before shutdown so that it is selected
on the next startup.)

-- 
-
Sue Klefstad    Ill. Natural History Survey    klefstad@uiuc.edu