BUG: Windows NT Version 4.0 Bug List - USER

Last reviewed: November 25, 1997
Article ID: Q156853

The information in this article applies to:
  • Microsoft Windows NT, version 4.0

SUMMARY

This article lists the bugs in the implementation of the Win32 API on Windows NT 4.0 that may be relevant to Application or Device Driver developers (ISVs or IHVs). This article contains only those bugs that were known at the time of the Windows NT 4.0 release.

MORE INFORMATION

- CreateWindowEx() with bogus EXSTYLE bits succeeds on win95 but fails on NT.

- NetDDE memory leak when retrying to establish connection to unreachable nodes.

- Menu hilite distorted if submenu removed during WM_INITMENUPOPUP.

- Menu item with 2 bitmaps is not displayed correctly.

- ShellExecute() returns the process ID of the app spawned via DDE instead of hInstance.

- SetVolumeLabel() does not check invalid characters for NTFS volume label.

- SHGetFileInfo() fails (Access Violation) when called using Desktop PIDL.

- Passing GetFileTitle() bogus Path\Filename can cause subsequent calls to fail.

- VerFindFile() does not return VFF_FILEINUSE when the file is in use.

- FindExecutable( ) fails if lpDirectory is set to a relative path.

- winhlp32: PositionWindow macro does not work for values off screen.

- winhlp32: Find macro doesn't take User to Found Text.

- winhlp32: Shellexecute macro does not work when called from hotspot.

- winhlp32: Bitmap buttons are distorted when using large system fonts.

Keywords          : UserMisc sdkbuglist40 kblist kbbuglist
Version           : winnt:4.0
Platform          : NT WINDOWS
Issue type        : kbbug


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: November 25, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.