home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 14 Text
/
14-Text.zip
/
mouinf.zip
/
MOUINF.INF
(
.txt
)
next >
Wrap
OS/2 Help File
|
1994-05-22
|
150KB
|
3,952 lines
ΓòÉΓòÉΓòÉ 1. NOTICES & AUTHORS ΓòÉΓòÉΓòÉ
Note: Click on bitmap to see authors.
The first section Boring Legal Stuff contains necessary legal language to keep
all the attorneys happy. You may wish to skip this, unless of course you
haven't been sleeping well of late.
There is also a section Trademarks and Service Marks which is another less than
earth shattering but deemed necessary section. Again, you may choose to
disregard it without fear of repercussion.
There is a somewhat useful section called How To Best Use This Guide which
gives a first time user some hints on how to best proceed through this
labyrinth of information.
Lastly, that most important of sections Authors in which our brief moment of
glory is displayed to all who choose to venture into this panel. Also contains
a copyright notice, and our Internet addresses should you wish to contact us.
Note: All references to C: in this document assume that OS/2 is installed on
the C: partition . If this is not true, simply change C: to the partition
drive letter upon which user has installed OS/2.
ΓòÉΓòÉΓòÉ 1.1. Boring Legal Stuff ΓòÉΓòÉΓòÉ
The following paragraph does not apply to the United Kingdom or any country
where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may not apply to
you.
This publication could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time.
It is possible that this publication may contain reference to, or information
about, IBM products (machines and programs), programming, or services that are
not announced in your country. Such references or information must not be
construed to mean that IBM intends to announce such IBM products, programming,
or services in your country.
Requests for technical information about IBM products should be made to your
IBM Authorized Dealer or your IBM Marketing Representative.
References in this publication to IBM products, programs, or services do not
imply that IBM intends to make these available in all countries in which IBM
operates. Any reference to an IBM product, program or service is not intended
to state or imply that only IBM's product, program, or service may be used.
Any functionally equivalent product, program, or service that does not infringe
any of IBM's intellectual property rights or other legally protected rights may
be used instead of the IBM product, program, or service. Evaluation and
verification of operation in conjunction with other products, programs, or
services, except those expressly designated by IBM, are the user's
responsibility.
IBM may have patents or pending patent applications covering subject matter in
this document. The furnishing of this document does not give you any license to
these patents. You can send license inquiries, in writing, to the IBM Director
of Commercial Relations, IBM Corporation, Purchase, NY 10577.
IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING WITHOUT
LIMITATION, WARRANTIES OF FITNESS AND MERCHANTABILITY WITH RESPECT TO THE
INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO
LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS.
ΓòÉΓòÉΓòÉ 1.2. Trademarks and Service Marks ΓòÉΓòÉΓòÉ
Terms in this publication that are trademarks of the IBM Corporation in the
United States and/or other countries. These include, but are not limited to:
o IBM
o 8516 Touch Display
o Micro Channel
o Operating System/2
o OS/2
o Personal System/2
o PS/2
o WIN-OS/2
o Workplace Shell
o XGA
o MMPM/2
o RISC 6000
o TRACKPOINT
Other trademarks appearing in this publication are owned by their respective
companies.
Intel, and Pentium are trademarks of Intel Corporation.
Logitech, Trackman, Mouseman are trademarks of Logitech Corporation.
Mouse Systems, PC Mouse, First Mouse, PC Mouse, Little Mouse, Omni Mouse, and
White Mouse, are trademarks of Mouse Systems Corporation.
Microsoft, MS Excel, Inport, Ballpoint, and Windows are trademarks of Microsoft
Corporation.
Expert Mouse, Kensington, are trademarks of Kensington Microsystems Inc.
PC Trac, Fast Trac, MicroTrac, Microspeed, are trademarks of Microspeed
Corporation.
Thumbellina, Appoint, are trademarks of Appoint Corporation.
Mouse One, LC Mouse, CLIXes, Genius, are trademarks of Genius Inc.
Felix Mouse, and ALTRA are trademarks of ALTRA Corporation.
TIMOUSE.SYS and Travelmate are trademarks of Texas Instruments Inc.
ΓòÉΓòÉΓòÉ 1.3. How To Best Use This Guide ΓòÉΓòÉΓòÉ
This guide to analyzing pointing device problems was designed using the OS/2
2.x Information Presentation Facility (IPF). Documentation created with IPF
has an INF suffix and can be examined using the OS/2 VIEW command. The online
help for OS/2 is also created with this facility. If you are using a hard copy
print out of this document, disregard the next two paragraphs, the table of
contents will be your best bet to finding what you are looking for.
The most efficient way to utilize this guide is the use the SEARCH facility of
the VIEW command. For example, say you get a "SYS1201 VMOUSE.SYS Not
Installed..." error when booting OS/2. You could do a search on SYS1201
(select ALL SECTIONS) and this would list all topics which have the word
SYS1201 listed.
You will find that every item in the table of contents (TOC) has some
information. The easiest way to read a section is to double click on the main
TOC item and use the FORWARD & BACKWARD buttons. If you are referred to another
section, you can return to your previous position by selecting the PREVIOUS
button.
ΓòÉΓòÉΓòÉ 1.4. Authors ΓòÉΓòÉΓòÉ
COMPILED, WRITTEN, AND UPDATED BY
CRAIG S. EUBANKS
IBM OS/2 Technical Support
Internet==>CEUBANKS@VNET.IBM.COM
&
GORDON WEBSTER
IBM OS/2 Development
Internet==>GWEBSTER@BCRVM1.VNET.IBM.COM
Revision 3.0
Copyright IBM Corporation, 1993, 1994 all rights reserved
ΓòÉΓòÉΓòÉ 2. INTRODUCTION ΓòÉΓòÉΓòÉ
This document was created out of necessity generated by the activities of the
OS/2 Technical Support team at Boca Raton IBM. It is an attempt to compile all
the information related to pointing devices and the various versions of OS/2,
including 1.3, 2.0, Service Pack 1, 2.1, and 2.1 for Windows. It is hoped that
this will be of use to all those involved in the support process, as well as
any internal or external users attempting to solve their own problem.
There are both technical sections on device drivers and certain types of OEM
mice, as well as a common problem/answer section for quick reference while
working with customer problems.
This work is constantly evolving as new information comes in. As this is now
an on line document the changes will be virtually real time. Check the MOU.INF
file date If you have two or more copies. The date is the compile date of this
file (if you are using the VIEW facility). Printed versions will have the
print date on the cover. If you spot any mistakes, have updated material that
you think should be added, or would just like to make a comment or ask a
question, please contact the authors at the following Internet addresses:
o Craig can be reached at CEUBANKS@VNET.IBM.COM
o Gordon can be reached at GWEBSTER@BCRVM1.VNET.IBM.COM
The authors would like to thank Andy Frankford and Ed Lozano of the MKBCMP
Warranty Support Team for their help in converting this document from text to
the format as it now appears, and also all of those who use this document and
remind the authors of the mistakes or omissions which may still exist. We
would also like to thank Joe Celi, Antonio Arias, Albert James, Ken Burgess,
and Pat Schoeller for all their valued input.
Note: All references to C: in this document assume that OS/2 is installed on
the C: drive partition. If this is not true, simply change C: to the partition
drive letter upon which user has installed OS/2.
ΓòÉΓòÉΓòÉ 2.1. Acronyms and Their True Meaning ΓòÉΓòÉΓòÉ
o PDI port - Pointing Device Interface port. Term often used to describe mouse
port.
o COM port- Communications port. Refers to serial communications port. These
are usually numbered from 1 to 4.
o GA - General Availability. This is a term to describe an IBM product that
has moved from the Beta test stage to the ready for sale to the populace
stage.
o OEM - Original Equipment Manufacturer. Often used to refer to non-IBM
equipment or equipment manufacturers.
o PDD - Physical Device Driver.
o VDD - Virtual Device Driver.
o VDM - Virtual DOS Machine.
o VMB - Virtual Machine Boot.
o BBS - Bulletin Board System.
o PM - Presention Manager.
o DDK - Device Driver Kit.
o DAP - Developers Assistance Program (at IBM).
o IDC - Inter-Device Communication.
o MS - Microsoft.
o UART - Universal Asychronous Receiver Transmitter.
o APAR - Authorized Problem Analysis Report.
ΓòÉΓòÉΓòÉ 3. MOUSE DEVICE DRIVERS ΓòÉΓòÉΓòÉ
The OS/2 operating system provides pointing support for the following:
o IBM 8516 Touch Display
o Microsoft three-byte protocol and 100% compatible devices
o PC Mouse Systems five-byte protocol and 100% compatible devices
OS/2 2.x has two basic device drivers for pointing devices: a Physical Device
Driver (PDD) called MOUSE.SYS, and a Virtual Mouse Driver (VMD) called
VMOUSE.SYS.
There are also two other device drivers provided with OS/2, POINTDD.SYS and
PCLOGIC.SYS.
POINTDD.SYS (Pointing Device Draw) provides pointer support for OS/2 in full
screen OS/2 mode only (not used in DOS full screen).
PCLOGIC.SYS provides support for PC Mouse Systems 5-byte protocol on serial
ports only.
ΓòÉΓòÉΓòÉ 3.1. Physical Device Drivers for 2.x ΓòÉΓòÉΓòÉ
Two classes of pointing devices are supported, relative and absolute. A
relative pointing device reports relative motion ie.how far the device has
moved. An example of a relative pointing device is a mouse, or a track ball.
An absolute pointing device reports absolute positions within some predefined
work space. An example of an absolute pointing device is a touch-sensitive
screen.
Some commonly used pointing device terms and their definitions:
Term Definition
MOUSE$ The OS/2 system-provided pointing device driver name, which
is defined in the device header field of MOUSE.SYS.
PCLOGIC$ The OS/2 system-provided pointing device driver name, which
is defined in the device header field of PCLOGIC.SYS.
IDC Inter-Device Communication. This is the means for
communicating between MOUSE.SYS and other mouse device
drivers.
Device-Independent Device Driver Another way of referring to MOUSE.SYS, which
handles all the IDC interfaces for pointing devices, and
redirects those commands to the rest of OS/2.
Device-Dependant Device Driver Hardware-specific device driver that reads mouse
events and communicates with MOUSE.SYS through the IDC for
additional pointing-device support.
ΓòÉΓòÉΓòÉ 3.1.1. Generic Pointing Device Support for OS/2 2.0 and Beyond ΓòÉΓòÉΓòÉ
The OS/2 operating system provides a physical mouse device driver called
MOUSE.SYS that will attempt to detect the type of pointing device currently
installed on the system, as long as the device is 100% Microsoft compatible
(ie. 3-byte packets of data). Once it detects the existence of a particular
pointing device, it dynamically sets up support for that device. The search
order for a pointing device is as follows:
1. Pointing Device Interface (PDI) port.
2. Serial ports. COM1, COM2, COM3, & COM4.
3. Inport. (AT bus only).
4. Bus card (AT bus only).
If the physical Mouse device driver is unable to detect the presence of a
pointing device as install time, the install program will prompt the user for
pointing device information. The install program then sets the appropriate
statement for the pointing device support in the config.sys file. The physical
Mouse driver will set up to support the first pointing device that it finds, in
the case there are two on the system.
ΓòÉΓòÉΓòÉ 3.1.2. High-Level Design ΓòÉΓòÉΓòÉ
During device driver initialization time, the physical Mouse device driver
first checks to see if the TYPE= overrider has been used. If the
DEVICE=C:\OS2\MOUSE.SYS
line in the CONFIG.SYS contains a TYPE= overider, then pointing device support
is established through an IDC interface with the device-dependent device driver
using the name which follows TYPE=. The device-dependent device driver must be
loaded before MOUSE.SYS, and its placement is above MOUSE.SYS in the CONFIG.SYS
file.
If a TYPE= overrider has not been specified, it is assumed that Generic
Pointing Device Support is desired.
ΓòÉΓòÉΓòÉ 3.1.3. Physical Mouse Device Driver Considerations ΓòÉΓòÉΓòÉ
System Install ensures that physical Mouse device driver initialization takes
place prior to physical ASYNC device driver initialization (COM port device
drivers). This allows the physical ASYNC device driver to determine that it is
not responsible for servicing the port which the pointing device is installed
on, which ensures that physical Mouse device drivers are not pre-empted from
the COMx ports by the physical ASYNC device drivers.
Note: When manually changing CONFIG.SYS, the user must place the MOUSE DEVICE=
statements before ASYNC DEVICE= statements (COM.SYS, and VCOM.SYS).
ΓòÉΓòÉΓòÉ 3.1.4. Adding Support for a Unique Pointing Device (OEM) ΓòÉΓòÉΓòÉ
OS/2 provides a method for supporting additional pointing devices. Pointing
device support can be obtained by writing a device-dependent device driver for
the device. This physical device driver will communicate with the OS/2-provided
device driver MOUSE.SYS, which is the device-independent device driver, through
the IDC interfaces. For further information consult the REFERENCES section for
IBM Physical Device Driver Reference Manual.
Additional information on developing unique device drivers can be obtained
through the Developers Assistance Program at IBM. See the OEM MOUSE DRIVERS
section of this document.
ΓòÉΓòÉΓòÉ 3.2. Virtual Mouse Driver ΓòÉΓòÉΓòÉ
The Intel 80386, 80486, and above processors have a feature which allows a DOS
program to run in its own one meg address space. This effectively isolates it
from the rest of the programs running on the system. This special mode is
called the Virtual 8086 Mode, and is utilized by OS/2 to run DOS applications
in their own memory partition. This is known as a Virtual DOS Machine (VDM) in
OS/2. OS/2 can support a large number of these VDM's at one time. The DOS
programs run in their own VDM without any knowledge of other programs running
on the system.
DOS programs that write directly to the system hardware or devices are
permitted to run in a DOS session. When the program writes directly to a
device or the hardware, the operation is trapped by the kernel and routed to a
Virtual Device Driver (VDD). The VDD is a special type of driver that emulates
the functions of a particular hardware device, such as a mouse or COM port.
The VDD appears as the actual device to the application, but direct access to
the device is in reality performed through a Physical Device Driver (PDD), such
as MOUSE.SYS. The MOUSE.SYS PDD reads from and writes to the device, and
passes the results to the VDD. The VDD will then send the results to the DOS
application.
VDDs are loaded at system boot time after any PDDs, but before the Presentation
Manager shell is started. The VDD will not load if the associated PDD is not
loaded. In the case of devices, if MOUSE.SYS does not find a pointing device
on the system it will not load itself, and thus the virtual mouse driver
VMOUSE.SYS will also not be loaded by the system. This results in the "SYS1201
VMOUSE.SYS not loaded..." error. When the DOS session is exited, the VDD must
perform any clean-up that is necessary. This usually includes releasing any
allocated memory and restoring the state of the device, in this case the mouse.
In OS/2, DOS applications which require the use of a pointing device are
supported via the INT 33h interface. There are no restrictions on any use of
the INT 33H interface, even when a DOS session is in background mode. For
example this interface will perform the following functions among others:
o Position and button tracking and notification
o Selectable pixel and mickey mappings (note: a mickey is 1/80 cm)
o Pointer location and shape
o Video mode tracking
o Emulation of a light pen
MOUSE.SYS is aware of which session currently owns the pointing device. Thus
when a DOS full-screen session owns the pointing device, MOUSE.SYS notifies the
virtual device driver of mouse type events. In the case of a DOS window,
MOUSE.SYS will route events through the Presentation Manager, which in turn
will route them to the virtual mouse driver. The Mouse Exclusive Access DOS
setting can be set to ON for the DOS windowed sessions, which will then bypass
the presentation manager causing mouse events to be sent directly from
MOUSE.SYS to the virtual mouse driver. This option is useful for applications
which draw and track their own pointing device, and will cure the problem of
having two pointers (arrows) show on the screen in a DOS window.
ΓòÉΓòÉΓòÉ 3.3. Virtual Touch Device Driver ΓòÉΓòÉΓòÉ
The Virtual Touch Device Driver (VTOUCH.SYS) provides support for the INT 7FH
for multiple DOS sessions. This VDD is limited (by default) to making actual
touch XYZ data available only to full screen DOS programs because the PDD,
which handles the touch data interrupts, cannot determine which window to send
the touch to when running with the Presentation Manager session in the
foreground. The physical Mouse device driver can determine which window to
send the mouse data to because it is able to feed the single queue of the
Presentation Manager, which can then determine which window is to receive the
event. If the window is a DOS window, it calls the virtual device driver.
ΓòÉΓòÉΓòÉ 4. OEM MOUSE DRIVERS & MANUFACTURERS ΓòÉΓòÉΓòÉ
The mouse device driver is layered allowing any OEM to easily add support for
their pointing device. By writing a small mouse device dependent device driver
they can get their device to work with OS/2. There is MOUSE.SYS and
PCLOGIC.SYS source code provided in the DDK (Device Driver Kit) for developers
to reference. Please contact the OEM manufacturer to find out if they provide
a device driver for OS/2, or are in the process of developing one. Any OEM
pointing device manufacturer should be referred to the Developers Assistance
Program at IBM if they require further assistance. They should also reference
the IBM technical publications on OS/2, some of which are listed in the
REFERENCES section at the end of this document. IBM publications can be
ordered by calling one of the following numbers:
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDevelopers Assistance Program (DAP)Γöé407 - 982 - 6408 Γöé
Γöéat IBM Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIBM Device Driver Source Kit for Γöé800 - 633 - 8266 Γöé
ΓöéOS/2 (DDK) Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIBM OS/2 Information, Sales, and Γöé800 - 3IBM - OS/2 Γöé
ΓöéDAP Γöé(342-6672) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIBM PC Technical Books Hotline Γöé800 - IBM - PCTB Γöé
Γöé Γöé(426-7282) Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 4.1. Hewlett Packard ΓòÉΓòÉΓòÉ
An example of an OEM manufacturer that provides OS/2 support is Hewlett
Packard. HP provides HILMOU.SYS & NOEXBIOS.SYS device drivers. Below are the
instructions for adding support for the Hewlett Packard HIL mouse. This mouse
has its own unique connector which looks similar to a phone jack.
Customers should go to their dealer for the diskette that contains HP mouse
support. Customers may also access the files on Compuserve by typing "GO HP".
As a last resort they can call HP at HP Customer Service. The number for HP is:
o (800) 752-0900
Directions for installing a Hewlett Packard mouse and drivers.
1. Select PS/2 mouse during system installation at the Pointing Device
selection panel.
2. Copy HILMOU.SYS and NOEXBIOS.SYS to C:\OS2 (these are supplied by HP)
3. Update the CONFIG.SYS file with the following statements in the order
shown:
add DEVICE=C:\OS2\NOEXBIOS.SYS
add DEVICE=C:\OS2\HILMOU.SYS
modify DEVICE=C:\OS2\MOUSE.SYS TYPE=HILMOU$
(This line should already be in the
CONFIG.SYS but will need the TYPE=... added )
4. Save the file.
5. Reboot the system.
ΓòÉΓòÉΓòÉ 4.2. Texas Instruments ΓòÉΓòÉΓòÉ
Texas Instruments makes a series of portable computers known as the Travelmate
portables. At least one of the models, the TI-4000, uses a non-8042
mouse/keyboard controller chip for its PDI mouse port. OS/2 will not recognize
a mouse in their port, resulting in the "ERROR SYS1201 VMOUSE.SYS NOT
INSTALLED".
TI has written a driver to allow mice to run on its PDI port. Call TI at the
tech support number to obtain this driver.
TI can be reached at:
o (800) TI-TEXAS
o (817) 774-6809 (BBS)
ΓòÉΓòÉΓòÉ 4.3. Gateway ΓòÉΓòÉΓòÉ
Gateway computers offers a laptop portable called the NOMAD. This is basically
a TI-4000 internally, and thus has the problem of having the non-8042
controller chip for the mouse port.
Gateway users will need to contact Gateway to see if they offer a mouse driver
that will work with the port. Otherwise contact Texas Instruments to obtain
their TI-4000 mouse driver.
Gateway can be reached at:
o (800) 846-2302
ΓòÉΓòÉΓòÉ 4.4. Kensington Microware ΓòÉΓòÉΓòÉ
Kensington Microware offers their users extra functionality with their mice
through the use of their mouse drivers. When OS/2 2.0 was first released, they
did not have a driver to offer the same functions as had been available under
DOS. They now have a mouse driver avilable for OS/2 which offers similar
functionality that were previously available under DOS and Windows. Call
Kensington at the below number for information on how to obtain the driver.
Kensington Microware can be reached at:
o (800) 535-4242
ΓòÉΓòÉΓòÉ 4.5. Dell Computer Corp. ΓòÉΓòÉΓòÉ
Dell computer has a couple of problems which occur with OS/2 and their systems.
They provide some fixes for these on their BBS system. One known fix they
provide for OS/2 concerning a mouse problem is...
o Problems with Logitech mice (they provide Logitech mice with some of their
systems). They have a fix available on their BBS called L_MS_OS2.ZIP which
cures Logitech mice which have problems with OS/2 and Dell machines.
Dell can be reached at the following numbers:
o BBS: (512) 728-8528
o Tech Support: (800) 624-9896
ΓòÉΓòÉΓòÉ 4.6. Microspeed Corp. ΓòÉΓòÉΓòÉ
Microspeed has certain models of their trackballs which are incompatible with
OS/2 either due to it being an older model with different hardware, or that by
design the trackball was made only for Windows 3.1 (eg. the WIN-TRAC).
Microspeed has in the past been very gracious about helping their customers
resolve these problems either by exchanging hardware or providing required
assistance, thus customer should give them a call.
Microspeed can be reached at the following number:
o Tech Support: (800) 232-7888
ΓòÉΓòÉΓòÉ 4.7. Logitech Corp. ΓòÉΓòÉΓòÉ
Though all recent model, and many of the older model Logitech devices do work
with OS/2, there is often confusion during install, and sometimes problems with
Dual Boot scenarios. Logitech is also looking into developing an OS/2 driver
to provide similar functionality for their users as was available under DOS and
Windows.
Logitech can be contacted at any of the following:
o Technical Support: (510) 795-8100
o Logitech BBS: (510) 795-0408 (N,8,1, 300-2400, full duplex)
o FaxBack System: (800) 245-0000
o Internet address: Tech_support@Logitech.com
ΓòÉΓòÉΓòÉ 4.8. Kye International Corp. (Genius) ΓòÉΓòÉΓòÉ
Kye International makes the Genius series of mice.
Kye can be reached at:
o Customer Service: (714) 923-2417
ΓòÉΓòÉΓòÉ 4.9. Mouse Systems Corp. ΓòÉΓòÉΓòÉ
Mouse Systems can be reached at:
o (510) 656-1117
ΓòÉΓòÉΓòÉ 4.10. ALTRA Corp. ΓòÉΓòÉΓòÉ
ALTRA can be reached at:
o (800) 726-6153
ΓòÉΓòÉΓòÉ 4.11. Leading Edge Technology Corp. ΓòÉΓòÉΓòÉ
Leading Edge Technology makes a PS2 Style mouse (model # IOWCM-Z8) which has
been found not not to work with OS/2. If the user contacts them, they will
replace it with a working model.
Leading Edge Technology can be reached at:
o (800) 874-3340
ΓòÉΓòÉΓòÉ 5. DOS & WINDOWS MOUSE DEVICE DRIVERS ΓòÉΓòÉΓòÉ
DO
NOT
INSTALL
THEM!!!
Nuff Said...
Installing DOS or Windows drivers on your OS/2 system can cause more troubles
than any human should have to deal with. The OS/2 mouse drivers MOUSE.SYS &
VMOUSE.SYS, the OS/2 and Virtual DOS mouse drivers, provide system wide mouse
functionality including DOS Windows, DOS Fullscreen, and WINOS2 Sessions. Thus
there is no need to install any other DOS or Windows mouse drivers on the
system.
DOS and Windows drivers will not function since they will not be permitted by
OS/2 to access the mouse hardware. If you have a DOS based driver that uses
software interrupts, it will work in an OS/2 VDM, but may not provide all the
functionality that was available under DOS.
Note: If you have a Microchannel Bus machine, certain DOS mouse drivers will
work, since interupt sharing is permitted under Microchannel architecture, but
our recomendation remains that you should not install them.
ΓòÉΓòÉΓòÉ 5.1. Microsoft Mouse Drivers ΓòÉΓòÉΓòÉ
DO NOT USE THE WINDOWS INSTALL!
If you use the MS Windows install under OS/2, it will completely hose your DOS
and WINOS2 sessions. The only way to recover from this is Selective Install
(if you are lucky) or a complet reinstall.
OS/2 supplies mouse support for all parts of the system, thus it is both
unecessary and unadvisable to do this.
ΓòÉΓòÉΓòÉ 5.2. Logitech Mouse Drivers ΓòÉΓòÉΓòÉ
DO NOT USE THE WINDOWS INSTALL!
If you use the Logitech Windows install under OS/2, it will completely hose
your DOS and WINOS2 sessions. The only way to recover from this is Selective
Install (if you are lucky) or a complet reinstall.
OS/2 supplies mouse support for all parts of the system, thus it is both
unecessary and unadvisable to do this.
Logitech is purported to be developing mouse drivers for OS/2 that offer all
the 3-button functionality that is available under DOS and Windows. We suggest
that you contact them for further information.
For information on how to install Logitech devices with OS/2 see the Logitech
Section later in this document
Note: Click on the highlighted Logitech for their phone and BBS numbers.
Click on Logitech Section for more info on Logitech mice and OS/2.
ΓòÉΓòÉΓòÉ 6. MOUSE INSTALL PROCESS ΓòÉΓòÉΓòÉ
There are important differences in the install process for pointing devices
between version 2.0 and version 2.1. The changes were made in an attempt to
reduce the confusion which caused users to overide the system's choice of a
mouse driver, and resulted in the incorrect statements to be added to the
CONFIG.SYS file.
The following sections will describe the install process for:
o Version 2.0 and the differences in
o Version 2.1
and the next two sections&
o Summary of Mouse Drivers
o Other known Mouse Drivers for OS/2
tell the size, date, and location on disks of mouse drivers used with the
various releases of OS/2 from 2.0 to most recent.
ΓòÉΓòÉΓòÉ 6.1. Version 2.0 ΓòÉΓòÉΓòÉ
During the install process, the mouse physical device driver, MOUSE.SYS, will
attempt to detect a pointing device. If a device is detected, you will NOT be
shown a mouse selection panel during the processing of diskette 2. Once the
system is rebooted to finish the installation, it is highly recommended that
you do NOT go into the PM mouse panel to change anything. Many customers are
selecting a mouse from this panel and are forcing a different device type than
what was detected. A prime example of this is the Logitech Series-M mouse.
This mouse is Microsoft compatible, and will be detected automatically. The
mouse panel will read MS Serial Mouse. Many customers are then going into the
Presentation Manager panel and choosing Logitech Serial. This choice will add
the PCLOGIC.SYS driver which does NOT work for the Logitech series M-mouse.
The bottom line is that if you are not prompted for any mouse information or
have a mouse pointer during the first part of the install process, do not
change the settings in the graphical mouse selection panel (ie. If it ain't
broke, don't fix it...).
Also note that if the selective install was used for any reason, it has been
known to leave undesirable statements behind. For example, if the person by
mistake originally chose a Logitech mouse, when in fact they had a MS
compatible, then later did selective install back to a PS/2 Style pointing
device (the MS compatible selection), on occasion the statements (shown in
bold)
DEVICE=C:\OS2\PCLOGIC.SYS SERIAL=COMx (where 'x' is 1 or 2)
DEVICE=C:\OS2\MOUSE.SYS TYPE=PCLOGIC$
have been left behind. This will cause various problems when in fact the user
believes everything should be okay. Check the config.sys file and see if there
are erroneous statements.
ΓòÉΓòÉΓòÉ 6.2. Version 2.1 ΓòÉΓòÉΓòÉ
In version 2.0, many users did not realize that the system would attempt to
detect what pointing device was connected to the system, and would install the
appropriate drivers. When the panel came up asking if the choice was correct,
many users believed that it was asking them to make a selection, and thus they
did. This led to many incorrect choices due to the layout of the panel itself
and the choices it provided. There was a choice for Logitech, but this was
only for the non-Microsoft compatible versions, thus those with the more recent
Logitech mice would end up with an incorrect install if they chose the Logitech
selection.
Install for 2.1 will attempt to detect a pointing device on the system, and
then display the choice, but will display the choice on a separate panel from
the one with the available choices. This will hopefully avoid confusion for
the user. If it unable to detect the mouse, or the user wishes to see the
other available choices, a second panel will come up with the following
selections
Note: Click on mouse panel bitmap to see a list of pointing devices supported
under OS/2.
This list will give an indication of which mouse is currently selected by a
black dot next to the selection and a box around the lettering. If this looks
correct hit OK and install will continue. If this is a Selective Install, then
hit Cancel if selection is already correct or OK if a change was made.
If user is uncertain as to which selection, they can consult the Readme file
that comes with OS/2.
ΓòÉΓòÉΓòÉ 6.3. Summary of Mouse Drivers ΓòÉΓòÉΓòÉ
The following is a table of OS/2 system mouse drivers for the various releases
of OS/2 from 2.0 to current.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéMouse Driver ΓöéLocation ΓöéOS/2 ΓöéSize ΓöéDate Γöé
Γöé Γöé ΓöéVersion Γöé(bytesΓöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMOUSE.SYS ΓöéDisk 1 ΓöéOS/2 2.0 Γöé12673 Γöé3-30-92 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéVMOUSE.SYS ΓöéDisk 11 ΓöéOS/2 2.0 Γöé14064 Γöé3-30-92 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPCLOGIC.SYS ΓöéDisk 4 ΓöéOS/2 2.0 Γöé1739 Γöé3-30-92 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMOUSE.SYS ΓöéDisk 12 ΓöéOS/2 2.0 Γöé12703 Γöé10-16-92 Γöé
Γöé Γöé ΓöéSP Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéVMOUSE.SYS ΓöéDisk 12 ΓöéOS/2 2.0 Γöé14784 Γöé10-16-92 Γöé
Γöé Γöé ΓöéSP Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMOUSE.SYS ΓöéDisk 1 ΓöéOS/2 2.1 Γöé15053 Γöé4-26-93 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéVMOUSE.SYS ΓöéDisk 15 ΓöéOS/2 2.1 Γöé14688 Γöé5-4-93 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMOUSE.SYS ΓöéDisk 1 ΓöéOS/2 4-WINΓöé15053 Γöé4-26-93 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéVMOUSE.SYS ΓöéDisk 1 ΓöéOS/2 4-WINΓöé14688 Γöé5-4-93 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMOUSE.SYS ΓöéDisk 1 ΓöéOS/2 2.11 Γöé15229 Γöé1-29-94 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéVMOUSE.SYS ΓöéDisk 15 ΓöéOS/2 2.11 Γöé15680 Γöé1-29-94 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Note: If driver is packed ( extension is .sy@ ) then use UNPACK.EXE to expand
file to proper size as follows:
UNPACK A:VMOUSE.SY@ C:\OS2\MDOS
this will unapack VMOUSE.SYS and copy it to the directory c:\OS2\MDOS.
ΓòÉΓòÉΓòÉ 6.4. Other Known Mouse Drivers For OS/2 ΓòÉΓòÉΓòÉ
There are a few other non-IBM mouse drivers that are needed in certain
circumstances to run pointing devices with OS/2. If you are reading this it is
likely you know you need one of these, and this section will tell you how to
obtain the necessary driver.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéMouse Driver ΓöéDescription & Location Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMOUSE.DRV ΓöéA Windows 3.1 GA Driver used with Γöé
Γöé ΓöéOS2-4-WIN: Disk 2 Size=10672 Γöé
Γöé ΓöéDate=3-10-92. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéTIMOUSE.SYS ΓöéFor TI-Travelmate. Available from TI BBSΓöé
Γöé Γöéat 817-774-6809. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéRODENT.SYS ΓöéAn OS/2 Shareware mouse driver. Γöé
Γöé ΓöéAvailable on COMPUSERVE, Library 3 in Γöé
Γöé ΓöéOS2USER. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéL_MS_0S2.ZIP ΓöéFor Dell computers using Logitech mice. Γöé
Γöé ΓöéAvailable from Dell Tech Support. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 7. CONFIG.SYS STATEMENTS ΓòÉΓòÉΓòÉ
For most pointing devices (not including touch screens), there are basically
only three statements needed in the CONFIG.SYS file. There needs to be a full
screen device driver, a system mouse driver, and a virtual mouse driver for the
Virtual DOS Machine (VDM) sessions.
There are hundreds of pointing devices available today. Most of these claim
they are Microsoft compatible. If the device is 100% Microsoft compatible, the
OS/2 mouse device driver will support it. The installation program of OS/2 has
the ability to automatically detect Microsoft compatible mice during the
install process and then install the correct support for those mice. For those
compatible pointing devices, the MOUSE.SYS device driver will detect them
during the install process and the OS/2 install program will add the following
lines for mouse support to the CONFIG.SYS system file.
DEVICE=C:\OS2\POINTDD.SYS
DEVICE=C:\OS2\MOUSE.SYS.
DEVICE=C:\OS2\MDOS\VMOUSE.SYS
There are other pointing devices, that are not detectable by MOUSE.SYS.
Although these devices are not autodetected, they are still supported ( with
some exceptions. eg. in version 2.0 the Mouse Systems and Kensington bus/serial
mouse cards were not supported. See COMMON PROBLEMS & SOLUTIONS). The OS/2
install program will add the following lines for mouse support to the
CONFIG.SYS system file for certain undetectable pointing devices, when the
LOGITECH selection is made from the mouse installation panel:
DEVICE=C:\OS2\POINTDD.SYS
DEVICE=C:\OS2\PCLOGIC.SYS SERIAL=COMx (where 'x' is 1 or 2)
DEVICE=C:\OS2\MOUSE.SYS TYPE=PCLOGIC$
DEVICE=C:\OS2\MDOS\VMOUSE.SYS
Warning: Serial pointing device support for COM ports above COM2 is available
only on machines that allow interrupt sharing such as IBM PS/2 and EISA
machines.
The following sections contain the statements necessary for
o PDI Port Devices
o Microsoft Compatible Devices
o Mouse Systems Compatible Devices
ΓòÉΓòÉΓòÉ 7.1. PDI Port Devices ΓòÉΓòÉΓòÉ
PDI Port: For any mouse designed to run in the "PS/2" style round mouse port
(PDI port) located on the planar next to the keyboard port. Usually PS/2's but
there are more and more clones with PDI mouse ports.
Note: These devices must be Microsoft compatible to work in a mouse port on a
machine running OS/2.
DEVICE=C:\OS2\MDOS\VMOUSE.SYS
DEVICE=C:\OS2\POINTDD.SYS
DEVICE=C:\OS2\MOUSE.SYS
DEVICE=C:\OS2\COM.SYS
ΓòÉΓòÉΓòÉ 7.2. Microsoft Compatible Devices ΓòÉΓòÉΓòÉ
MS Compatible Serial: Serial mice designed to run on a communications port
(either a DB9 pin connector or DB25 pin connector) and run under the MicroSoft
INT 33 mouse interface.
DEVICE=C:\OS2\MDOS\VMOUSE.SYS
DEVICE=C:\OS2\POINTDD.SYS
DEVICE=C:\OS2\MOUSE.SYS
DEVICE=C:\OS2\COM.SYS
ΓòÉΓòÉΓòÉ 7.3. Mouse Systems Compatible ΓòÉΓòÉΓòÉ
Mouse Systems Compatible and Logitech C-series: Serial mice designed to run on
a communications port and are not run under the MicroSoft INT 33 mouse
interface.
DEVICE=C:\OS2\MDOS\VMOUSE.SYS
DEVICE=C:\OS2\POINTDD.SYS
DEVICE=C:\OS2\PCLOGIC.SYS SERIAL=COMx (where x is 1 or 2)
DEVICE=C:\OS2\MOUSE.SYS TYPE=PCLOGIC$
DEVICE=C:\OS2\COM.SYS
Note: Most newer Logitech devices are MicroSoft Compatible and will install as
such.
See the Logitech Section later in this document for more information on
Logitech mice and trackballs.
ΓòÉΓòÉΓòÉ 8. OS/2 COMPATIBLE DEVICES ΓòÉΓòÉΓòÉ
We have found that some devices are not 100% compatible and therefore are not
supported (see the Incompatible Devices for list of unsupported devices). But
for those pointing devices that OS/2 does support, the following is a list that
shows the proper configuration associated for each model. This list shows just
those pointing devices that have been tested by IBM, or are known to work, but
does not limit the support to only those that are listed. There are hundreds of
mice and trackballs on the market, some of which we have never heard of, but we
have tried to cover the most common makes and models.
Note: This list is not complete!
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription ΓöéType ΓöéModel# ΓöéConfig ΓöéButtΓöé
Γöé Γöé Γöé ΓöéType Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAppoint Mouse Pen ΓöéPS/2 ΓöéSquare Body ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAppoint Mouse Pen ΓöéPS/2 ΓöéRound Body ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAppoint Mouse Pen ΓöéSerial ΓöéRound Body ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAppoint Thumbelina ΓöéPS/2 ΓöéN/A ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAppoint Thumbelina ΓöéSerial ΓöéN/A ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéC&H Products ΓöéSerial Γöé400-501 (ps2ΓöéType 1 Γöé2 Γöé
ΓöéRollermouse Γöé Γöé400-502, bus Γöé Γöé Γöé
Γöé Γöé Γöé400-503) Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéChicony Keyboard w/ ΓöéSerial ΓöéN/A ΓöéType 3 Γöé3 Γöé
ΓöéTrackball Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCLIXes (by Genius) ΓöéSerial ΓöéCX-3500 ΓöéType 3 Γöé2/3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéDexxa Mouse ΓöéSerial ΓöéN/A ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéDexxa Mouse ΓöéSerial ΓöéN/A ΓöéType 1 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéGenius LC Mouse ΓöéSerial Γöéserial ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéGenius LC Mouse ΓöéSerial Γöéserial ΓöéType 2 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéGenius JX Mouse ΓöéSerial Γöéserial ΓöéType 2 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéGenius Mouse One ΓöéSerial Γöéserial 3B ΓöéType 3 Γöé2/3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéGenius GM-D321 ΓöéSerial ΓöéGM-D321 ΓöéType 3 Γöé2/3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéGenius Serial & PS/2ΓöéMultiple ΓöéGM-F203 ΓöéType 3 Γöé2/3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéGenius Wireless ΓöéSerial ΓöéGM-W220 ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéGenius Genie TRAC ΓöéMultiple ΓöéHI-TRAC ΓöéType 3 Γöé2/3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIBM PS/2 ΓöéPS/2 Γöé33G3835 ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIBM PS/2 ΓöéPS/2 Γöé6450350 ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIBM PS/2 "dove bar" ΓöéPS/2 Γöé33G5430 ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIBM PS/2 RISC 6000 ΓöéPS/2 ΓöéM-SB9-6MD ΓöéType 1 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIBM Trackpoint II ΓöéPS/2 ΓöéN/A ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIBM Track\Mouse ΓöéPS/2 Γöé1396670 ΓöéType 1 Γöé2 Γöé
Γöécombo Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIBM Touch Display Γöéother Γöé8516 ΓöéType 4 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéKensington Expert ΓöéSerial Γöé62368 ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéKensington Expert ΓöéPS/2 Γöé62368 ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéKensington Serial ΓöéSerial Γöé62364 ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLexmark Keyboard w/ ΓöéPDI Γöé1398155 ΓöéType 1 Γöé3 Γöé
ΓöéTrackball Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLexmark Keyboard w/ ΓöéPDI Γöé1398799 ΓöéType 1 Γöé3 Γöé
ΓöéTrackball Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLogitech Mouseman ΓöéSerial ΓöéM-MC13-DB9F ΓöéType 1 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLogitech Mouseman ΓöéSerial ΓöéM-RB24 or ΓöéType 1 Γöé3 Γöé
ΓöéCordless Γöé ΓöéM-RA12 Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLogitech Mouseman ΓöéSerial/PDIΓöéM-CJ13 ΓöéType 1 Γöé3 Γöé
ΓöéCombo Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLogitech Mouseman ΓöéBus ΓöéM-PD13-9MD ΓöéType 1 Γöé3 Γöé
ΓöéBus Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLogitech Trackman ΓöéSerial ΓöéT-CC2-9F ΓöéType 1 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLogitech Trackman ΓöéSerial ΓöéT-CA1-9F ΓöéType 2 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLogitech Series 9 ΓöéPS/2 ΓöéCE9-6MD ΓöéType 1 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLogitech Series 9 ΓöéSerial ΓöéCC-93-9F ΓöéType 2 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLogitech Series 2 ΓöéPS/2 Γöé2-7S ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLogitech Mouse ΓöéSerial ΓöéCA-93-6MD ΓöéType 2 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLogitech Mouse ΓöéSerial ΓöéP7-3F ΓöéType 2 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLogitech Clear MouseΓöéSerial ΓöéLT515 ΓöéIncompatibΓöé2/3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLogitech Kidz Mouse ΓöéSerial Γöéunknown ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMarstek ΓöéSerial ΓöéE22 ΓöéType 1 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMicrosoft Bus ΓöéBus ΓöéGreen ButtonsΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMicrosoft Inport ΓöéInport ΓöéGrey Buttons ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMicrosoft Inport ΓöéMultiple ΓöéN/A ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMicrosoft Serial ΓöéSerial ΓöéGrey Buttons ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMicrosoft Serial ΓöéSerial ΓöéN/A ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMicrosoft BallPoint ΓöéSerial Γöé11340 ΓöéType 1 Γöé2/4 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMicrosoft BallPoint ΓöéPS/2 Γöé11340 ΓöéType 1 Γöé2/4 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMicrospeed ΓöéSerial/BusΓöéN/A ΓöéType 1 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMicrospeed ΓöéSerial/BusΓöéN/A ΓöéType 1 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMicrospeed MicroTRACΓöéSerial ΓöéN/A ΓöéType 1 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMouse Systems PC ΓöéSerial Γöé402462-001 ΓöéType 3 Γöé2/3 Γöé
ΓöéMouse III Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMouse Systems LittleΓöéSerial Γöé402462-001 ΓöéType 3 Γöé2 Γöé
ΓöéMouse/PC Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMouse Systems ΓöéSerial Γöé403470-001 ΓöéType 3 Γöé2 Γöé
ΓöéOmniMouse II Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMouse Systems White ΓöéSerial Γöé403303-001 ΓöéType 3 Γöé2/3 Γöé
ΓöéMouse III Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMouse Systems ΓöéSerial ΓöéN/A ΓöéType 1 Γöé2/3 Γöé
ΓöéOptical Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMouse Systems ΓöéSerial Γöé901794 ΓöéType 2 Γöé3 Γöé
ΓöéOptical (red led) Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéVisi On Optical ΓöéSerial ΓöéM1 ΓöéType 2 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéVisi On Optical ΓöéSerial ΓöéM2 ΓöéType 2 Γöé2 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÿ
Of the above listed pointing devices, any that are of Type 1 are those that are
automatically detected by the MOUSE.SYS device driver and do not need a Device
Dependant device driver like PCLOGIC.SYS.
The IBM Trackpoint II is the pointing "stick" that comes with certain IBM
portables. It is a flexible black or red rubber piece in between the G & H
keys which moves the pointer, and looks like a pencil eraser.
There are two types of Mouse Systems Optical mice. The most recent version of
the optical mouse uses an infrared LED (not visible to the eye), has white
buttons, and has a switch for 2 or 3 button operation. There is an earlier
version of this mouse which is 3 button only, uses a red LED, and has grey
buttons. This earlier version will work as a serial mouse with OS/2 , but has
been known to have hardware problems.
Note: IBM 3-button mice operate the same as a Logitech mouse.
Note: IBM Touch Screens are not supported on family one machines.
ΓòÉΓòÉΓòÉ 8.1. CONFIG.SYS statements ΓòÉΓòÉΓòÉ
The following pages will describe the CONFIG.SYS statements for devices
utilizing different types of protocol. For those devices which do not need a
custom driver, there are basically three sets of statements, Type 1, Type 2,
and Type 4. A Type 3 device is one which can use more than one protocol,
usually both Microsoft 3-byte and Mouse Systems 5-byte compatible.
Of the listed pointing devices, any that are of Type 1 are those that are
automatically detected by the MOUSE.SYS device driver and do not need a Device
Dependant device driver like PCLOGIC.SYS.
Type 1 devices are those which are Microsoft Compatible (3 byte).
Type 2 devices are those which are Mouse Systems Compatible (5 byte).
ΓòÉΓòÉΓòÉ 8.1.1. Type 1 CONFIG.SYS Statements ΓòÉΓòÉΓòÉ
These statements are for any device which is 100% Microsoft compatible. Only
supports 2 button mode.
Note: All three buttons will be enabled for Logitech Series-M 3-button mice
only, and only in OS/2 version 2.1.
DEVICE=C:\OS2\MDOS\VMOUSE.SYS
DEVICE=C:\OS2\POINTDD.SYS
DEVICE=C:\OS2\MOUSE.SYS
ΓòÉΓòÉΓòÉ 8.1.2. Type 2 CONFIG.SYS Statements ΓòÉΓòÉΓòÉ
These are the correct statements for any mouse which uses the Mouse Systems
mode. These are generally 3-button mice, but do not have to be such. Many of
the older Logitech devices will use these statements.
DEVICE=C:\OS2\MDOS\VMOUSE.SYS
DEVICE=C:\OS2\POINTDD.SYS
DEVICE=C:\OS2\PCLOGIC.SYS SERIAL=COMx
DEVICE=C:\OS2\MOUSE.SYS TYPE=PCLOGIC$
( where 'x' is the COM port number. Either 1 or 2)
ΓòÉΓòÉΓòÉ 8.1.3. Type 3 CONFIG.SYS Statements ΓòÉΓòÉΓòÉ
o If the mouse is set on 2 button mode or Microsoft mode then use the Type 1
configuration.
DEVICE=C:\OS2\MDOS\VMOUSE.SYS
DEVICE=C:\OS2\POINTDD.SYS
DEVICE=C:\OS2\MOUSE.SYS
o If the mouse is set on 3 button mode or Mouse Systems mode, use the the Type
2 configuration.
DEVICE=C:\OS2\MDOS\VMOUSE.SYS
DEVICE=C:\OS2\POINTDD.SYS
DEVICE=C:\OS2\PCLOGIC.SYS SERIAL=COMx
DEVICE=C:\OS2\MOUSE.SYS TYPE=PCLOGIC$
( where 'x' is the COM port number. Either 1 or 2)
ΓòÉΓòÉΓòÉ 8.1.4. Type 4 CONFIG.SYS Statements ΓòÉΓòÉΓòÉ
These are the statements which are needed in the CONFIG.SYS file for the IBM
8516 Touch Screen. This device is only supported on Family 2 machines (Micro
Channel Bus).
DEVICE=C:\OS2\MDOS\VMOUSE.SYS
DEVICE=C:\OS2\POINTDD.SYS
DEVICE=C:\OS2\MDOS\VTOUCH.SYS
DEVICE=C:\OS2\PDITOU02.SYS CODE=C:\TOUC021D.BIN INIT=C:\TOUCH.INI
DEVICE=C:\OS2\TOUCH.SYS TYPE=PDITOU$
RUN=C:\OS2\CALIBRAT.EXE -C C:\CALIBRAT.DAT
DEVICE=C:\OS2\MOUSE.SYS TYPE=PDIMOU$
ΓòÉΓòÉΓòÉ 8.2. Pointing Devices Incompatible with OS/2 ΓòÉΓòÉΓòÉ
The following have been tested or confirmed by IBM to be incompatible with OS/2
2.x. They will likely need their own driver to operate with OS/2, which will
be up to the manufacturer.
Note: This list is not complete.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription ΓöéType ΓöéModel # ΓöéButtons Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMicrospeed TrackballΓöéBus Γöé9037 Γöé3 Γöé
Γöé(older model. check Γöé Γöé Γöé Γöé
Γöémod#) Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMouse Systems ΓöéBus Γöé903573-001/a ΓöéN/A Γöé
ΓöéSerial/Bus card as Γöé Γöé Γöé Γöé
Γöébus card Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéProhance Power MouseΓöéSerial ΓöéN/A Γöé40 Γöé
Γöé100 Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMicrotouch UnMouse ΓöéSerial ΓöéUN2000 Γöé1/2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMicrospeed WinTrac ΓöéSerial ΓöéN/A Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLogitech Clear MouseΓöéSerial ΓöéLT515 Γöé2/3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéALTRA Felix ΓöéSerial ΓöéPC-100 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLeading Edge ΓöéSerial ΓöéI0WCM-Z8 Γöé2 Γöé
ΓöéTechnology PS2 StyleΓöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéKurta Digitizing ΓöéSerial/BΓöéN/A Γöé4 Γöé
ΓöéTablet (all models) Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéSummagraphics ΓöéSerial/BΓöéN/A Γöé4 Γöé
ΓöéDigitizing Tablet Γöé Γöé Γöé Γöé
Γöé(all models) Γöé Γöé Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Note: IBM Touch Screens are not supported on family one machines.
ΓòÉΓòÉΓòÉ 9. COMMON PROBLEMS & SOLUTIONS ΓòÉΓòÉΓòÉ
The following sections describe common mouse problems and solutions which have
been discovered since the General Availability (GA) release of OS/2 2.0. This
information is chronological by section, in that it starts with Version 2.0 GA,
then has a Service Pack 1 section, a Version 2.1 GA section, and OS/2 2.1 for
Windows.
Just because the problem you are looking at is in a later version, does not
mean that the solution from a previous section will not apply.
ΓòÉΓòÉΓòÉ 9.1. Version 2.0 GA ΓòÉΓòÉΓòÉ
The problems discussed in this section were found in the initial release of
OS/2 2.0, but are not necessarily limited to that release.
ΓòÉΓòÉΓòÉ 9.1.1. No mouse pointer or movement ΓòÉΓòÉΓòÉ
o Problem:
No mouse pointer movement or no mouse pointer. An error is received upon
boot up: SYS1201 VMOUSE.SYS not installed...
o Explanation:
Note: This does not mean that VMOUSE.SYS was not installed when OS/2 was
installed, rather it means that at boot time the physical mouse driver
MOUSE.SYS did not load itself for some reason, and thus the virtual DOS mouse
VMOUSE.SYS was not "installed" since it was not needed.
This means that the MOUSE.SYS mouse driver was installed, but could not find
a pointing device on the system, thus the virtual mouse driver for DOS VDM's
"VMOUSE.SYS" was not installed. If it can not find a connected mouse, then
it will not install VMOUSE.SYS (It does not mean that vmouse.sys was not
found as the error implies). Either the install program could not correctly
determine what type of mouse it was, or could not determine that a mouse was
indeed present.
o Resolution(s):
This problem can be due to one of the following:
1. An unsupported type of mouse. Check to see if there are any dip
switches on the mouse. Some mice have setable switches that put it into
MicroSoft Mouse emulation mode. Also some mice have switches for either
2 or 3 button mode. Switch must be in two button mode.
2. If this is a dual boot machine, make sure the user is NOT loading the
DOS MOUSE.SYS or DOS Device Dependant drivers in place of the OS/2 mouse
drivers.
3. If there was mouse support during the graphical install portion of the
installation process (after first reboot), then mouse driver was
probably changed from the mouse driver that OS/2 had already chosen.
Run the Selective Install program found in the OS/2 System/System Setup
folder and choose a different driver, or edit CONFIG.SYS with correct
lines.
4. An interrupt conflict. Check the interrupts (see IRQ Settings). On an
AT bus system, a serial mouse will only install on COM1 and COM2, and
only if COM1 and COM2 are at the standard I/O addresses and IRQs: COM1=
3F8, IRQ4 and COM2= 2F8, IRQ3. See "Serial Communications and OS/2 2.x"
(in REFERENCES) for a detailed review of Interrupts and OS/2.
5. A bus mouse that is not being detected. See next heading.
ΓòÉΓòÉΓòÉ 9.1.2. A bus mouse won't install ΓòÉΓòÉΓòÉ
o Problem:
A bus mouse won't install.
o Explanation:
There are a myriad of reasons as to why a bus card won't install, ranging
from incompatibility to IRQ conflicts. Work through the possible solutions
below. Please keep in mind that other devices on the system may use same
interupt or address. These devices include sound cards, SCSI cards, and
modem cards among others.
o Possible Solution(s):
This may be due to one of the following:
1. Bus mouse cards which have setable interrupts on the card. These
usually are set at interrupt 2 which is often either a system interrupt,
or on some systems is re-mapped to irq 9. set the interrupt to irq 5
(this is only if they do not have a second printer on lpt2). this
should solve problem. If they have a second printer on lpt2 then they
are out of luck since most cards only give the choices of 2-5, and 3 and
4 are reserved for com1 and com2.
2. Some bus mouse connections use IRQ0 which is the same as that used by
the system timer. This is common when the mouse port is on the
motherboard. A serial connection adapter can be used to get around this
(ie. using the mouse as a serial mouse versus in the mouse port).
3. The MS Bus Mouse and the MS Inport Mouse (Grey Button) require a special
card that only works on an AT style bus. This has IRQ jumper settings
for 2-5. use IRQ5 when possible.
4. There is a problem with the Mouse Systems Serial/Bus card. This results
in the system not "seeing" the mouse at install and thus it will not
work. The problem is due to the particulare UART used on this card.
The card can be used as a serial card using the standard addresses for
COM1 : COM2. Most of their mice conform to the Microsoft standard, and
thus can be used without the card in a standard 9-pin serial port.
Note: There is a shareware mouse driver for OS/2 called RODENT which
will work with this card.
5. Some Kensington Expert Bus Mice are not working. The mouse card is
plugged into the bus and set for IRQ 10 and address 0338. The OS/2
mouse driver available in later releases of OS/2 will work with this
card, and Kensington now also provides mouse drivers for OS/2.
ΓòÉΓòÉΓòÉ 9.1.3. Hewlett Packard HIL mouse will not work with OS/2. ΓòÉΓòÉΓòÉ
o Problem:
Hewlett Packard HIL mouse will not work with OS/2.
o Explanation:
The HP mouse will not work with OS/2 without its own drivers. HP provides
HILMOU.SYS & NOEXBIOS.SYS device drivers. Below is the instructions for
adding support for the Hewlett Packard HIL mouse. This mouse has its own
unique connector which looks similar to a phone jack.
o Solution:
Customers should go to their dealer for the diskette that contains HP mouse
support. Customers may also access the files on Compuserve by typing "GO HP".
As a last resort they can call HP at HP Customer Service. The number for HP
is:
- (800) 752-0900
Directions for installing a Hewlett Packard mouse and drivers.
1. Select PS/2 mouse during system installation at the Pointing Device
selection panel.
2. Copy HILMOU.SYS and NOEXBIOS.SYS to C:\OS2 (these are supplied by HP)
3. Update the CONFIG.SYS file with the following statements in the order
shown:
add DEVICE=C:\OS2\NOEXBIOS.SYS
add DEVICE=C:\OS2\HILMOU.SYS
modify DEVICE=C:\OS2\MOUSE.SYS TYPE=HILMOU$
(This line should already be in the
CONFIG.SYS but will need the TYPE=... added )
4. Save the file.
5. Reboot the system.
ΓòÉΓòÉΓòÉ 9.1.4. Mouse pointer will not move ΓòÉΓòÉΓòÉ
o Problem:
Get a pointer on the screen, but when mouse is moved there is no movement or
response from the pointer on the screen.
o Explanation:
This is a classic symptom of an interrupt conflict. The mouse was installed
(thus the pointer on the screen), but another device has stolen the interrupt
away from the mouse so when it is moved nothing happens.
o Solution:
You will need to figure out what is causing the conflict. If it is a bus
card, there should be settings on the card to allow you to choose other IRQs.
See section IX for standard system interrupt mappings. This will help in
deciding a free interrupt to use. IRQ5 is often a safe choice if there is
not a second printer on LPT2. If the mouse is in a serial port, check the
other devices on the machine. Modem cards, Tape backup devices, Soundblaster
cards, and other ASYNCH communications devices may have preset interrupts on
their cards which conflict with the standard IRQs assigned to COM1 and COM2.
As a last resort, you may have to ask them to remove all the other cards on
the system one at a time to see who the culprit is.
Note: For further assistance with interrupt problems, refer to the "Serial
Communications and OS/2 2.x" document (see REFERENCES).
ΓòÉΓòÉΓòÉ 9.1.5. IBM mouse is not working, or is giving "wild mouse" or intermittent behavior. ΓòÉΓòÉΓòÉ
o Problem:
IBM mouse is not working, or is giving "wild mouse" or intermittent behavior.
o Explanation:
Some of the IBM mice with a black roller ball that are manufactured in Taiwan
have hardware specification deficiencies.
o Solution:
Replace mouse with a grey ball IBM mouse, or any MS compatible mouse.
ΓòÉΓòÉΓòÉ 9.1.6. On a 3 button mouse, only 2 of the buttons will work. ΓòÉΓòÉΓòÉ
o Problem:
On a 3 button mouse, only 2 of the buttons will work.
o Explanation:
The OS/2 mouse driver only supports 2 button mice, thus on a 3 button mouse
only two of the buttons will function. Effectively the 3 button mouse acts
as a 2 button type.
o Solution:
Contact the manufacturer to see if they have or are currently developing
their own drivers for OS/2 to allow three button functionality. Otherwise
for the time being use as a 2 button mouse.
ΓòÉΓòÉΓòÉ 9.1.7. Prohance Power Mouse 100 will not work with OS/2. ΓòÉΓòÉΓòÉ
o Problem:
Prohance Power Mouse 100 will not work with OS/2.
o Explanation:
This is a programmable mouse with over 40 buttons on it, which allows it to
emulate not only all mouse functions, but also all keyboard functions. It
can be tailored so that a specific button will perform a certain operation,
based on which application is currently running. This of course requires its
own special set of drivers and software programs. This mouse is not
Microsoft compatible.
o Solution:
At this time Prohance has no OS/2 device driver for OS/2. The customer way
wish to write/call Prohance and ask them to develop drivers for OS/2. In the
mean time advise them to get a standard serial mouse to enable them to be
able to have a mouse on their system.
ΓòÉΓòÉΓòÉ 9.1.8. Unattended start mode resident on MOD 90 and 95 disables mouse ΓòÉΓòÉΓòÉ
o Problem:
Unattended start mode resident on MOD 90 and 95 disables mouse
o Explanation:
If the unattended start mode is set on a mod 90 or 95 and the password is not
typed in prior to the mouse device driver being loaded, the system will come
up, but an error message comes up from config.sys "sys1201
C:\OS2\MDOS\VMOUSE.SYS device driver in that path was not installed......
ignored,press enter,". If the password is then typed in, the system will
continue to come up but the mouse is totally disabled in the workplace shell.
If the unattended start mode password is typed prior to the boot manager 's
time out, then the mouse works correctly.
Note: This problem is a permanent restriction.
The 8042 chip controller handles both the keyboard and mouse ports. By
setting a power-on password, I/O is blocked from this chip. User key
sequences are internally buffered and compared against the password stored in
CMOS. Once a match is made, the keyboard and mouse ports are again enabled.
The MOUSE.SYS and any other mouse driver needs to access this port in order
to load. When it is locked, it cannot.
Unfortunately, this feature is not of much use for systems with mice. Both
the mouse and the keyboard ports are locked by the 8042 controller chip.
o Solution:
1. Make sure you enter the password prior to OS2LOGO "Loading, Please
Wait".
2. Add PAUSEONERROR=NO to CONFIG.SYS. This will not allow mouse device
drivers to load, but will allow system to boot without hitting enter key
at error messages.
ΓòÉΓòÉΓòÉ 9.1.9. When in net server mode the mouse device driver will not load. ΓòÉΓòÉΓòÉ
See previous problem Unattended start mode resident on MOD 90 and 95 disables
mouse
ΓòÉΓòÉΓòÉ 9.1.10. The mouse will not work after a resume from power down on L40SX or other laptop. ΓòÉΓòÉΓòÉ
o Problem:
The mouse will not work after a resume from power down on L40SX or other
laptop.
o Explanation:
This is due to a problem with the 8042 controller chip on the PDI port. This
is fixed in version 2.1 Serial, bus, and inport mice will still function
after a power down/ resume as they do not access the system through the 8042
controller chip.
o Solution:
User must upgrade to version 2.1. The only other solution is to switch to a
serial, bus, or inport mouse, as they are not affected by the 8042 controller
chip.
ΓòÉΓòÉΓòÉ 9.1.11. A serial mouse won't work even though the IRQs check out. ΓòÉΓòÉΓòÉ
o Problem:
A serial mouse won't work even though the IRQs check out.
Additional Problem Determination:
1. If the mouse is attached to COM3 or COM4, it will not work at this time.
We only support attachment to COM1 and COM2.
2. If the mouse is attached to COM1 or COM2, verify that the com port is at
the standard I/O address and IRQ.
3. Issue a MODE COMx (where x is 1 or 2) from an OS/2 or DOS command
prompt. This is a test of the COM ports:
a. If it reports that the port (the one the mouse is attached to) is NOT
available, then MOUSE.SYS is LOADED. This means that the drivers
are correct; don't change the CONFIG.SYS statements.
b. If it reports the baud rate and all the other COM port parameters,
then MOUSE.SYS did not recognize the mouse and did NOT Load. See
"Serial Communications and OS/2 2.x" INF file for more information.
Note: If com problem suspected consult "Serial Communications and OS/2 2.x"
document (see REFERENCES) steps to resolve problem.
ΓòÉΓòÉΓòÉ 9.1.12. Mouse Systems bus mice will not work under OS/2 at all, including during install. ΓòÉΓòÉΓòÉ
o Problem:
Mouse Systems bus mice will not work under OS/2 at all, including during
install.
o Explanation:
The Mouse Systems Serial/Bus card (MSC 903573-001) will not work with OS/2
when configured as a bus card, at this point in time. This seems to be due
to an addressing problem. It is likely that it will require either it's own
driver, or mouse.sys to be modified for it to work. The card will work as a
serial card configured for COM1 OR 2 however, and thus for now should be used
as such if possible.
o Solution:
Card should be removed, and reconfigure it as COM1 or 2 and re-install it as
a serial pointing device. Most of the Mouse Systems mice will operate with
the Microsoft standard, and can be used as serial mice with or without the
card. They come with a DB-9 connector, but if the customer only has a 25 pin
serial port on machine, they will need an adapter. If the mouse has a
2-button/3-button switch, it must be set to the 2-button position. Install
as a serial pointing device. If mouse still does not work, it may be that it
is one of their older models which do not operate with the MS standard INT33
interrupt. Check the list in this document or have customer call Mouse
Systems.
ΓòÉΓòÉΓòÉ 9.1.13. Kensington bus mice will not work under OS/2 at all, including during install. ΓòÉΓòÉΓòÉ
o Problem:
Kensington bus mice will not work under OS/2 at all, including during
install.
o Explanation:
The Kensington Serial/Bus card will not work with OS/2 when configured as a
bus card, at this point in time. This seems to be due to an addressing
problem similar to the Mouse Systems problem. The card will work as a serial
card however, and thus for now should be used as such if possible.
Kensington has a driver for OS/2 in beta test as of this writing, and it
should be available soon. This driver will allow the bus card to work with
OS/2.
o Solution:
Card should be removed, and reconfigure it as COM1 or 2 and re-install it as
a serial pointing device. Kensington mice will operate with the Microsoft
standard, and can be used as a serial mouse or in the PDI port with or
without the card. They come with a DB-9 connector, but if the customer only
has a 25 pin port on machine, they will need an adapter. Note that there are
dip switches on these trackballs which should be set to click lock positions
as explained in their instructions. Customer should contact Kensington to
see when their mouse driver will be available.
ΓòÉΓòÉΓòÉ 9.1.14. After performing dual boot to DOS, Logitech mouse does not work. ΓòÉΓòÉΓòÉ
o Problem:
After performing dual boot to DOS, Logitech mouse does not work.
o Explanation:
Some Logitech mice have "memory" that remembers the mode it was in
previously. Often while in DOS, these will be in "Mouse Systems Protocol" (5
byte, 1200 baud) and need to be returned to "Microsoft Protocol".
o Solution:
Before performing the dual boot, open a DOS window or full screen and type
MOUSE PC. (If the mouse is in COM2, type MOUSE 2 PC.) You can also perform
a cold boot if this command does not work, this should allow the mouse to
reset.
Note: must be using the mouse.com that came with the mouse (primarily
Logitech), or the command will not work.
ΓòÉΓòÉΓòÉ 9.1.15. No mouse pointer in a VMB (Virtual Machine Boot). ΓòÉΓòÉΓòÉ
o Problem:
No mouse pointer in a VMB (Virtual Machine Boot).
o Explanation:
The 80386 virtual 8086 mode supports execution of 8086 or 8088 programs in a
protected-mode environment. Virtual 8086 mode enables system software to
emulate an 8086 environment with a "virtual Machine. the 80386 hardware
provides an encapsulated virtual 8086 environment, while system software
controls the external interfaces of the virtual machine, such as I/O devices
and interrupts. The booted DOS in a VMB session receives mouse support
services from its VDM environment ( assuming default settings). DOS should
not load its own mouse driver, it may cause an error in the VDM. O S/2
provides alternative 'stub' drivers to avoid this problem. The mouse driver
is call MOUSE.COM and is located in the OS2\MDOS subdirectory.
o Solution:
Make sure that they are using the MOUSE.COM provided in OS2\MDOS
subdirectory.
ΓòÉΓòÉΓòÉ 9.1.16. The mouse gets out of sync on a 50 MHz Systems (AT bus). ΓòÉΓòÉΓòÉ
o Problem:
The mouse gets out of sync on a 50 MHz Systems (AT bus).
o Explanation:
There have been some intermittent problems with AT-style bus machines with a
mouse. The mouse can get out of synch. Input will function through the
keyboard and the mouse, but it is recommended to shutdown the system and
restart to "resynch" the mouse.
o Solution:
Shutdown system to resynch the mouse.
ΓòÉΓòÉΓòÉ 9.1.17. The mouse pointer suddenly zips over to the side of the screen and hangs there, no longer ΓòÉΓòÉΓòÉ
o Problem:
The mouse pointer suddenly zips over to the side of the screen and hangs
there, no longer responding to any mouse movements. Sometimes Windows will
open and close when mouse is moved, or pointer will only move up and down the
side. This has been given the dubious moniker of "Wild Mouse". In most
cases, a cold boot has been the only remedy.
o Explanation:
This is caused by a hardware glitch and cannot be prevented from happening,
but can be recovered from without a cold boot being required by using the
newest version of the mouse driver (dated 9/9/92 or later), which is also in
the service pack.
o Solution:
Obtain 9/9/92 or later MOUSE.SYS. This will be in the service pack.
ΓòÉΓòÉΓòÉ 9.1.18. The PS/2 Mouse on a PS/2 machine is responding too slow. ΓòÉΓòÉΓòÉ
o Problem:
The PS/2 Mouse on a PS/2 machine is responding too slow.
Solution:
Obtain 9/9/92 or later MOUSE.SYS. This will be in the service pack for 2.0.
ΓòÉΓòÉΓòÉ 9.1.19. Clix mouse (Genius Clix) will not work. ΓòÉΓòÉΓòÉ
o Problem:
Clix mouse (Genius Clix) will not work.
o Solution:
The Clix mouse is a Genius clone mouse and needs the following lines inserted
into the CONFIG.SYS file
DEVICE=C:\OS2\PCLOGIC.SYS SERIAL=COM1
DEVICE=C:\OS2\MOUSE.SYS TYPE=PCLOGIC$
After reboot the mouse should work.
ΓòÉΓòÉΓòÉ 9.1.20. Clix 3-button MS-compatible mouse not being recognized by OS/2. Get SYS1201 ERROR. ΓòÉΓòÉΓòÉ
o Problem:
Clix 3-button MS-compatible mouse not being recognized by OS/2. Get SYS1201
ERROR.
o Explanation:
This Clix mouse is a 3 button mouse. It has a switch to make it work as a 2
or 3 button mouse. The 2-button state is Microsoft compatible, the 3 button
state is non-Microsoft compatible.
o Solution:
Once switch is changed to the 2-button setting mouse should work fine. You
may need to reboot for this to take effect.
ΓòÉΓòÉΓòÉ 9.1.21. Toshiba Docking Station exhibits "Wild Mouse" symptoms. ΓòÉΓòÉΓòÉ
o Problem:
Toshiba Docking Station exhibits "Wild Mouse" symptoms.
o Explanation:
The Toshiba Docking Station allows a portable to be connected to a main frame
or LAN. The mouse must be unplugged from the back of the portable and
plugged into the docking station mouse port. The Docking station will exhibit
the wild mouse symptoms when mouse is unplugged and replugged back into the
docking station port., because this allows the mouse byte information to get
out of synch. This is known as a "hot plug mouse" problem.
o Solution:
The most current mouse driver, dated 9/9/92 (or later), will allow this
particular version of the wild mouse behavior to reset. This driver is in
the service pack. A future release of the mouse driver will allow all hot
plug situations to exist with no errant behavior (ie. you will be able to
unplug your mouse and plug it back in with out having to reboot in order to
regain the mouse).
ΓòÉΓòÉΓòÉ 9.1.22. When using touch screen device cannot get mouse to work, or get wild mouse type behavior. ΓòÉΓòÉΓòÉ
o Problem:
When using touch screen device cannot get mouse to work, or get wild mouse
type behavior.
o Explanation:
This is due to a hardware compatibility problem and is a permanent
restriction. Since there is no real standard to which mouse hardware is
written, the data rates and protocols vary widely and is really up to the
manufacturer. The IBM touch screens are designed to work with the IBM grey
ball mice only.
The 8516/Touch Select drives its mouse port slightly differently that the
planar does. The planar keyboard/mouse (8042) controller sits with both the
keyboard and the mouse enabled, ready to accept input from either. When one
device starts to give a report, it disables the other by inhibiting it and
driving the clock line low. Generally speaking, although it can accept the
input from only one device at a time, due to the low data rates and small
amount of processing of the data (just reading in the bytes, checking parity
and putting them in an output register and raising an interrupt line) data
reports are never lost from either device.
With the 8516, things are a lot different, as the same controller handling
the mouse input is also doing all the signal processing and calculations to
convert the strain gauge values to x,y,z reports. The end result is that the
reading of the mouse port is at the end of a priority list, which mainly
consists of things that must be done to handle the touch screen part. Only
when there is no higher priority touch screen activity, does it go and poll
the mouse port for data. To keep the mouse quiet, it keeps it inhibited by
driving the clock line low. So when it has finished the touch chores, it
de-inhibits the mouse by raising the clock line, and then waits for the mouse
to give a report if it has one. It only waits so long, before being called
back to doing the touch screen processing which is done off a timer
interrupt. The polling thus happens periodically but it is done frequently
enough to cope with all but the highest mouse report rate. Where it fails
though, is when the mouse is not quick enough off the mark to notice the
clock line going high and give its report in time before the line is raised
again as the controller handles the touch screen.
With the black ball mouse, the 'window of opportunity' was extended
sufficiently to allow it work. At the time, we thought that this was the same
problem with the Microsoft Mouse, as it seemed to exhibit the same behavior,
but this was a red herring and the real reason was that the spare two bits in
byte 0 of its report were set differently from the IBM mice.
o Solution:
Use an IBM grey ball mouse.
ΓòÉΓòÉΓòÉ 9.1.23. Chicony keyboard w/built in trackball. Trackball not working or get SYS1201 error. ΓòÉΓòÉΓòÉ
o Problem:
Chicony keyboard w/built in trackball. Trackball not working or get SYS1201
error.
o Explanation:
The Chicony keyboard w/trackball comes with DOS mouse driver that allows you
to set the mouse mode. The mouse may be set in a mode which is not compatible
with the current installed OS/2 mouse driver configuration.
o Solution:
Use the setup program in real DOS provided with the keyboard to determine the
current mode of the keyboard trackball.
If the trackball is set to Mouse Systems type of device (ie. Type 2), then
edit the CONFIG.SYS file in the root directory as shown below:
1. Change the line that reads
DEVICE=C:\OS2\MOUSE.SYS
to read
DEVICE=C:\OS2\MOUSE.SYS TYPE=PCLOGIC$
2. Just above this line add the following line
DEVICE=C:\OS2\PCLOGIC.SYS SERIAL=COMx (where x is 1 or 2)
3. Save CONFIG.SYS file, and reboot computer.
If trackball is set as Microsoft compatible (ie. Type 1 device), make sure
the CONFIG.SYS line for the MOUSE.SYS driver reads as follows:
DEVICE=C:\OS2\MOUSE.SYS
ΓòÉΓòÉΓòÉ 9.1.24. When mouse set as left handed on desktop, will not be set in Win-OS2, or if set both on desktop ΓòÉΓòÉΓòÉ
o Problem:
When mouse set as left handed on desktop, will not be set in Win-OS2, or if
set both on desktop and in Win-OS2 and a seamless Windows app is run on
desktop, mouse reverts to right handed mouse.
o Explanation:
In both the GA and Service Pack releases of OS/2, when the mouse is set as
lefthanded on the desktop it does not change it automatically in Win-OS2.
Once it is changed, if a seamless Windows app is run on the OS/2 desktop, it
is changed back to right handed by the desktop settings because it does not
know that it has already been toggled to left handed by the WIN-OS2 settings.
o Solution:
This is fixed in 2.1, but for now there is nothing that can be done. If the
user chooses to run all Windows applications seamlessly on the desktop, then
if they DO NOT set mouse as left handed in WIN- OS/2, it will be lefthanded
when running in the seamless window.
ΓòÉΓòÉΓòÉ 9.1.25. Mouse plugged into PDI mouse port on non IBM machines does not work or exhibits intermittent or ΓòÉΓòÉΓòÉ
o Problem:
Mouse plugged into PDI mouse port on non IBM machines does not work or
exhibits intermittent or flaky behaviour.
o Explanation:
The Mylex MNE-486-33 Motherboard among others, has a compatibility issue at
their end (ie: they use a 8242 chip as the keyboard, mouse port controller).
Any of the mouse ports that use a non 8042 chip will not always respond
properly to mouse input, or the mouse driver may not even recognize the there
is a mouse on the system. Texas Instruments and Packard Bell also use a
non-8042 mouse port controller on some of their machines.
o Solution:
Use a serial or bus mouse. In the case of Texas Instruments, they have
developed their own OS/2 mouse driver. For Packard Bell see the section
titled same.
ΓòÉΓòÉΓòÉ 9.1.26. The OS/2 2.0 Toolkit Device Driver Documentation Incorrect ΓòÉΓòÉΓòÉ
o Problem:
The OS/2 2.0 Toolkit documentation, specifically the manual "OS/2 2.0
Physical Device Driver Reference" was not changed to reflect the code change
made in touch display drivers.
o Explanation:
The mouse IDC, Process_Absolute, has been changed in OS/2 2.0 because a
defect was raised for the IBM Touch Display support added to 2.0. The change
was to remove the function where the MOUSE.SYS device driver would check the
movement of the mouse pointer against the button mask that was passed in and
change that mask if there was a discrepancy. This was deemed in error since
there are occasions where the device dependent driver may want to pass these
bogus values up the chain to running applications. The OS/2 2.0 Toolkit
documentation, specifically the manual " OS/2 2.0 Physical Device Driver
Reference" was not changed to reflect the code change. In chapter 12,
Physical Mouse Device Driver in the Mouse IDC section, on page 12-3 there is
a reference to the "EVENT" field that should be changed.
o Solution:
Remove / Ignore the following sentence. The event field should never
indicate that motion was associated with the event. MOUSE$ determines if
motion occurs.
ΓòÉΓòÉΓòÉ 9.1.27. In AUTOCAD, ATI mouse responds differently than other 3 button mice. ΓòÉΓòÉΓòÉ
o Problem:
In AUTOCAD, ATI mouse responds differently than other 3 button mice.
o Explanation:
Logitech serial mouse uses buttons 1 : 2 normally on desktop, but in autocad
logitech uses all 3 buttons. In autocad, uses button 3 to call up the popup
menu .
The ATI 3 button mouse has #2 button non-functional on desktop, and button 2
stays non- functional even in autocad. can not get popup menu with #2 button
(or any other for that matter).
o Solution:
If shift key is held down and hit button 2, then can get the popup menu with
no problem.
ΓòÉΓòÉΓòÉ 9.1.28. Outside vendor writes a pointing device driver but mouse won't work and gets no other errors. ΓòÉΓòÉΓòÉ
o Problem:
Outside vendor writes a pointing device driver but mouse won't work and gets
no other errors.
o Explanation:
Prodigy wrote their own cad driver for summagraphics, but the pointer did not
move. problem was that Workplace shell asks what type device is attached, and
this device driver returned unkown. So got the pointer but it didn't move.
Desktop basically said since i don't know what kind of mouse it is, it won't
respond to mouse input.
o Solution:
Device driver must return what type of device it is.
ΓòÉΓòÉΓòÉ 9.1.29. Right mouse button will not work on desktop. May not drag icons or bring up menu. ΓòÉΓòÉΓòÉ
o Problem:
Right mouse button will not work on desktop. May not drag icons or bring up
menu.
o Explanation:
Many times this is due to currupted .INI system file(s).
o Solution:
A reformat/reinstall has been known to fix this, but this is a drastic move
which should be avioded except as a last resort. A better way to fix is to
use the MAKEINI command or even easier is to just boot from a DOS disk or
OS/2 install disks, and then copy over the OS2.INI and OS2SYS.INI from the
C:\OS2\INSTALL directory to the C:\OS2 directory. This will usually solve
the problem.
ΓòÉΓòÉΓòÉ 9.1.30. System exhibits problems after install of Microsoft mouse drivers ΓòÉΓòÉΓòÉ
o Problem:
System exhibits any number of unusual behaviors after customer claims to have
installed the Microsoft mouse drivers that came with their mouse. In some
cases either one or both of the DOS and Windows sessions are unusable, and
may cause traps or hangs.
o Explanation:
System has a contaminated DOS/Windows device driver or possibly the wrong
system mouse driver as well, due to using the install program on the disk
which accompanies the Microsoft mouse. The 0X error refers to the SYSTEM.INI
file. If this has been altered due to the install, it will be found that the
system will attempt to load a mouse.sys from the OS2\MDOS directory that is
not there.
o Solution:
There may be a lot involved in recovering from this mess. The install
program may copy the Microsoft MOUSE.SYS file over the OS/2 MOUSE.SYS mouse
driver. Check the file dates and sizes with the ones on the install disk and
on OS/2's system diskettes.
Often times a selective install of WINOS2 support is necessary to recover
from the Microsoft install. Best advice is DON'T DO IT!
ΓòÉΓòÉΓòÉ 9.1.31. Mouse pointer disapears randomly ΓòÉΓòÉΓòÉ
o Problem:
Mouse pointer disapears randomly, yet button clicks still function.
o Explanation:
A few customers have reported this to us, but no one has ever been able to
pinpoint what they were doing when the pointer disapeared. A similar problem
was reported in version 1.3 of OS/2 involving MS Word for OS/2, and our
belief is that it is due to an application that does the following...
o Solution:
Since this is considered to be an application specific problem (until we are
shown otherwise), the best we can offer is a workaround as follows:
Open the E editor that comes with OS/2 and keep it minimzed, if the pointer
should disapear, hit CTRL/ESC to bring up the window list. Use the arrow
keys to select the E editor.
We would appreciate any instances of pointer disapearing to be passed on to
us, as we would like to keep a list of any applications that may cause this
behaviour. It should also be reported to application vendor so they can
correct the problem.
ΓòÉΓòÉΓòÉ 9.2. Problems After Service Pack 1 ΓòÉΓòÉΓòÉ
The problems discussed in this section were found in the service pack for the
GA release of OS/2 2.0, but are not necessarily limited to that release.
ΓòÉΓòÉΓòÉ 9.2.1. Flaky mouse pointer in Win-OS2 applications with an 8514 display. ΓòÉΓòÉΓòÉ
o Problem:
Flaky mouse pointer in Win-OS2 applications with an 8514 display. Especially
noticeable with the ATI 8514 card.
o Explanation:
When using the 8514 display drivers users can't have seamless window
sessions. The mouse pointer is only flaky in a Window app (e.g. Excel) run
in full screen mode. What is occurring is likely due to interrupts either
being lost or not interpreted fast enough and what results is jerky movement
of the mouse pointer on the screen relative to the actual mouse movement.
The pointer is always catching up to the mouse even when it is moved slowly.
o Solution:
Changing Idle-Sensitivity to 100 and Idle-Seconds to 20 seems to solve the
problem, but this is not an ideal solution.
A temporary fix that seems to work for the ATI ULTRA card is as follows:
1. From the ATI 1.3 Video Device Drivers Diskette copy the Windows 3.0
device driver called ULTRA.DRV to the OS2\MDOS\WINOS2\SYSTEM
subdirectory.
2. From the OS2\MDOS\WINOS2 subdirectory type E SYSTEM.INI
3. Change DISPLAY.DRV=8514.DRV to DISPLAY.DRV=ULTRA.DRV
4. Save the changes.
5. From WINOS2 Full Screen settings set the 8514 IO Trap to OFF and set
Video Notification ON. Save settings.
6. Shut down WINOS2 Full Screen session and restart to enable changes.
Note: using this device driver makes it so user is unable to use alt/esc in
WINOS2.
ΓòÉΓòÉΓòÉ 9.2.2. There are various symptoms of inconsistant behavior on the desktop ΓòÉΓòÉΓòÉ
o Problem:
There are various symptoms of funny mouse behavior on the desktop, such as
jerky pointer movement, right button not bringing up menu all the time,
pointer disappearing, etc.
o Explanation:
There were changes made to the Presentation Manager interface in service pack
which seem to have affected how the mouse events are interpreted while on the
desktop. The events are picked up by MOUSE.SYS, but as they are passed on
either they get lost or misinterpreted.
o Solution:
For the problem of the right mouse button not working (ie. bring up menus, or
unable to drag objects), the INI files will need to be remade, as they have
somehow become corrupted. If a backup of the INI files are available, use a
boot disk to boot system and copy the INI files back and reboot. This is
preferable to remaking the INI files.
ΓòÉΓòÉΓòÉ 9.3. Version 2.1 GA ΓòÉΓòÉΓòÉ
The problems discussed in this section were found in the initial release of
OS/2 2.1 GA, but are not necessarily limited to that release.
ΓòÉΓòÉΓòÉ 9.3.1. Receive SYS1201 ERROR upon first boot after install of 2.1 ΓòÉΓòÉΓòÉ
o Problem:
Receive SYS1201 ERROR upon first boot after install of 2.1 over existing
operating system (ie. DOS, OS/2 1.x or 2.x, or Windows).
o Explanation:
If there is a previous mouse driver on the system with the name MOUSE.SYS,
the install program finds it and copies it into the \OS2 directory instead of
the OS/2 2.1 MOUSE.SYS driver from the install disks. This is an error in
the install program, not the mouse driver.
o Solution:
The following steps should be followed to verify that the correct mouse
driver is loaded.
1. Have the customer review the CONFIG.SYS file (i.e. E.EXE CONFIG.SYS)
and verify that the DEVICE= statment points to MOUSE.SYS in the x:\OS2
directory (where x: is the installed drive and is usually 'c').
2. Have the customer SEARCH for MOUSE.COM. This should NOT exist in the
CONFIG.SYS file for OS/2.
3. Have the customer give you the DATE and SIZE of the MOUSE.SYS driver
which is located in the x:\OS2 directory (x: being the installed disk
drive letter which is usually 'c').
4. The MOUSE.SYS should have a date of 4-26-93 and a file size of 15053
bytes. If this is not the case, have the customer rename the current
MOUSE.SYS and copy the MOUSE.SYS from DISK 1 of the installation set for
OS/2 2.1.
5. If the customer installed from CD-ROM and gets the SYS1201 VMOUSE NOT
INSTALLED or MOUSE DRIVER NOT INSTALLED, have the customer copy the
MOUSE.SYS driver from DISK 1 of the installation set for OS/2 2.1. EVEN
IF THE DATE AND FILE SIZE MATCH, IF THE CUSTOMER INSTALLS FROM CD-ROM,
HAVE THE CUSTOMER FOLLOW THIS PROCEDURE.
6. The APAR for this problem is PJ08916.
ΓòÉΓòÉΓòÉ 9.3.2. ERROR SYS1201 VMOUSE NOT INSTALLED at boot up ΓòÉΓòÉΓòÉ
o Problem:
Receive ERROR SYS1201 VMOUSE NOT INSTALLED for mouse in a serial port at boot
up. May not occur all the time.
o Explanation:
Due to some new features added into the mouse driver, on certain hardware
mouse combinations, will grab the com-port as it sets up for the mouse, but
it won't let go. this then prevents the loading of the correct code for that
mouse, and thus the VMOUSE.SYS driver will not load and the error occurs.
o Solution:
First see previous panel to determine that the correct version 2.1 MOUSE.SYS
system mouse driver was installed. If not follow the steps in that panel to
correct the problem. If it is the correct 2.1 driver, see next paragraph.
In some cases simply unplugging and replugging the mouse will allow the port
to reset. If not try a warm boot ( CTL-ALT-DEL ). If this does not work and
they have a previous version of OS/2 they can copy that mouse driver into the
\OS2 directory and use that one instead (save the other just in case).
The apar for this problem is PJ08908.
ΓòÉΓòÉΓòÉ 9.3.3. 3-button mouse does not work as left handed ΓòÉΓòÉΓòÉ
o Problem:
3-button mouse does not work correctly as left handed on desktop.
o Explanation:
Originally OS/2 only supported 2-button mice. When the 3-button mouse
support was added, it was decided that the desired mappings of the left/
middle/right buttons would be 1-3-2 meaning that the left button would be the
same as on the 2-button mice, and the right button would be the same as the
right button on the 2-button mice, and the middle button would be the extra
button.
This caused confusion with the button mappings of the workplace shell, as it
was expecting the l/m/r order to be 1-2-3. The expected mapping should be
2-3-1 but what occurs is 3-1-2.
This problem is in PMWIN.DLL.
o Solution:
This fix will be available in a future service pak for version 2.1.
The apar for this problem is PJ08854.
ΓòÉΓòÉΓòÉ 9.3.4. IBM 700 series (Thinkpad) mouse lost on resume from suspend. ΓòÉΓòÉΓòÉ
o Problem:
IBM 700 Series (Thinkpad) pointing stick control lost on resume from suspend.
Note: On occasion the pointing stick will seem to work in every direction
except the negative Y direction (towards bottom of screen). In this
direction it will move as if through peanut butter, agonizingly slow. This is
a symptom of the same problem.
o Explanation:
When a 700 series laptop is put into suspended mode (power saving mode), the
pointing stick is powered down as well. When resuming to normal operations,
there is a lag time while machine is cycled up. During this period the
pointing stick is powered up and the 8042 mouse port chip is reset (the
Trackpoint II pointing stick runs from this chip). If the pointing stick is
moved (ie. move screen pointer) before power up is completed, data from the
device is sent to the chip and it hoses the reset process and the interupt is
lost.
o Solution:
1. DO NOT MOVE THE MOUSE UNTIL THE BEEP SOUNDS , which signals resume is
complete and all hardware enabled. At that point there will be no
problem with the mouse.
2. If pointer has already been lost or is moving slow, hit the suspend
button again and go through the resume cycle this time not touching
stick until beep sounds.
This will be fixed in Service Pak II for 2.0 and Service Pak I for 2.1.
The apar for this problem is PJ08909.
ΓòÉΓòÉΓòÉ 9.3.5. PC Mouse Systems mouse does not work ΓòÉΓòÉΓòÉ
o Problem:
Mouse Systems mouse does not work, even though MOUSE SYSTEMS driver was
selected from mouse install panel.
o Explanation:
Some of the newer Mouse Systems mice use the Microsoft protocol. If they
have a 2/3 button switch on the bottom, 2 is Microsoft protocol, and 3 is
Mouse Systems protocol. Depending on which setting the button is on, will
determine which mouse driver to install. Either setting will work with the
correct driver.
Some of the mice do not have the switch, and use the Microsoft protocol. The
only way to be sure is to call Mouse Systems and ask them based on the model
number on the bottom of the mouse.
Mouse Systems can be reached at:
- (510) 656-1117
o Solution:
Determine which protocol the mouse is using and install the correct driver,
or edit the CONFIG.SYS file with the correct mouse statements. See Chapter 7
CONFIG.SYS Statements, for the correct statement information.
ΓòÉΓòÉΓòÉ 9.3.6. Felix PC-100 Mouse by ALTRA does not work w/OS/2 ΓòÉΓòÉΓòÉ
o Problem:
Felix PC-100 Mouse by ALTRA does not work with OS/2.
o Explanation:
This is a unique type of pointing device and requires special drivers to work
with OS/2, since it does not use one of the standard protocols.
o Solution:
Contact ALTRA to obtain the necessary device drivers. ALTRA can be reached
at:
- (800) 726-6153
ΓòÉΓòÉΓòÉ 9.3.7. Leading Edge Technology PS2 Style Mouse will not work w/OS/2 ΓòÉΓòÉΓòÉ
o Problem:
Leading Edge Technology PS2 Style Mouse will not work w/OS/2.
o Explanation:
This mouse has been found to be incompatible with OS/2.
o Solution:
Contact Leading Edge Technology, they will replace mouse. They can be
reached at:
- (800) 874-3340
ΓòÉΓòÉΓòÉ 9.3.8. Logitech bus mouse will not work with PCLOGIC.SYS ΓòÉΓòÉΓòÉ
o Problem:
Logitech bus mouse will not work with PCLOGIC.SYS driver.
o Explanation:
The Logitech bus mouse is designed to work as a 100% Microsoft compatible bus
mouse, but the PCLOGIC.SYS driver is for those devices which utilize the
Mouse Systems 5-byte protocol and thus will not work with the Logitech bus
mouse.
o Solution:
Install the mouse as a Logitech M-series mouse if using selective install, or
see the Type 1 CONFIG.SYS Statements section, for the correct statement
information.
Note: The newer model of this mouse ( Mouseman Bus version ) is a 3-button
mouse. It will only work as a two button mouse since it cannot use the
PCLOGIC.SYS driver.
Note: For more information on Logitech devices, see Logitech Devices
section later in this document.
The APAR for this is PJ09304
ΓòÉΓòÉΓòÉ 9.3.9. Trident SVGA video driver causes jumpy mouse behavior ΓòÉΓòÉΓòÉ
o Problem:
Trident SVGA(800x600) video driver causes jumpy mouse behavior
o Explanation:
Under normal circumstances, this video driver will cause no problems with
OS/2, however if there is a problem with system memory, or the system memory
board, then the problem can show up as intermittant mouse pointer movement.
Note: Problem may seem to disappear when generic SVGA is installed back on
the system.
o Solution:
Check all system memory and memory boards. We have seen this problem
disappear when a bad memory board was replaced.
ΓòÉΓòÉΓòÉ 9.3.10. Kensington trackball button(s) not working ΓòÉΓòÉΓòÉ
o Problem:
Kensington trackball button(s) not working.
o Explanation:
The Kensington Trackballs have a set of six jumpers on the back side under a
small panel. If these jumpers are set incorrectly, the buttons will respond
in a manner other than expected, or not at all.
o Solution:
Remove the panel, and flip all 6 jumpers to the up position.
Note: Kensington now has mouse drivers available for OS/2. Kensington can
be reached at:
- (800) 535-4242
ΓòÉΓòÉΓòÉ 9.3.11. Microsoft Ballpoint mouse will not work as left handed in OS/2 ΓòÉΓòÉΓòÉ
o Problem:
Microsoft Ballpoint mouse will not work as left handed in OS/2.
o Explanation:
This particular trackball mouse is unique in that it comes with buttons on
two sides of it, and with a stand that allows it to rotate 180 degrees (ie.
taking it from a right handed position to a left handed one). Thus unlike a
normal mouse or trackball where to make it left handed, all that is needed is
to swap the button mappings, this one uses an entirely different set of
buttons, and also needs the X & Y coordinate readings of the ball translated
so that the pointer will move as expected.
In order to use this mouse as left handed with OS/2, a special driver will be
needed.
o Solution:
There is no current driver available for this mouse to use in order to
operate as left handed in OS/2. Since this is not an IBM product, the burden
lies with the manufacturer to write and support such a driver.
ΓòÉΓòÉΓòÉ 9.3.12. Gateway Nomad mouse won't work in PDI port ΓòÉΓòÉΓòÉ
o Problem:
Gateway Nomad mouse won't work in PDI port.
o Explanation:
The Gateway Nomad is in fact the same machine as the TI-4000 made by Texas
Instruments. These machines do not use an 8042 mouse/keyboard controller
chip for the mouse port, thus they need a special device driver to get the
mouse to work on the port.
o Solution:
The user can do one of two things to resolve this.
1. The quick fix is to use the mouse on a serial port. The problem only
lies with the mouse port itself, not the serial port(s).
2. Contact Texas Instruments for their mouse driver which is designed for
their portables. It allows the use of the mouse port for these
machines. Texas Instruments can be reached at:
- (800) TI-TEXAS.
ΓòÉΓòÉΓòÉ 9.3.13. Compaq LTE built in trackball not working ΓòÉΓòÉΓòÉ
o Problem:
Compaq LTE built in trackball not working.
o Explanation:
This particular portable has a unique way of initializing the trackball in
its default mode. In its "Autoconfiguration Mode" the trackball it set to
IRQ15, yet it is running through the mouse/keyboard controller chip. This is
effectively the same as running on a PDI mouse port. Problem is that the
OS/2 mouse driver only recongnizes IRQ12 as being the dedicated mouse port,
so it gives the SYS1201 error since it does not recognize that the device is
there.
o Solution:
Machine must be configured as having the trackball on COM2. Follow the
instructions that come with the machine, or call the Compaq support line for
assistance. Then if OS/2 is already installed, do a selective install of the
mouse, choosing "Serial Pointing Device" in com2. This should work, but if it
doesn't then a complete re-install will be needed.
Note: An external mouse on a serial port will work with no problems.
Compaq Support can be reached at:
- (800) 345-1518
ΓòÉΓòÉΓòÉ 9.3.14. Mouse Systems serial / bus card does not work with OS/2 ΓòÉΓòÉΓòÉ
o Problem:
Mouse Systems serial / bus card does not work with OS/2.
o Explanation:
This card allows the use of up to 15 IRQs and 4 addresses in any combination,
but our mouse driver at this point in time only seems to work with this card
when it is configured as COM1 or COM2.
The problem was determined to be due to a problem involving the specific UART
used on this card. When probed by the autodetect mechanism in the OS/2 mouse
driver, it returns numerous spurious random interupts which causes the
autodetect to fail, and resort to com1,com2.
o Solution:
This problem has been determined to be a hardware issue due to the UART on
the Mouse Systems card. Kensington makes an almost identical bus/serial card
which uses a different UART, and the mouse driver has no problems working
with any of the interupts available. Mouse Systems has been notified of this.
Customers have basically 2 options they can try:
1. Use the card configured as COM1 or COM2. If these ports currently
exist, then use the mouse in one of these.
Note: The apar for this problem is PJ09343
2. Some of our customers have found that a shareware mouse driver known as
RODENT, has resolved this problem, and allowed them the full use of this
card. We do not support this mouse driver, but the developer is reported
to give needed support. Rodent can be obtained from one of the
following...
Genie : M . FINNEY
Internet: M.FINNEY@GENIE.GEIS.COM
Internet: 71573.1075@COMPUSERVE.COM
Compuserve: 71573,1075
Compuserve: look in LIBRARY #3 in OS2USER for RODENT1.ZIP
and by U.S. Mail at:
Michael Lee Finney
114 Old Wiggington Road
Lynchburg, Va. 24502-4669
ΓòÉΓòÉΓòÉ 9.3.15. SWAN technologies SN460 mouse port not working ΓòÉΓòÉΓòÉ
o Problem:
SWAN technologies SN460 mouse port not working.
o Explanation:
Swan Technologies has an internal mouse port which can be enabled or disabled
in cmos. The port comes enabled, but for some reason in this state OS/2 will
not recongnize the mouse when it is plugged into the port (it is likely that
the internal mouse port uses an IRQ other than 12).
o Solution:
Disable the internal port in cmos setup by using ESC + F2 at boot time. Then
reboot with mouse plugged into the port. As an alternative, the mouse can be
used in the com port, but since it only comes with one com port this will
likely not be a satisfactory option.
ΓòÉΓòÉΓòÉ 9.3.16. Dell Dimension series 486 & Logitech PS/2 style mouse not working ΓòÉΓòÉΓòÉ
o Problem:
Dell Dimension series 486 not working with Logitech PS/2 style mouse (model
M/N M-SR14) installed in the mouse port.
o Explanation:
This model of Logitech mouse (model M/N M-SR14), is a very recent addition to
the Logitech line of mice. There is for some reason, difficulty in using it
in the mouse port of the Dell Dimension series of computers. Dell is aware
of this problem.
o Solution:
Customers with this problem will need to contact Dell for an updated mouse
device driver (L_MS_OS2.ZIP), to resolve this problem.
Dell can be reached at the following numbers:
- BBS - (512) 728-8528
- Tech Support - (800) 624-9896
ΓòÉΓòÉΓòÉ 9.3.17. UnMouse by MicroTouch will not work in OS/2 ΓòÉΓòÉΓòÉ
o Problem:
UnMouse by MicroTouch will not work w/OS/2.
o Explanation:
The UnMouse by MicroTouch is a unique type of pointing device. It resembles
a small digitizing pad with a big red button on it. It uses a small
transformer power supply that runs at 5.2 volts dc. It is supposed to be
Microsoft compatible, but in conversations with MicroTouch they basically
said an OS/2 driver is needed for this device, and they did not wish to write
one.
o Solution:
The user can do one of two things to resolve this problem:
1. Get another pointing device, or
2. Contact MicroTouch and ask them to develop a driver for OS/2.
MicroTouch can be reached at&
- (508) 694-9900
ΓòÉΓòÉΓòÉ 9.3.18. WinTrac by Microspeed will not work in OS/2 ΓòÉΓòÉΓòÉ
o Problem:
WinTrac by Microspeed will not work w/OS/2, or exhibits unstable behaviour
(eg. double click not working).
o Explanation:
This particular model of trackball was designed only to work with MS Windows
version 3.1, and even then needs a special device driver. Its performance
under OS/2 is not supported by Microspeed, and would be unstable at best.
o Solution:
The user can do one of two things to resolve this problem:
1. Get another pointing device, or
2. Contact Microspeed and bug them to develop a driver for OS/2, or ask
them if they will exchange the Win-Trac for a model that is known to
work with OS/2.
Microspeed can be reached at:
- (800) 232-7888
ΓòÉΓòÉΓòÉ 9.3.19. Kensington Trackball V4.0 L&R buttons will not bring up window list ΓòÉΓòÉΓòÉ
o Problem:
Kensington Trackball V4.0 Left & Right buttons will not bring up window list.
o Explanation:
This particular model of trackball has been redesigned with programmable
buttons when used with the Kensington mouse drivers. Unfortunately this will
not work with OS/2. What happens is the Left/Right button combination pushed
down at the same time, sends a MIDDLE BUTTON message, instead of LEFT + RIGHT
message. Since this is not the correct message to pop up the window list,
nothing predictable occurs.
o Solution:
The user can do one of two things to resolve this problem:
1. By pressing in order first the LEFT, then the RIGHT button, the window
list will pop up since this sequence sends the correct message.
2. Try the shareware driver rodent available on Compuserv. It allows
limited remapping of button messages such as MIDDLE=LEFT+RIGHT. Note
this has not been tested
Rodent can be obtained from one of the following:
1. Genie: M.FINNEY
2. Internet: M.FINNEY@GENIE.GEIS.COM
3. Internet: 71573.1075@COMPUSERVE.COM
4. Compuserve: 71573,1075
5. Compuserve: look in LIBRARY #3 in OS2USER for RODENT1.ZIP
ΓòÉΓòÉΓòÉ 9.3.20. Logitech Radio Mouse pointer freezes in OS/2 ΓòÉΓòÉΓòÉ
o Problem:
Logitech Radio Mouse pointer freezes in OS/2. This can occur at any time,
but ususally in graphical environment (ie. pm, correl draw etc.). will work
fine on same machine under dos (this eliminates possibility of EMF
interference from computer or monitor).
o Explanation:
For a cordless mouse often the problem lies in either EMF interference for
radio mice, or line of sight problems for infrared mice. If it is isolated
that neither is the case, then it is most likely the case the machine has
wrong video drivers. This has been found with ATI video cards and the
Logitech Cordless Radio mouse.
o Solution:
Install the correct video drivers on the machine. Consult the board
manufacturer or manual to determine correct driver.
ΓòÉΓòÉΓòÉ 9.3.21. Valuepoint mouse exhibits unusual behavior ΓòÉΓòÉΓòÉ
o Problem:
Valuepoint mouse exhibits unusual behavior, such as right button clicks not
responding.
o Explanation:
Valuepoints load information used by the mouse into CMOS. Sometimes this
information gets corrupted in the same way that .ini files get corrupted, and
need to be reset.
o Solution:
Reboot machine, and hold both mouse buttons down during reboot. This resets
the CMOS. If this does not work, problem may lie in .ini files or mouse
hardware.
ΓòÉΓòÉΓòÉ 9.4. OS/2 2.1 For Windows ΓòÉΓòÉΓòÉ
The problems discussed in this section were found in the initial release of
OS/2 2.1 for Windows, but are not necessarily limited to that release.
OS/2 2.1 for Windows (OS2-4-win) is the same OS/2 as comes with the 2.1 GA
release, but with the WINOS2 code removed. This installs over the top of
"native" Windows and DOS and runs the native Windows in a VMB
Thus the OS/2 mouse driver (MOUSE.SYS) is still the same as in 2.1 GA including
the size and date, and its respective problems (eg. install copying the wrong
MOUSE.SYS driver into the OS2 directory). Any problems occuring with Windows
will be new and different than in 2.1 Ga.
ΓòÉΓòÉΓòÉ 9.4.1. Receive SYS1201 ERROR upon first boot after install of 2.1 ΓòÉΓòÉΓòÉ
o Problem:
Receive SYS1201 ERROR upon first boot after install of 2.1 over existing
operating system (ie. DOS, OS/2 1.x or 2.x, or Windows).
o Explanation:
If there is a previous mouse driver on the system with the name MOUSE.SYS,
the install program finds it and copies it into the \OS2 directory instead of
the OS/2 2.1 MOUSE.SYS driver from the install disks. This is an error in
the install program, not the mouse driver.
o Solution:
The following steps should be followed to verify that the correct mouse
driver is loaded.
1. Have the customer review the CONFIG.SYS file (i.e. E.EXE CONFIG.SYS)
and verify that the DEVICE= statment points to MOUSE.SYS in the x:\OS2
directory (where x: is the installed drive and is usually 'c').
2. Have the customer SEARCH for MOUSE.COM. This should NOT exist in the
CONFIG.SYS file for OS/2.
3. Have the customer give you the DATE and SIZE of the MOUSE.SYS driver
which is located in the x:\OS2 directory (x: being the installed disk
drive letter which is usually 'c').
4. The MOUSE.SYS should have a date of 4-26-93 and a file size of 15053
bytes. If this is not the case, have the customer rename the current
MOUSE.SYS and copy the MOUSE.SYS from DISK 1 of the installation set for
OS/2 2.1.
5. If the customer installed from CD-ROM and gets the SYS1201 VMOUSE NOT
INSTALLED or MOUSE DRIVER NOT INSTALLED, have the customer copy the
MOUSE.SYS driver from DISK 1 of the installation set for OS/2 2.1. EVEN
IF THE DATE AND FILE SIZE MATCH, IF THE CUSTOMER INSTALLS FROM CD-ROM,
HAVE THE CUSTOMER FOLLOW THIS PROCEDURE.
6. The APAR for this problem is PJ08916.
ΓòÉΓòÉΓòÉ 9.4.2. Pointer Hot Spot off in Seamless Windows on OEM machines ΓòÉΓòÉΓòÉ
o Problem:
Pointer Hot Spot off in Seamless Windows on OEM machines including but not
limited to
- Dell machines.
- Gateway
- ZEOS
- Compaq
o Explanation:
These OEM machines have a unique version of pre-loaded Windows that comes
with them. It has 8 diskettes vs 6 for the off the shelf Windows 3.1. Many
of the files are different sizes and dates, implying that perhaps it has been
customized for the manufacturer. It seems to work fine except that the mouse
pointer hot spot is way off from where the pointer is located when running in
Windows, or running seamless Windows on the desktop. Through experimenting
it was discovered that this problem seems to be caused only by one file,
MOUSE.DRV.
o Solution:
This problem can be cured by simply obtaining a copy of the MOUSE.DRV file
from an off the shelf version of Windows 3.1 (on disk 2 of the 6-disk
version. you will need to use the EXPAND command to explode it), and placing
it in the
C:\WINDOWS\SYSTEM
directory and rebooting the machine.
Of course the trick here is getting this driver, since it implies that one
has a version of regular Windows in addition to the pre-load that comes with
the machine. IBM cannot provide this driver since it is Microsoft licensed
code. We are trying to contact the manufacturers about this, since they may
be able to provide a corrected driver. We recommend that the user call the
provider of the pre-loaded Windows.
The APAR for this problem is PJ11561.
ΓòÉΓòÉΓòÉ 9.4.3. Error OS2MOUSE.DRV not installed when starting Windows ΓòÉΓòÉΓòÉ
o Problem:
Get the error OS2MOUSE.DRV NOT INSTALLED when attempting to start Windows.
The Windows session will then abort and not start. Sometimes the error does
not appear on the screen, but rather Windows will not start. If user issues
the command WINDOWS /B, and then looks in the boot log, they will find the
startup aborted at OS2MOUSE.DRV.
o Explanation:
The actual cause of this problem is as of yet unknown. In some cases it is
as simple as an incorrect path statement or line in an .INI file, but there
are many of these which just do not work. Development and Support are
researching this problem.
o Solution:
First check the following:
1. Check the path statement in the AUTOEXEC.BAT file. Make sure the PATH=
statement points to the WINDOWS directory.
2. Verify that MOUSE.DRV is located in the WINDOWS\SYSTEM directory and is
dated 3-10-92, and is 10672 bytes.
3. Do a Selective Install of WIN-OS2 support. This should only be done in
cases where selections were made during the original install of OS/2 for
Windows. This procedure may prompt for diskettes, either OS/2 or
Windows, for various files to be installed or drivers to be loaded to
recover the Windows setup. Caution should be exercised that files
and/or drivers are not deleted beforehand, or else the sustem
configuration will be altered.
If none of the above work the customer will need to speak to an IBM Warranty
Support Windows Analyst.
ΓòÉΓòÉΓòÉ 10. LOGITECH POINTING DEVICES AND OS/2 ΓòÉΓòÉΓòÉ
All recent model Logitech pointing devices will work with version 2.x of OS/2
provided proper installation options are chosen during the OS/2 system
configuration, and the mouse hardware is in the proper protocol state ( this
can be altered by the DOS mouse drivers and result in problems). The older the
particular model of Logitech mouse, the more likely it will be the case that it
is either incompatible with OS/2, or that there will be problems with switching
from DOS to OS/2.
This following lists the pointing device and the steps to make it function
properly. They have all been tested with OS/2, by the Logitech Corporation.
ΓòÉΓòÉΓòÉ 10.1. M-Series Serial Mice ΓòÉΓòÉΓòÉ
These include but are not limited to the following devices which run as
Microsoft compatible devices&
o Mouseman Serial
o Radio
o Trackman Portable
o Trackman II on serial port
The proper selection for these devices is LOGITECH M-SERIES
During initial install for OS/2, the operating system finds and configures the
system for the mouse correctly without user intervention. Thus you should not
need to select a driver for the pointing device. Check the systems selection,
the proper selection is the M-SERIES selection.
When updating from No Pointing Device or other type of mouse, user should pick
the Serial Pointing Device selection for version 2.0 and service pack, and the
Logitech M-Series Mouse selection for version 2.1. Follow the prompts and
identify the port mouse is on, with the choices being COM1 or COM2 (at this
time OS/2 will not support a pointing device on COM3 or COM4). Continue with
installation, inserting diskettes as requested.
ΓòÉΓòÉΓòÉ 10.2. C-Series Serial Mice ΓòÉΓòÉΓòÉ
These include but are not limited to the following devices which run as Mouse
Systems compatible devices&
o C-7
o CC
o CA
o CE
o TrackMan-1 on serial port
The proper selection for these devices is LOGITECH C-SERIES.
The initial OS/2 installation procedure will NOT find these devices and at the
appropriate time during the installation, OS/2 will ask the user which device
they would like to use. Select the LOGITECH SERIAL MOUSE and when asked, pick
either COM1 or COM2. Complete the installation, turn off the computer, boot to
OS/2, and the mouse will then be working.
Note: On Dual Boot and Boot Manager
When using OS/2's DUAL BOOT or BOOT MANAGER feature, it is important to note
that the C-series mice, when used in DOS, are MM protocol and must be reset to
the Mouse Systems protocol (5 Byte,1200 Baud) by typing MOUSE PC (or LMOUSE PC)
at the DOS command line and then issuing the command to return to OS/2 and
performing a warm boot. If for some reason this command does not work, then
user can try the following either&
1. unplug and replug mouse or
2. perform a cold boot to OS/2.
The MOUSE PC command must be used with the Logitech MOUSE.COM (or LMOUSE.COM)
under DOS. This command and the dual boot command can be combined into a one
word batch file.
ΓòÉΓòÉΓòÉ 10.3. Bus & PS/2 Style Mice ΓòÉΓòÉΓòÉ
These include but are not limited to the following devices which run as
Microsoft compatible devices
o P7
o PA
o PD on BUS card with correct IRQ SETTINGS
o PS/2 models
The proper selection for these devices is PS/2 STYLE POINTING DEVICE..
Note: IRQ settings and bus cards. It is important that the IRQ setting on the
bus mouse card be set to an available interrupt number. If you have a choice
in the range 2-5, the only open IRQ is 5, and this is only true if you are not
using LPT2 for a second printer (see section called IRQ Settings)
ΓòÉΓòÉΓòÉ 10.4. CONFIG.SYS Statements for Logitech Devices ΓòÉΓòÉΓòÉ
The lines needed for each type of pointing device are shown below. It is not
absolutely necessary to run the selective install to change the system
configuration for the mice. By changing the CONFIG.SYS file for OS/2, the
system can be re-configured for each type of pointing device.
In every case there are some lines which DO NOT need to be changed, but still
need to exist.
These include:
DEVICE=C:\OS2\MDOS\VMOUSE.SYS
DEVICE=C:\OS2\POINTDD.SYS
Lines that DO CHANGE follow for each specific type of mouse.
o BUS and PS/2 TYPE: Will add the following if not already there.
DEVICE=C:\OS2\MOUSE.SYS
o M-Series Serial Mice:
DEVICE=C:\OS2\MOUSE.SYS SERIAL=COMx (where x=1 or 2)
o C-Series Serial Mice:
DEVICE=C:\OS2\PCLOGIC.SYS SERIAL=COMx ( x= 1 or 2 )
DEVICE=C:\OS2\MOUSE.SYS TYPE=PCLOGIC$
ΓòÉΓòÉΓòÉ 10.5. List of Logitech Models ΓòÉΓòÉΓòÉ
Known Logitech Model Numbers as they appear on the hardware (not complete!!!):
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÉ
ΓöéDescription ΓöéType ΓöéModel NumberΓöéCONFIG.SYS ΓöéButΓöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöñ
ΓöéMouseman ΓöéSerial ΓöéM-MC13-DB9F ΓöéType 1 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöñ
ΓöéLogitech Mouseman ΓöéBus ΓöéM-PD13-9MD ΓöéType 1 Γöé3 Γöé
ΓöéBus Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöñ
ΓöéMouseman Cordless ΓöéSerial ΓöéM-RB24 or ΓöéType 1 Γöé3 Γöé
Γöé Γöé ΓöéM-RA12 Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöñ
ΓöéLogitech Mouseman ΓöéSerial/PDIΓöéM-CJ13 ΓöéType 1 Γöé3 Γöé
ΓöéCombo Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöñ
ΓöéTrackman(old) ΓöéSerial ΓöéT-CA1-9F ΓöéType 2 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöñ
ΓöéTrackman(new) ΓöéSerial ΓöéT-CC2-9F ΓöéType 1 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöñ
ΓöéSeries 9 ΓöéPS/2 ΓöéCE9-6MD ΓöéType 1 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöñ
ΓöéSeries 9 ΓöéSerial ΓöéCC-93-9F ΓöéType 2 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöñ
ΓöéSeries 2 ΓöéPS/2 Γöé2-7S ΓöéType 1 Γöé2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöñ
ΓöéClear Mouse ΓöéSerial ΓöéLT515 ΓöéIncompatible Γöé2/3Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöñ
ΓöéLogitech Mouse ΓöéSerial ΓöéCA-93-6MD ΓöéType 2 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöñ
ΓöéLogitech Mouse ΓöéSerial ΓöéP7-3F ΓöéType 2 Γöé3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöñ
ΓöéKidz Mouse ΓöéSerial Γöéunknown ΓöéType 1 Γöé2 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 11. INTERRUPTS & IRQ SETTINGS ΓòÉΓòÉΓòÉ
There are three general types of interrupts that can occur in a PC:
o Hardware Interrupts
o Software Interrupts
o Processor Exceptions
With OS/2, most of the problems users will encounter with pointing devices,
will be with hardware interrupts in the form of conflicts. An interrupt
conflict will often show itself as a non-moving mouse pointer on the desktop.
The conflict will often be with other devices on the system such as:
o Modem cards
o Sound cards
o SCSI adapters
among others. Please consult the manuals for your devices or their
manufacturer for more information on what interrupts are the device is using.
The following section IRQ Settings, should help to resolve some of these
issues.
ΓòÉΓòÉΓòÉ 11.1. IRQ Settings ΓòÉΓòÉΓòÉ
The descriptions reflect the usual assignments for the given hardware
interrupt.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéIRQ Level ΓöéDescription of usage Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIRQ 0 ΓöéSystem Timer ( channel 0 ) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIRQ 1 ΓöéKeyboard Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIRQ 2 ΓöéSecondary Interrupt Controller ( see Γöé
Γöé Γöénote below ) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIRQ 3 ΓöéCOM2 - Serial Communications Port #2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIRQ 4 ΓöéCOM1 - Serial Communications Port #1 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIRQ 5 ΓöéLPT2 - Parallel Port #2 (Available if Γöé
Γöé Γöénot using a second printer. Reserved inΓöé
Γöé ΓöéPS/2 systems) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIRQ 6 ΓöéDiskette Drive A Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIRQ 7 ΓöéLPT1 - Parallel Port #1 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIRQ 8 ΓöéReal-Time Clock Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIRQ 9 ΓöéRedirected to IRQ2 ( see note below ) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIRQ 10 Γöéopen Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIRQ 11 Γöéopen Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIRQ 12 ΓöéPDI Port (mouse port on PS/2 systems, Γöé
Γöé Γöéand some EISA bus systems. Open if not Γöé
Γöé Γöéin use.) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIRQ 13 ΓöéMath Coprocessor ( if installed ) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIRQ 14 ΓöéHard Disk Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIRQ 15 Γöéopen Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Standard I/O addresses and IRQs for COM1 and COM2
o COM1: address = 3F8, interrupt = IRQ4
o COM2: address = 2F8, interrupt = IRQ3
Note: On the IBM-AT (ISA bus) the IRQ9 pin is identical with the IRQ2 pin on
the original IBM-PC. If you have an older, 8-bit adapter whose documentation
states that it uses IRQ2, then be aware that this will actually be seen as IRQ9
when plugged into the 16-bit ISA bus. The PS/2 also uses this same cascade of
interrupts.
If an error appears saying that COM.SYS or VCOM.SYS is not loaded or that in
particular, COM1 or COM2 are not loaded, then it is likely the case that there
is an interrupt conflict in the system. Check the settings on the bus mouse
card to see if IRQ3 or IRQ4 are set, and if so change the setting otherwise the
serial port(s) will not work.
If an interrupt or COM port problem is suspected, consult the "Serial
Communications and OS/2 2.x" in the REFERENCES section for further information.
ΓòÉΓòÉΓòÉ 12. OS/2 VERSION 1.3 INFORMATION ΓòÉΓòÉΓòÉ
Some important notes on OS/2 1.3.02;
o Family one bus machines use the ....01.sys drivers.
o Family two bus machines use the ....02.sys drivers.
o Family one uses the AT style adapters cards.
o Family two uses PS/2 Microchannel type adapter cards
All mouse files are on disk two, and have the extension .sy@. they can be
expanded using the unpack command.
UNPACK A:MSSER01.SY@ C:\OS2
Note: Latest CSD system level is version WR05200. This is the only version of
1.3 that is currently supported.
The previous version of this system was CSD WR05050, and next previous version
of this system was CSD WR05016.
Supported OEM Equipment: The only OEM machine supported on 1.3 is Compaq. Any
mouse which is 100% Microsoft compatible is supported, but many of them are
untested since they did not exist when 1.3 came out. This creates a bit of a
gray area about what is supported and what is not. There is a list below of
some which have recently been tested and the statments which they use in
CONFIG.SYS.
ABIOS patch for the P75: Is dated 12-13-91. It can be forwarded to any
customer using OS/2 version 1.x who can not update to OS/2 v 2.0. It includes
fixes for several problems including the system hardware problem with the Mouse
interface on the P75. OS/2 v2.0 does not require this patch as the corrective
code is built into the OS/2 kernel.
A CSD sould be available to 1.3 users that has this fix. Please check and see
if the file F85200.BIO is available through OS/2 support and that P75 users
are instructed to add this module name to their ABIOS.SYS file so that it is
loaded. If a P75 user has this file F85200.BIO with the current date of
12-13-91 or later and is still having mouse problems, it is likely that the
ABIOS.SYS has not been updated correctly by the user or the install program was
not run to include it.
This ABIOS patch will prevent 99% of the Wild Mouse failures that normally
occur on a P75. It is not 100% effect. Nor will it do any good once the mouse
is out of sync but at least it will greatly reduce the failures seen by the
customer.
P75 customers with this wild mouse problem should also be advised that the old
style IBM mouse with the black ball will fail more than others on the P75. If
possible, they should swap mice and use the IBM gray ball mouse on P75's.There
is nothing wrong with the old style black ball mouse, it will work OK on other
systems. It also works OK on the P75 with the ABIOS patch F85200.BIO dated
12-13-91 correctly installed.
ΓòÉΓòÉΓòÉ 12.1. CONFIG.SYS Statements for Supported Mice ΓòÉΓòÉΓòÉ
The following panels describe the appropriate CONFIG.SYS and other setup
information for various mice, including OEM mice...
ΓòÉΓòÉΓòÉ 12.1.1. IBM Mouse In PDI Mouse Port ΓòÉΓòÉΓòÉ
This works using the following statements for PS/2 machines ( family 2 )
DEVICE=C:\OS2\IBMMOU02.SYS
DEVICE=C:\OS2\MOUSE.SYS TYPE=IBMMOU$
This works using the following statements for Valuepoint & PS/1 machines (
family 1 )
DEVICE=C:\OS2\IBMMOU01.SYS
DEVICE=C:\OS2\MOUSE.SYS TYPE=IBMMOU$
ΓòÉΓòÉΓòÉ 12.1.2. Microsoft Inport Mouse w/ Inport Card ΓòÉΓòÉΓòÉ
With card set on primary address (jumper J1) , IRQ5 (jumper J3), and on normal
slot (jumper J2). This works using the following statements in CONFIG.SYS:
DEVICE=C:\OS2\MSINP01.SYS
DEVICE=C:\OS2\MOUSE.SYS TYPE=MSINP$
Note: MSINP01.SYS is for non-Microchannel bus machines. This card will not
work on a Microchannel bus (PS/2 machines).
ΓòÉΓòÉΓòÉ 12.1.3. Inport Mouse In PDI Mouse Port ΓòÉΓòÉΓòÉ
This works using the following statements
DEVICE=C:\OS2\MSPS201.SYS
DEVICE=C:\OS2\MOUSE.SYS TYPE=MSPS2$
Note: MSPS201.SYS is for non-Microchannel bus machines. MSPS202.SYS is for
the PS/2 microchannel machines (family 2).
ΓòÉΓòÉΓòÉ 12.1.4. Inport Mouse In Serial Port ΓòÉΓòÉΓòÉ
This works using the following statments
DEVICE=C:\OS2\MSSER01.SYS SERIAL=COMx ('x' = 1 or 2)
DEVICE=C:\OS2\MOUSE.SYS TYPE=MSSER$
Note: MSSER01.SYS is for non-Microchannel bus machines. MSSER02.SYS is for
the PS/2 microchannel machines (family 2).
ΓòÉΓòÉΓòÉ 12.1.5. Microsoft Bus Mouse ΓòÉΓòÉΓòÉ
Card set on IRQ5. Works with following statements
DEVICE=C:\OS2\MSBUSO1.SYS
DEVICE=C:\OS2\MOUSE.SYS TYPE=MSBUS$
Note: MSBUS01.SYS is for non-Microchannel bus machines. This card will not
work on a Microchannel bus (PS/2 machines).
ΓòÉΓòÉΓòÉ 12.1.6. MicroSpeed PCTRAC Trackball w/MicroSpeed Card ΓòÉΓòÉΓòÉ
Card set on PRIMARY address, and IRQ5 works with following statements
DEVICE=C:\OS2\MSBUS01.SYS
DEVICE=C:\OS2\MOUSE.SYS TYPE=MSBUS$
Note: MSINP01.SYS is for non-Microchannel bus machines. This card will not
work on a Microchannel bus (PS/2 machines).
ΓòÉΓòÉΓòÉ 12.2. Problems with version 1.3x ΓòÉΓòÉΓòÉ
The following panels contain known problems with version 1.3x of OS/2.
ΓòÉΓòÉΓòÉ 12.2.1. Mouse hangs in upper left corner of screen ΓòÉΓòÉΓòÉ
o Problem:
Mouse hangs in upper left corner of screen when in graphics mode.
o Explanation:
This occurs when in an application a switch is made from text mode ( 25 rows
by 80 cols ) to graphics mode, but the system still thinks it is in the text
mode. This results in the graphical desktop drawing the mouse pointer in an
area 25 by 80 pixels in the upper left hand corner. This problem has to do
with the video drivers.
o Solution:
At this point in time there is only a work-around available, and that is to
go to a full screen OS/2 session, and then go back to the desktop. this will
reset the video mode to its correct state.
The apar for this problem is JR07259.
ΓòÉΓòÉΓòÉ 13. POINTING DEVICE APARS ΓòÉΓòÉΓòÉ
The following table lists known OS/2 APARs by number and title. Note that some
of these have been cancelled as unreproducible or not an OS/2 problem.
ΓòÉΓòÉΓòÉ 13.1. OS/2 APARs including currently open APARs ΓòÉΓòÉΓòÉ
For open apars, if the customer has a similar problem add them to the IP page
of the APAR. The information in the infoapars is not necessarily current.
Information in this document should be considered more recent and accurate in
case of a conflict.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéAPAR ΓöéAPAR Title and Description Γöé
ΓöéNumber Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ03802 ΓöéSeamless Apps don't recognize left-hand Γöé
Γöé Γöémouse setting when both OS/2 :WINOS2 setΓöé
Γöé Γöéleft-handed Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ03822 ΓöéProblems with serial mouse on HP RS/20C Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04073 ΓöéOS/2 supports only one Mouse. (APAR Γöé
Γöé ΓöéCLOSED as suggestion). Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04196 ΓöéSelective install does not always removeΓöé
Γöé ΓöéDEVICE statements Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04244 ΓöéLogimenu.com will not work in OS/2 VDM Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04275 ΓöéRight mouse button select and drag can Γöé
Γöé Γöécatch wrong icon Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04330 ΓöéMouse hangs at right side of screen Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04351 ΓöéCannot use 3-button mouse PJ04396 L40SX Γöé
Γöé Γöémouse frozen after resume if mouse movedΓöé
Γöé Γöéduring suspended state Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04413 ΓöéDOS mouse drivers that work in MS-DOS Γöé
Γöé Γöé5.0 don't work in VDM or VMB Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04415 ΓöéLogitech 3 Button Mouse. 3rd button Γöé
Γöé Γöédoesn't work. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04429 Γöé8516 Touch screen driver only operates Γöé
Γöé Γöéwith IBM mouse Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04479 ΓöéSpecial program for disabled users has Γöé
Γöé Γöésticky keys Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04534 ΓöéKensington Expert Mouse will not work Γöé
Γöé Γöéwith OS/2 V2.0 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04754 ΓöéMouse Systems PC BUS Mouse won't work Γöé
Γöé Γöéwith OS/2 V2.0 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04545 ΓöéLogitech trackman Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04589 ΓöéCHICONI Tracking Keyboard with built in Γöé
Γöé Γöé3 button trackball Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04611 ΓöéSemigraphics tablet will not work in Γöé
Γöé ΓöéOS/2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04628 ΓöéMouse will not work with WINOS2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04810 ΓöéMouse systems optical mouse Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04812 ΓöéChicony Trackball Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04855 ΓöéMS bus mouse will not work under OS/2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04866 ΓöéMouse pointer lost in WINOS2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04904 ΓöéToshiba Docking Station hot plug mouse Γöé
Γöé Γöéproblem (acts like wild mouse problem) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ04921 ΓöéEmerson E-mouse erratic under DOS VDM Γöé
Γöé Γöésessions Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ05254 ΓöéLogitech C7 mouse will not work with Γöé
Γöé ΓöéOS/2 v2.0 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ05310 ΓöéMouse support problem with WORD4 on VGA Γöé
Γöé Γöémachine Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ05615 ΓöéMouse sluggish in WINOS2 when plotting Γöé
Γöé Γöéin background Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ05681 ΓöéPC Mouse Systems mouse unusable in Γöé
Γöé ΓöéWINOS2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ05730 ΓöéMouse Systems serial mouse won't work Γöé
Γöé Γöéwith DOS apps in OS/2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ05799 ΓöéMouse disappears with video notificationΓöé
Γöé Γöéon when t/r ram size set to 64k on AMI Γöé
Γöé Γöéboards Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ05853 Γöé8516 touch screen display gets video Γöé
Γöé Γöécorruption when running Windows apps Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ05896 ΓöéKurta, Summagraphic : other tablets Γöé
Γöé Γöéwon't work with OS/2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ06011 ΓöéIncorrect touch and mouse events Γöé
Γöé Γöéreturned from touchscreen APIs in OS/2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ06201 ΓöéMouse event handler gives incorrect Γöé
Γöé Γöéresults when run from an OS/2 window Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ06259 ΓöéMouse Systems bus mouse and other OEM Γöé
Γöé Γöébus/serial cards will not work with OS/2Γöé
Γöé Γöé2.0 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ06273 ΓöéMouse won't work after resume from powerΓöé
Γöé Γöédown on L40SX laptop Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ06299 ΓöéMS mouse exhibits jerky movement Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ06309 ΓöéMouse pointer changes shape when on lastΓöé
Γöé Γöépage of settings in notebook Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ06550 ΓöéProblems with mouse pointer disappearingΓöé
Γöé Γöéin WINOS2 after service pack Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ06826 ΓöéDeluxe Paint enhanced pixel movement is Γöé
Γöé Γöéwrong Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ07239 ΓöéMouse very sluggish on large (19") Γöé
Γöé Γöémoniters Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéJR07259 ΓöéVersion 1.3, mouse hangs in top left Γöé
Γöé Γöécorner Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ07264 ΓöéMicrosoft mouse jumpy/erratic after Γöé
Γöé Γöéservice pack on IBM mod70 w/8513 displayΓöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ07360 Γöé<DUPLICATE OF PJ07264> Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ07916 ΓöéErratic or jerky mouse pointer movement Γöé
Γöé Γöéon mod 90 : 95 running at greater than Γöé
Γöé Γöé33 mhz ... Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ08030 ΓöéUnatended start mode using power on Γöé
Γöé Γöépassword disables mouse plugged in mouseΓöé
Γöé Γöéport Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ08043 ΓöéMouse driver not working with MicrospeedΓöé
Γöé Γöébus card Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ08206 ΓöéMouse driver will not recognize Mouse Γöé
Γöé ΓöéSystems Serial/Bus card. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ08292 ΓöéATI Mouse not working after CSET/2 Γöé
Γöé Γöéinstalled Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ08293 ΓöéATI Graphics Ultra mouse right button Γöé
Γöé Γöéfunctions not all working Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ08411 ΓöéPS/2 style mouse port does not work on Γöé
Γöé ΓöéOEM notebook pc's Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ08854 ΓöéButton mappings incorrect for 3-button Γöé
Γöé Γöémouse when used as left handed Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ08908 ΓöéAfter install of 2.1, mouse will not Γöé
Γöé Γöéwork on reboot unless first unplugged Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ08909 ΓöéMouse fails on resume from power down onΓöé
Γöé ΓöéIBM Thinkpad 700c Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ08916 ΓöéMouse lost on reboot after install on Γöé
Γöé Γöéversion 2.1, due to install of other Γöé
Γöé Γöésystem mouse driver into c:/OS2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ09282 ΓöéMouse Systems mouse will not work with Γöé
Γöé Γöé........ Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ09290 ΓöéDocumentation error on pointer size Γöé
Γöé Γöécommand files....... Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ09304 ΓöéLogitech bus mouse will not work with Γöé
Γöé ΓöéPCLOGIC.SYS Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ09326 ΓöéMouse driver incorrectly detects bus Γöé
Γöé Γöémouse on com2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ09337 ΓöéHeavy print spooling causes mouse to Γöé
Γöé Γöémove in opposite direction Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ09441 ΓöéMicrosoft Ballpoint mouse will not work Γöé
Γöé Γöécorrectly when set left handed Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ09343 ΓöéMouse Systems serial/bus card not Γöé
Γöé Γöéworking with OS/2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ09673 ΓöéPointer hot spot off in seamless WindowsΓöé
Γöé Γöéapps Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ09784 ΓöéMouse movement slow in full screen DOS Γöé
Γöé Γöéapps Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ09789 ΓöéJerky Mouse behavior in WINOS2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ09845 ΓöéToo many 3-button events reported when Γöé
Γöé Γöéhold down 3rd button and move mouse Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ10047 Γöérexx pointer utility in OS/2 readme doesΓöé
Γöé Γöédoes not work with xga Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ10051 Γöéprinting causes errant mouse behaviour Γöé
Γöé Γöéin ver 2.1 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ10885 ΓöéIn DOS Fullscreen, pointer freezes when Γöé
Γöé Γöéaccessing a Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ11224 ΓöéQMODEM Pro in RIP graphics mode has not Γöé
Γöé Γöépointer in Fullscreen mode Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ11561 ΓöéPointer "hot spot" is off in Seamless Γöé
Γöé ΓöéWINOS2 in OS2-4-WIN Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ11607 ΓöéIBM 7554 Touchscreen will not install Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPJ11834 ΓöéIncorrect use of STYPE= statement in Γöé
Γöé ΓöéCONFIG.SYS hangs system Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 14. POINTING DEVICE MODELS & MANUFACTURERS ΓòÉΓòÉΓòÉ
The following table contains many of the mice and trackballs in use today.
There are likely omissions as there are new devices release everyday, as well
as older ones where the company is no longer manufacturing them or is out of
business. This is just a reference, we do not expect it to be all encompassing
or even completely accurate.
ΓòÉΓòÉΓòÉ 14.1. Table Abbreviations ΓòÉΓòÉΓòÉ
Below are some abbreviations used in the table.
o McSoft => Microsoft 3-byte protocol
o MouSys => Mouse Systems 5-byte protocol
o Both => can use either Microsoft or Mouse Systems protocol (usually has a
switch on the device to change this)
o unk = unknown
o ser = serial
o bus = bus
o PDI = PDI port (PS/2 port)
o inp = inport
ΓòÉΓòÉΓòÉ 14.2. Pointing Devices Table ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéCompany NameΓöéDevices ΓöéMS ΓöéInterfacesΓöéIRQs Γöé
Γöé Γöé ΓöéCompatibleΓöé ΓöéSupported Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéA4Tech Γöé3-Button Serial Γöéunk Γöéser Γöé3,4 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAltra ΓöéFelix Γöéunique Γöéser,PDI Γöé3,4,12 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAmazing ΓöéAMX-300 mouse ΓöéMcSoft Γöéser, bus, Γöé? Γöé
ΓöéTechnologiesΓöé Γöé ΓöéPDI Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAmazing ΓöéAAK-300 trackball ΓöéMcSoft Γöéser, bus, Γöé? Γöé
ΓöéTechnologiesΓöé Γöé ΓöéPDI Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAppoint ΓöéMouse Pen ΓöéMcSoft Γöéser, PDI Γöé3, 4 Γöé
Γöé ΓöéProfessional Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAppoint ΓöéThumbelina ΓöéMcSoft Γöéser, PDI Γöé3, 4 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéAntec Inc. ΓöéArtec-21 Plus ΓöéBoth Γöéser Γöé3, 4 Γöé
Γöé ΓöéMouse Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCalcomp Inc.ΓöéWiz Mouse System ΓöéMouSys Γöéser, PDI Γöé2, 3, 4, 5Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéChicony ΓöéKeyboard w/ ΓöéBoth Γöéser Γöé4 Γöé
ΓöéAmerica Inc.Γöétrackball Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCH Products ΓöéRollerMouse ΓöéMcSoft Γöéser, bus, Γöé3, 4 Γöé
Γöé Γöé Γöé ΓöéPDI Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCMS ΓöéCMS Mini Mouse ΓöéMouSys Γöéser, bus Γöé2, 3, 4, 5Γöé
ΓöéEnhancementsΓöé(standard) Γöé Γöé Γöé Γöé
ΓöéInc. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCMS ΓöéCMS Mini Mouse ΓöéMouSys Γöéser, bus Γöé2, 3, 4, 5Γöé
ΓöéEnhancementsΓöé(hi-res) Γöé Γöé Γöé Γöé
ΓöéInc. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCommax Inc. ΓöéCity Mouse ΓöéBoth Γöéser Γöé0, 3, 7, 8Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCommax Inc. ΓöéFancy Mouse ΓöéBoth Γöéser Γöé0, 3, 7, 8Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCommax Inc. ΓöéWitty Ball ΓöéBoth Γöéser Γöé0, 3, 7, 8Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéComputer ΓöéTrackball Plus ΓöéBoth Γöéser Γöé1, 2 Γöé
ΓöéProducts Co.Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéDell ΓöéDell Serial Mouse ΓöéMcSoft Γöéser Γöé4 Γöé
ΓöéComputer Γöé Γöé Γöé Γöé Γöé
ΓöéCorp. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéDFI Inc. ΓöéDMS-200 Mouse ΓöéBoth Γöéser Γöé3, 4 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéDFI Inc. ΓöéDMS-200H Mouse ΓöéBoth Γöéser Γöé3, 4 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéDFI Inc. ΓöéDMS-400x Mouse ΓöéBoth Γöéser Γöé3, 4 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéDyna Point ΓöéDyna Mouse Γöéunk Γöéser,PDI Γöé3,4,12 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéEvergreen ΓöéDiamond 24 ΓöéMcSoft Γöéser, bus, Γöéunk Γöé
ΓöéSystems Γöétrackball Γöé ΓöéPDI Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéEvergreen ΓöéDiamond 20 ΓöéMcSoft Γöéser, bus, Γöé? Γöé
ΓöéSystems Γöétrackball Γöé ΓöéPDI Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéEvergreen ΓöéOmega ΓöéMcSoft Γöéser, PDI Γöéunk Γöé
ΓöéSystems Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéFocus ΓöéAlum Mouse Γöéunk Γöéser,PDI Γöé3,4,12 Γöé
ΓöéElectronic Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéFocus ΓöéFocus FT-100 ΓöéBoth Γöéser Γöé1, 2 Γöé
ΓöéFulcrum ΓöéTracker Γöé Γöé Γöé Γöé
ΓöéCorp. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéGRID SystemsΓöéGRID IsoPoint ΓöéMcSoft ΓöéN/A Γöé3, 4, 5 Γöé
ΓöéCorp. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIBM Corp. ΓöéIBM PS/2 Mouse ΓöéMcSoft ΓöéPDI Γöé12 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIBM Corp. ΓöéPS/2 Trackpoint ΓöéMcSoft ΓöéP Γöé12 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIMSI ΓöéIMSI Mouse ΓöéMcSoft Γöéser, bus Γöé? Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéIMSI ΓöéPET Mouse ΓöéMcSoft Γöéser, bus, Γöé? Γöé
Γöé Γöé Γöé ΓöéPDI Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéInternationaΓöéThe Mouse Pen ΓöéMcSoft Γöéser, PDI Γöé0, 3, 4 Γöé
ΓöéMachine Γöé Γöé Γöé Γöé Γöé
ΓöéControl Γöé Γöé Γöé Γöé Γöé
ΓöéSystems Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéITAC SystemsΓöéMouse-Trak (ball 2ΓöéBoth Γöéser, bus, Γöé3, 4, 5, Γöé
ΓöéInc. Γöébutton) Γöé ΓöéPDI, inp Γöé7,10,11,12Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéITAC SystemsΓöéMouse-Trak (ball 3ΓöéBoth Γöéser, bus, Γöé3, 4 Γöé
ΓöéInc. Γöébutton) Γöé ΓöéPDI, inp Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéITAC SystemsΓöéMouse-trak (ball) ΓöéMcSoft Γöéser, bus, Γöé? Γöé
ΓöéInc. ΓöéIndustrial Γöé ΓöéPDI Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéITAC SystemsΓöéMouse-trak (ball) ΓöéMouSys Γöéser, bus, Γöé? Γöé
ΓöéInc. ΓöéProfessional Γöé ΓöéPDI Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéKensington ΓöéExpert Mouse ΓöéMcSoft ΓöéPDI, bus, Γöé2, 3, 4, Γöé
ΓöéMicroware Γöé Γöé ΓöéPDI Γöé5,7,10,11,Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéKey Tronic ΓöéProfessional ΓöéMcSoft Γöéser,bus Γöé2, 3, 4, 5Γöé
ΓöéCorp. ΓöéSeries Mouse Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéKraft ΓöéKraft Trackball ΓöéMouSys Γöéser Γöé3, 4 Γöé
ΓöéSystems Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéKraft ΓöéTopTrak Trackbal ΓöéMcSoft Γöéser Γöé3, 4 Γöé
ΓöéSystems Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéKYE ΓöéGenius Mouse GM-6XΓöéBoth Γöéser Γöé1, 2, 3, Γöé
ΓöéInternationaΓöé Γöé Γöé Γöé4, 5 Γöé
ΓöéCorp. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéKYE ΓöéGenius Mouse ΓöéBoth Γöéser Γöé1, 2, 3, Γöé
ΓöéInternationaΓöéGM-6000 Γöé Γöé Γöé4, 5 Γöé
ΓöéCorp. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéKYE ΓöéGenius Mouse ΓöéBoth Γöéser Γöé1, 2, 3, Γöé
ΓöéInternationaΓöéGM-F301 Γöé Γöé Γöé4, 5 Γöé
ΓöéCorp. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéKYE ΓöéGenius Mouse ΓöéBoth Γöéser,PDI Γöé1, 2, 3, Γöé
ΓöéInternationaΓöéGM-F302 Γöé Γöé Γöé4, 5 Γöé
ΓöéCorp. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéKYE ΓöéGenius Mouse ΓöéBoth Γöéser,PDI Γöé1, 2, 3, Γöé
ΓöéInternationaΓöéGM-F303 Γöé Γöé Γöé4, 5 Γöé
ΓöéCorp. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéKYE ΓöéGenius Mouse GM-S2ΓöéBoth ΓöéPDI Γöé1, 2, 3, Γöé
ΓöéInternationaΓöé Γöé Γöé Γöé4, 5 Γöé
ΓöéCorp. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéKYE ΓöéClix Mouse ΓöéMouSys Γöéser, bus, Γöé? Γöé
ΓöéInternationaΓöé Γöé ΓöéPDI Γöé Γöé
ΓöéCorp. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéKYE ΓöéClix Plus mouse ΓöéMouSys Γöéser, bus, Γöé? Γöé
ΓöéInternationaΓöé Γöé ΓöéPDI Γöé Γöé
ΓöéCorp. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéKYE ΓöéGenie Track ΓöéMouSys Γöéser, bus, Γöé? Γöé
ΓöéInternationaΓöé(ball)GK-T32 Γöé ΓöéPDI Γöé Γöé
ΓöéCorp. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLightwave ΓöéLester the ΓöéMcSoft Γöéser, bus, Γöé? Γöé
ΓöéTechnologiesΓöéCordless Mouse Γöé ΓöéPDI Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLiuski ΓöéProCorp Mouse ΓöéMouSys Γöéser Γöé2, 3, 4, 5Γöé
ΓöéInternationaΓöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLiuski ΓöéProCorp Mouse ΓöéMouSys Γöébus Γöé2, 3, 4, 5Γöé
ΓöéInternationaΓöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLogitech ΓöéSee Logitech Γöé Γöé Γöé Γöé
ΓöéInc. Γöésection of this Γöé Γöé Γöé Γöé
Γöé Γöédocument Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLogitech ΓöéDexxa Mouse ΓöéMouSys Γöéser, bus Γöé2, 3, 4, 5Γöé
ΓöéInc. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéLynx ΓöéLynx Turbo ΓöéMouSys Γöéser, bus, Γöé2, 3, 4, 5Γöé
ΓöéComputer ΓöéTrackball Γöé ΓöéPDI Γöé Γöé
ΓöéProducts Γöé Γöé Γöé Γöé Γöé
ΓöéInc. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMagitronic ΓöéProcorp Mouse ΓöéMouSys Γöéser, bus, Γöé? Γöé
Γöé Γöé Γöé ΓöéPDI Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMarconi ΓöéMarcus Trackball ΓöéMcSoft Γöéser, bus Γöé2, 3, 4, 5Γöé
ΓöéCircuit TechΓöéRB2-305 Γöé Γöé Γöé Γöé
ΓöéCorp. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMarconi ΓöéMarcus Trackball ΓöéMcSoft Γöéser, bus Γöé2, 3, 4, 5Γöé
ΓöéCircuit TechΓöéRB2-306 Γöé Γöé Γöé Γöé
ΓöéCorp. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMicrocomputeΓöéIMSI Mouse ΓöéMcSoft Γöéser, bus Γöé4 Γöé
ΓöéSoftware Γöé Γöé Γöé Γöé Γöé
ΓöéInc. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMicroSoft ΓöéMicroSoft Mouse ΓöéMcSoft Γöéser, bus, Γöé2, 3, 4, 5Γöé
ΓöéCorp. Γöé Γöé ΓöéPDI, inp Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMicroSoft ΓöéBallPoint ΓöéMcSoft Γöéser, PDI ΓöéAll (0-15)Γöé
ΓöéCorp. ΓöéTrackball Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMicrospeed ΓöéPC-Trac Trackball ΓöéBoth Γöéser, bus, Γöé2, 3, 4, Γöé
ΓöéInc. Γöé Γöé ΓöéPDI, inp Γöé5, 7 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMicrospeed ΓöéFastTRAP TrackballΓöéBoth Γöéser,B Γöé2, 3, 4, Γöé
ΓöéInc. Γöé Γöé Γöé Γöé5, 7 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMicrospeed ΓöéMicroTRAC ΓöéMcSoft Γöéser, PDI Γöé? Γöé
ΓöéInc. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMouse ΓöéPC Mouse ΓöéMouSys Γöéser, bus, Γöé2, 3, 4, Γöé
ΓöéSystems Γöé Γöé ΓöéPDI Γöé5, 7 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMouse ΓöéPC Mouse II ΓöéBoth Γöéser, bus Γöé2, 3, 4, Γöé
ΓöéSystems Γöé Γöé Γöé Γöé5, 7 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMouse ΓöéPC Mouse III ΓöéBoth Γöéser, bus, Γöé2, 3, 4, Γöé
ΓöéSystems Γöé Γöé ΓöéPDI Γöé5, 7 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMouse ΓöéOmniMouse II ΓöéMcSoft Γöéser, bus Γöé2, 3, 4, Γöé
ΓöéSystems Γöé Γöé Γöé Γöé5, 7 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMouse ΓöéThe White Mouse ΓöéBoth Γöéser, bus, Γöé2, 3, 4, Γöé
ΓöéSystems Γöé Γöé ΓöéPDI Γöé5, 7 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMouse ΓöéPC Trackball ΓöéMcSoft Γöéser, PDI Γöé2, 3, 4, Γöé
ΓöéSystems Γöé Γöé Γöé Γöé5, 7 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMouse ΓöéThe Little ΓöéMcSoft Γöéser, PDI Γöé2-15 Γöé
ΓöéSystems ΓöéMouse/PC Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCumonics ΓöéManager Mouse ΓöéBoth Γöéser Γöé1, 2, 3, 4Γöé
ΓöéCorp. ΓöéCordless Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéCumonics ΓöéManager Mouse ΓöéBoth Γöéser Γöé1, 2, 3, 4Γöé
ΓöéCorp. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPenny & ΓöéTrackerMouse TM1 ΓöéMouSys Γöéser, PDI Γöé3, 4 Γöé
ΓöéGiles Γöé Γöé Γöé Γöé Γöé
ΓöéControls Γöé Γöé Γöé Γöé Γöé
ΓöéInc. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPenny & ΓöéTrackerMouse TM1 ΓöéMouSys Γöéser Γöé3, 4 Γöé
ΓöéGiles ΓöéPlus 16 Γöé Γöé Γöé Γöé
ΓöéControls Γöé Γöé Γöé Γöé Γöé
ΓöéInc. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPenny & ΓöéTrackerMouse TM1 ΓöéMouSys Γöéser, PDI Γöé3, 4 Γöé
ΓöéGiles ΓöéPlus 32 Γöé Γöé Γöé Γöé
ΓöéControls Γöé Γöé Γöé Γöé Γöé
ΓöéInc. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPenny & ΓöéTrackerMouse II ΓöéMcSoft Γöéser, bus, Γöé? Γöé
ΓöéGiles Γöé Γöé ΓöéPDI Γöé Γöé
ΓöéControls Γöé Γöé Γöé Γöé Γöé
ΓöéInc. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPractical ΓöéThe Cordless MouseΓöéMouSys Γöéser, PDI Γöé3, 4 Γöé
ΓöéSolutions Γöé Γöé Γöé Γöé Γöé
ΓöéInc. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéProHance ΓöéProHance Power Γöéneither Γöéser, bus ΓöéAll Γöé
ΓöéTechnologiesΓöéMouse 50 Γöé Γöé Γöé Γöé
ΓöéInc. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéProHance ΓöéProHance Power Γöéneither Γöéser, bus ΓöéAll Γöé
ΓöéTechnologiesΓöéMouse 70 Γöé Γöé Γöé Γöé
ΓöéInc. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéProHance ΓöéProHance Power Γöéneither Γöéser, bus ΓöéAll Γöé
ΓöéTechnologiesΓöéMouse 100 Γöé Γöé Γöé Γöé
ΓöéInc. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéProHance ΓöéProMouse ΓöéMcSoft Γöéser, bus Γöé? Γöé
ΓöéTechnologiesΓöé Γöé Γöé Γöé Γöé
ΓöéInc. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéProHance ΓöéPS/2 Trackball ΓöéMcSoft ΓöéP Γöé? Γöé
ΓöéTechnologiesΓöé Γöé Γöé Γöé Γöé
ΓöéInc. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéProHance ΓöéPowerTrack (ball) ΓöéMouSys Γöéser, bus Γöé? Γöé
ΓöéTechnologiesΓöé Γöé Γöé Γöé Γöé
ΓöéInc. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéQtronix ΓöéMight Cat Mouse ΓöéMouSys Γöéser, bus, Γöé? Γöé
Γöé Γöé Γöé ΓöéPDI Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéQtronix ΓöéCordless Mouse ΓöéMouSys Γöéser, bus, Γöé? Γöé
Γöé Γöé Γöé ΓöéPDI Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéQtronix ΓöéTB-90 Trackball ΓöéMouSys Γöéser, bus, Γöé? Γöé
Γöé Γöé Γöé ΓöéPDI Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéQtronix ΓöéTB-90 Trackball ΓöéMouSys Γöéser, bus, Γöé? Γöé
Γöé Γöé Γöé ΓöéPDI Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéQualitas ΓöéSamurai Mouse ΓöéMcSoft Γöéser Γöé3, 4 Γöé
ΓöéTrading Co. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéSmarTEAM ΓöéSmarTEAM Mouse ΓöéMcSoft Γöéser, bus ΓöéNone Γöé
ΓöéInc. Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéSuncom ΓöéMouseTrac Γöé? Γöéser Γöé3, 4 Γöé
ΓöéTechnologiesΓöéTrackball Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéSuncom ΓöéSunMouse Γöé? Γöéser Γöé3, 4 Γöé
ΓöéTechnologiesΓöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéSuncom ΓöéICONtroller ΓöéMcSoft Γöéser Γöé3, 4 Γöé
ΓöéTechnologiesΓöémini-joystick Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéSuncom ΓöéCrystal Mouse ΓöéMcSoft Γöéser Γöé? Γöé
ΓöéTechnologiesΓöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéTandy Corp. ΓöéTandy Serial ΓöéMcSoft Γöéser Γöé3, 4 Γöé
Γöé ΓöéMouse Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéTandy Corp. ΓöéTandy 2-button ΓöéMcSoft ΓöéP Γöé0 Γöé
Γöé ΓöéMouse Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéZeny ΓöéZen Mouse ΓöéMouSys Γöéser Γöé? Γöé
ΓöéComputer Γöé Γöé Γöé Γöé Γöé
ΓöéSystems Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéZ-Nix ΓöéZ-Nix SuperMouse ΓöéMcSoft Γöéser, bus, Γöé? Γöé
Γöé ΓöéII Γöé ΓöéPDI Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéZ-Nix ΓöéZ-Nix Cordless ΓöéMcSoft Γöéser, bus, Γöé? Γöé
Γöé ΓöéSuperMouse Γöé ΓöéPDI Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 15. REFERENCES ΓòÉΓòÉΓòÉ
The following panel contains references used in the complilation of this
document as well as those recomended for further technical information.
ΓòÉΓòÉΓòÉ 15.1. Reference List ΓòÉΓòÉΓòÉ
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
Author Title Publisher Issue
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
Deitel, H. "The Design Of OS/2 Addison Wesley 1992
M., : (32 Bit OS/2)"
Kogan, M.
S.
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
Desmond, "Finding The Perfect PC World September
M., Touch" Magazine 1993
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
Flynn, M. "Mice : PC Magazine August
K. Trackballs... 1990, pp.
Choices for the New 211-277.
Generation of
Applications"
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
Howard, B. "Field Mice... PC Magazine October
Different, Yes. 15, 1990,
Better, Maybe." pp.
111-133
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
IBM "OS/2 2.0 Technical International First
Library Physical Business Edition
Device Driver Machines Corp. 1992, IBM#
Reference Version 10G6266.
2.00"
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
IBM "OS/2 2.0 Technical International First
Library Virtual Business Edition
Device Driver Machines Corp. 1992, IBM#
Reference Version 10G6310.
2.00"
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
IBM "OS/2 2.0 Tips : IBM September IBM#
Techniques" 1992 53G1930.
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
IBM 'Red "International International April
Books' Technical Support Business 1992, IBM#
Centers, OS/2 Machines Corp. GG24-3731-
Version 2.0 Volume
2: DOS and Windows
Environment"
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
Lincoln, "Keyboards, Mice, PC World June 1990,
S. : and Trackballs With pp.
Lusty, S. The Personal Touch" 166170.
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
Mastriani, "Writing OS/2 2.0 Van Nostrand 1992.
S. J. Device Drivers In C" Reinhold
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
Smith, C. "Input Devices" PC World May 1992,
pp.
140-147.
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
Schoeller, "Serial IBM Warranty January
P. Communications and Support 1994
OS/2 2.x" Document
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ