Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!orion.oac.uci.edu!okazaki.acs.uci.edu!gcardwel
From: gcardwel@okazaki.acs.uci.edu (Guy Cardwell)
Newsgroups: comp.windows.x
Subject: Re: Xsun (from MIT) on an IPC
Summary: -zaphod does not do the right thing!
Keywords: cgfour cgthree bwtwo
Message-ID: <27FD3EBA.14038@orion.oac.uci.edu>
Date: 6 Apr 91 03:21:30 GMT
References: <7945@idunno.Princeton.EDU> <27FD104E.5282@orion.oac.uci.edu> <ADRIANHO.91Apr5183438@barkley.berkeley.edu>
Organization: University of California, Irvine
Lines: 26
Nntp-Posting-Host: okazaki.acs.uci.edu

In article <ADRIANHO.91Apr5183438@barkley.berkeley.edu> adrianho@barkley.berkeley.edu (Adrian J Ho) writes:
>In article <27FD104E.5282@orion.oac.uci.edu> gcardwel@okazaki.acs.uci.edu (Guy Cardwell) writes:
>
>>Try specifying the frame buffer when you start the server..
>
>>Xsun -dev /dev/cgfour0
>
>>or something along those lines.
>
>Nope, that's the *default* (which causes the problem).  Use:
>
>Xsun -zaphod   or   xinit -- :0 -zaphod
Sorry, but  -zaphod only prevents the mouse from moving off the
screen.  It does not disable 
the other screen!  My example -dev /dev/cgfour0 is correct with the
exception that the frame buffer is /dev/cgthree0. The cgfour is a
color display with a mono overlay plane display which can be used as
two X displays.  It is NOT the framebuffer on the IPC.  The IPC uses a
cgthree which is a very normal color board, and a bwtwo on the mother
board.  The default, by the way, is to poll and
initialize the available frame bufffers.  -dev /dev/cgthree0 does the
right thing on an IPC, believe me! 

Apologies for the confusion!

Guy