Xref: utzoo comp.windows.x:16109 comp.sys.ibm.pc:40495
Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!munnari.oz.au!murtoa.cs.mu.oz.au!murdu!ucsvc!ltu!ccmk
From: CCMK@latvax8.lat.oz (Mark Kosten - Computer Centre, La Trobe Uni.)
Newsgroups: comp.windows.x,comp.sys.ibm.pc
Subject: Re: DECwindows on PCs
Message-ID: <303@latvax8.lat.oz>
Date: 21 Dec 89 17:12:59 GMT
References: <28362@amdcad.AMD.COM> <297@latvax8.lat.oz> <28447@amdcad.AMD.COM>
Organization: VAX Cluster, Computer Centre, La Trobe University
Lines: 21

In article <28447@amdcad.AMD.COM>, phil@diablo.amd.com (Phil Ngai) writes:
> In article <297@latvax8.lat.oz> CCMK@latvax8.lat.oz (Mark Kosten - Computer Centre, La Trobe Uni.) writes:
> |only uses DECnet (as part of PCSA software) and is not Xwindows.
> |The last point simply means that you run windows as supplied
> |on DEC systems, which is DECwindows.  You are only a server
> 
> What do you mean? I thought DECwindows and X were the same or a
> superset or something. Did you actually try this? Why do you say this? 

I didn't mean to imply DECwindows was not Xwindows, just that because
PC DECwindows uses DECnet you are limited to using a DEC client,
which only supplies DECwindows.  Note that an Xwindows applications
compiled for a DEC machine will happily display on the PC server
(coincidentally I just ran xclock, which proves the point).

Mark Kosten,          phone: +61 3 479-2767
Computer Centre,      ACSnet/UUCP/Bitnet: ccmk@latvax8.lat.oz
La Trobe University,  X25: 234730008 (ccmk@latrobe.edu.au)
Bundoora,
Victoria 3083
Australia