Mail Archives: opendos/2003/11/25/01:13:58
Well, since I don't think this message was followed up, I would
suggest that "Couldn't you have both in a single driver so that we
can opt easely?" means "Couldn't we have the option to select
PS/2 mouse detection via either BIOS or hardware?". This would
make sense, rather than have one method used in 1.9.x (BIOS
detection) and another in 2.0.x (hardware detection) ...
Anyway, I have found a new problem. I replaced my old mouse
(details not important, but it worked OK with CTMOUSE) with
another old mouse, a 2HW73-7ES "ball-less" mouse made by
Keytronic for Honeywell. This is a two button Micro$oft-mode
serial port mouse, however CTMOUSE (1.8b8 and 1.9.1a1 and
2.0a4) insists on using Mouse Systems mode, which is wrong.
If I specify "/Y" to prevent this from happening, it says "Device
not found". However, if I run the COMTEST utility, this detects
the mouse correctly as a Micro$oft-mode mouse. In addition,
both Linux and Caldera's DRMOUSE R1.1 (as you know, this
was based on an early version of CTMOUSE) correctly detect
this mouse and work OK with it.
So, there may be two separate problems. Clearly CTMOUSE is
not detecting this mouse correctly. In addition, it is possible that
the "/Y" command line switch doesn't work properly.
Joe.
> -----Original Message-----
> From: Arkady V.Belousov [SMTP:ark AT belous DOT munic DOT msk DOT su]
> Sent: Thursday, October 23, 2003 5:33 AM
> To: opendos AT delorie DOT com
> Subject: Re: ANNOUNCE: CuteMouse 1.9.1 alpha 1 and CuteMouse 2.0
> alpha 4
>
> Hi!
>
> 22-οΛΤ-2003 12:31 _alainm AT pobox DOT com (Alain) wrote to
> <opendos AT delorie DOT com>:
>
> >> dSJ> In case it's relevant, before config.sys and autoexec.bat are
> >> dSJ> processed, there is a brief message "Panning Support Driver
> >> dSJ> V1.0 ... (C) Toshiba ...". I have no idea what this is, however
> AB>> This is program/code, which unshrinks image in LCD screen.
> Without
> AB>> this, image on the screen is shrinked about 2/3 of screen height
> (with high
> AB>> black stripes above and below).
> A> Couldn't you have both in a single driver so that we can opt easely?
>
> This program is proprietary closed software from Toshiba. Other
> notebooks manufacturers have its own software or their notebooks are not
> subject of this sickness. Read:
>
> 1. you have no sources/specifications for this code.
> 2. this code is very harware and vendor specific.
> 3. this code not relates to mouse functions (mouse driver uses solely
> standard video functions of CGA/EGA/VGA and not comes down at lower
> level
> to chipsets; currently CTMOUSE even not uses VESA).
>
>
- Raw text -