OS2MOUSE - "ERROR LOADING OS2MOUSE.DRV" IN OS/2 2.1 SPECIAL EDITION FOR USE WITH WINDOWS VERSION 3.1 02/02/96 ======================================================================= "Error Loading OS2MOUSE.DRV" in OS/2 2.1 Special Edition for Use with Windows Version 3.1 ======================================================================= Please Read Entire Document for Full Explanation of Procedures -------------------------------------------------------------- DESCRIPTION This document describes two situations when the message, "Error loading OS2MOUSE.DRV", occurs in OS/2 2.1 Special Edition for Use with Windows Version 3.1 (hereafter referred to as "Special Edition"): * Randomly after installation of Special Edition. * When starting a WIN-OS/2 session running Special Edition. It also describes what to do if you experience an erratic mouse pointer in WIN-OS/2 sessions. RESOLUTION Note: Make sure you have a backup of any file you intend to change. Overview -------- After installing Special Edition, you cannot start any WIN-OS/2 session applications that are migrated to the OS/2 Workplace Shell. If you try to start WIN-OS/2 from a DOS Full Screen session, "Error loading OS2MOUSE.DRV" appears. Possible causes are: * The PATH statement in either the OS/2 CONFIG.SYS file or the AUTOEXEC.BAT file was not updated during installation. Changing the statement to point to the correct location of the Windows files will solve the problem. * OS/2 2.1 requires default Microsoft Windows 3.1 language, drivers, and font information to properly install the WIN-OS/2 component. Make sure the MOUSE.DRV file is in the WINDOWS\SYSTEM directory, that its size is 10672 bytes, and that it is dated 3-10-92. Any Desktop tools utility program that includes its own shell can change Windows language, driver, and font information. Utilities such as PCTOOLS for Windows, Norton Desktop, Dashboard, and others, must not be installed before Special Edition. Reinstallation of Microsoft Windows 3.1 is necessary if such a utility is present on the system. Using the "Uninstallation" feature of these utilities might not remove changes made to Windows 3.1 system files, font information, or drivers. Do a Selective Install of WIN-OS/2 to enable WIN-OS/2 support: 1. Open System Setup. 2. Select Selective Install. 3. Bypass the first window; then check WIN-OS/2 Support. 4. Select Install. Error Message Occurs Randomly ----------------------------- After the installation of Special Edition in 386/486, SX/DX, and Dell systems, "Error loading OS2MOUSE.DRV" occurs randomly. The problem occurs when the Program Manager is started and the OS2MOUSE.DRV=MOUSE.DRV statement in the SYSTEM.INI file of the WINDOWS directory is remarked out. The statement should NOT be remarked out. Do the following: Note: If either PCTOOLS for Windows or Norton Desktop for Windows was present before OS/2 for Windows was installed, only do step 5. 1. Re-create the symptom: a. Edit the SYSTEM.INI file in the WINDOWS directory. b. Change: OS2MOUSE.DRV=MOUSE.DRV To: REM OS2MOUSE.DRV=MOUSE.DRV c. Save and exit the SYSTEM.INI file. d. From the DOS command line, start Windows or a WIN-OS/2 session. The error message appears, and control passes back to the DOS session command line. --OR-- Start Windows or the WIN-OS/2 session with the /B switch. For example, at the command prompt, type the following and press Enter: WIN /B This creates the BOOTLOG.TXT file. When you edit the file, look for the load failure code, 02. e. With PCTOOLS or Norton Desktop for Windows installed: 1) Reinstall Windows base code. 2) Do a Selective Install of WIN-OS/2 support; this prompts you for both Windows and OS/2 diskettes. 3) Open the Program Manager to test Windows. 4) Reinstall PCTOOLS and Norton Desktop. 2. Correct the PATH statement in the AUTOEXEC.BAT file to point to the WINDOWS directory, if necessary. 3. Do a Selective Install of WIN-OS/2 support. This should be done only when selections were made during the original installation of OS/2 for Windows. You are prompted for either OS/2 or Windows diskettes to install various files or drivers to recover the Windows setup. Ensure the files and drivers are not deleted to avoid altering the system setup. 4. Verify that MOUSE.DRV is in the WINDOWS\SYSTEM subdirectory, is dated 3-10-92, and is 10672 bytes in size. 5. Unpack the Windows 3.1 GA mouse driver from the Windows Installation Diskette 2 to the \WINDOWS\SYSTEM subdirectory. Error Message when Starting a WIN-OS/2 Session ---------------------------------------------- When starting a WIN-OS/2 session running Special Edition, "Error Loading OS2MOUSE.DRV" appears and the session halts. Some systems experience similar symptoms if the session is started from a DOS Full Screen; the error message appears, and the DOS session halts. The same message appears if the DOS session is started from an icon. The icon reappears so quickly, the message usually is not seen. 1. Ensure MOUSE.DRV is in the \WINDOWS\SYSTEM subdirectory, is dated 3-10-92, and is 10672 bytes in size. 2. Edit SYSTEM.INI file and make sure OS2MOUSE.DRV=MOUSE.DRV is in the [Boot] section. 3. Edit the AUTOEXEC.BAT file and make sure the PATH statement includes x:\WINDOWS (x is the drive where Windows is installed). 4. Edit the CONFIG.SYS file and make sure the PATH statement includes x:\WINDOWS. 5. Do a Selective Install of WIN-OS/2 support: a. Open System Setup. b. Select Selective Install. c. Bypass the first window; then select OK. d. Check WIN-OS/2 Support. e. Select Install. If you are NOT prompted for Windows diskettes at the end of Selective Install, installation of the WIN-OS/2 component failed. Erratic Mouse Pointer in WIN-OS/2 Sessions ------------------------------------------ If you have an erratic pointer in your WIN-OS/2 programs, set the following WIN-OS/2 settings: MOUSE_EXCLUSIVE_ACCESS to ON IDLE_SENSITIVITY to 100 IDLE_SECONDS to 20 ______________________________________________________________________ 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.