Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!cs.utexas.edu!rice!sun-spots-request
From: montanaro@crdgw1.ge.com
Newsgroups: comp.sys.sun
Subject: Re: Setting up a Sparcstation lab.
Keywords: Windows
Message-ID: <3779@brazos.Rice.edu>
Date: 6 Dec 89 13:20:55 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 14
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v8n166, Replies: v8n172 v8n192 v8n194 v8n198 v8n206 v8n211
X-Sun-Spots-Digest: Volume 8, Issue 217, message 2 of 23

Charles Hedrick writes:

   Everyone agrees that XNeWS requires more memory than current window
   systems.  But this is not a problem with SunOS.  It's not even sloppy
   coding in XNeWS.  It is an obvious implication of running software that
   implements two window systems at the same time.... The X-based
   applications from XNeWS work fine with the MIT X server ...

If the XNeWS server is run with X11ONLY set, memory consumption is
drastically reduced. (On my machine it went from 4+ MB to 2+ MB, according
to top.) SunView applications can still be run, but WINDOW_PARENT must be
set explicitly to /dev/win0. There appear to be some problems running
XView applications like filemgr if X11ONLY is set (problems displaying
property sheets, etc.).