Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!sdd.hp.com!spool.mu.edu!uunet!shelby!portia.stanford.edu!elaine32.stanford.edu!alee From: alee@elaine32.stanford.edu (Andrew Lee) Newsgroups: comp.protocols.appletalk Subject: Re: PC on Appletalk Message-ID: Date: 11 Feb 91 21:08:39 GMT References: <142574@tiger.oxy.edu> Sender: news@portia.Stanford.EDU (Mr News) Distribution: na Organization: AIR, Stanford University Lines: 26 alee@elaine21.stanford.edu (Andrew Lee) writes: >There seem to be a large number of freely available TCP/IP packages >that will support the LocalTalk boards for PCs, including NCSA and >KA9Q. SI PC-IP was written here at Stanford, though it's no longer ^^ SU >supported; they decided to go with Wollongong's WIN/TCP, which I'm >using right now. > Andrew Lee > alee@portia.stanford.edu It seems that my article caused some confusion. First of all, Stanford is still supporting its own Mac-IP, as far as I know. They decided, since the campus is now so heavily Mac-oriented, to drop support of SU PC-IP, and made a deal with Wollongong under which they wrote some drivers for WIN/TCP in exchange for a site license or something like that. Also, I don't remember where I found NCSA and KA9Q with LocalTalk support. (I believe I found the former at NCSA.) I do remember that both used low level drivers from the board manufacturers (Apple or TOPS), which wouldn't solve any of my problems, and that I didn't have time to figure out how to configure them properly. WIN/TCP, at least as distributed here, requires almost no effort to set up. Andrew Lee