Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!know!news.cs.indiana.edu!cs.widener.edu!ukma!dftsrv!quercus.gsfc.nasa.gov!karl
From: karl@quercus.gsfc.nasa.gov (Karl Anderson)
Newsgroups: comp.windows.open-look
Subject: Re: White on White
Message-ID: <1991Mar25.161147@quercus.gsfc.nasa.gov>
Date: 25 Mar 91 21:11:47 GMT
References: <DOWDING.91Mar23142607@palm.ai.sri.com>
Sender: news@dftsrv.gsfc.nasa.gov
Reply-To: karl@quercus.gsfc.nasa.gov (Karl Anderson)
Distribution: comp
Organization: NASA/GSFC code 923
Lines: 32

In article <DOWDING.91Mar23142607@palm.ai.sri.com>, dowding@ai.sri.com
(John Dowding) writes:
|> 
|> Running some open look applications (not written here) as the
|> side-effect of causing openlook to leave the screen in a 
|> white-on-white state when it exits.  The machine is not weged,
|> you just can see what you type, or what the response is.
|> If you restart openwin, it resets the screen, and you are back
|> to normal.
|> 
|> Does anyone know how to prevent this from happening?
|> 
|> I am running openlook 2.0 on spark 1s and 2s, running Sun Unix
4.1.1.
|> 
|> Thanks,
|> John Dowding
|> dowding@ai.sri.com

In /usr/openwin/bin/openwin, after this line:
$OPENWINHOME/bin/xinit -- ${SERVER-$OPENWINHOME/bin/xnews} $DISPLAY
$PASSTHRU $AUTH 

insert the following:
clear_colormap

Works for me.

--
Karl A. Anderson		| Internet: karl@forest.gsfc.nasa.gov
NASA/GSFC code 923 (STX)	| voice: (301) 286-3815
Greenbelt, MD 20771		| #include "std_disclaimer"