Caps Lock May Not Synchronize in a Client Session When You Are Running an MS-DOS-Based Program (278709)


The information in this article applies to:

  • Microsoft Windows NT Server 4.0 Terminal Server Edition SP4
  • Microsoft Windows NT Server 4.0 Terminal Server Edition SP5
  • Microsoft Windows NT Server 4.0 Terminal Server Edition SP6
  • Microsoft Windows 2000 Server SP1
  • Microsoft Windows 2000 Advanced Server SP1
  • Microsoft Windows 2000 Datacenter Server
This article was previously published under Q278709

SYMPTOMS

When you are running an MS-DOS-based program in a Terminal Services client session, the Caps Lock status in the session may not be synchronized with the actual Caps Lock status indicator on the keyboard.

CAUSE

This problem can occur if the Caps Lock key is toggled while the current active window is not the Terminal Services session. In this case, the indicator light may not be synchronized with the existing MS-DOS-based program. A newly started MS-DOS based program runs as expected.

RESOLUTION

For Windows 2000

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

The English version of this fix should have the following file attributes or later:
   Date        Time     Version         Size        File name
   -----------------------------------------------------------
  11/03/2000   6:09PM   5.0.2195.2291     222,480   Gdi32.dll
  11/03/2000   6:09PM   5.0.2195.2303     379,152   User32.dll
  11/03/2000   5:59PM   5.0.2195.2641   1,639,760   Win32k.sys
  11/03/2000   6:09PM   5.0.2195.2228     243,472   Winsrv.dll

For Windows NT 4.0 Terminal Server Edition SP6

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:
   Date        Time     Version          Size        File name    Platform
   -----------------------------------------------------------------------
  07/11/2000   5:45PM   4.0.1381.33392     170,256   Gdi32.dll    x86
  07/11/2000   5:44PM   4.0.1381.33392     331,536   User32.dll   x86
  11/06/2000   8:54PM   4.0.1381.33472   1,276,688   Win32k.sys   x86
  08/17/2000   7:16PM   4.0.1381.33472     195,856   Winsrv.dll   x86


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 2.

MORE INFORMATION

For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:

249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes


Modification Type:MinorLast Reviewed:9/26/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbHardware kbTermServ kbWin2000PreSP2Fix KB278709
©2004 Microsoft Corporation. All rights reserved.