Xref: utzoo comp.sys.att:6440 comp.unix.wizards:16063
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cwjcc!tut.cis.ohio-state.edu!rutgers!att!mhuxu!jmcook
From: jmcook@mhuxu.UUCP (Joel M. Cook)
Newsgroups: comp.sys.att,comp.unix.wizards
Subject: Xwindows problems on AT&T 6386 with SysVR3.2
Keywords: Xwindows, UNIX
Message-ID: <9331@mhuxu.UUCP>
Date: 11 May 89 11:42:55 GMT
Distribution: usa
Organization: AT&T Bell Laboratories
Lines: 12

A week or so ago I posted a note about a problem I was having with
Xwindows 1.0 on my AT&T 6386 running the UNIX/386 (SVR3.2).
The symptoms were random window invocations, menus coming and going etc--all
without my intervention.  For no obvious reason, I removed the busmouse
driver stuff using removepkg, remade the kernel, rebooted, reinstalled the
mouse driver stuff and all's been fine since!!!  THe only difference is that
now the mouse driver package has been installed after the Xwindow stuff, rather
than before.  Performance is quite good, stable, and generally works as
advertised!!  Have no idea why it should be so, but there you have it!

					Satisfied Xwindows user,
						Joel Cook