home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
RMOUSE.FAX
< prev
next >
Wrap
Text File
|
1995-02-22
|
7KB
|
159 lines
OS2MOUSE - LOADING OS2MOUSE.DRV ERROR MESSAGE
10/19/94
================================================================
LOADING OS2MOUSE.DRV ERROR MESSAGE
================================================================
Please Read Entire Document for Full Explanation of Procedures
----------------------------------------------------------------
ERROR LOADING OS2MOUSE.DRV IN OS/2 FOR WINDOWS SPECIAL EDITION
OVERVIEW
After installing OS/2 2.1 Special Edition for Windows, you
cannot start any WIN-OS/2 session Applications that are
migrated to OS/2's Workplace Shell. If you try to start
WIN-OS/2 from a DOS Full Screen session, the error message
ERROR LOADING OS2MOUSE.DRV appears.
1. The PATH statement in either OS/2's CONFIG.SYS or
AUTOEXEC.BAT was not updated during installation.
Changing these statements to point to the correct
location of the Windows files resolves the problem.
2. OS/2 2.1 requires default Microsoft Windows 3.1 language,
drivers, and font information to properly install the
WIN-OS/2 component. Ensure the MOUSE.DRV file is located
in the WINDOWS\SYSTEM directory and is 10672 bytes in
size and dated 3-10-92.
Any desktop tools utility that includes it's own shell can
change WINDOWS language, driver, and/or font information.
Utilities such as PCTOOLS for Windows, NORTON DESKTOP,
Dashboard, and others must not be installed before installing
OS/2 2.1 for Windows Special Edition. Reinstallation of
Microsoft Windows 3.1 is necessary if such a utility is
present on the system. Using the "Uninstallation" of these
utilities MAY NOT remove changes made to Windows 3.1 system
files, font information and/or drivers.
Do a Selective Install of WIN-OS/2 to enable WIN-OS/2 support:
1. Select Selective Install from the System Setup Folder.
2. Bypass the first panel of the utility.
3. Place a check mark on WIN-OS/2 Support.
4. Select Install.
ERROR LOADING OS2MOUSE.DRV OCCURS RANDOMLY AFTER INSTALL OF OS/2
2.1 FOR WINDOWS SPECIAL EDITION
SYMPTOMS:
Error loading OS2MOUSE.DRV occurs randomly in 386/486, SX/DX
and Dell systems. This failure occurs in systems where the
statement OS2MOUSE.DRV=MOUSE.DRV is REMed in SYSTEM.INI in
the Windows directory after installation of OS/2 2.1 for
Windows Special Edition,and PROGRAM MANAGER is started.
The statement should not be REMed. It becomes REMed when the
error is recreated.
NOTE: If either PCTOOLS for Windows or NORTON DESKTOP for
Windows is present prior to OS/2 for Windows being
installed, only do step 5.
RESOLUTION:
Recreate the symptom as follows before trying procedure for
resolution:
1. Edit SYSTEM.INI statement in Windows directory to:
REM OS2MOUSE.DRV=MOUSE.DRV
2. Save new SYSTEM.INI. Start Windows (or WIN-OS/2 session)
from DOS command line.
3. Error message appears: Error loading OS2MOUSE.DRV
4. Control passes back to the VDM command line.
Or,
With SYSTEM.INI edited, start Windows or WIN-OS/2 session
with /B switch. Example, at command prompt, Type:
WIN /B and press Enter
This creates BOOTLOG.TXT file. When you edit the
BOOTLOG.TXT file,the load failure code is 02.
5. With PCTOOLS or NORTON DESKTOP for Windows installed:
A. Reinstall Windows base code.
B. Selectively install WIN-OS/2 support, which prompts
you for both Windows and OS/2 diskettes.
C. Bring up Program Manager to test windows.
D. Reinstall PCTOOLS and NORTON DESKTOP.
RESOLUTION:
After recreating error or viewing symptom:
1. Correct PATH= statement in AUTOEXEC.BAT to point to
WINDOWS directory, if necessary.
2. Selective Install of WIN-OS/2 support. This should only
be done when selections were made during the original
install 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
that the files and drivers are not deleted to avoid
altering the system configuration.
3. Verify that MOUSE.DRV is located in the WINDOWS\SYSTEM
directory, is dated 3-10-92, and is 10672 bytes in size.
4. Unpack the Windows 3.1 GA mouse driver from WINDOWS
Installation Diskette 2 to X&colon.\WINDOWS\SYSTEM directory.
ERROR LOADING OS2MOUSE.DRV ERROR IS ENCOUNTERED WHEN STARTING A
WINOS2 SESSION RUNNING OS/2 2.1 FOR WINDOWS SPECIAL EDITION.
SESSION HALTS.
SYMPTOMS:
Some systems are experiencing similar symptoms when WINOS2
Sessions (Full Screen or Seamless) cannot start. If the
Session is started from a DOS Full Screen, the error message,
Error Loading OS2MOUSE.DRV appears and the VDM is halted.
The same error appears from the VDM if the Session is
started from an Icon. The Icon reappears so quickly, the
message is usually not seen.
1. Ensure MOUSE.DRV, located in the X&colon.\WINDOWS\SYSTEM
directory is dated 3-10-92 and is 10672 bytes in size.
2. Edit SYSTEM.INI to ensure the OS2MOUSE.DRV=MOUSE.DRV
This statementis located in the BOOT paragraph.
3. Edit AUTOEXEC.BAT to determine the path statement
includes X&colon.\WINDOWS.
4. Edit CONFIG.SYS making sure the PATH=STATEMENT includes
X&colon.\WINDOWS.
NOTE: X&colon.\ = is the drive where Windows 3.1 resides
\WINDOWS = is the Directory for Windows 3.1
5. Do a Selective Install of WIN-OS/2 to enable
WIN-OS/2 support:
A. Select Selective Install from System Setup folder
B. Bypass the first panel of the utility, select OK
C. Place a checkmark on WIN-OS/2 Support
D. Select Install
6. 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.