Path: utzoo!attcan!uunet!mcsun!hp4nl!charon!frankk From: frankk@cwi.nl (Frank Kuiper) Newsgroups: comp.windows.open-look Subject: Framebuffer problem in OW2.0? Keywords: openwindows Message-ID: <2560@charon.cwi.nl> Date: 19 Nov 90 15:03:34 GMT Sender: news@cwi.nl Organization: CWI, Kruislaan 413, 1098 SJ Amsterdam, The Netherlands Lines: 42 I'm having a problem with OpenWindows 2.0, running on a Sun 4/110 with OS 4.0.3. When I start OW 2.0, using the command (shell script) ``openwin'' and all default rc and init files (that is, no .Xdefaults, .xinitrc and .openwin-init specified in the $HOME directory), I see an error message printec "on the console" as there is no console window yet. The message in this case is: Unable to open /etc/filetype Have you run install_filemgr? My problem is not the above message itself, but the fact that in no way I am able to clear the screen from that message! I can do a ``refresh'' in the ``Utilities >'' sub-menu, to no avail. If I do a /bin/clear-colormap, the *entire* screen becomes white. But then I can't get my OW environment back (``refresh'' doesn't help). Starting up a SunView Program (in OpenWindows) leaves the error messages on the screen. Now, my idea is that somewhere, somehow the framebuffer get's written to, but can not be cleared again by either olwm or sunview. The environment used *does* work on Sparcs running 4.1 or 4.0.3. The error message(s) do get displayed, but a simple ``refresh'' will get rid of them. I know there's a difference in framebuffers between Sparcs (/dev/cgthree) and the 4/110 (/dev/cgfour) and I've correctly set the $FRAMEBUFFER variable in both cases. I'm confused. Please e-mail me, as I don't regularly read this list. Thanks a bundle in advance. -- Frank Kuiper . ___ Internet: frankk@cwi.nl _][__| | AppleLink: HOL0042 <_______|-1 Llanfairpwllgwyngyllgogerychwyrndrobwllllantysiliogogogoch. O-O-O