Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!mips!mips!sdd.hp.com!cs.utexas.edu!sun-barr!male.EBay.Sun.COM!exodus.Eng.Sun.COM!sun!amdcad!BitBlocks.com!bvs From: bvs@BitBlocks.com (Bakul Shah) Newsgroups: comp.unix.bsd Subject: Re: Motif on X386??? Message-ID: <1992Aug19.062455.12847@BitBlocks.com> Date: 19 Aug 92 06:24:55 GMT References: <1992Aug17.140857.3882@lgc.com> <1992Aug18.015024.8369@fcom.cc.utah.edu> <1992Aug18.174802.9845@BitBlocks.com> <090m_#b.hasty@netcom.com> Organization: Bit Blocks, Inc. Lines: 33 hasty@netcom.com (Amancio Hasty Jr) writes: >In article <1992Aug18.174802.9845@BitBlocks.com> bvs@BitBlocks.com (Bakul Shah) writes: >>Make sure you are using the latest com.c driver (with select() >>bug fixed). But even then there is some problem with the mouse >>code in X386 as the very first button press is not seen until >>after you either release the button or move the mouse a bit. >> >>If you wish to track this problem down, check out file >>$X11R5/mit/server/ddx/x386/x386Io.c. Routine x386MseEvents() >>seems to be the culprit. >> >Rich (rich@rice.edu) already fix this problem in the next upcoming release >of X386 1.2E 1.0.2 for 386bsd 0.1, please ask him for the fix. The problem >in a nutshell is that X386Io.c is not setting the cflag. the fix was also >previously posted by me. I have already applied that patch but I still see the same symptom. May be this only happens with a Microsoft compatible mouse. >Additionally, there are problems with the X server not grabbing the keyboard, >this problem has been also resolved. >So just ask Rich when he is going to release X again. Hopefully, it will be >soon. I just hate to see the same problems being reported over and over again >even though there has been previous postings relating to the problem with >suggested fixes. I too hate repititions but I think this problem is different from tty.c_cflag not being set in x386SetSpeed() in the #ifdef __386BSD__ leg. -- Bakul Shah <bvs@bitblocks.com>