Hi!
4-Янв-2008 15:10 [EMAIL PROTECTED] (Eric Auer) wrote to
freedos-devel@lists.sourceforge.net:
EA> you are right, disabling the wheel only helps compatibility
EA> in the PS2 case. But as said, I assumed that wheel usage in
EA> DOS is rare, so /O (OPT_noWheel) affects both PS2 and COM
EA> at the moment even though COM wheels seem to be no real risk
EA> for compatibility... Would be easy to change :-). Maybe you
EA> can think of a good line for the /? screen to describe your
EA> suggested /O option style.
/3 - force 3-button mode (for Microsoft and PS/2 mice only)
force wheel support (for PS/2 mice)
BTW, /3 option was used to force middle button support through L+R
extension. Now there remains only option.
>> AM> I can tell is that Cutemouse 1.6b can use ANY serial mouse and
>> AM> switch ON THE FLY from ANY serial mouse to ANY other mouse.
>> Including MSys? I remember we discuss reinitializing UART
EA> Alain has already clarified in another mail: His code only
EA> supports on the fly detection of the 7bit serial mouse types,
EA> it does never switch to MSys or other. Luckily ;-).
He clarify, that MSys supported too. :)
>> >> releasing it once to get the driver back in sync. But maybe
>> >> there are other protocols where for example "LR encodes a M
>> >> toggle" is used to get along with only 3 bytes...?
>> was idea for it support, but it was excluded after some testing.
EA> Actually, are there mice which use such a protocol? Or are
I doubt. Why, if there is MS+wheel protocol?
EA> they "dinosaurs" like ancient Genius mice before they learned
EA> to use the MS protocol for 2 or all 3 buttons...? ;-)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
