[comp.windows.x] X.V11R3 on Apollos

bowbeer@APOLLO.COM (Joe Bowbeer) (02/11/89)

        You've seen the questions on comp.windows.x
                    You've ...
                      ...

                 [ drum roll ]


            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. Ken Krippner (kek@dinorah.wustl.edu) may post
something on this, too.

First of all, X.V11R3 as it comes from MIT will build and run on Apollo
workstations. Monochrome and color. sr9.7 and sr10. There are a few
stumbling blocks which I'll cover below. BTW, a ready-made SR10 R3 server
will be available through ADUS soon. This may include DN10000 support.
Official SR10 and R3 products - with DN10000 support - are coming, too.

1. Backingstore doesn't work very well on color displays.

  You'll need to use your coding pencil to fix this one.

2. Building R3 on sr9.7 nodes.

  The only stumbling block here is that cpp doesn't work in sr9.7.
  This means you can't run imake - see server/ddx/apollo/README.

  The good news is that cpp works in sr10.

3. Running R3 on sr9.7 nodes.

  The number of clients seems to be limited to about 10.

  This is a lot better in sr10. The number of open files per process has
  been raised to 128. You can run 25 or more clients - depending on your
  system's resources. The number of xterm/shells is however limited to 12.
  This limit will probably increase in future OS releases.

4. Building R3 on sr10 nodes.

  In article <17869@shemp.CS.UCLA.EDU> casey@admin.cognet.ucla.edu
  (Casey Leedom) posted a set of patches for building on sr10. I summarize:

  - util/imake.includes/Apllo.macros:
    Added _APOLLO_SR10 define

  - util/imake.includes/Imake.tmpl:
    Added "-A nansi" (ifdef _APOLLO_SR10) to *CDebugFlags

  - server/ddx/apollo/apc/Imakefile:
    Added "obj2coff apcfont.bin" step (ifdef _APOLLO_SR10)

  - server/ddx/apollo/apc/apctext.h:
    Added missing #endif.

  According to Ken Krippner, simply obj2coff'ing apcfont.bin might not
  be enough. If you don't have a pascal compiler with which to recompile
  apcfont.pas, you may also need to get a new /bin/ld. Call the Apollo
  hotline (1-800-2APOLLO) for details.

  If lib/Xaw/Load.c can't find /sys/ins/base.ins.c and /sys/ins/time.ins.c,
  copy them from server/ddx/apollo/include/sys/ins.

5. Running R3 on sr10 nodes.

  In article <17940@shemp.CS.UCLA.EDU> Casey Leedom posted some patches to
  xterm needed for sr10. Without these patches, your pseudo tty isn't your
  controlling tty, which leads to a problem if you access /dev/tty.

  In article <15672@iuvax.cs.indiana.edu> jec@iuvax.cs.indiana.edu (James
  Conley) reported a problem rlogin'ing from an Apollo.
  In article <15789@iuvax.cs.indiana.edu> sahayman@iuvax.cs.indiana.edu
  (Steve Hayman) reported a work-around. This problem will be fixed in
  sr10.2.

  In article <395@ntcsd1.UUCP> klt@ntcsd1.UUCP (Kristopher Tyra) reported
  a problem with sending/receiving large blocks (and reported to have a fix
  for it). I'm sending my own fix to xbugs. This problem will be partially
  fixed in sr10.2 and completely fixed in sr11.

I hope you Apollo users find this useful. 
I don't claim these are all the problems. 
Keep us posted.

=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
        [These opinions are my own and not necessarily those of my employer]
	Joe Bowbeer
	Apollo Computer		bowbeer@apollo.com
	(508)256-6600		{attunix,decwrl!decvax,mit-eddie}!apollo!bowbeer

-------

kek@DINORAH.WUSTL.EDU (Ken Krippner) (02/12/89)

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
    /
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~