From owner-freebsd-questions Mon Jul 8 00:07:25 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA12845 for questions-outgoing; Mon, 8 Jul 1996 00:07:25 -0700 (PDT) Received: from gdi.uoregon.edu ([128.223.186.250]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA12840 for ; Mon, 8 Jul 1996 00:07:23 -0700 (PDT) Received: (from dwhite@localhost) by gdi.uoregon.edu (8.6.12/8.6.12) id AAA00393; Mon, 8 Jul 1996 00:06:29 -0700 Date: Mon, 8 Jul 1996 00:06:29 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: "Ran d'Adi" cc: questions@freebsd.org Subject: Re: olwm In-Reply-To: <199607071740.VAA02884@styx.aic.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 7 Jul 1996, Ran d'Adi wrote: > I have the following problem: > olwm will not run normal. > When I run X in 8bit/pixel mode, everything is OK, > but when I start X as bpp 16 olwm will switch to monochrom mode. olwm doesn't support 16 bit mode then. There are several apps that don't like 16 bit mode (vic, for instance); it's not uncommon. > Video card is S3-Trio64 with 2 Mb RAM > greh doesn't run in 1024x768x64k mode, but I cannot accept also such a > kind of olwm. :( Olwm is ported/contributed binary, and is meant for backward compatibility. If you are looking for more robustness try fvwm or ctwm(?). Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major