Microsoft KB Archive/173994
Article ID: 173994
Article Last Modified on 11/1/2006
- Microsoft Windows NT Server 4.0, Terminal Server Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Server 4.0 Standard Edition
This article was previously published under Q173994
In certain instances under Windows NT 4.0, application code that uses the GetExtentPoint32W API and the lpszText parameter to point to text containing certain Unicode characters may fail. Using GetLastError() to find the problem in the code will have no return code. The same application running under Windows NT 3.51 does not have this problem.
Using a debugging tool to single-step through a failing application may reveal that the function fails if the data at the lpszText pointer contains extended characters. These characters include umlauts, grave accents, and so on, or any Unicode characters greater than hex value 0x100. This problem is difficult to reproduce because the application code may work fine if cStrTest is on the stack.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Additional query words: CreateCompatibleBitmap win32k prodnt
Keywords: kbbug kbenv kbfix KB173994