Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!ucsd!rutgers!apple!bloom-beacon!DINORAH.WUSTL.EDU!kek
From: kek@DINORAH.WUSTL.EDU (Ken Krippner)
Newsgroups: comp.windows.x
Subject: X.V11R3 on Apollos
Message-ID: <8902112246.AA06341@dinorah.wustl.edu>
Date: 11 Feb 89 22:46:21 GMT
References: <8902101826.AA08376@apollo.UUCP>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 35

JB writes:
>           Now you get some ANSWERS!
>---------
>
>I couldn't resist. Recent postings have been full of problem reports and
>questions about building and running X.V11R3 on Apollos. I will try to
>straighten things out. ...

Having spoken to JB by phone just prior (or during?) the preparation
of the above reference, I am unable to add anything substantial.  Thanks,
Joe, for summarizing.

To emphasize the number of client issue, I had 26 xterms going at one
point and at another I had 37 xclocks all without complaints or
plumbing problems {broken pipes}:-)

The backing store is really neat and does a nice job for a few times
but if you click the uwm menu over a window a dozen times, count on
abnormal behavior, once I had to do the red-button reboot.  Anyone
have ideas about that?

If there are Apollo uses lacking the Casey fixes, Id be glad to send
them directly; just ask.


Ken
	{uunet...}!wucs1!dinorah!kek	or
	wucs1.wustl.edu!dinorah!kek	or
	kek@dinorah.wustl.edu		or
	314-362-2950
    \~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~	
    /	X-wife -- see X-widow
    \	X-widow -- spouse (often neglected) of an Xprogrammer
    /
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~