Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!OCLCRSUN.BITNET!tlt
From: tlt@OCLCRSUN.BITNET (Tom L. Terrall)
Newsgroups: comp.windows.x
Subject: (none)
Message-ID: <8805261427.AA24716@zeus.com>
Date: 26 May 88 14:27:40 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 41

Dear Sir:

   We experienced a similar problem in getting X to run on an Apollo Network
of DN300 nodes running SR9.7.

   I believe that you have the X server running. The most likely occurance
is that xterm as started by xinit is not successfully communicating with
X server.  We, as a diagnostic tactic, ignored xinit and started X Windows
with the following script.

          X 0 tlt &
          sleep 10
          xterm -geometry +1+1 -n login  -display tom:0 &
          sleep 10
          uwm -display tom:0  -f system.uwmrc &

    This will start the X server (stipple pattern + x cursor), then start xterm
(window in upper left of screen with unix prompt) and then start the window
+ manager
(mouse buttons call forth menus). It takes X almost a minute to get going and
the whole script can take over 2 minutes.

    In order to make the script work it was necessary to use actual
name ("tom" in this instance) of node. It will not work with "unix:0" in
spite of what documentation says. It is also necessary for TCP/IP
to be running on the node(s) on which you are running. You may find it necessary
to increase the sleep time if you get a 'X server not running' error.

system.uwmrc is copy of example in man pages for uwm. Note: correct

  line     "Iconify at New Position:  f.lowericonify"

    to     "Iconify at New Position:  f.newiconify"


   Once this script is working for you I believe xinit should work.


   Good luck.

Tom Terrall - OCLC, Office of Research