151) 6/26/2004 178110178110  178110.html">File and Print Services for NetWare Does Not Allow OS/2 Clients to Open Files
(178110) - OS/2 Warp clients version 3.0 or 4.0 can log on to a computer running Windows NT Server 4.0 Service Pack 3 and File and Print services for NetWare (FPNW). However, the client cannot map a network drive or access a file from the command prompt.

152) 6/26/2004 177113177113  177113.html">Incomplete Print Jobs Using JetDirect over SPX
(177113) - If you have a computer running Windows NT Service Pack 2 or 3 and have the HP JetAdmin utility installed on your computer, you may see only partial print jobs during periods of intense printer usage. You must be configured to print to an HP printer...

153) 6/26/2004 174266174266  174266.html">"Print Screen" from MS-DOS Application May Print Twice
(174266) - When you use the "Print Screen" (PrintScrn) key to print the contents of an MS-DOS application running on Windows NT 4.0, two copies of the screen contents may appear in the printer output. This problem typically occurs only on very fast computers,...

154) 6/26/2004 171564171564  171564.html">TCP/IP Dead Gateway Detection Algorithm Updated for Windows NT
(171564) - You may experience a loss of connectivity to computers across the router when your primary gateway fails, even though your computer running Windows NT is configured with multiple default gateways for redundancy.

155) 6/26/2004 174058174058  174058.html">Delayed Worker Threads Causes a STOP 7A
(174058) - Delayed worker threads may cause a STOP 7A - KERNEL_DATA_INPAGE_ERROR message to be displayed.

156) 6/26/2004 171180171180  171180.html">Non-Paged Pool Memory Leak in IRP Pool Tag
(171180) - Running a service or an application that makes repeated SCSI ioctl calls may cause the computer running Windows NT Server to stop responding (hang).

157) 6/26/2004 172124172124  172124.html">Poledit.exe Does Not Get Updated During Windows NT Service Pack 3 Installation
(172124) - After you apply Windows NT 4.0 Service Pack 3 (SP3), you find that the file Poledit.exe has not been replaced as documented in the following Microsoft Knowledge Base article: 162774 Policy Editor Crashes When Using Large Custom ADM Files

158) 6/22/2004 298566298566  298566.html">"Stop 0x0000000A" error message may be displayed when you use the Novell Netware Nwfs.sys redirector
(298566) - When you use the IntranetWare Client Redirector for Windows NT (the Nwfs.sys file) by Novell Netware that is dated before May 2001, you may receive the following error message on a blue screen: Stop 0x0000000A (0x0003aa0c, 0x00000002, 0x00000000,...

159) 6/18/2004 322939322939  322939.html">You may receive a "Stop 0x00000050" error message in Windows NT 4.0 Terminal Server Edition
(322939) - Describes a hotfix for an issue that causes a Stop error message when you use your Windows NT 4.0 Terminal Server Edition-based computer.

160) 6/18/2004 831408831408  831408.html">A large segment of time is lost when you use GetTickCount in a custom program in Windows NT 4.0
(831408) - Provides a resolution for an issue that occurs when GetTickCount returns a large difference in time between GetTickCount calls in Windows NT 4.0.

161) 6/10/2004 329689329689  329689.html">You receive a "Stop 0x0000001E" error message when you try to perform a network read operation in Windows NT 4.0
(329689) - Fixes a problem in Windows NT 4.0 where you receive a Stop 0x0000001E error message when you try to perform a read operation across the network. The first argument in the error message is always c000009a.

162) 5/28/2004 279619279619  279619.html">An access violation occurs when you use DCOM operations on a multi-processor computer that is running Windows NT Server 4.0
(279619) - Fixes a problem that may occur if you run Windows NT Server on a multi-processor computer that is under heavy stress.

163) 5/27/2004 306038306038  306038.html">Your computer does not start if the SYSTEM hive is too large
(306038) - When you start your computer, you may receive the following error message: In Windows NT 4.0 Windows NT could not start because the following file is missing or corrupt: \WINNT\SYSTEM32\CONFIG\SYSTEM In Windows 2000: Windows 2000 could not start...

164) 4/29/2004 841384841384  841384.html">"STOP 0x00000079" error message after you install the security update that is described in Microsoft Security Bulletin MS04-011 on a Windows NT 4.0-based computer
(841384) - Explains how to work around a problem that may occur after you install the MS04-011 security update on a multiprocessor Windows NT 4.0-based computer.

165) 4/15/2004 187392187392  187392.html">PATCH: Stop 0x0000000A in Wind32k.sys xxxDDETrackWindowDying
(187392) - Occasionally, Stop 0x0000000A occurs in Win32k.sys during DDE cleanup as a window is closing.