Changing Mouse Drivers in OS/2 1.3x

ID: Q97887

The information in this article applies to:

Microsoft LAN Manager, version 2.2

SUMMARY

If a mouse driver is configured for use with OS/2 1.3x and needs to be changed at a later date due to an incorrect selection or a change in the type of mouse being used, CONFIG.SYS must be edited to conform to the changes and the drivers must be placed on the system.

MORE INFORMATION

The following table lists the mouse drivers shipped with OS/2 1.3x, and a description and their "type" setting.


Driver         Description                  Type
------------------------------------------------

MSBUS01.SYS    Microsoft bus Mouse          MSBUS$
MSINP01.SYS    Microsoft InPort Mouse       MSINP$
MSSER01.SYS    Microsoft serial Mouse       MSSER$
MSPS201.SYS    Microsoft PS/2 Mouse         MSPS2$
PCMOU01.SYS    Mouse Systems PC Mouse       PCMOU$

**Use the Mouse Systems driver with the LogiTech three button Mouse

VISION01.SYS   Visi-On Mouse with IBM PC/AT VISION$

(For IBM PS/2 Systems Model 50 and above - Micro Channel):

MSSER02.SYS    Microsoft serial Mouse       MSSER$
MSPS202.SYS    Microsoft PS/2 Mouse         MSPS2$
VISION02.SYS   Visi-On Mouse with PS/2      VISION$

The following three lines must be in your CONFIG.SYS file regardless of the mouse you use. The xxxxxx and yyyyy parameters will be replaced with the information for the mouse you use from the table above, xxxxxx being the mouse device dependent driver (specific for the type of mouse you are using) and yyyyy being the mouse type.


   device=c:\os2\pointdd.sys (mouse pointer device driver)
   device=c:\os2\xxxxxx.sys
   device=c:\os2\mouse.sys type=yyyyy$ (device independent - used for all
                                        mice)

For example, if your system uses a PS/2 style mouse:


   device=c:\os2\pointdd.sys
   device=c:\os2\msps201.sys
   device=c:\os2\mouse.sys type=msps2$

To change the mouse your system uses from the installed version, you will need to change the xxxxxx and yyyyy values in CONFIG.SYS and ensure that the correct device dependent driver is installed on the system. The mouse drivers can be found in packed format on OS/2 1.3x Disk 2. The UNPACK.EXE program will automatically be installed in your C:\OS2 subdirectory. To unpack the driver onto your system, insert Disk 2 into drive A and type:

unpack a:\xxxxxx.sy@ c:\os2

Other Parameters

To specify that a serial mouse is connected to COM2 instead of COM1, use the "serial=" parameter:


   device=c:\os2\msser01.sys model=199 serial=com2

Note that this parameter goes on the device dependent driver line. The "model=" parameter specifies the points per inch (ppi) value for the mouse (for example, 099 for 100 ppi, 199 for 200 ppi).

Note: Serial mouse drivers must be loaded before other serial port drivers (COM01/2.SYS) in order to function properly.

The "mode=" parameter can be used on the device independent load line to specify which sessions you want to enable the mouse for.


   device=c:\os2\mouse.sys type=msser$ mode=b

A value of "b" enables the mouse in all sessions. "p" enables the mouse in only protected mode sessions, and "r" enables the mouse in only real mode sessions.

REFERENCES

"Microsoft OS/2 User's Guide"

Additional query words: 2.20 change configure 1.3

Keywords :
Version : :2.2
Platform :
Issue type :