OSMKMOUS - MOUSE PROBLEMS RUNNING OS/2 WARP 3.0 01/26/96 ======================================================================= Mouse Problems Running OS/2 Warp 3.0 ======================================================================= Please Read Entire Document for Full Explanation of Procedures -------------------------------------------------------------- DESCRIPTION This document provides solutions to various mouse problems. RESOLUTION Notes: 1. Make sure you have a backup of any file you intend to change. 2. x is the drive where OS/2 is installed in all of the following procedures. Existing Mouse Does Not Work Correctly -------------------------------------- If the mouse that was connected to the computer before you installed OS/2 now works improperly, for example, movements appear "jerky" or the mouse does not respond when you move it, do the following: 1. Open OS/2 System. 2. Open Command Prompts. 3. Open OS/2 Window. If you installed OS/2 from a CD, continue with step 4. If you installed from diskettes, go to step 5. 4. Type ATTRIB -R x:\OS2\MOUSE.SYS and press Enter. 5. Insert the diskette that came with your mouse into drive A. This diskette contains the mouse device driver. 6. Type COPY A:\MOUSE.SYS X:\OS2\MOUSE.SYS and press Enter. 7. Shut down and then restart the system. Mouse Does Not Work after Installation -------------------------------------- If you installed a mouse while installing OS/2, or used Selective Install to install a new mouse, and the mouse is not working, you need to edit the CONFIG.SYS file. 1. At the command prompt, type E CONFIG.SYS and press Enter. 2. Delete all mouse device-driver statements in the file; for example, DEVICE=C:\OS2\MOUSE.SYS. Note: There might be more than one mouse statement. 3. Save and exit the file. 4. Shut down and then restart the system. 5. Use Selective Install to install a different mouse driver. Serial Mouse Not Working ------------------------ If the serial mouse is connected to a serial port, make sure the serial port is set up for default settings. Mouse Does Not Work on an IBM PS/2 Model 90 or 95 ------------------------------------------------- If a Model 90 or 95 has the Unattended Start Mode option (set through the System Programs), the mouse driver does not load during startup. Disable Unattended Start Mode. Mouse Does Not Work on COM3 or COM4 ----------------------------------- OS/2 supports connection to only COM1 or COM2, at the standard input/output (I/O) address and interrupt request (IRQ) setting. Mouse Pointer Does Not Move --------------------------- The mouse pointer on the screen does not move when you move the mouse. Verify that no device that uses an IRQ setting is conflicting with another IRQ setting. Mouse Statements in CONFIG.SYS ------------------------------ The mouse statements that should appear in your CONFIG.SYS file depend on the type of mouse connected to the system. Serial Mouse ------------ For a serial mouse, the CONFIG.SYS file should have the following statements: DEVICE=x:\OS2\MDOS\VMOUSE.SYS DEVICE=x:\OS2\POINTDD.SYS DEVICE=x:\OS2\PCLOGIC.SYS SERIAL=COMx DEVICE=x:\OS2\MOUSE.SYS TYPE=PCLOGIC$ COMx is either COM1 or COM2. Microsoft or IBM Mouse ---------------------- DEVICE=x:\OS2\MDOS\VMOUSE.SYS DEVICE=x:\OS2\POINTDD.SYS DEVICE=x:\OS2\MOUSE.SYS Three-Button Mouse Not Working Correctly ---------------------------------------- OS/2 supports only the 2-button mode on a 3-button mouse. If the mouse has a switch to change a 2-button mode, change the switch. If it doesn't, replace the mouse with a 2-button mouse. If you receive the following error message, the device drivers in the specified file were not installed successfully: SYS1201: The device driver "***" specified in the *** command on line *** of the CONFIG.SYS file was not installed. Line *** is ignored. The device driver specified might be: VMOUSE.SYS COM.SYS VCOM.SYS Do the following: 1. Edit the CONFIG.SYS file and remark-out (REM) the following statements: DEVICE=OS2\BOOT\COM.SYS DEVICE=OS2\MDOS\VCOM.SYS 2. Restart the system. Erratic Mouse Pointer in WIN-OS/2 Sessions ------------------------------------------ If you have an erratic pointer in your WIN-OS/2 programs, change the WIN-OS/2 settings as follows: MOUSE_EXCLUSIVE_ACCESS to On IDLE_SENSITIVITY to 100 IDLE_SECONDS to 20 Mouse Not Recognized on a non-IBM Computer ------------------------------------------ If the mouse attached to the mouse port of a non-IBM computer is not recognized, the mouse might be incompatible with the port because of the chip on the mouse adapter. Attach the mouse to a serial port. If the mouse still does not work, try a different mouse with the mouse port. Mouse and Keyboard Stop Working ------------------------------- If your system has AMI BIOS, you might have an old version. Contact the computer manufacturer for an updated BIOS level. Error Loading OS2MOUSE.DRV -------------------------- After installing OS/2, you receive the message "Error Loading OS2MOUSE.DRV" when trying to start a WIN-OS/2 session application from a DOS Full Screen session. The PATH statement in the CONFIG.SYS or AUTOEXEC.BAT file was not updated during installation. Change the statements to point to the correct location of the Windows files. 1. Go to a DOS Full Screen session; then type WINOS2/b and press Enter. 2. If "Error Loading OS2MOUSE.DRV" appears, go to an OS/2 Window session; then type the following, pressing Enter after each: CD WINDOWS E SYSTEM.INI 3. Make sure that both MOUSE.DRV=MOUSE.DRV and OS2MOUSE.DRV=MOUSE.DRV are in the [Boot] section. 4. Make sure the MOUSE.DRV file is dated 3-10-92 and is 10672 bytes. 5. Check the WIN.INI file for duplicate statements. Rename any duplicate statements that you find. 6. If the above does not correct the problem, do a Selective Install of the mouse support. 7. If the problem is still not corrected, do a Selective Install of WIN-OS/2 Support. Mouse Does Not Work in WIN-OS/2 Using OS/2 Warp 3.0 --------------------------------------------------- There is a white mouse pointer in the middle of the screen in a WIN-OS/2 session, but the mouse does not work. In a WIN-OS/2 Window session, the mouse pointer is black on the OS/2 Desktop. When the mouse pointer is moved over the window session, the pointer turns into an hour glass. In both cases the keyboard works. Check the IRQ settings. There is probably an IRQ conflict between serial ports. If the mouse is on COM1, disable COM3 or assign it to another IRQ. You can change COM3 and COM4 IRQs and addresses; for example: x:\OS2\COM.SYS(3,03e8,2) Note: If you want to use IRQ5, you must disable LPT port 2. If you use IRQ 2 or 9, remember that these are connected IRQs. ______________________________________________________________________ IBM disclaims all warranties, whether express 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. Copyright (c) 1994, 1996 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.