BUG: Win32 SDK Version 3.51 Bug List - WOW and Subsystems

MORE INFORMATION

WOW

• Windows NT loses long file names saved by 16-bit Windows-based applications.

• 16-bit Windows-based applications require DLLs on the local machine.

• GetExitCodeProcess() does not return exit codes for 16-bit Windows-based applications in WOW.

• Locking at negative offsets fails in WOW.

• WOW incorrectly handles the FBSTP instruction.

• WOW incorrectly handles FISTP DWORD PTR.

• GetWindowPlacement() returns the wrong length in WINDOWPLACEMENT in WOW.

• WOW EndDeferWindowPos() does not return a nonzero value for success.

• You cannot change the number of NetBIOS names available for WOW.

• GetMessageTime() can return a value greater than GetCurrentTime() returns.

• Custom focus does not work in WOW.

• WOW WNetServerBrowseDialog() returns WM_SUCCESS, not WM_CANCEL, when the user clicks the Cancel button.

• WOW WNetDisconnectDialog() returns error 5 for printers under WOW, even printers connected explicitly with the NET USE command.

• Printing from 16-bit Windows-based applications using old quick linker fails in WOW.

Subsystems

• A remote NetUserAdd from the OS/2 subsystem causes an internal OS/2 subsystem error.

• Calls to OS/2 DosSemClose can fail if another process called DosSemWait on the same semaphore.

• OS/2 queue handles should be enumerated starting from 1, not 0.

• OS/2 DosPeekQueue causes a general protection (GP) fault in the OS/2 subsystem.

• POSIX printf does not handle EINTR.

• POSIX does not handle NTFS_MAX_LINK_COUNT.

• Command prompt is changed by MS-DOS-based applications upon exit.

• INT 21, function 60 returns incorrect UNC handles.

• The mouse pointer is reset with Full Screen MS-DOS-based applications.

• The mouse pointer trapped in the upper-left corner with MS-DOS-based applications.

• VddInstallHook() does not block duplicate mappings.

• Line-by-line scrolling by pressing CTRL+UP and CTRL+DOWN does not work in an MS-DOS-based editor if NUM LOCK is enabled.