Hi Arkady, > I not seen your edition yet, so I not have any ideas. :)
It is on www.coli.uni-saarland.de/~eric/ctmouse21b3.zip Your points about the macros are okay :-) > "is empty or attached mouse in Mouse Systems mode". :) And Genius > mice are long ago based on Logitech protocol. Which even means that only -old- Genius mice use Mouse Systems. > Well, I never seen such bug report... You are right - users can be so lazy that they just download another driver instead ;-). > >> EA> has an option /Y ignore Mouse Systems, and most people > Well, I myself always use /y - I not like and not use mouse systems > mice, whereas I prefer not remain in my RAM useless code stubs. So you agree to make /y the default :-) I suggest to introduce a new option (name? maybe /yy?) which means ENABLE Mouse Systems mode, and ignore the /y option because DISABLE Mouse Systems would be the default in the future. > EA> default, too, as disabling the wheel improves compatibility > EA> quite a bit. > How it improves compatibility? Using the wheel needs a "handshake" (a sequence of clock changes) and it needs the not-so-common 4 byte protocol. The 2.0 driver used direct keyboard controller programming, which sometimes (too often) crashed my keyboard and which might confuse BIOS USB mouse drivers which emulate PS2 via the BIOS PS2 interface and/or by feeding the data into the keyboard controller. For example some user recently reported that 2.0 hangs his PC. The 2.1 driver is "plain BIOS", but I got a bug report that some emulated PCs do not support 4 byte protocol in their BIOS, while they do support the wheel detection handshake... In short, the wheel stuff is less foolproof than the protocol without wheel, and as 95% of the DOS apps do not use the wheel anyway, I suggest to use the disable wheel option for example in the autoexec of a generic boot floppy or boot cdrom or dvd. > Microsoft: 01LRyyxx, 00xxxxxx, 00yyyyyy (high bits are in 1st byte) > Logitech: 01LRyyxx, 00xxxxxx, 00yyyyyy, 00M00000 (4th only if M change) > MS Wheel: 01LRyyxx, 00xxxxxx, 00yyyyyy, 000Mwwww (w is wheel) > EA> In PS2, you tell the BIOS to select a protocol size and reset > EA> communication to know "where you are"... > ...without possibility to resync. :( You could resync by selecting the protocol again, possibly after a rate change or similar to make it clear that there is something to be synced. > Not need - review again resync check at start of MSLTproc. Yes yes. You only get one bad packet, but in Logitech and MS Wheel protocol, this means that the middle button state might be wrong until you press that button again. If you have some protocol which does "L+R means toggle middle" (pre-Wheel MS 3 button mice?), it can be quite hard to resync the state of the middle button. Well I guess you just press both buttons simultaneously to force a toggle then :-). > Bad, very bad protocol design. :( How annoys such brain damaged > working... Basically PS2 mice are like PS2 keyboards - not designed for hotplugging. Might even damage something, although unlikely. Eric ------------------------------------------------------------------------- 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
