Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!mmlai!burzio
From: burzio@mmlai.UUCP (Tony Burzio)
Newsgroups: comp.sys.hp
Subject: HP Network X Server...
Keywords: Thoughts...
Message-ID: <8@gauss.mmlai.UUCP>
Date: 7 Aug 90 04:43:06 GMT
Organization: Martin Marietta Labs, Baltimore
Lines: 40

We have been using the HP provided server offered on the
net a while back.  Pretty impressive so far.  There have,
however, been a few problems:

TurboSRX: (combined mode, 4 & 24 planes)

	- The X cursor I defined (two bit planes in color to
	  define the X logo) has an erroneous line of pixels
	  on the right hand side.

	- It is somewhat slower than the old 24 plane server.

CH: (two screens, 3 & 8 planes)

	- Sometimes when a window drops out, the titles of the mwm
	  frames are corrupted.  Visible when many frames are stacked
	  atop another, such as a line of xloads along the right-hand
	  side of the screen.  A screen refresh fixes it.

	- When you exit with ctrl-shift-reset the display text does not
	  come back up by itself.  You must didle with the HP softkeys
	  to bring up the text mode.

	- xeyes flickers.  Don't know why, because it never did before.

In all, it has worked out very well.  I am slowly getting our Sun
users to run mwm from our HPs to manage their local screens :-)
You can do this if you have a network bridge to keep babbling uVAXen off
your Ethernet link...

Now if I can fix the ksh .sh_history explosion problem.
CLUE #27:  successive ^Cs on a process that was spawning subprocesses
(popens and system calls) seems to cause the problem!  The .sh_history,
before it explodes, has many ^P, ^C, etc. entries...

*********************************************************************
Tony Burzio               * Tick tock tick tock....
Martin Marietta Labs      *
mmlai!burzio@uunet.uu.net *
*********************************************************************