🚀 go-pugleaf

 /*----------------------------------------------------------*
  * olwm for OpenWindows 3.0 and Apple Macintosh MacX 1.1.7  *
  *                                                          *
  *                     S O L U T I O N                      *
  *----------------------------------------------------------*/

 Fellow netters :

 I'm posting the solution to the problem I had getting olwm 3.0 to
 run under MacX 1.1.7.  Here's a recap of the problem :

 Problem
 =======

 I am currently unable to get the olwm for OpenWindows 3.0 to run as an
 X client under MacX 1.1.7.  I have no difficulty running olwm for release 
 2.0 of OpenWindows under MacX 1.1.7.  

 I bring up MacX on the Mac and execute a remote command to fire up the
 olwm application on my Sun server.  I am prompted that an X client is trying
 to connect to my Mac display and I "OK" the connection. The olwm client never
 appears but in the MacX command output window for the olwm X client I get
 the following message :

 olwm: Fatal X Error: BadAccess (attempt to access private resource denied)
 Perhaps there is another window manager running?

 I know there is no other window manager running and am lost as to the cause
 of this problem.

 The remote command that I execute is (this is one continuous command) :

 setenv DISPLAY "my mac internet address:0.3";
 setenv LD_LIBRARY_PATH /usr/openwin3.0/lib;
 setenv OPENWINHOME /usr/openwin3.0;
 $OPENWINHOME/bin/olwm -3 &

 This same command works when I change the OpenWindows environment variables
 to point to OpenWindows 2.0.

 I am displaying the client on a color rooted window and this has been 
 specified in the MacX remote command window.

 I have heard of other MacX users with the same problem but I have not heard
 of anyone who has resolved it.  It is not clear whether the problem is with
 olwm v3.0 or MacX 1.1.7.

 Solution
 ========

Use olwm -single.  This should work.  The problem is that MacX
creates 2 different screens for X, the regular screen that works
like any X server, and a "rootless" screen that gives you more
Mac like windows.  MacX will not allow you to start a window
manager on the second screen.

In OWN 2.0, olwm, by default, did not try to manage every screen
available.  You had to start a copy on every screen, which was
kind of a pain.  In OWN V3, olwm by default trys to manage all
screens, and trips over the rootless screen MacX won't let it
touch.  The -single option overrides the default behavior.


 Thanks To All Netters Who Replied,

 Ross Derrod 
 Lawrence Berkeley Laboratory

 (510) 486-5813

 email address : RADerrod@lbl.gov

------------------------------------------------------

A Favorite Quote On The National Pastime             |

Baseball is 90% mental.  The other half is physical. |

Yogi Berra                                           |

------------------------------------------------------