Path: utzoo!attcan!uunet!husc6!bloom-beacon!GOLDHILL.COM!ejs
From: ejs@GOLDHILL.COM (Eric Swenson)
Newsgroups: comp.windows.x
Subject: [ejs@goldhill.com: X11/R3 on Sun 3/60s with SunOS 3.5 and Sunview]
Message-ID: <8811031430.AA23307@goldhill.com>
Date: 3 Nov 88 14:30:54 GMT
References: <1169@stiatl.UUCP>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 26


   Date: 2 Nov 88 14:20:27 GMT
   From: kong!emory!stiatl!meo@gatech.edu  (Miles O'Neal)
   Organization: Sales Technologies Inc., Atlanta, GA
   Sender: xpert-request@athena.mit.edu

   In article <8811012351.AA13588@special-k.ai.mit.edu> sundar@WHEATIES.AI.MIT.EDU (Sundar Narasimhan) writes:
   >R2 when xinit is run from within Sunview.  Under R2, when one
   >started up xinit from within Sunview, it seemed as though Sunview was
   >(correctly) inhibited and Sunview updates did not show through and mess
   >up the X windows display.

   Which version of Sunview, and on what hardware? We have NEVER been able
   to run X11 and Sunview simultaneously. We have always had interference
   problems; the X11 gurus told us this was normal. Even the source (or was
   it the doc?) from the dist. tape said this was likely. Which is why we
   have been waiting not-so-patiently for the new, merged Sunview/X11 product
   from Sun. We have seen this on a 386i under 4.0 and a 3/160 under 3.something.

Actually, it was I (ejs@goldhill.com) who posed the initial query.  It
turns out that I had failed to set UseSunWindowsInServer in Sun.macros
before building the world.  Once I set this, everything worked fine
and the X Window System and Sunview worked fine together (i.e. Sunview
was inaccessible while X was running) but there was no interference.

-- Eric Swenson