Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!uunet!nimbus!rpcfod@nimbus@UUNET.UU.NET From: rpcfod@nimbus@UUNET.UU.NET Newsgroups: comp.sys.mac.apps Subject: Re: DECwindows communications with a Mac Message-ID: <134@nimbus.UUCP> Date: 23 May 91 13:24:37 GMT References: <1991Apr24.151351.16576@colorado.edu> <583@rosie.NeXT.COM> <1991May6.145423.16625@honte.uleth.ca> Sender: usenet@nimbus.UUCP Distribution: na Organization: The World Bank Lines: 31 Nntp-Posting-Host: 138.220.20.101 In article <1991May6.145423.16625@honte.uleth.ca> senetza@honte.uleth.ca (Len Senetza) writes: >hoepfner@heawk1.gsfc.nasa.gov (Patrick Hoepfner) writes: >>In order to run DECwindows, you will need to run something that understands >>DECwindows. I don't think that anything out there except DEC's own >>LanWORKS does this. > >Nope. eXodus runs them fine. I've got both on my IIci, and have gotten >both to work quite nicely. MacX is nice, cuz it's got rootless windows, >but I heard that eXodus is doing that too in the next release. > Quite right -- MacX runs DecWindows fine too -- it is "packaged" as part of Pathworks, but is really an apple product. First, I have to disappoint you a little. There have been long conversations on the subject of X over phone lines in comp.sys.mac.comm, and short of some fairly incredible kludges, nothing has shaken loose. The main barrier is lack of SLIP or PPP support in MacTCP. Is Apple listening? But that's the only barrier. DecWindows is X -- it uses its own upper layers, look-and-feel, etc. So, once you can get a SLIP link working, you should be home free with at least two products. *********************************************************************** * All opinions are my own, and do not | Robert Patt-Corner, IBRD * * necessarily represent my employer, | AppleLink PATTCORNER1 * * colleagues or family | Compuserve 76547,1660 * ***********************************************************************