BUG: GetTextExtentPoint Fails in App Based on Windows/Win32s (147647)
The information in this article applies to:
- Microsoft Windows Software Development Kit (SDK) 3.1
- Microsoft Win32 Application Programming Interface (API), when used with:
- the operating system: Microsoft Windows NT 3.51
This article was previously published under Q147647 SYMPTOMS
GetTextExtentPoint fails when all of the following conditions are present:
- You have either a 16-bit application running under Windows 3.1 or a
32-bit application running under Win32s.
- The application uses GetTextExtentPoint().
- The string buffer parameter has been allocated with GlobalAlloc() or has
been reallocated with GlobalReAlloc().
- The string size is an exact multiple of 32 bytes.
Under Win32s, GetLastError returns an error 87 (Invalid Parameter). The
debug version of Windows 3.1 displays a Fatal Exit code 0x700A with this
error message:
GetTextExtentPoint - Invalid string
CAUSE
As stated earlier, this problem occurs only when the allocated size of the
string is an exact multiple of 32 bytes.
This is a bug in Microsoft Windows 3.1 that causes ramifications in a
16-bit application running under Windows 3.1. A 16-bit application running
under Windows NT 3.51 will have the same problem, but it will run without
any problems under Windows 95.
This bug is not specific to Win32s. However, because Win32s runs under the
Windows environment, a 32-bit application running under Windows 3.1 by way
of Win32s will also exhibit this problem. However, a 32-bit application
running under Windows NT or Windows 95 will not exhibit this problem.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article. We are researching this problem and will
post new information here in the Microsoft Knowledge Base as it becomes
available.
Modification Type: | Major | Last Reviewed: | 4/12/2004 |
---|
Keywords: | kbGDI KB147647 |
---|
|