Mouse Malfunctions in MS-DOS Applications
Article ID: 153175
Article Last Modified on 10/27/2006
APPLIES TO
- Microsoft Systems Management Server 1.0 Standard Edition
- Microsoft Systems Management Server 1.1 Standard Edition
This article was previously published under Q153175
SYMPTOMS
When an MS-DOS Application is executed from within Windows 3.1 or Windows
for Workgroups 3.11, the mouse will no longer be available or will function
erratically.
CAUSE
When a Windows 3.1 or Windows for Workgroups 3.11 client is configured with
the SMS client software, the Autoexec.bat is modified to call Client.bat,
which is located in the \Ms\Sms\Data directory. Client.bat loads
Usertsr.exe into memory in order for remote control to function.
When Usertsr.exe is loaded after the MS-DOS mouse driver, it can keep the
mouse from functioning correctly when the MS-DOS application is started
from Windows.
WORKAROUND
To avoid this problem, move the MS-DOS mouse driver statement in the
Autoexec.bat so that it occurs after the Client.bat statement.
It might be necessary to force the call to Client.bat to be inserted in a
specific location of the Autoexec.bat. For information on a method to
accomplish this, please the following article in the Microsoft Knowledge
Base:
139142 Client Setup of Systems Management Server Alters AUTOEXEC.BAT
This problem does not occur with Windows 95 clients.
STATUS
Microsoft has confirmed this to be a problem in Systems Management Server
versions 1.0 and 1.1. We are researching this problem and will post new
information here in the Microsoft Knowledge Base as it becomes available.
Additional query words: prodsms mouse DOS usertsr
Keywords: kbconfig kbenv kbnetwork kbsetup KB153175