X-Authentication-Warning: delorie.com: mail set sender to opendos-bounces using -f
X-Authentication-Warning: piglet.mos.ru: uubelous set sender to belous!belous.munic.msk.su!ark using -f
>Received: by belous.munic.msk.su (dMail for DOS v2.7.10, 24Jul03);
          Wed, 26 Nov 2003 09:22:33 +0300
To: opendos AT delorie DOT com
X-Comment-To: "da Silva, Joe" <Joe DOT daSilva AT emailmetering DOT com>
References: <01FD6EC775C6D4119CDF0090273F74A4FD6C5B AT emwatent02 DOT meters DOT com DOT au>
Message-Id: <2.7.10.8I93.HOY4DJ@belous.munic.msk.su>
From: "Arkady V.Belousov" <ark AT belous DOT munic DOT msk DOT su>
Date: Wed, 26 Nov 2003 09:22:31 +0300 (MSK)
X-Mailer: dMail [Demos Mail for DOS v2.7.10]
Subject: RE: ANNOUNCE: CuteMouse 1.9.1 alpha 1 and CuteMouse 2.0 alpha 4
MIME-Version: 1.0
Content-Type: text/plain; charset=koi8-r
X-MIME-Autoconverted: from 8bit to quoted-printable by box.mos.ru id hAQ6OYc07027
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id hAQ6OjX2021830
Reply-To: opendos AT delorie DOT com

Hi!

25-ξΟΡ-2003 17:14 _Joe DOT daSilva AT emailmetering DOT com (da Silva, Joe) wrote to
"'opendos AT delorie DOT com'" <opendos AT delorie DOT com>:

dSJ> Well, since I don't think this message was followed up, I would
dSJ> suggest that "Couldn't you have both in a single driver so that we
dSJ> can opt easely?" means "Couldn't we have the option to select
dSJ> PS/2 mouse detection via either BIOS or hardware?". This would

     Of course, this written in the plans. Though, there are some issues on
this way.

dSJ> Anyway, I have found a new problem. I replaced my old mouse (details not
dSJ> important, but it worked OK with CTMOUSE) with another old mouse, a
dSJ> 2HW73-7ES "ball-less" mouse made by Keytronic for Honeywell. This is a
dSJ> two button Micro$oft-mode serial port mouse, however CTMOUSE (1.8b8 and
dSJ> 1.9.1a1 and 2.0a4) insists on using Mouse Systems mode, which is wrong.

     May you send me result of "PROTOCOL 1 3>RESULT"? Run this command, move
mouse up/down/left/right, then press Esc.

dSJ> If I specify "/Y" to prevent this from happening, it says "Device not
dSJ> found". However, if I run the COMTEST utility, this detects the mouse
dSJ> correctly as a Micro$oft-mode mouse. In addition,

     Which hardware (CPU) on your machine?

dSJ> both Linux and Caldera's DRMOUSE R1.1 (as you know, this was based on an
dSJ> early version of CTMOUSE) correctly detect this mouse and work OK with it.

dSJ> So, there may be two separate problems. Clearly CTMOUSE is
dSJ> not detecting this mouse correctly. In addition, it is possible that
dSJ> the "/Y" command line switch doesn't work properly.

     No, /Y option works properly, as expected - it prevents Mouse Systems
mode handler if no mouse in MS or Logitech mode is detected, as explained in
CTMOUSE.TXT.