Hi ZB,
Please, note: CuteMouse v2.1 beta4 probably is flawed. One day
I was tried it with "Civilization", but when using this mouse
driver the game always has been hung after relatively short
>> period of time (like 30-40 moves) and then I wasn't able to
do any more input (it was beeping at me like in case of
keyboard buffer overflow). Used it as "mouse /3" (Microsoft mode).
Please provide more details :-) At the moment, I am way behind with
reading the mailing list, so if somebody could give me some hints
which threads are most relevant at the moment - thanks!
CuteMouse v2.1 beta4 [FreeDOS]
Options:
/V - reverse search: find PS/2 after serial mouse
/P - force PS/2 mouse mode, do not probe serial ports
/S[c[i]] - force serial mouse mode at COM port c (1-4) with IRQ i (1-7)
/3 - force 3-button mode if Microsoft or PS/2 mouse found
/O - enable PS2 and BIOS USB wheel detection (might hang)
/M - try *old* Mouse Systems / Genius for non-PnP mice
/R[h[v]] - horizontal / vertical resolution: h,v = 1-9, or 0 for auto
(no value = use default: auto for h, or "as h" for v)
/L - swap left and right button
/B - cancel run if mouse services are already present
/N - load CuteMouse as new TSR, even if CuteMouse is already loaded
(useful for batch files which unload CuteMouse at end)
/W - do not allow CuteMouse to move itself into UMB
/U - uninstall driver, remove TSR from memory
/? - show this help
I would suggest to check whether /3 mode or /O mode work and let
me know whether this mouse is USB or actual PS/2. In the USB case,
the BIOS typically tries to make the mouse visible both via BIOS
PS/2 interrupts and by simulating keyboard controller input on
the port I/O level, because PS/2 shares that controller between
mice and keyboards. The latter can get messy if you have a mix
of real PS/2 and USB, or even when you have more than one USB
device at all, because the BIOS normally expects that only simple
software like OS installers will need that "USB legacy support",
while "real" operating systems for more intense use of USB devices
are expected to have their own USB drivers. So BIOS programmers do
not put much effort into making the support stable and using mouse
wheels in that context is a bit of a hack anyway.
I also recommend to compare different CTMOUSE versions: 1.9, 2.0
and 2.1 for example, which approach the USB and/or wheel topic in
different ways. Thanks for testing :-)
Eric
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
