OS/2 Professional

home *** CD-ROM | disk | FTP | other *** search

/ OS/2 Professional / OS2PRO194.ISO / os2 / driver / com / maus / readme.1st next >

Wrap

Text File | 1993-04-07 | 34.2 KB | 835 lines

--------------------------------- Copyright ---------------------------------- Copyright (c) 1993 by Michael Lee Finney. All rights reserved. --------------------------------- Shareware ---------------------------------- This program is shareware. If you find this program useful you must register your copy. To register a private copy, send $15.00 (US funds) to: Michael Lee Finney 114 Old Wiggington Road Lynchburg, Va. 24502-4669 Please make remittance payable to: Michael Lee Finney, and include your company (for a corporate license), name, address and phone number. The registration cost for corporate site licenses is... 1..4 copies -- $25 each 5..10 copies -- $20 each 11..20 copies -- $15 each 21..40 copies -- $10 each 41... copies -- $5 each These prices are accumulative, so the first four copies cost $25 each, the next six cost $20 each, and so on. Therefore, a corporate license for 23 copies would cost: 4 @ $25 ... $100 6 @ $20 ... $120 10 @ $15 ... $150 3 @ $10 ... $60 ------ $430 for an average cost of: $18.70. To obtain the latest version of this program when you register, send $10 for shipping and handling to the above address. This $10 does NOT apply to the registration cost and only one copy will be sent regardless of the number of copies registered. Note: Registration is not required for beta releases of this program. However, the license to use the beta release expires when the general availability release of this program is issued. ---------------------------------- License ----------------------------------- Unregistered users (personal or corporate) are permitted to use this program for a trial period of one month. By the end of this period you must either register the program or remove it from your system(s). Registered users are permitted to use this program on one system at a time and may make as many archived copies for backup purposes as needed. It may be used on multiple systems (for a single license) only under the condition that only one of the systems is in use at a time. Since this program is an operating system device driver, the assumption is that it is in continual use when the system in use. Therefore a registered copy is required for each system on which this program is used simultaneously. Registered users are entitled to support. Since this program is a shareware product, the author assumes that you have not registered a copy if it fails to operate correctly. However, if after registration a program error is found, the author will make every attempt possible to repair the program. If the failure cannot be repaired and makes the product unusable the author will refund the registration fee. Furthermore, registered users are eligible for the "bug" reward (see details below). Additionally, registered users will also be sent notices of new versions of this program, and of other shareware releases by the author. In particular a registered beta user will be notified of the general availability release. Your name will NOT be sold to a mailing list. This program is not intentionally crippled in any manner, therefore a new copy of the program will NOT be sent when the program is registered. A registered user may upgrade to the latest version of this program for a cost of $5 ($15 if a copy on diskette is desired). Upgrading from a beta release is free ($10 if a copy on diskette is desired). Note: The license to use the beta release expires when the general availability release of this program is issued. ---------------------------------- Contents ---------------------------------- The distribution file, RODENT.ZIP, contains the following files... README.1ST - This file. RODENT.SYS - Mouse driver. RODENT.EXE - Presentation Manager test program. If this device driver is placed on a bulletin board, all three files must be distributed -- preferably in the original RODENT.ZIP file. ---------------------------------- Summary ----------------------------------- RODENT.SYS is a mouse driver which supports most buss mice and serial mice. It provides three button support. The advantages of RODENT.SYS over the IBM mouse drivers (assuming that they even work for your mouse) are... 1. Both 2 button and 3 button mice are fully supported. 2. The middle button on a 3 button mouse can be programmed as a chord of the left and right buttons. 3. The interrupt handlers have been carefully tuned resulting in a lower system load (compared to the IBM mouse drivers) when the mouse is active. 4. The FIFO buffer of the 16550AFN or 16552 can be enabled, further lowering the system load. 5. More serial mice are supported than the IBM mouse drivers support. Some digitizer tablets are supported as mice as well (diabled in the beta release). 6. Auto-detects the type of mouse. 7. Auto-detects the number of mouse buttons, where possible. 8. Auto-detects the type of uart (for serial mice). 9. Supports additional baud rates over the basic 1200 provided by the IBM mouse drivers. Baud rates of 150, 300, 600, 1200, 2400, 4800, 9600 and 19200 are supported (for those mice which allow the baud rate to be set). 10. Any 8250-compatible uart can be used at any port address and any irq. The IBM drivers only support COM1..COM4 (and may have trouble supporting COM3 and COM4). 11. Should not "lose" the mouse during a reboot via Ctrl-Alt-Del. 12. Mouse deinstalls correctly on ABIOS systems (a bug in some of the IBM mouse drivers). 13. Low battery detection for Logitech radio mice is provided during system boot. 14. The actual mouse resolution can be specified. ---------------------------------- Support ----------------------------------- This is a shareware product. Support is only available to registered users. The registration cost is only $15 so PLEASE register if you find this product useful. Problems can be reported via email (in order of preference -- I check Genie more often because it is free and CI$ is not) at: Genie: M.FINNEY Internet: M.FINNEY@GENIE.GEIS.COM Compuserve: 71573,1075 Internet: 71573.1075@COMPUSERVE.COM and by U.S. Mail at: Michael Lee Finney 114 Old Wiggington Road Lynchburg, Va. 24502-4669 Please include all pertinent information regarding the problem, including hardware configuration, operating system release and corrective service level. Include your name, address, email address, phone number, etc. so that I can contact you. Please include time zone, and the best hours to reach you by phone and the hours you would rather NOT be reached by phone. I will attempt to resolve any reported problems. However, if the problem is caused by a hardware incompatibility then resolution may be difficult if I am unable to locate equivalent hardware. I will work with you as far as possible. I am willing to support incompatible mice, but I must be able to get the necessary hardware. If you have such a mouse send me a note with a return address or phone number and I will work with you. ----------------------------------- Reward ----------------------------------- In order to promote software quality, and as an assurance of the existing software quality of this product, a reward of 25% of the registration fee (minimum of $5.00) is offered to any registered user who reports a previously unknown program error. RULES: 1. The reward is only offered to registered users (however, I will accept bug reports from any user). 2. The maximum reward paid to a single user is limited to twice the registration cost paid by the user (if you register 10 copies then your maximum possible reward is greater than if you register 1 copy). 3. I am the final arbiter in regards to precedence between users reporting the same program error. 4. I am the final arbiter in determining that a reported program error does, in fact, exist. 5. Failure to support incompatible hardware is NOT considered an error. I cannot be responsible for every device some twisted hardware designer creates (even IBM cannot do that). However, I will work with users to resolve any problem to the best of my ability. 6. This reward is not offered for beta releases. -------------------------------- Installation -------------------------------- Installation. The file RODENT.SYS should be copied to a directory of your choice -- the C:\OS2 directory is the usual choice, but any directory can be used. Your CONFIG.SYS file should be altered to contain the following two lines... DEVICE=C:\path\RODENT.SYS [options...] DEVICE=C:\OS2\MOUSE.SYS TYPE=RODENT$ and any existing lines relating to the mouse driver should be removed. For example, assuming that RODENT.SYS has been placed in the C:\OS2 directory: DEVICE=C:\OS2\RODENT.SYS BAUD=19200 BUFFERED DPI=400 DEVICE=C:\OS2\MOUSE.SYS TYPE=RODENT$ DEVICE=C:\OS2\RODENT\RODENT.SYS DEVICE=C:\OS2\MOUSE.SYS TYPE=RODENT$ DEVICE=C:\OS2\RODENT.SYS COM=73D8 IRQ=11 BAUD=2400 BUFFERED MOUSE=C PROTOCOL=MM BUTTONS=2 DPI=300 DEVICE=C:\OS2\MOUSE.SYS TYPE=RODENT$ The first DEVICE line in the last example is longer than 80 characters. In almost all cases an installation similar to the first two examples would be used. If you have multiple mice attached to your system, then you may need to specify the mouse type or the serial port for the desired mouse. Only one mouse can be used at a time. Lines in your CONFIG.SYS which are mouse related are... DEVICE=C:\OS2\VISION.SYS... DEVICE=C:\OS2\PCLOGIC.SYS... DEVICE=C:\OS2\MOUSE.SYS... all such lines should be removed and replaced as shown above. This mouse driver has been tested under OS/2 2.0 GA, 2.0 GA+SP and the 2.1 March beta. It has been tested on a 50Mhz 486DX AT-clone and on an IBM PS/2 model 70 (serial mice only for this machine). The following mice have been tested... Logitech C9 Mouse (buss) Logitech First Mouse (serial) Logitech MouseMan Cordless Mouse (serial) Logitech MouseMan Mouse (buss) Logitech TrackMan Mouse (serial -- Mouse Systems compatible) Microsoft Mouse (serial) Only these mice are certified to function correctly with this mouse driver. However, the driver is MUCH more capable because special provisions have been made to support "partially" compatible mice. In particular, it should be noted that the driver has only been tested with Mouse Systems "compatible" mice and that REAL Mouse Systems mice might behave slightly differently or not support some of the programming codes used. In some cases a mouse might function with the driver, but require some of the more exotic options (see the option list below). For example, you could have a mouse which recognized most of the protocols associated with a Mouse System's mouse, but could not be automagically recognized. In this case you would use the CONFIG.SYS entries: DEVICE=C:\OS2\RODENT.SYS MOUSE=C DEVICE=C:\OS2\MOUSE.SYS TYPE=RODENT$ which forces the mouse driver to accept the mouse as a Mouse Systems mouse, but avoids the recognition check. However, all programming codes are still sent to the mouse. Or as a more severe example, you could have a mouse which supports the Mouse System communication 5B protocol (default with Mouse Systems mice) but nothing else works. In that case you would use the CONFIG.SYS entries: DEVICE=C:\OS2\RODENT.SYS MOUSE=X PROTOCOL=5B DEVICE=C:\OS2\MOUSE.SYS TYPE=RODENT$ which forces the mouse driver to use the correct communication protocol, but with NO attempt made at sending programming codes to the mouse. The mouse must default to the appropriate state to use the specified protocol. Most mice can be setup this way because almost all mice default to one of the available communications protocol (however, digitizer tablets intrinsically REQUIRE programming and cannot be setup in this manner). ---------------------------------- Testing ----------------------------------- After booting OS/2 preliminary testing can be accomplished simply by moving the mouse and making sure that the mouse cursor follows the movement of the mouse. Execute RODENT.EXE to further test this device driver. This test program will display a Presentation Manager window. It will display the number of buttons as perceived by OS/2 and the mouse resolution as perceived by OS/2. Further, if you click the mouse buttons, the associated OS/2 mouse event is displayed. The most recent mouse event is flagged by an asterisk. If the mouse pointer follows mouse movement correctly and all buttons operate correctly then you will probably not have any trouble with the mouse driver. Other signs of trouble might be consistently missing mouse events (such as clicks) or events occurring without any associated physical mouse action. When evaluating missing or extra events reasonable care should be taken. It has been observed that occasionally OS/2 will "lose" a mouse click during rapid mouse activity -- this is related to the fact that OS/2 only maintains a small mouse event queue to avoid "piling" up an extremely large number of events. Sometimes losing a button release has the appearance of additional clicks if an application auto-repeats while a mouse button is pressed. The loss, by OS/2, of mouse events is fairly rare except under very heavy mouse activity. However, it appears to be slightly more common when using higher baud rates because the internal OS/2 queue is more likely to overflow. This has been seen using the Logitech radio mouse at 9600 baud. Also this lose might not actually be the fault of OS/2, but is occurring in the applications instead (actually more probable). Nevertheless, this behavior has sometimes been seen, both with these mouse drivers AND with the OS/2 mouse drivers. It has been seen most often using Logitech's radio mouse and Microsoft's PWB in a full screen session. This is a low-level mouse driver. OS/2 handles all of the higher level functions, including routing mouse events to DOS sessions OS/2 sessions and PM sessions. OS/2 reports all mouse events (in the appropriate form) to the currently active session. Therefore DOS sessions CAN take advantage of all three buttons. Since this mouse driver is not involved in these actions, failure of OS/2 in that manner are probably not caused by this device driver. Note: The resolution reported by OS/2 is in "mickeys per centimeter". Therefore, the dots per inch provided to the device driver is divided by 2.54 and rounded when reporting to OS/2. This device driver reports the closest value possible. For example, 400 dpi reports as 157 mickeys. Since the value reported to OS/2 is a fixed point number, the result if multiplied by 2.54 is only 399 (after rounding) instead of the original 400. ---------------------------------- Options ----------------------------------- The following options are supported... COM=# This option allows the serial port to explicitly specified. This option may be specified as: COM=1 COM=2 COM=3 COM=4 COM=xxxx where 1..4 is one of the standard com ports, and "xxxx" is the hex address of the serial port. So, COM=1 is normally equivalent to: COM=03f8 IRQ=4 Any serial port which is compatible with the 8250 uart may be used. This mouse driver is not restricted to COM1..COM4, unlike the IBM mouse drivers. If this option is omitted then the mouse driver will scan COM1..COM4 (in order) to find the mouse. This procedure works and is reasonably reliable, however it is impossible to completely restore the uart state so automatic scanning could potentially cause problems with other devices attached to serial ports. This mouse driver will restore more of the serial port state than the IBM mouse drivers. Specifying this option also reduces the time required to initialize the mouse driver -- by as much as a couple of seconds. IRQ=# This option allows the interrupt number to explicitly specified. Any interrupt from 2..15 may be used, unlike the IBM drivers which are restricted to interrupts 2..7. If omitted, the interrupt level to be used will be determined from the port address. This procedure is only reliable for the standard COM1 and COM2 port addresses 3f8 and 2f8. It may work for COM3 and COM4 (depending on the actual port addresses). The IBM mouse driver has the same (undocumented) problem, but does not provide a mechanism to specify the interrupt number. BAUD=# This option allows the baud rate to be specified. It may be one of 150, 300, 600, 1200, 2400, 4800, 9600 or 19200 All mice do not support all baud rates. To use the lowest baud rate supported by the mouse specify: BAUD=150 and to use the highest baud rate supported by the mouse specify: BAUD=19200. The lowest baud rate which gives good performance should be used to reduce system load. If this option is not specified then it defaults to a value determined by the protocol in use. Each protocol has a default baud rate based on the default mouse baud rate. If a baud rate is specified which is not supported by the protocol the highest baud rate which is less than the specified baud rate will be used, if any, and otherwise the lowest baud rate which is higher than the specified baud rate will be used. BUFFERED This option enables the FIFO buffer if a 16550 uart is determined. The FIFO buffer is NOT enabled by default because some 16550 uarts do not function correctly. All 16550AFN uarts should function correctly, if you have a 16550, 16550A or 16550AF uart then it should be replaced by a 16550AFN uart. MOUSE=xx This option allows the mouse type to be specified. This is useful to reduce the time required to load the mouse driver, or if the mouse used responds correctly but the mouse type cannot be auto-determined. If an invalid mouse type is specified the mouse driver may or may not load, and if loads may fail to operate properly. This option may be specified as: MOUSE=B Buss mouse, can be two button or three button Protocols: BS default: BS MOUSE=C Mouse System's compatible mouse Protocols: 5B, MM, RE default: 5B better: MM Baud Rate: 1200, 2400, 4800, 9600 default: 1200 MOUSE=D CalComp digitizer -- this is an "absolute" pointing device. Each point on the digitizer table corresponds exactly to a point on the screen. This is similar to "touch" screens in operation. This feature can be awkward to those not used to it, but may be preferred by those who use a digitizer tablet on a regular basis. Protocols: HR default: HR Baud Rate: 150, 300, 600, 1200, 2400, 4800, 9600, 19200 default: 9600 Note: This option is disabled in the beta release. MOUSE=M Microsoft compatible serial 2 button mouse, non-programmable Protocols: MI default: MI Baud Rate: 1200 default: 1200 MOUSE=MW Microsoft/Mouse System's compatible serial 2 button mouse Protocols: MI, MP, 5B default: MP Baud Rate: 1200, 9600 default: 1200 MOUSE=V Microsoft compatible serial 3 button mouse, non-programmable. If the MI protocol is used then the middle mouse button cannot be programmed as a chord. Protocols: MI, MP default: MP Baud Rate: 1200 default: 1200 MOUSE=VW Microsoft/Mouse System's compatible serial 3 button mouse Protocols: MI, MP, 5B default: MP Baud Rate: 1200, 9600 default: 1200 MOUSE=S This causes RODENT.SYS to only check for serial mice. Any other mice are ignored. This could be useful if a buss mouse interface is present, but the mouse itself is not present. This option is supplied because some motherboards and video adapters have a buss mouse interface built-in. MOUSE=X Unknown mouse. The protocol to be used must be specified. This option would be used when the mouse is known to communicate with a given protocol, but the mouse type cannot be recognized and the mouse cannot be programmed. Some protocols REQUIRE the ability to program the mouse and this ability is also used to check for the presence of the mouse. Therefore these protocols cannot be directly specified. PROTOCOL=xx This option allows the communications protocol to be specified. This is useful to select a non-default protocol and when using the MOUSE=X option. If the mouse type is known and an unsupported protocol is selected the default protocol for that mouse type will be used. This option may be specified as: PROTOCOL=MI Microsoft compatible 2 button protocol. Can be used with a 3 button mouse, but completely ignores the middle button. PROTOCOL=MP Extension to MI protocol which supports either 2 or 3 buttons. If only two buttons are present the MI protocol is more efficient. PROTOCOL=RE Relative Bit Pad One protocol, supports either 2 or 3 buttons. PROTOCOL=5B Five byte binary protocol, this protocol does not resynchronize well. It is the default for Mouse System's compatible mice, but the MM protocol is preferred (if supported by the mouse). If it MUST be used then hold the mouse still and clicking a button should cause resynchronization. Loss of synchronization does not normally occur so this is not a problem likely to be seen. This protocol supports either a 2 button or 3 button mouse. PROTOCOL=MM Mouse System's compatible protocol, supports either 2 or 3 buttons. In addition, there are two other supported protocols which cannot be specified. These protocols are inferred from the mouse type. PROTOCOL=BS Buss mouse protocol, supports either 2 or 3 buttons. This protocol is used for mouse type: MOUSE=B. PROTOCOL=HR CalComp high resolution binary digitizer protocol, supports either the 4 button puck (which may actually have 6 buttons, but two of the buttons are hardware-wired as chords of the remaining buttons) or the 16 button puck. OS/2 only supports three buttons so the extra buttons are mapped to chord clicks. This protocol is inferred from mouse type: MOUSE=D. Note: This option is disabled in the beta release. BUTTONS=# This option indicates the number of buttons to be supported. All protocols other than the MI protocol support both 2 button and 3 button mice. This option may be specified as: BUTTONS=2 BUTTONS=3 If BUTTONS=3 is specified for a 2 button mouse the mouse driver will function normally, but will report to OS/2 that there are two buttons. However, events for the third button will simply never occur. If BUTTONS=3 is specified for a 3 button mouse (the default) then all three buttons will be returned to OS/2. OS/2 treats clicking any two (or three) mouse buttons together as a "chord" click. It also handles single or double clicks and single click and drag from all three buttons. If BUTTONS=2 is specified for a 3 button mouse then mouse driver will convert pressing the middle button into a press of both left and right buttons. This means that clicking the middle button is equivalent to a "chord" click. However, if PROTOCOL=MI is specified for a three button mouse (the default is PROTOCOL=MP) this cannot be done because the Microsoft-compatible 2 button protocol is not aware of events for the middle button. In this case the middle button will simply be ignored. The included PM test program will report the number of mouse buttons as seen by OS/2. DPI=# This option allows the mouse resolution to be specified. This must be in the range 100..640 (inclusive). The default is DPI=200. Most newer mice are higher resolution (and even some of the older mice). The C9 Logitech Buss Mouse has a resolution of 320 dpi and the newer Logitech mice have a resolution of 400 dpi. The value used should be the HARDWARE resolution, many DOS mouse drivers allow the resolution to be "set" in the software -- this does not affect the actual mouse events but only their reporting by the DOS mouse driver. This value is reported to OS/2, but at this time, OS/2 does not appear to make a significant use of the value. The included PM test program will report the value as seen by OS/2. ---------------------------------- CalComp ----------------------------------- The CalComp digitizers are used with either a "4-button" puck or a "16-button" puck. However, the 4-button puck may actually have 6 buttons and the 16 button puck may only have 6 buttons. It can be difficult to tell these devices apart. However, functionally they behave differently. This driver eliminates most of those differences. Assuming six buttons, the actions taken by the driver are... .......Buttons seen by OS/2....... ...Buttons pressed... BUTTONS=3 BUTTONS=2 +---+---+---+ +---+---+---+ +---+---+ | | | | | | | | | | | | 1 | | | | L | | | | L | | | | | | | | | | | | | +---+---+---+ +---+---+---+ +---+---+ | | | | | | | | | | | | +---+---+---+ +---+---+---+ +---+---+---+ +---+---+ | | | | | | | | | | | | | 2 | | | | M | | | L | R | | | | | | | | | | | | +---+---+---+ +---+---+---+ +---+---+ | | | | | | | | | | | | +---+---+---+ +---+---+---+ +---+---+---+ +---+---+ | | | | | | | | | | | | | | 3 | | | | R | | | R | | | | | | | | | | | | +---+---+---+ +---+---+---+ +---+---+ | | | | | | | | | | | | +---+---+---+ +---+---+---+ +---+---+---+ +---+---+ | | | | | | | | | | | | | | | | L | M | | | L | R | | | | | | | | | | | | +---+---+---+ +---+---+---+ +---+---+ | | | | | 4 | | | | | | | +---+---+---+ +---+---+---+ +---+---+---+ +---+---+ | | | | | | | | | | | | | | | | L | | R | | L | R | | | | | | | | | | | | +---+---+---+ +---+---+---+ +---+---+ | | | | | | 5 | | | | | | +---+---+---+ +---+---+---+ +---+---+---+ +---+---+ | | | | | | | | | | | | | | | | | M | R | | L | R | | | | | | | | | | | | +---+---+---+ +---+---+---+ +---+---+ | | | | | | | 6 | | | | | +---+---+---+ And on pucks with more than six buttons... +---+---+---+ +---+---+---+ +---+---+ | | | | | | | | | | | | | | | | L | M | R | | L | R | | | | | | | | | | | | +---+---+---+ +---+---+---+ +---+---+ | | | | | | | | | | | | +---+---+---+ | | | 7 | | | +---+ On pucks which have four physical buttons arranged in a diamond pattern... .......Buttons seen by OS/2....... ...Buttons pressed... BUTTONS=3 BUTTONS=2 +---+ | | | | | | +---+---+---+ +---+---+---+ +---+---+ | | | | | | | | | | | | 1 | | | | L | | | | L | | | | | | | | | | | | | +---+---+---+ +---+---+---+ +---+---+ | | | | | | +---+ +---+ | | | 2 | | | +---+---+---+ +---+---+---+ +---+---+ | | | | | | | | | | | | | | | | | M | | | L | R | | | | | | | | | | | | +---+---+---+ +---+---+---+ +---+---+ | | | | | | +---+ +---+ | | | | | | +---+---+---+ +---+---+---+ +---+---+ | | | | | | | | | | | | | | 3 | | | | R | | | R | | | | | | | | | | | | +---+---+---+ +---+---+---+ +---+---+ | | | | | | +---+ +---+ | | | | | | +---+---+---+ +---+---+---+ +---+---+ | | | | | | | | | | | | | | | | L | | R | | L | R | | | | | | | | | | | | +---+---+---+ +---+---+---+ +---+---+ | | | 4 | | | +---+ On pucks which have four physical buttons arranged in a row... .......Buttons seen by OS/2....... ...Buttons pressed... BUTTONS=3 BUTTONS=2 +---+---+---+---+ +---+---+---+ +---+---+ | | | | | | | | | | | | | 1 | | | | | L | | | | L | | | | | | | | | | | | | | +---+---+---+---+ +---+---+---+ +---+---+ +---+---+---+---+ +---+---+---+ +---+---+ | | | | | | | | | | | | | | 2 | | | | | M | | | L | R | | | | | | | | | | | | | +---+---+---+---+ +---+---+---+ +---+---+ +---+---+---+---+ +---+---+---+ +---+---+ | | | | | | | | | | | | | | | 3 | | | L | | R | | L | R | | | | | | | | | | | | | +---+---+---+---+ +---+---+---+ +---+---+ +---+---+---+---+ +---+---+---+ +---+---+ | | | | | | | | | | | | | | | | 4 | | | | R | | | R | | | | | | | | | | | | | +---+---+---+---+ +---+---+---+ +---+---+ Given this button mapping, the only functional difference which distinguishes the pucks is that the 16 button puck CANNOT recognize two buttons pressed at the same time. Therefore, pressing buttons 4, 5, 6 or 7 is the ONLY way to obtain a "chord click". Notice that OS/2 regards ANY multiple button click as a chord click. However, applications CAN tell the difference if they so choose. The choices of which buttons generate which chord clicks are constrained by the design of the 4 button puck with 6 actual buttons because buttons 4 and 6 are hard-wired to generate the chords above. Therefore the actions of the 16 button puck and of button 4 have been chosen for consistency with the 4 button puck and for completeness. All buttons above 7 on the 16 button puck will be ignored. The actions taken for the first three buttons are also consistent with the actions taken by all other two and three button mice. --------------------------------- What's New --------------------------------- Release ..Date.. ..........................Changes.......................... 0.90 93/04/07 Beta of initial release with digitizer support disabled. -------------------------------- Coming Soon --------------------------------- The production release (hopefully to be released shortly) will be tested with more mice, and will include support for both CalComp and SummaGraphics digitizer tablets. ------------------------------------------------------------------------------