Terminal Server Creates Separate NTVDM for Each 16-bit Process Created from a Client Session |
Q216995
The information in this article applies to:
- Microsoft Windows NT Server versions 4.0, 4.0 SP4, 4.0 SP6, Terminal Server Edition
- Microsoft Windows 2000 SP1 Professional
- Microsoft Windows 2000 SP1 Server
- Microsoft Windows 2000 SP1 Advanced Server
SYMPTOMS
When a user runs an application written in 16-bit code, Terminal Server and Windows 2000 SP1 may start separate NTVDMs for each instance of the application started. This is not the expected behavior of a 16-bit application and may cause behavior problems for the 16-bit application.
RESOLUTION
NOTE: If you are running Windows 2000 with Service Pack 1, you must roll back to Windows 2000 with no Service Pack installed to work around this issue. If you are running a Microsoft NT Terminal Server with Service Pack 6, you must roll back to Service Pack 5 to work around this issue.
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 : TSESP4Fix
Issue type : kbbug
Technology : kbWinNTsearch kbWinNTSsearch kbWinNTS400xsearch kbWinNTS400 kbNTTermServ400 kbNTTermServSearch
Last Reviewed: November 29, 2000 |
