Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!csd4.milw.wisc.edu!srcsip!falcon!rogers
From: rogers@falcon.SRC.Honeywell.COM (Brynn Rogers)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re^2: Solitile  mouse problem
Message-ID: <25187@srcsip.UUCP>
Date: 9 Jul 89 19:57:40 GMT
References: <25036@srcsip.UUCP> <14@cica.cica.indiana.edu> <6069@watdcsu.waterloo.edu> <15@cica.cica.indiana.edu>
Sender: news@src.honeywell.COM
Reply-To: rogers@falcon.UUCP (Brynn Rogers)
Distribution: na
Organization: Honeywell Systems & Research Center, Camden, MN
Lines: 22

pfratar@watdcsu.waterloo.edu (Paul Frattaroli - Department of Computing Services) writes:

>If your documentation tells you how to do this then simply redefine your
>mouse buttons to the PageUP and HOME keys.

I also tried this, and it doesn't fix it.  also remember I told the
mouse to use all the different protocols it had, and none of them worked.

The strangest thing about it , is whenever it wants me to confirm a
action like a new board or layout or color, then the mouse buttons work
perfectly.

About the only thing I haven't tried yet is to remove CLICK and LOGIMENU from m
My autoexec.bat and see what happens. (I may have tried this already, actually)

I wrote a letter to the author of the program, hopefully I'll get some 
response.



 Brynn Rogers    Honeywell S&RC        rogers@src.honeywell.com
                                       nic.MR.net!srcsip!rogers