Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!src.honeywell.com!beethoven!engstrom
From: engstrom@SRC.Honeywell.COM (Eric Engstrom)
Newsgroups: comp.windows.open-look
Subject: Re: Framebuffer problem in OW2.0?  (messages and cgfour)
Message-ID: <1990Dec19.193008.11613@src.honeywell.com>
Date: 19 Dec 90 19:30:08 GMT
References: <2560@charon.cwi.nl> <1990Nov30.050143.26837@sq.sq.com>
Sender: news@src.honeywell.com (News interface)
Organization: Honeywell Systems & Research Center
Lines: 80
In-Reply-To: lee@sq.sq.com's message of 30 Nov 90 05:01:43 GMT
Nntp-Posting-Host: beethoven.src.honeywell.com


[Sorry to repost nearly the entire previous message, but it was a long time
ago, and I want to give some context...]

In article <mumble mumble> lee@sq.sq.com (Liam R. E. Quin) writes:

> frankk@cwi.nl said that he had a problem whereby error messages appeared on
> his screen when he ran openwin, and he couldn't erase them, since they were
> on the monochrome frame buffer.

[(pseudo-)solution #1 deleted :-)]

> (2) Once openwin has started, you can control the other display with
>     switcher -e 0
>     to turn it off, and
>     switcher -e 1
>     to turn it on (you don't want to do the second one, I expect!)

> This has the advantage of working if you typed "openwin" and then realised
> too late the problem...  I certainly don't like waiting ages for openwin to
> start again if I do this!

> (2) Heather Rose of Sun gave by far the best solution:
> 	openwin -dev /dev/cgfour0 -dev /dev/bwtwo0
>     will make openwin use both screens -- you can move the mouse-pointer off
>     the edge of the colour screen and onto the monochrome one.
>     You'll want to run
> 	olwm -display unix:0.1
>     if you use olwm -- twm knows about the other frame buffer and uses it
>     automatically anyway.

This (# 3) is what I have been TRYING to do on a Sun 3/60C [mumble, curse,
curse]...

At first, I did what the docuementation (OpenWindows Version 2;
Installation and Start-Up Guide; Revision A, of 11 June 1990) told me to do
(pages 18-20):

 1) I created the device file /dev/bwtwo0.
 2) modified my .xinitrc file to include the following lines

        eval `$OPENWINHOME/bin/svenv -env -display :0.0`
	olwm -display :0.0 &
	eval `$OPENWINHOME/bin/svenv -env -display :0.1`
	olwm -display :0.1 &

    (the first and third lines are so I can run SunView applications on
    those "screens")

 3) started OpenWindows:
 	% openwin -dev /dev/fb -dev /dev/bwtwo0

    Now I get _THREE_ "screens", the first is color an the other two seem
    to be the console (i.e., they show the text of console from when I
    started OW) These two "extra" screens are off the color one to the
    right and top.  Also, the two extra screens have no cursor.

 Since #3 didn't work, I went looking for a possible solution.  Found the
 referenced message and tried the following:

 3b) 	% xinit ~/.xinitrc -- xnews -dev /dev/cgfour0 -dev /dev/bwtwo0
					      ^^^^^^^

    This didn't work either (I still get three screens).  I also tried
    using twm instead of olwm, tried leaving the two "eval" lines out of my 
    .xinitrc file, an I even tried an old Ojibway cerimonial dance :-), but 
    nothing seemed to work.

 If anyone has ANY suggestions, I'd really appreciate them...

 (for completeness:  Sun 3/60C, Sun OS 4.0.3, OW Ver. 2.0)

Thanks much,
Eric
+---------
Eric Engststrom, Honeywell SRC		   | 
ARPA:  engstrom@src.honeywell.com	   | [DISCLAIMER: 
UUCP:  {umn-cs,ems,bthpyd}!srcsip!engstrom |  My own opinions - 3.1415 = 
MAIL:  3660 Technology Drive, Mpls, MN     |           orgainically grown]
Phone: (612) 782-7318                      |