Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!ames!dftsrv!palantir.gsfc.nasa.gov!rdominy
From: rdominy@palantir.gsfc.nasa.gov (Robert Dominy)
Newsgroups: comp.sys.ti.explorer
Subject: Re: X server AND MacTCP incompatibilites
Message-ID: <832@dftsrv.gsfc.nasa.gov>
Date: 8 Feb 90 20:29:17 GMT
References: <9002070910.AA22367@lri.lri.fr>
Sender: news@dftsrv.gsfc.nasa.gov
Distribution: inet
Organization: NASA Goddard Space Flight Center
Lines: 23

In article <9002070910.AA22367@lri.lri.fr> mvm@FRLRI61.BITNET writes:
> It is my understanding that the X server does not run on the 
microExplorer
> and that TI is waiting for Apple to release their X server on the mac
> (under MacOS). My question is: has anyone tried to make it run with
> alternative X servers on the mac (for example Exodus). What would be
> involved in making it work (i.e. how much work).
One problem with the Mac X server (say Exodus or MacX) and a microExplorer
X client running on the same machine is that the microExplorer seems to
be incompatible with Apple's MacTCP drivers. I suspect that this is because
both MacTCP and the uExplorer are trying to insert their own handlers for
the same protocol.

Does anyone know if TI is working on this problem? It seems logical that they
could dump their own TCP drivers and use/license the MacTCP drivers.  The 
current situation is a minor annoyance to me as I have to reboot without 
the MacTCP drivers to use the uExplorer - it will become a major problem
soon when I'll need to run Mac application that uses TCP concurrently with
uExplorer for an upcomming project.

-------------------------------
Robert Dominy
NASA Goddard Space Flight Center