BUG: Win32 on Windows NT Version 3.51 Bug List - Base

Last reviewed: September 25, 1995
Article ID: Q136432
The information in this article applies to:
  • Microsoft Win32 Application Programming Interface (API) included with:

        - Microsoft Windows NT version 3.51
    

SUMMARY

This article lists the bugs in the Win32 API implemented on Windows NT version 3.51 that were known at the time the product was released.

MORE INFORMATION

  • Call CreateProcess() with the command line "myapp" in the directory where Myapp.exe exists. CreateProcess() does not execute myapp.exe if the directory that contains Myapp.exe also contains a subdirectory named Myapp.
  • FindFirstFile() returns incorrect file time on FAT.
  • GetMailSlotInfo() returns the wrong next message size.
  • 32-bit string I/O instructions are not supported.
  • NetUserSetInfo() returns NERR_PasswordTooShort instead of returning NERR_PasswordHistConflict during password history conflict.
  • NetGroupAdd() returns the wrong error code with invalid group name.
  • LogonUser() is not multithread protected.
  • Logon to a domain doesn't generate a logon event on the DC.
  • The documentation for MsgWaitForMultipleObjects() says that the API returns successfully when either the objects are signalled or the input is available. However, the API behaves as if it requires that the objects are signalled and the input is available.
  • CreateProcess() fails to locate .exe file is the current directory is a UNC name.
  • SetLastErrorEx() does not raise a RIP_INFO debug event.
  • The Characteristics field of the IMAGE_IMPORT_DESCRIPTOR structure is declared incorrectly in Winnt.h. The field is really the RVA of the INT array.
  • ASCII characters in the command line of a console application are converted to ANSI.
  • The SourceName and Computername fields of the EVENTLOGRECORD structure are not WCHAR if you call the ANSI version of the API. They should be declared TCHAR.
  • WINDEF.H should define CDECL as __cdecl.
  • AddAtom does not return an error for an illegal parameter.
  • CreateFileMapping() of a device handle returns different error codes from FAT, NTFS, and CDFS. The error on NTFS is ERROR_INVALID_PARAMETER, while the error on FAT and CDFS is ERROR_BAD_EXE_FORMAT.
  • InterruptRegister() does not notify of Ctrl+Alt+SysRq.
  • Windows NT cannot use or boot from a DblSpace drive.
  • Overlapped I/O that extends the file is not asynchronous on NTFS.
  • Using file compression causes the mouse to become unresponsive.
  • Deleting *.tes deletes file.test, because its short name is file~1.tes.
  • Windows NT can only mount up to 26 file systems.
  • GetInformationByHandle returns an incorrect link count over the network.
  • OpenSCManager() does not work when passed the name of the local machine.
  • Service Control Manager will not delay more than 20 seconds PENDING time with SERVICE_PAUSE_PENDING, then error 2186 is generated.
  • If a service has a timeout of 30 sec, the value stored in the event log is 30 msec.
  • The service controller does not allow multiple logged-on services which share a process.
  • Redirected drives created by services not listed by net use.
  • QueryServiceObjectSecurity corrupts the handle if passed an invalid pointer for the security descriptor.


Additional reference words:
KBCategory: kbprg kbbuglist
KBSubcategory: BseMisc


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: September 25, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.