The information in this article applies to:
- Microsoft Windows operating system versions 3.0, 3.0a
SYMPTOMS
If more than one virtual machine (VM) runs the Microsoft mouse driver
in 386 enhanced mode, the mouse driver for the additional virtual
machines returns error messages. In some cases, when you return to
Windows, the mouse stops responding (hangs).
MORE INFORMATION
Steps to Reproduce Problem
- Start Windows 3.0 in 386 enhanced mode without an MS-DOS-level
driver present (that is, without MOUSE.SYS or MOUSE.COM).
- In the Program Manager, start an MS-DOS command prompt. At the
MS-DOS command prompt, type "mouse.com" (without the quotation marks)
and press ENTER. The Microsoft mouse driver displays the message
"Mouse driver installed."
- Type "exit" (without the quotation marks) to return to Windows.
Windows then sends a message to the MS-DOS screen about "Windows
Pop-Up Program Support."
- In the Program Manager, start an MS-DOS command prompt again. At
the MS-DOS command prompt, run MOUSE.COM again (see step 2). The
Microsoft Mouse driver displays the message "Driver not installed --
interrupt jumper missing."
- Press ALT+TAB to return to Windows.
The mouse is frozen.
- Press ALT+TAB to return to the MS-DOS command prompt. Type "exit"
(without the quotation marks).
You can now use the mouse again.
- Repeat steps 4-6.
The mouse is frozen again.
STATUS
Microsoft has confirmed this to be a problem in Windows versions 3.0
and 3.0a. We are researching this problem and will post new information
here in the Microsoft Knowledge Base as it becomes available.
|