Quote:>I feel a bit sheepish asking this cause it will probably be something
>absolutely trivial, but...
>On several occasions, while working on a SS20 or SS5 in Openwindows and
>when either killing the wrong process (killing the X server in the
>process) or forcing a logout from within Openwindow (instead of quitting
>OW and THEN logging out), the console gets totally screwed up, filling up
>with junk characters & such. After this, you cannot even logon, cause you
>can't read what the machine is displaying. The machine is ok, cause you
>can telnet into it and all is working fine; it's just that the console
>display gets totally confuzzed.
There are two unrelated problems:
kbd_mode problem. Log in from remote and as root do
"kbd_mode -a"
colormap problem. (gf = bg = smae color)
You need something like "clear_colormap" which
isn't standard.
The solaris FAQ says:
3.20) And what about screendump, screenload and clear_colormap?
You can FTP Jef's screenload, screendump, etc., if you need that
functionality, and for free you get a pixrect (clone) library.
Get one of these:
ftp.netcom.com:/pub/jef/raster-pixrect_30dec93.tar.Z
ee.lbl.gov:/raster-pixrect_30dec93.tar.Z
The 4.1.x versions of these programs will not run under
Solaris 2.2 or later. The pixrect BCP library is no
longer supported.
--- end of excerpt from the FAQ
Questions marked with a * or + have been changed or added since
the FAQ was last posted
The most recently posted version of the FAQ is available from
ftp.fwi.uva.nl in directory /pub/solaris
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.