Xref: utzoo comp.unix.sysv386:5480 comp.windows.x:33283
Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!wuarchive!uwm.edu!ogicse!pdxgate!eecs!brians
From: brians@eecs.cs.pdx.edu (Brian Smith)
Newsgroups: comp.unix.sysv386,comp.windows.x
Subject: Re: X386 1.1 Problems
Message-ID: <1764@pdxgate.UUCP>
Date: 25 Feb 91 22:05:23 GMT
References: <1991Feb25.035635.5003@coyote.datalog.com> <1991Feb25.065741.18576@portia.Stanford.EDU>
Sender: news@pdxgate.UUCP
Lines: 20


In article <1991Feb25.035635.5003@coyote.datalog.com> ejm@coyote.datalog.com (E.J. McKernan) writes:
>[stuff related to v1.0 deleted]
>
>Creating TCP socket: No such file or directory
>InitOutput(pScreenInfo=0x40ae04, argc=2, argv=0x7fffff44)
>X386VTInit()
>vgaScreenInit(index=0, pScreen=0x42d400, argc=2, argv=0x7fffff44)
>bus error

Are you using a Microsoft mouse?  If so, that is your problem!  I had the
exact same bus error when using a MS mouse.  Switching to a Mouse Systems
mouse cut out the bus errors.  Try fiddling with the config settings, and
see if that doesn't reduce your bus errors.  It won't help you if you don't
have a Mouse Systems or Logitech mouse, but you will know where the problem
lies.


Brian
(brians@cs.pdx.edu)