Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!hplabs!hpda!hpcuhb!hpindda!huilin
From: huilin@hpindda.HP.COM (Hui Lin Lim)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Mouse problems (for left hander)
Message-ID: <40970005@hpindda.HP.COM>
Date: 21 Feb 89 23:29:01 GMT
References: <40970003@hpindda.HP.COM>
Organization: HP Information Networks, Cupertino, CA
Lines: 39

Well I finally managed to swop the functions of the mouse buttons
around by using debug to trace the code attached to the serial
port interrupt.  This allowed me to find out where the mouse
driver was intepreting the data being sent by the mouse and
reverse the result.

For the interest of others who have the same problem, you can
forget about doing any hardware mods if the PC Mouse and PC
Mouse II are anything to go by.  The microswitches are mounted on
printed circuit boards and there aren't any wires that can be
cross connected.  About the only thing that you could do would be
to cut traces and install jumpers (not something that I'd want to
try - but then again I'm a software person).

Thanks to all those who offered suggestions which can basically
be summarised as (my comments about each proposed solution follow
in parentheses):

1.  Use the application software which comes with the mouse to do
the customisation (won't work for applications which use int33h to
access the mouse)

2.  Write your own driver (too complicated)

3.  Write a TSR which watches int33h and modifies the returned
values (also fairly complex if one is to provide the full
functionality that the driver does since several functions return
information about the mouse buttons)

I'd like to apologise for not giving the names of those who
helped me with their suggestions but I'm afraid I ran out of
space and had to purge my mail and I forgot to save the names.
Once again please accept my thanks.


Hui-Lin Lim
ARPA: huilin%hpinddf@hplabs.hp.com
UUCP: {ucbvax,hplabs}!hpinddf!huilin
Phone:  (408)447-2835