Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!hplabs!hp-pcd!hpcvlx!everett
From: everett@hpcvlx.HP.COM (Everett Kaser)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Solitile  mouse problem
Message-ID: <102760013@hpcvlx.HP.COM>
Date: 11 Jul 89 16:36:27 GMT
References: <25036@srcsip.UUCP>
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 17

(Just to set you in the proper frame of mind, I'm the author of Solitile :-)
I've been on vacation and just got back, so I haven't had a chance to check
into this problem with Logitech mice, but from what I've read, I think it's
a problem with the Logitech driver (of course :-).  When I wrote the program,
I just used the "standard" Microsoft interface (INT 33H), according to the
Microsoft documentation, for reading the mouse position and status changes of
the buttons.  Since the Logitech bus mouse (at least one version) worked, and
the problem appears to be with the "New" serial mouse, I can't help but lean
towards pointing the finger at the Logitech driver (or, at least, at the way
it's been configured (or hasn't)).

As I find out more, I'll let you know.  (If anyone that has one of these mice
finds out anymore info, I'd appreciate hearing from you, too!)

Everett Kaser                   "Your thoughts create your reality."
!hplabs!hp-pcd!everett
everett%hpcvlx@hplabs.hp.com