Application Compatibility Flag Registry Setting for DOS Application Not Read Correctly

ID: q214500

The information in this article applies to:

SYMPTOMS

Normally, an administrator can use the registry to set compatibility flags for specific applications being run on Windows Terminal Clients. For example, adding the following registry key and value to HKEY_LOCAL_MACHINE on the Terminal Server will force the application, in this case NTVDM, to use the Terminal Server's Windows System folder, instead of the user's Windows folder:


   Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\Applications\ 

   KEY: NTVDM
   VALUE: Flags  reg_dword  0x400

This setting can be used to force all applications running within NTVDM to use the _Default.pif file on the server for custom settings, rather than requiring the administrator to copy the _Default.pif file to the Windows folder of each user.

After you add the Application Compatibility Flag to the registry, the application does not respond to the flag.

For additional information, please see the following article(s) in the Microsoft Knowledge Base:
QQ186499 Terminal Server Registry Settings for Applications


CAUSE

The system does not correctly retrieve the application name. Therefore, the application compatibility flag in the registry is not found.


RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, please see the following article in the Microsoft Knowledge Base:

Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack


STATUS

Microsoft has confirmed this to be a problem in Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

Additional query words: 4.00 wts tse 


Keywords          : kbbug4.00 kbfix4.00 TSESP4Fix 
Version           : winnt:4.0
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: April 9, 1999