[comp.windows.x] olwm errors

jeanne@hfh.edu (Jeanne Li) (05/08/90)

I installed olwm on our sun 4/150 and tried to run it from my NCD16. I got a error 
message:

Base frame not passed parent window in environment. Cannot create base frame.
Process aborted.

Don't know what this means. Could someone out there help me out?
If more info is needed just e-mail.

Thank you in advance.

Jeanne Li

jeanne@hfh.edu
uunet!sharkey!hfhrv!jeanne


-- 
Jeanne Li              internet: jeanne@hfh.edu  
Systems Analyst        uucp:     {rutgers,tut,uunet}!sharkey!hfhrv!jeanne
Henry Ford Hospital    voice:    (313)-876-1344  (313)-876-1428
Detroit MI 48202       FAX:      (313)-875-0315

raja@bombay.cps.msu.EDU (Narayan S. Raja) (05/09/90)

In article <1990May7.205315.1094@hfh.edu>, (Jeanne Li) writes:

|>I installed olwm on our sun 4/150 and tried to run it from my NCD16. I
got a error 
|>message:
|>
|>Base frame not passed parent window in environment. Cannot create base frame.
|>Process aborted.
|>
|>Don't know what this means. Could someone out there help me out?
                       

My sister is a doctor in your hospital!   :-)


Anyway, your problem is not due to olwm.
Rather, it is because various OpenWindows
(XView) applications have the SAME names
as the corresponding Sunview applications
(eg. cmdtool, mailtool, shelltool, textedit).

So when you try to bring up an appication from
olwm menu, (e.g. shelltool), the Sunview program
comes up, finds itself in the wrong window
environment, and exits with the "Base frame..."
message.

I presume you have the corresponding
OpenWindows (XView) applications available
somewhere (e.g. on my system, Sunview tools are
in /usr/bin, while the OpenWindows ones are
in /home/openwin/bin/xview).

The simplest fix (there are others) would
be to create a file called .olwmmenu in your
root directory (the same goes for your other
olwm users), and customize it to use your
OpenWindows binaries rather than the Sunview
ones.  You can get a sample .olwmmenu from
"man olwm".  In my case, I might use:



TITLE     "Workspace"
PIN

DEFAULT "Programs"            MENU
    "cmdtool"                 "/home/openwin/bin/xview/cmdtool"
    "mailtool"                "/home/openwin/bin/xview/mailtool"
    "other"                       MENU
          TITLE               "Other Tools"
          PIN
          "shelltool"         "/home/openwin/bin/xview/shelltool"
          "clock"             "/home/openwin/bin/xview/clock -Wi"
    END
END

"Repaint Screen"              REFRESH

"Properties ..."                  PROPERTIES

Exit                          EXIT




Hope it helps.


Narayan Sriranga Raja.

montnaro@spyder.crd.ge.com (Skip Montanaro) (05/09/90)

raja@bombay.cps.msu.EDU (Narayan S. Raja) writes:

   The simplest fix (there are others) would be to create a file called
   .olwmmenu ...

One of the alternatives is to make sure the OpenWindows binary directories
are ahead of /usr/bin in your path, since the SunView versions of shelltool et al
are in /usr/bin.

--
Skip (montanaro@crdgw1.ge.com)