Newsgroups: comp.windows.open-look
Path: utzoo!sq!lee
From: lee@sq.sq.com (Liam R. E. Quin)
Subject: Re: Framebuffer problem in OW2.0?  (messages and cgfour)
Message-ID: <1990Nov30.050143.26837@sq.sq.com>
Organization: SoftQuad Inc.
References: <2560@charon.cwi.nl>
Date: Fri, 30 Nov 90 05:01:43 GMT
Lines: 39

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.

Although I sent him mail, it turns out that there are several good solutions.

(1) Run openwin with errors redirected:
	openwin 2> /tmp/xerrs.liam
    and then inside a console window I run
	tail -f /tmp/xerrs.liam

This is the worst solution, although it does work.

(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.


Perhaps this will alleviate some aggravation for others.

Lee

-- 
Liam R. E. Quin,  lee@sq.com, SoftQuad Inc., Toronto, +1 (416) 963-8337