Copyright: Copyright 1993 Microsoft Corp.
Citation: Copyright 1993 Microsoft Corporation. All rights reserved.


 Windows NT 3.5 U.S. Service Pack 3

Prepared 06/13/95

 README.TXT File

 Fixlist Knowledge Base Articles

THE INFORMATION IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES EITHER EXPRESSED OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR 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 FORGOING EXCLUSION OR LIMITATION MAY NOT APPLY.Copyright (c) 1994 Microsoft Corporation.  All rights reserved.


README.TXT File
 Windows NT 3.5 U.S. Service Pack 3

 README.TXT File

 README.TXT: Windows NT Version 3.5 U.S. Service Pack

 Fixlist Knowledge Base Articles


Fixlist Knowledge Base Articles
 Windows NT 3.5 U.S. Service Pack 3

 README.TXT File

 Fixlist Knowledge Base Articles

 CALC.EXE Display Error in Floating Point Number Calculation

 WinNT 3.5 Software Update for the Pentium Floating Point Error

 GP Fault in WINLOGON.EXE

 Mail Fails with Memory or Network Errors

 Diamond Viper VLB Video Adapter Driver Fails To Load

 Backup Creates Many REGXXXX Files, Can't Copy .EVT Files

 File Write to Network Share Using MS-DOS 21h Function Fails

 Can't Choose Paper Tray with Postscript Printer Driver

 MIPS Four-Processor Computer Halts for Long Time

 SET Batch File Command Resets Error Levels

 Two Token Ring Adapters Forces Source Routing on Both Adapters

 Printing Postscript from Project, Task Bars Shaded or Darkened

 Error and Warning Events Not Described in System Log

 STOP Message on MIPS Computer Caused by NET Command

 Fonts Look Different When Printed and on Screen

 Copy from One Novell Server to Another Fails

 ACLs Not Translated When User Names Have Extended Characters

 Watermark Software HP 1300T Removable Disk Stuck or Corrupted

 Err Msg: "Out of Memory" Browsing Network Files as Administrator

 Turkish Characters in Directory Name Hangs Windows NT

 Cannot Input Unicode Characters >256 into Dialog Edit Field

 Characters Change When Pasted into 16-bit Applications

 SFM: Copying Files Between Volumes Freezes Other Mac Clients

 Err Msg: "Access denied" Running MS-Mail SMTP Gateway in VDM

 Kyocera FS-3500A PCL Driver Will Not Print from Lower Paper Tray

 WinNT 3.1 to 3.5 Upgrade Does Not Copy OEM SCSI Drivers to Disk

 Dual Processor MIPS Computer with Proteon NIC Hangs At Startup

 STOP: 0x0000000A When CadexNet on LM Clients Stress SRV.SYS

 STOP 0x0000001E in SRV.SYS

 Alert for "<" Condition Fails to Run Batch File

 STOP Message Caused by NTFS with Long Filenames

 Deadlocks When Using Asynchronous Named Pipes

 Err Msg: Access Denied Connecting to NetWare Resource

 Format Limits Stripe Sets to 4 GB

 Event Id 2000 Errors In System Log

 Err Msg: System Error 59 Has Occurred, an Unexpected...

 "Insufficient Memory" Messages Appear When You Use Word 6

 Err Msg: Mail Could Not Read the Entire Message...

 Unexpected Network Error When Changing WfWG Password

 LMHOSTS #INCLUDE of Local Files May Fail on Windows NT 3.5

 Err Msg: OS Loader V3.5 Windows NT Could Not Start...

 Memory Leak in LMREPL Service

 Error Message with Compaq Smart SCSI

 Print Job Stalls Printing to NEC NPDL2

 Justified Words Printed with PostScript Driver Contain Spaces

 Closing Timed-Out Applications Without Choosing End Task

 Windows NT 3.5 Fails to Unlock a Record Area After Locking It

 Client Hangs Accessing Remote Downlevel LAN Manager Server

 Err Msg: The Remote Computer is Not Available

 Windows NT 3.5 Computer with Intel Neptune PCI Chip Hangs

 Time and Date Stamp of Word 6.0 Document Updated

 Backup Incorrectly Sets Archive Bit on WFWG 3.11 Files

 Extra Keys on Brazilian Keyboard Do Not Work at Command Prompt

 SFM Performance Degrades Due to Memory Problem

 Err Msg: STOP Message in DLC.SYS

 Multiple ISDN Adapters Cannot Be Installed

 Administrators Permissions for a Printer Change to Read

 Graphics and True Type Fonts Print Garbage on Okidata ML320

 Changing Registry Does Not Prevent User from Changing Delay

 CACLS.EXE Err Msg: No More Internal IDs Available

 Windows NT Backup Writes Incorrect Times To Log

 STOP 0x0000001e Err Msg with NetBEUI Client/Server Applications

 Unexpected Error Accessing MS Mail Postoffice Through GSNW

 Cannot Run RAS Programs When a Service References RASAPI32.DLL

 Secure Erase on Exabyte 2501 Err Msg: The Computer Has Rebooted

 Windows NT Err Msg: No more connections to the remote...

 Opening a File Causes the Application to Close

 Invalid User Names Causes Memory Leak

 Error Updating PowerPoint 4.0 File Using CSNW/GSNW

 Server Service Hangs When Using GSNW

 Can't Get Zone Information with Compaq Netflex II TR NIC

 Sequential File Reads of 4K Instead of 64K Blocks

 CD-ROM File System Does Not De-allocate Non-paged Pool Memory

 Windows NT Setup Err Msg on Compaq: Stop 0x0000008B

 FTP OnNet 1.1 PPP Client Hangs Windows NT 3.5 RAS Service

 Event Log Service Fails to Start Due to Event Log Corruption

 Memory Loss During Application Process Creation

 Registry Editor Hangs When You Select a Key

 Cannot Build VC++ Projects (.PDB & .PCH Files) on Netware Server

 Forced Disconnect for Macintosh Users Not Working

 STOP 0x00000026 when Accessing a CD Using an Indirect Path

 Non Critical Error with IR32_32.DLL and Mitsumi IDE CD-ROM

 Windows NT 3.1 Computer Cannot Log On to Windows NT 3.5 Domain

 SFM: File Permissions Problem When Volume is Shared at Root

 Error 33: DOSRead and DOSWrite APIs from OS/2 Application

 Service Logged On w/ User Account Able to Interact with Desktop

 Unable to Disable Print Event Logging in Windows NT 3.5

 VBApp & OLE Do Not Work If Network Components Are Not Installed

 DC21040 Causes Windows NT 3.5 to Stop Responding (Hang)

 SFM Err Msg: The Item...Is Missing and Was Probably Deleted...

 DHCP Client Does Not Support Domain Name Option

 Very Large or Very Small Transfers to SCSI Printers Fail

 STOP Message with SFMATALK.SYS

 STOP Message 0x0A Running Performance Monitor on NEC 3360

 Problems Accessing Drive Formatted with Ontrack Disk Manager

 Using Ontrack Disk Manager to Support Large IDE Drives

 Slow Processing with Windows NT PDC and LAN Manger BDC

 Application in VDM May Receive Overrun Error

 STOP 0x0000000A when Accessing NetWare Server

 NTFS Integrity Problems with Large Stripe Sets

 Event Viewer Does Not Report System Log Errors Correctly

 Software Compression Compatibility in Windows NT 3.5 RAS

 Computer with Intel Neptune PCI Chip Hangs on Warm Reboot

 Windows NT3.5 Improves Performance with Intel Neptune PCI Chip

 Setup Err Msg on Intel Xpress Deskside: Inaccessible Boot...

 16-Bit Process Creation Can Result in Memory Loss

 Equinox Serial Driver Causes the Win16 Subsystem to Fail

 DCs Fail to Synchronize or Validate Users Over NWLINK

 Clients Fail to Connect to Windows NT Server

 LMHOSTS File Generates STOP 0x00000050

 Date and Time Stamp of Files Change When Copied to Netware

 Running PKZIP Hangs WFW or Windows NT MS-DOS Command Prompt

 Event Error 2000 Logged Repeatedly Due to Illegal Command

 GSNW Share Names Displayed as DELETED with RAS Server Running

 File Size and Date Reported Incorrectly On NTFS Drive

 Windows NT Mail Err Msg: The Network Path You Entered Could...

 RAS Callback Via ISDN Uses Only One Channel

 SNA Server: Windows NT Client Loses Session To Server

 Can not Create NetBIOS Session Over TCP/IP

 FDDI MAC Address Issue with Windows NT 3.5

 NPMCA.SYS Causes STOP 0x0A in TCPIP.SYS

 STOP 0x24 Generated With NTFS

 IBM Token Ring /A Adapter Fails To Start in Windows NT 3.5

 STOP 0x0A in STREAMS.SYS with DEC Pathworks Loaded

 LAN Manager Clients Cannot See Windows NT Computers

 Printing to WinNT Queue Attached to NetWare Queue Hangs NetWare

 Problems Using Event Viewer from Windows for Workgroups

 Granularity Value Changes After Installing Service Pack 2

 Seed Routing Not Working With C.O.P.S. LocalTalk NIC

 Setting BDC to be WINS Proxy Agent May Cause Broadcast Storms

 Stop Msg: C0000218 "Unknown Hard Error" When Registry is Overrun

 IPX Subnet Clients Unable to Connect to Windows NT

 NT to LAN  Manager UAS Replication Problem after using PORTUAS

 Enumeration of Large NTFS Directory Takes a Long Time

 RAS Event ID 20013: The User Connected to Port...

 Memory Leak: MS-DOS-Based Apps Starting Non-MS-DOS-Based Apps

 Periods Not Displayed in CD-ROM Disc Volume Label

 PCI Adapter Incorrectly Identified on Dual-bus Computers

 Systems Management Server Inventory Via RAS Causes STOP Screen

 Large Zeroing Operations Cause Systems To Appear Hung

 Windows NT 3.5: STOP 0x0000000a in NETBT.SYS When Memory is Low

 Frame Corruption in Retransmitted IPX Packet

 STOP Msg: 0x0000000A or 0X0000001E Dis/Reconnecting to WfWG Svr

 Unable to Change Printer Settings From Windows Applications


README.TXT: Windows NT Version 3.5 U.S. Service Pack

Article ID: Q123863

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

Following is the README.TXT file that accompanies the Microsoft Windows

NT 3.5 Workstation and Server U.S. Service Pack 3:

---------------------------------------------------------------------------

              Microsoft Windows NT 3.5 Workstation and Server

                            U.S. Service Pack 3

---------------------------------------------------------------------------

Contents

--------

1.0  Introduction

2.0  Installation Instructions for the Windows NT 3.5 U.S. Service Pack 3

2.1  User Notes

2.2  List of Bugs Fixed in Windows NT 3.5 U.S. Service Pack 3

1.0  Introduction

-----------------

This release of Microsoft(R) Windows NT(TM) 3.5 U.S. Service Pack 3 is

easy to apply from within Windows NT and changes only those files that

were originally set up on the Windows NT Workstation or Windows NT Server

system.  Service Pack releases are cumulative: they contain all previous

fixes, as well as any new fixes made to the system.

2.0  Installation Instructions for the Windows NT U.S. Service Pack

-------------------------------------------------------------------

Installing the Service Pack from a floppy disk:

1.  Insert Service Pack Disk 1 into the floppy drive.

2.  At the Windows NT Command Prompt, change to that floppy drive (that is,

    A: or B:) and type UPDATE.

3.  Follow the instructions given on the screen.

Installing the Service Pack from a CD-ROM:

1.  Insert the Service Pack CD-ROM disk into the CD-ROM drive.

2.  At the Windows NT Command Prompt, change to that CD-ROM drive, then

    change to the i386, MIPS, or ALPHA directory (depending upon whether

    you have an Intel(TM), MIPS(R), or ALPHA AXP(TM) CPU), and type UPDATE.

3.  Follow the instructions given on the screen.

Installing the Service Pack from a network drive:

1.  At the Windows NT Command Prompt, type the command to connect to the

    network drive on which the Service Pack files reside.

2.  Change to that network drive and type UPDATE.

3.  Follow the instructions given on the screen.

2.1  User Notes

---------------

*** Emergency Repair Disk

If it is necessary to use the Windows NT Emergency Repair Disk to repair

your Windows NT system at some time after you apply the Service Pack, you

will need to re-apply the Service Pack after the repair is completed.  This

is because the Emergency Repair Disk repairs your system by restoring your

original Windows NT setup.  After the repair has completed, simply follow

the above Installation Instructions to reapply the Service Pack.

*** Adding New Components to the System

If new software or hardware components are changed or added to your system

after you have applied the Service Pack, it will be necessary to reapply

the Service Pack.  This is because the files taken from the original

Windows NT disk set may not be equivalent to the files on the Service Pack

disk set.

It is not possible to install new components directly from the Service Pack

media (such as a new keyboard or printer driver).  New components must be

installed from the original product media.

*** Installing Symbol Files from the CD-ROM

To install the symbol files corresponding to the new binaries in Service

Pack 3, do the following (assuming your CD-ROM drive is D:, your symbol

files are located in the C:\WINNT\SYMBOLS directory, and you are installing

the files for an x86 machine):

    XCOPY /S /U /D D:\SUPPORT\DEBUG\I386\SYMBOLS C:\WINNT\SYMBOLS

This will copy the Service Pack 3 .DBG files over the existing versions of

these files.  The XCOPY command shown will copy only those .DBG files that

are already installed (/U switch), and only those with a more recent time-

date stamp (/D switch).

*** Remote Access Service (RAS)

Several fixes were made to Windows NT Remote Access Service (RAS) that are

included in this Service Pack. Following is background information on

client compatibility with RAS.

NOTE: If you don't already have RAS installed, install it from your

original Windows NT setup media before applying the Service Pack.

RAS Software Compression Compatibility with WFW 3.11 And Windows NT 3.1

In addition to other fixes, the Service Pack installs files that make

Windows NT 3.5 software compression compatible with Windows for Workgroups

(WFW) 3.11 and Windows NT 3.1. Throughput should improve significantly

unless previously compressed files are copied. For best performance

Microsoft suggests you configure the RAS client software on WFW 3.11,

Windows NT 3.1, and Windows NT 3.50 as follows:

1. In Remote Access, make sure the Disable Software Compression option in

   the Options menu is clear (not checked).

2. Choose Edit, choose Modem, and select the following:

    - Enable Hardware Flow Control

    - Enable Modem Error Control

   Clear the Enable Modem Compression check box so software compression

   and modem compression are not used at the same time (as this reduces

   throughput).

Windows NT 3.5 RAS Clients Need No Change for RAS Software Compression

If you install the Service Pack on a Windows NT 3.5 RAS server, unmodified

Windows NT 3.5 RAS clients do not lose software compression compatibility

when calling the RAS server. WFW 3.11 and Windows NT 3.1 RAS clients can

use RAS software compression without any need for new files, except as

noted below.

All copies of Windows NT 3.5 have RAS software compression built-in. Only

Windows NT 3.5 computers that are acting as RAS servers need the Service

Pack for compression compatibility with Windows NT 3.1 and WFW 3.11 RAS

clients. However, because of several code improvements, Microsoft

recommends that you also apply this patch to Windows NT 3.5 RAS clients.

The patch is required for RAS software compression compatibility when you

call a Windows NT 3.1 or WFW 3.11 RAS server from a Windows NT 3.5 RAS

client.

Software Compression in WFW 3.11 and Windows NT 3.1 RAS Clients

Software compression is available by default on these RAS clients unless

you set the Disable Software Compression option in the Options menu or you

purchased your copy of WFW 3.11 or Windows NT 3.1 after February 1994. You

can tell whether you have RAS software compression or not by using the

following information:

Windows for Workgroups 3.11:

   File name    Bytes   Compression

   ----------   -----   -----------

   RASMAC.386   49209   YES

   RASMAC.386   27193   NO

Windows NT 3.1:

   File name      Bytes    Compression

   ------------   -----    -----------

   ASYNCMAC.SYS   53188    YES

   ASYNCMAC.SYS   53716    YES

   ASYNCMAC.SYS   33732    NO

NOTE: The Windows NT 3.1 and Windows for Workgroups 3.11 RAS compression

files can be obtained from the SUPPORT\RAS directory on the Windows NT 3.5

U.S. Service Pack 3 CD.

2.2  List of Bugs Fixed in Windows NT 3.5 U.S. Service Pack 3

-------------------------------------------------------------

NOTE: Use the Qxxxxxx number that precedes the title of the bug fix to

query the Microsoft Knowledge Base to find an article about that bug.

Q122182: CALC.EXE Display Error in Floating Point Number Calculation

Q122323: WinNT 3.5 Software Update for the Pentium Floating Point Error

Q110882: GP Fault in WINLOGON.EXE

Q110932: Mail Fails with Memory or Network Errors

Q110947: Diamond Viper VLB Video Adapter Driver Fails To Load

Q111026: Backup Creates Many REGXXXX Files, Can't Copy .EVT Files

Q111027: File Write to Network Share Using MS-DOS 21h Function Fails

Q111325: Can't Choose Paper Tray with Postscript Printer Driver

Q111420: MIPS Four-Processor Computer Halts for Long Time

Q111429: SET Batch File Command Resets Error Levels

Q111450: Two Token Ring Adapters Forces Source Routing on Both Adapters

Q111736: Printing Postscript from Project, Task Bars Shaded or Darkened

Q112547: Error and Warning Events Not Described in System Log

Q112637: STOP Message on MIPS Computer Caused by NET Command

Q112874: Fonts Look Different When Printed and on Screen

Q113916: Copy from One Novell Server to Another Fails

Q114304: ACLs Not Translated When User Names Have Extended Characters

Q114577: Watermark Software HP 1300T Removable Disk Stuck or Corrupted

Q114892: Err Msg: "Out of Memory" Browsing Network Files as Administrator

Q115431: Turkish Characters in Directory Name Hangs Windows NT

Q115602: Cannot Input Unicode Characters >256 into Dialog Edit Field

Q116341: Characters Change When Pasted into 16-bit Applications

Q117359: SFM: Copying Files Between Volumes Freezes Other Mac Clients

Q119277: Err Msg: "Access denied" Running MS-Mail SMTP Gateway in VDM

Q119568: Kyocera FS-3500A PCL Driver Will Not Print from Lower Paper Tray

Q119574: WinNT 3.1 to 3.5 Upgrade Does Not Copy OEM SCSI Drivers to Disk

Q120693: Dual Processor MIPS Computer with Proteon NIC Hangs At Startup

Q120770: STOP: 0x0000000A When CadexNet on LM Clients Stress SRV.SYS

Q121645: STOP 0x0000001E in SRV.SYS

Q121725: Alert for "<" Condition Fails to Run Batch File

Q121726: STOP Message Caused by NTFS with Long Filenames

Q121822: Deadlocks When Using Asynchronous Named Pipes

Q122043: Err Msg: Access Denied Connecting to NetWare Resource

Q122224: Format Limits Stripe Sets to 4 GB

Q122248: Event Id 2000 Errors In System Log

Q122329: Err Msg: System Error 59 Has Occurred, an Unexpected...

Q122368: "Insufficient Memory" Messages Appear When You Use Word 6

Q122385: Err Msg: Mail Could Not Read the Entire Message...

Q122445: Unexpected Network Error When Changing WfWG Password

Q122781: LMHOSTS #INCLUDE of Local Files May Fail on Windows NT 3.5

Q122793: Err Msg: OS Loader V3.5 Windows NT Could Not Start...

Q122838: Memory Leak in LMREPL Service

Q122903: Error Message with Compaq Smart SCSI

Q122961: Print Job Stalls Printing to NEC NPDL2

Q122986: Justified Words Printed with PostScript Driver Contain Spaces

Q123058: Closing Timed-Out Applications Without Choosing End Task

Q123062: Windows NT 3.5 Fails to Unlock a Record Area After Locking It

Q123083: Client Hangs Accessing Remote Downlevel LAN Manager Server

Q123155: Err Msg: The Remote Computer is Not Available

Q123159: Windows NT 3.5 Computer with Intel Neptune PCI Chip Hangs

Q123166: Time and Date Stamp of Word 6.0 Document Updated

Q123215: Backup Incorrectly Sets Archive Bit on WFWG 3.11 Files

Q123275: Extra Keys on Brazilian Keyboard Do Not Work at Command Prompt

Q123338: SFM Performance Degrades Due to Memory Problem

Q123447: Err Msg: STOP Message in DLC.SYS

Q123478: Multiple ISDN Adapters Cannot Be Installed

Q123500: Administrators Permissions for a Printer Change to Read

Q123607: Graphics and True Type Fonts Print Garbage on Okidata ML320

Q123678: Changing Registry Does Not Prevent User from Changing Delay

Q123716: CACLS.EXE Err Msg: No More Internal IDs Available

Q123717: Windows NT Backup Writes Incorrect Times To Log

Q123738: STOP 0x0000001e Err Msg with NetBEUI Client/Server Applications

Q123740: Unexpected Error Accessing MS Mail Postoffice Through GSNW

Q123741: Cannot Run RAS Programs When a Service References RASAPI32.DLL

Q123744: Secure Erase on Exabyte 2501 Err Msg: The Computer Has Rebooted

Q123745: Windows NT Err Msg: No more connections to the remote...

Q123862: Opening a File Causes the Application to Close

Q123942: Invalid User Names Causes Memory Leak

Q123957: Error Updating PowerPoint 4.0 File Using CSNW/GSNW

Q123964: Server Service Hangs When Using GSNW

Q123965: Can't Get Zone Information with Compaq Netflex II TR NIC

Q123976: Sequential File Reads of 4K Instead of 64K Blocks

Q124021: CD-ROM File System Does Not De-allocate Non-paged Pool Memory

Q124037: Windows NT Setup Err Msg on Compaq: Stop 0x0000008B

Q124084: FTP OnNet 1.1 PPP Client Hangs Windows NT 3.5 RAS Service

Q124120: Event Log Service Fails to Start Due to Event Log Corruption

Q124121: Memory Loss During Application Process Creation

Q124142: Registry Editor Hangs When You Select a Key

Q124157: Cannot Build VC++ Projects (.PDB & .PCH Files) on Netware Server

Q124242: Forced Disconnect for Macintosh Users Not Working

Q124284: STOP 0x00000026 when Accessing a CD Using an Indirect Path

Q124360: Non Critical Error with IR32_32.DLL and Mitsumi IDE CD-ROM

Q124374: Windows NT 3.1 Computer Cannot Log On to Windows NT 3.5 Domain

Q124375: SFM: File Permissions Problem When Volume is Shared at Root

Q124484: Error 33: DOSRead and DOSWrite APIs from OS/2 Application

Q124542: Service Logged On w/ User Account Able to Interact with Desktop

Q124549: Unable to Disable Print Event Logging in Windows NT 3.5

Q124582: VBApp & OLE Do Not Work If Network Components Are Not Installed

Q124648: DC21040 Causes Windows NT 3.5 to Stop Responding (Hang)

Q124747: SFM Err Msg: The Item...Is Missing and Was Probably Deleted...

Q124796: DHCP Client Does Not Support Domain Name Option

Q124816: Very Large or Very Small Transfers to SCSI Printers Fail

Q124853: STOP Message with SFMATALK.SYS

Q124874: STOP Message 0x0A Running Performance Monitor on NEC 3360

Q124909: Problems Accessing Drive Formatted with Ontrack Disk Manager

Q124910: Using Ontrack Disk Manager to Support Large IDE Drives

Q124912: Slow Processing with Windows NT PDC and LAN Manger BDC

Q124936: Application in VDM May Receive Overrun Error

Q124940: STOP 0x0000000A when Accessing NetWare Server

Q124958: NTFS Integrity Problems with Large Stripe Sets

Q125573: Event Viewer Does Not Report System Log Errors Correctly

Q125625: Software Compression Compatibility in Windows NT 3.5 RAS

Q125646: Computer with Intel Neptune PCI Chip Hangs on Warm Reboot

Q125759: Windows NT3.5 Improves Performance with Intel Neptune PCI Chip

Q126020: Setup Err Msg on Intel Xpress Deskside: Inaccessible Boot...

Q126277: 16-Bit Process Creation Can Result in Memory Loss

Q126429: Equinox Serial Driver Causes the Win16 Subsystem to Fail

Q126752: DCs Fail to Synchronize or Validate Users Over NWLINK

Q127818: Clients Fail to Connect to Windows NT Server

Q128565: LMHOSTS File Generates STOP 0x00000050

Q129045: Date and Time Stamp of Files Change When Copied to Netware

Q130117: Running PKZIP Hangs WFW or Windows NT MS-DOS Command Prompt

Q130120: Event Error 2000 Logged Repeatedly Due to Illegal Command

Q130480: GSNW Share Names Displayed as DELETED with RAS Server Running

Q125385: File Size and Date Reported Incorrectly On NTFS Drive

Q126142: Windows NT Mail Err Msg: The Network Path You Entered Could...

Q126383: RAS Callback Via ISDN Uses Only One Channel

Q126451: SNA Server: Windows NT Client Loses Session To Server

Q126560: Can not Create NetBIOS Session Over TCP/IP

Q126652: FDDI MAC Address Issue with Windows NT 3.5

Q126724: NPMCA.SYS Causes STOP 0x0A in TCPIP.SYS

Q126974: STOP 0x24 Generated With NTFS

Q126978: IBM Token Ring /A Adapter Fails To Start in Windows NT 3.5

Q127775: STOP 0x0A in STREAMS.SYS with DEC Pathworks Loaded

Q127789: LAN Manager Clients Cannot See Windows NT Computers

Q127814: Printing to WinNT Queue Attached to NetWare Queue Hangs NetWare

Q127821: Problems Using Event Viewer from Windows for Workgroups

Q127908: Granularity Value Changes After Installing Service Pack 2

Q127909: Seed Routing Not Working With C.O.P.S. LocalTalk NIC

Q127922: Setting BDC to be WINS Proxy Agent May Cause Broadcast Storms

Q128254: Stop Msg: C0000218 "Unknown Hard Error" When Registry is Overrun

Q128335: IPX Subnet Clients Unable to Connect to Windows NT

Q128415: NT to LAN  Manager UAS Replication Problem after using PORTUAS

Q128447: Enumeration of Large NTFS Directory Takes a Long Time

Q128448: RAS Event ID 20013: The User Connected to Port...

Q128550: Memory Leak: MS-DOS-Based Apps Starting Non-MS-DOS-Based Apps

Q129054: Periods Not Displayed in CD-ROM Disc Volume Label

Q129111: PCI Adapter Incorrectly Identified on Dual-bus Computers

Q129482: Systems Management Server Inventory Via RAS Causes STOP Screen

Q129600: Large Zeroing Operations Cause Systems To Appear Hung

Q130661: Windows NT 3.5: STOP 0x0000000a in NETBT.SYS When Memory is Low

Q130901: Frame Corruption in Retransmitted IPX Packet

Q131339: STOP Msg: 0x0000000A or 0X0000001E Dis/Reconnecting to WfWG Svr

Q131479: Unable to Change Printer Settings From Windows Applications

KBCategory: kbreadme kbfixlist3.50.SP3

KBSubcategory: ntdistrib

Additional reference words: prodnt 3.50 servpack SP3 bug fix qfe compact


CALC.EXE Display Error in Floating Point Number Calculation

Article ID: Q122182

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

The Windows NT Calculator application (CALC.EXE) has a display error in its

floating point number calculation.

NOTE: This display error is not related to the Pentium processor floating

point division hardware.

RESOLUTION

==========

Microsoft has updated CALC.EXE to resolve this problem. The new Calculator

application works on all Microsoft Windows NT versions and on all hardware

platforms supported by Windows NT.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT and Windows NT

Advanced Server version 3.1 and Windows NT Workstation and Windows NT

Server version 3.5. This problem was corrected in the latest U.S. Service

Pack for Windows NT version 3.5. For information on obtaining the Service

Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbtool kbbug3.10 kbfix3.50.sp1

KBSubcategory: ntutil

Additional reference words: prodnt 3.10 3.50


WinNT 3.5 Software Update for the Pentium Floating Point Error

Article ID: Q122323

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SUMMARY

=======

Microsoft has developed a utility (PENTNT.EXE) that, on Pentium-based

systems, checks whether the processor contains the floating point division

error, reports the current status of floating point, and allows disabling

and re-enabling of hardware floating point.

This software effectively turns off the math coprocessor by trapping the

floating point instructions.  This makes the Pentium processor behave

similarly to 486SX or 386 processors that do not have a math coprocessor.

The utility works on Pentium and x86 systems.

Additionally, the solution is implemented through registry settings so that

system policy administrators can control the use of Pentium floating point

hardware on user systems.

STATUS

======

This utility is available in the latest U.S. Service Pack for Windows NT

version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

MORE INFORMATION

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

Performance Considerations

--------------------------

Core operating system code (for window management, disk and file

operations, and application programming interfaces) in Windows NT does not

perform floating point calculations, and so will not be affected either by

the potential floating point hardware division errors, or by disabling

hardware floating point.  However, choosing software emulation of floating

point will result in lower performance of floating point operations.  Some

utilities and applications such as the Calculator application provided with

Windows NT, and the OpenGL rendering engine, may use floating point

hardware when present.  Most word processors, databases, email, and so on,

perform few or no floating point operations.

Math-intensive applications, including spreadsheets and technical

applications, typically perform floating point operations, and therefore

will experience some performance degradation.  The OpenGL rendering engine,

which is part of Windows NT 3.5, and other 3D and CAD applications, are

instances of this type of application.  The user of such applications will

be able to choose between the higher speed of hardware floating point, or

slower floating point software emulation libraries, which will not

encounter the Pentium floating point division error.  Many applications

contain their own floating point libraries to use in this case.  A few

applications (such as Autocad) require floating point hardware and will not

run without it.  Customers running these applications will need to replace

their Pentium processor in order to avoid the floating point division

error.  The floating point software emulation's libraries are used on

systems with 486SX or 386 processors.

Running PENTNT.EXE

------------------

To start the PENTNT.EXE utility, at the MS-DOS prompt type:

    PENTNT [-C|-c] [-F|-f] [-O|-o] [-?|-H|-h]

The utility will test floating point division.  If no error is found, a

message will appear recommending that you use floating point hardware.  If

a division error is detected, a message appears notifying you of the error.

You then have several choices: to disable floating point hardware only if

you are using a Pentium processor with a division error, or disable

floating point hardware always.  If you choose to disable or re-enable

floating point emulation, you must restart the computer for the changes to

take effect.

The complete PENTNT command syntax is as follows:

PENTNT [-C|-c] [-F|-f] [-O|-o] [-?|-H|-h]

where:

-C|-c      Turns on conditional emulation.  This means that floating point

           emulation will be forced on if and only if the system detects

           the Pentium floating point division error at start time.  If you

           select this parameter, you must restart the computer for the

           changes to take effect.

-F|-f      Turns on forced emulation. This means that floating point

           hardware is disabled and floating point emulation will always be

           forced on, regardless of whether the system exhibits the Pentium

           division error.  This parameter is useful for testing software

           emulators and for working around floating point hardware defects

           known to the operating system.  If you select this parameter,

           you must restart the computer for the changes to take effect.

-O|-o      Turns off forced emulation and re-enables floating point

           hardware if it is present.  If you select this parameter, you

           must restart the computer for the changes to take effect.

-?|-H|-h   Displays help for the command.

Registry Entry

--------------

The Registry entry for the PENTNT utility is located in the Registry

subtree HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager.

The following parameter is used by the PENTNT utility:

REG_DWORD

ForceNpxEmulation = 0 | 1 | 2

Specifies if the floating point emulation is turned on or off.  If set to

0, floating point emulation is not enabled and floating point hardware is

enabled. If set to 1, conditional floating point emulation is enabled.  If

set to 2, unconditional emulation is enabled.  By default, this parameter

is set to 0.

KBCategory: kbtool kbfix3.50.sp1

KBSubcategory: ntutil

Additional reference words: prodnt 3.50 fpu bug intel


GP Fault in WINLOGON.EXE

Article ID: Q110882

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

You log on with a newly created account and choose to have your Windows

settings migrated to Windows NT. When you later log in again, WINLOGON.EXE

generates a general protection (GP) fault.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntgeneral

Additional reference words: prodnt 3.50


Mail Fails with Memory or Network Errors

Article ID: Q110932

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Microsoft Mail under Windows NT (the 32-bit version of Mail) fails and

reporting memory and network errors.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntinterop

Additional reference words: prodnt 3.50


Diamond Viper VLB Video Adapter Driver Fails To Load

Article ID: Q110947

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

After installing the driver for the Diamond Viper VLB video adapter, the

driver fails to load.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntdriver

Additional reference words: prodnt 3.50


Backup Creates Many REGXXXX Files, Can't Copy .EVT Files

Article ID: Q111026

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Using an account that is a member of the Backup Operators group, you back

up a partition that Windows NT resides on. Windows NT Backup fails to

access the Event Viewer files, all ending in .EVT. During these access

failures, Backup creates many files of the form REG<xxxx> (where <xxxx> is

a number sequence).

WORKAROUND

==========

This problem does not occur if your account is a member of the

Administrators group.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbtool kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntutil

Additional reference words: prodnt 3.50


File Write to Network Share Using MS-DOS 21h Function Fails

Article ID: Q111027

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you use MS-DOS function 21h to write to a file on a network share, the

following error appears in the event log:

   System Process - Lost Delayed-Write Data

   The system was attempting to transfer file data from buffer to <network

   share>. The write operation failed, and only some of the data may have

   been written to the file.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kberrmsg kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntdosap

Additional reference words: prodnt 3.50


Can't Choose Paper Tray with Postscript Printer Driver

Article ID: Q111325

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

If a printer has two paper trays, both containing paper of the same size,

you cannot specify which tray is used with the Windows NT Postscript

printer driver.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.10 kbfix3.50.sp2

KBSubcategory: ntprint

Additional reference words: prodnt 3.50


MIPS Four-Processor Computer Halts for Long Time

Article ID: Q111420

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

A MIPS-based four-processor Windows NT Server may halt (deadlock) for a

long period of time (as much as several hours).

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbhw kbbug3.50 kbfix3.50.sp2

KBSubcategory: nthw

Additional reference words: prodnt 3.50


SET Batch File Command Resets Error Levels

Article ID: Q111429

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

After you upgrade to Windows NT, some of your MS-DOS batch files may fail

to work as expected. This is due to how the SET command's functionality has

changed. Under MS-DOS, the SET command did not reset the error level,

enabling you to SET variables and handle error levels later in your batch

files. This problem also exists in the following batch file commands: PATH,

DPATH, and PROMPT.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbenv kbinterop kbbug3.10 kbfix3.50.sp2

KBSubcategory: ntgerneral

Additional reference words: prodnt 3.50 3.10


Two Token Ring Adapters Forces Source Routing on Both Adapters

Article ID: Q111450

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you install two Token Ring network adapters on a Windows NT Server

computer, it will force both adapters to use Source Routed frames. In a

non-

bridged environment, this isolates the computer to the physical ring it is

attached to. Removing an adapter from Control Panel does not solve this

problem as the adapter Registry values remain.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: nthw

Additional reference words: prodnt 3.50


Printing Postscript from Project, Task Bars Shaded or Darkened

Article ID: Q111736

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you print from Microsoft Project to a Postscript printer, task bars

appear incorrectly as shaded or darkened bars (as oppossed to striped or

cross-hatched). This problem does not occur with PCL printers.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbprint kbbug3.10.sp2 kbfix3.50.sp2

KBSubcategory: ntprint

Additional reference words: prodnt 3.50


Error and Warning Events Not Described in System Log

Article ID: Q112547

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Instead of a description of an error or warning event, the system log

contains the following statement:

   The description for Event ID <x> in Source <driver name> could not

   be found. It contains the following insertion string(s): <strings>.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntgeneral

Additional reference words: prodnt 3.50


STOP Message on MIPS Computer Caused by NET Command

Article ID: Q112637

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

A MIPS-based computer running Windows NT may halt with a STOP message if

you connect to it from another Windows NT computer (non-MIPS) and use the

NET command. The STOP message is 0x0000001E.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kberrmsg kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntstop

Additional reference words: prodnt 3.50


Fonts Look Different When Printed and on Screen

Article ID: Q112874

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Some fonts appear differently (or not at all) on the screen than they do

when printed.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntprint

Additional reference words: prodnt 3.50


Copy from One Novell Server to Another Fails

Article ID: Q113916

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you copy a file from one Novell file server to another using Gateway

Services for NetWare, the copy operation fails. During the copy, other

computers connected to the Novell file servers may halt until the copy

operation fails.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntinterop

Additional reference words: prodnt 3.50


ACLs Not Translated When User Names Have Extended Characters

Article ID: Q114304

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you convert a group of accounts using NWCONV, user names containing

extended characters do not get converted along with their access control

lists (ACLs).

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntsetup

Additional reference words: prodnt 3.50


Watermark Software HP 1300T Removable Disk Stuck or Corrupted

Article ID: Q114577

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Your Watermark Software - HP 1300T removable SCSI hard disk becomes stuck

or files on the disk are corrupted when you eject the disk shortly (20

seconds or less) after Windows NT has written to it.

There is no problem when reading from the disk and then ejecting it.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

The HP 1300T is manufactured by Watermark Software, Inc., a vendor

independent of Microsoft; we make no warranty, implied or otherwise,

regarding this product's performance or reliability.

KBCategory: kbhw kbbug3.50 kbfix3.50.sp2

KBSubcategory: nthw

Additional reference words: prodnt 3.50


Err Msg: "Out of Memory" Browsing Network Files as Administrator

Article ID: Q114892

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

File Manager reports an "Out of Memory" or "Not Enough Storage" error when

you browse network files after logging on to a Windows NT Workstation and

Windows NT Server version 3.5 as Administrator.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbtool kberrmsg kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntdomain

Additional reference words: prodnt 3.50


Turkish Characters in Directory Name Hangs Windows NT

Article ID: Q115431

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you create a long directory name in File Manager using Turkish

characters (for example, by pasting characters from Charmap) and then try

to open the directory a STOP Message appears and your computer stops

responding (hangs).

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbtool kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntstop ntfilesys

Additional reference words: prodnt 3.50


Cannot Input Unicode Characters >256 into Dialog Edit Field

Article ID: Q115602

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

You cannot input Unicode characters that have a character code of greater

than 256 into a common dialog edit field.

This includes the following characters from code page 1252:

   Code

   Page

   1252   Unicode  Description

   ----   -------  ----------------------------------------

   0x82   0x201a   Single Low-9 Quotation Mark

   0x83   0x0192   Latin Small Letter F With Hook

   0x84   0x201e   Double Low-9 Quotation Mark

   0x85   0x2026   Horizontal Ellipsis

   0x86   0x2020   Dagger

   0x87   0x2021   Double Dagger

   0x88   0x02c6   Modifier Letter Circumflex Accent

   0x89   0x2030   Per Mille Sign

   0x8a   0x0160   Latin Capital Letter S With Caron

   0x8b   0x2039   Single Left-Pointing Angle Quotation Mark

   0x8c   0x0152   Latin Capital Ligature Oe

   0x82   0x201a   Single Low-9 Quotation Mark

   0x83   0x0192   Latin Small Letter F With Hook

   0x84   0x201e   Double Low-9 Quotation Mark

   0x85   0x2026   Horizontal Ellipsis

   0x86   0x2020   Dagger

   0x87   0x2021   Double Dagger

   0x88   0x02c6   Modifier Letter Circumflex Accent

   0x89   0x2030   Per Mille Sign

   0x8a   0x0160   Latin Capital Letter S With Caron

   0x8b   0x2039   Single Left-Pointing Angle Quotation Mark

   0x8c   0x0152   Latin Capital Ligature Oe

   0x91   0x2018   Left Single Quotation Mark

   0x92   0x2019   Right Single Quotation Mark

   0x93   0x201c   Left Double Quotation Mark

   0x94   0x201d   Right Double Quotation Mark

   0x95   0x2022   Bullet

   0x96   0x2013   En Dash

   0x97   0x2014   Em Dash

   0x98   0x02dc   Small Tilde

   0x99   0x2122   Trade Mark Sign

   0x9a   0x0161   Latin Small Letter S With Caron

   0x9b   0x203a   Single Right-Pointing Angle Quotation Mark

   0x9c   0x0153   Latin Small Ligature Oe

   0x9d   0x009d

   0x9e   0x009e

   0x9f   0x0178   Latin Capital Letter Y With Diaeresis

Additionally, a large portion or all of the following locales cannot input

their characters:

   LCID       Locale Name

   --------   -----------

   00000402   Bulgarian

   0000041a   Croatian

   00000405   Czech

   00000408   Greek

   0000040e   Hungarian

   00000415   Polish

   00000418   Romanian

   00000419   Russian

   0000041b   Slovak

   00000424   Slovenian

   0000041f   Turkish

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbother kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntgeneral

Additional reference words: prodnt 3.50


Characters Change When Pasted into 16-bit Applications

Article ID: Q116341

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you paste certain characters into 16-bit applications, they become

different characters. For example, using the English locale, if you copy

the trademark symbol, and attempt to paste it into Word for Windows, it is

pasted as an exclamation mark (!).

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbother kbbug3.50 kbfix3.50.sp2

KBSubcategory: nt16ap

Additional reference words: prodnt 3.50


SFM: Copying Files Between Volumes Freezes Other Mac Clients

Article ID: Q117359

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When a Macintosh client copies a file from a shared disk volume on a

Windows NT server running Services for Macintosh (SFM) to another volume on

the same server, other Macintosh clients that have connections to the

volume freeze, showing network activity, until the file transfer is

complete.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT and Windows NT

Advanced Server version 3.1 and Windows NT Workstation and Windows NT

Server version 3.5. This problem was corrected in the latest U.S. Service

Pack for Windows NT version 3.5. For information on obtaining the Service

Pack, query on the following word in the Microsoft Knowledge Base (without

the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.10 kbfix3.50.sp2

KBSubcategory: ntmac

Additional reference words: prodnt 3.10 3.50


Err Msg: "Access denied" Running MS-Mail SMTP Gateway in VDM

Article ID: Q119277

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you run the Japanese version of Microsoft Mail Gateway to SMTP at a

Windows NT command prompt, an "Access denied" error message appears when

mail is sent to or received from the gateway server.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntinterop

Additional reference words: prodnt 3.50 Mail 3.02


Kyocera FS-3500A PCL Driver Will Not Print from Lower Paper Tray

Article ID: Q119568

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

The Windows NT PCL driver for the Kyocera FS-3500A laser printer does not

allow you print from the lower paper tray. The printer pulls paper from the

upper instead.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

The FS-3500A laser printer is manufactured by Kyocera, a vendor independent

of Microsoft; we make no warranty, implied or otherwise, regarding this

product's performance or reliability.

KBCategory: kbprint kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntdriver

Additional reference words: prodnt 3.50


WinNT 3.1 to 3.5 Upgrade Does Not Copy OEM SCSI Drivers to Disk

Article ID: Q119574

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When upgrading your computer from Windows NT version 3.1 to Windows NT

version 3.5, OEM SCSI drivers are not copied from the OEM setup floppy to

the %SYSTEMROOT%\SYSTEM32\DRIVERS directory. The 3.1 version of the driver

is remains in the directory.

Some computers cannot boot Windows NT 3.5 using the 3.1 version of their

SCSI driver.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbsetup kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntsetup

Additional reference words: prodnt 3.50


Dual Processor MIPS Computer with Proteon NIC Hangs At Startup

Article ID: Q120693

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Your dual processor MIPS-based computer with a Proteon Network Interface

Card (NIC), stops responding (hangs) during Windows NT startup.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbhw kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntdriver

Additional reference words: prodnt 3.50


STOP: 0x0000000A When CadexNet on LM Clients Stress SRV.SYS

Article ID: Q120770

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When Windows NT is heavily stressed by LAN Manager 2.2 clients running

CadexNet document control software, the following STOP message appears:

   STOP: 0x0000000A(0x004E00CB, 0x00000002,0x00000000,0x801135D8

   Memory at 0x004E00CB was accessed at IRQL 2 for 0 [r] access from

      0x801135D8

   Base 80100000 == NTOSKRNL.EXE

       0x801135D8

   -   0x80100000

   -----------------

   offset: 0x000135D8

This only occurs with LAN Manager 2.2 and 2.2b clients. It does not occur

with Windows for Workgroups 3.11 clients.

CAUSE

=====

The STOP Message occurs when CadexNet heavily stresses a file with FCB

open/close operations.

RESOLUTION

==========

Microsoft has updated the Windows NT file, SRV.SYS.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT and Windows NT

Advanced Server version 3.1 and Windows NT Workstation and Windows NT

Server version 3.5. This problem was corrected in the latest U.S. Service

Pack for Windows NT version 3.1 and U.S. Service Pack for Windows NT

version 3.5. For information on obtaining these Service Packs, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

CadexNet is manufactured by a vendor independent of Microsoft; we make no

warranty, implied or otherwise, regarding this product's performance or

reliability.

Additional reference words: prodnt wfw wfwg 3.10 3.50

KBCategory: kbnetwork kb3rdparty kbbug3.10 kbfix3.10.sp3 kbfix3.50.sp2

KBSubcategory: ntstop ntnetserv


STOP 0x0000001E in SRV.SYS

Article ID: Q121645

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

The following STOP message appears:

   STOP 0x1E (0xC0000005, 0xfc9f7bee, 0, 0xc) - SRV.SYS

   Unhandled kernel exception in 0xfc9f7bee has base at 0xfc9f0000

   0xC0000005 - Access violation.

   Offset = 0x7bee

CAUSE

=====

An illegal transact SMB (function WaitNamedPipe) was received. The

transaction name in the SMB was "\PIPE\EVENTLOGOG" without the null

character termination.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT and Windows NT

Advanced Server version 3.1 and Windows NT Workstation and Windows NT

Server version 3.5. This problem was corrected in the latest U.S. Service

Pack for Windows NT version 3.5. For information on obtaining the Service

Pack, query on the following word in the Microsoft Knowledge Base (without

the spaces):

   S E R V P A C K

KBCategory: kbnetwork kberrmsg kbbug3.10 kbfix3.50.sp2

KBSubcategory: ntstop

Additional reference words: prodnt 3.10 3.50


Alert for "<" Condition Fails to Run Batch File

Article ID: Q121725

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Performance Monitor is capable of correctly detecting conditions where the

value of a parameter falls below the specified limit. When this condition

occurs an alert can be generated and a batch file run. However, Performance

Monitor will not run the batch file correctly.

For example, if Performance Monitor is configured to send an alert and run

a batch file any time CPU utilization falls below 5%, the alert will be

sent but the batch file won't run.

CAUSE

=====

Performance Monitor allows parameters to be passed to the batch job. The

"<" parameter  is being interpreted as a redirection from the STDIN port,

confusing the job.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbtool kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntutil

Additional reference words: prodnt 3.50


STOP Message Caused by NTFS with Long Filenames

Article ID: Q121726

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Bugcheck 00000024 : 00190146 fc99fc64 fc99faa0 80139150

Stopped at an unexpected exception: code=80000003 addr=fa0eb606

Hard coded breakpoint hit

Stack Trace (using kernel debugger):

FramePtr  RetAddr   Param1   Param2   Param3   Function Name

fc99f9a8  fa10a65f  fcd250e8 fc99f9d4 fa0e71e0

   NTFS!NtfsExceptionFilter+0x46e1

fc99f9b4  fa0e71e0  fc99f9dc 00000000 fc99f9dc

   NTFS!NtfsFspClose+0x10fcc

fc99ff34  801198b6  00000000 fc99ff7c 00000000

   NTFS!_except_handler3+0x47

fc99ff4c  80134936  00000000 00000000 00000000 NT!ExpWorkerThread+0x6a

fc99ff7c  8013e7fa  8011984c 00000000 00000000

   NT!PspSystemThreadStartup+0x40

00000000  00000000  00000000 00000000 00000000 NT!KiThreadStartup+0xe

CAUSE

=====

An NTFS structure was corrupted.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbother kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntfilesys ntstop

Additional reference words: prodnt 3.50 blue


Deadlocks When Using Asynchronous Named Pipes

Article ID: Q121822

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

 - Microsoft SNA Server for Windows NT, version 2.0

 - Microsoft SNA Server for Windows NT, version 2.1

----------------------------------------------------------------------

SYMPTOMS

========

When Windows NT Workstation and Windows NT Server version 3.5 are stressed

by asynchronous named pipes, such as by Microsoft SNA Server for Windows

NT, the Windows NT redirector (RDR.SYS) doesn't create enough worker

threads fast enough and system deadlock occurs.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntinterop

Additional reference words: prodnt 3.50


Err Msg: Access Denied Connecting to NetWare Resource

Article ID: Q122043

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

After you disconnect from the Gateway Service for NetWare in Windows NT

version 3.5, an "Access Denied" message appears when you attempt to connect

to a NetWare resource with a Universal Naming Convention (UNC) name from

the NetWare network service.

CAUSE

=====

This problem occurs because NetWare limits accounts to a single session per

user account and when you disconnect from the Gateway Service for NetWare,

the service is stopped but the network connection remains with the NetWare

server.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

NetWare is manufactured by Novell, Inc., a vendor independent of Microsoft;

we make no warranty, implied or otherwise, regarding this product's

performance or reliability.

KBCategory: kbnetwork kberrmsg kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntinterop

Additional reference words: prodnt 3.50 disappear lost gone


Format Limits Stripe Sets to 4 GB

Article ID: Q122224

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Advanced Server version 3.1

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you configure a hard disk drive that is larger than 4 GB as a stripe

set, with or without parity and format the disk drive from Disk

Administrator or at the Command Prompt, the disk capacity is incorrectly

shown as 4 GB.

CAUSE

=====

The FTDISK.SYS driver limits stripe sets to 4 GB.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Advanced Server

version 3.1 and Windows NT Server version 3.5. This problem was corrected

in the latest U.S. Service Pack for Windows NT version 3.5. For information

on obtaining the Service Pack, query on the following word in the Microsoft

Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbother kbbug3.10 kbfix3.50.sp2

KBSubcategory: ntfault

Additional reference words: prodnt 3.10 3.50 fault tolerance


Event Id 2000 Errors In System Log

Article ID: Q122248

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

You find many occurrences of the following error in your system log:

   EVENT ID 2000

   The server's call to a system service failed unexpectedly.

   0000: 00040000 00540001 00000000 c00007d0

   0010: 00000000 c0000008 00000000 00000000

   0020: 00000000 00000000 00000bc0

   c00000008 define STATUS_INVALID_HANDLE ((NTSTATUS)0xC0000008L)

   00000bc0  define SRV_SVC_NT_Query_INFO_FILE 0xbc0

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbother kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntgeneral

Additional reference words: prodnt 3.50


Err Msg: System Error 59 Has Occurred, an Unexpected...

Article ID: Q122329

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When your Windows NT Server version 3.5 computer is using the LMHOSTS file

and TCP/IP is the only protocol, the following message may appear when you

attempt to connect to a Windows NT Server version 3.5 that was recently

rebooted:

   System Error 59 has occurred, an unexpected network error occurred.

CAUSE

=====

When a Windows NT Server version 3.5 shuts down, it sends out a remove name

request for its server name. If the Windows NT server name was cached by

other Windows NT version 3.5 servers through the LMHOSTS file, the server

name entry (servername <20>) is removed from cache and those computers are

not able to contact the server when it reboots. This behavior has been

reproduced on a one-way trust between two domains.

WORKAROUND

==========

On the Windows NT servers that cannot connect to the recently rebooted

Windows NT server, use the command NBTSTAT -R to reload the cache. You can

then reestablish connections with the rebooted Windows NT Server.

NOTE: If a computer receives the above error message, you can determine if

the server name was removed from its cache by using the command NBTSTAT -c.

STATUS

======

Microsoft has confirmed this to be a problem with Windows NT Server version

3.5. This problem was corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory:  kbnetwork kbtool kbui kberrmsg kbbug3.50 kbfix3.50.sp2

KBSubcategory: nttcp ntutil ntui

Additional reference words: prodnt 3.50


"Insufficient Memory" Messages Appear When You Use Word 6

Article ID: Q122368

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

 - Microsoft Word for Windows, versions 6.0 and 6.0a

----------------------------------------------------------------------

SYMPTOMS

========

When you use Microsoft Word for Windows version 6.0 with Windows NT version

3.5, "insufficient memory" error messages may appear when you switch

between default printers.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem was corrected in the latest U.S. Service Pack for Windows NT

version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory:  kbinterop kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntprint ntinterop

Additional reference words: prodnt 3.50 msword


Err Msg: Mail Could Not Read the Entire Message...

Article ID: Q122385

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

 - Microsoft Mail for Windows NT, versions 3.2 and 3.2a

----------------------------------------------------------------------

SYMPTOMS

========

When a Windows NT version 3.5 Workstation or Server sends mail to or

receives mail from a Microsoft Mail client, you receive this error message:

   Mail System Error

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

   Mail could not read the entire message from the post office.

   Some parts of the message may be missing.

   Ask sender to resend the message.

CAUSE

=====

The Windows NT Workstation and Server Mail client incorrectly zeros out

the subject field before a message is transmitted. This effects the .MAI

file.

RESOLUTION

==========

Microsoft fixed this problem in an updated version of the Windows NT file,

MSSFS32.DLL.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbinterop kbfasttip kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntutil MailPCNT

Additional reference words: prodnt 3.50 3.20 3.20a S14980


Unexpected Network Error When Changing WfWG Password

Article ID: Q122445

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

In a Windows NT domain, if you attempt to change the password of your

Windows for Workgroups version 3.11 client workstation, and if the minimum

password age has not expired, the following error message appears:

   Error 59: An unexpected network error has occurred.

CAUSE

=====

Windows NT uses a Transact server to respond to downlevel client Transact

API. To change the password, the downlevel client uses the

NetUserPasswordSet API. This problem occurs due to the transact server not

sending the correct return code for this API. As a result, the client

workstation shows a generic error message of Error 59.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT and Windows NT

Advanced Server version 3.1 and Windows NT Workstation and Windows NT

Server version 3.5. This problem was corrected in the latest U.S. Service

Pack for Windows NT version 3.5. For information on obtaining the Service

Pack, query on the following word in the Microsoft Knowledge Base (without

the spaces):

   S E R V P A C K

KBCategory: kbinterop kberrmsg kbbug3.10 kbfix3.50.sp2

KBSubcategory: ntdomain

Additional reference words: prodnt 3.50 3.10 wfw wfwg dos


LMHOSTS #INCLUDE of Local Files May Fail on Windows NT 3.5

Article ID: Q122781

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Using the #INLCUDE statement in LMHOSTS files to include local files may

not work reliably in Windows NT version 3.5. For example:

   #INLCUDE c:\temp\lmhosts

The NBTSTAT -C command may show that the names and addresses in the

C:\TEMP\LMHOSTS file did not get loaded into cache.

CAUSE

=====

A bug in the text-parsing routines resulted in an incorrect full path being

generated for the local file.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem was corrected in the latest U.S. Service Pack for Windows NT

version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory:  kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: nttcp ntnetserv

Additional reference words: prodnt 3.50


Err Msg: OS Loader V3.5 Windows NT Could Not Start...

Article ID: Q122793

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you have more than 3,000 shares on Windows NT version 3.1, the

following message may appear when you upgrade to Windows NT version 3.5 and

reboot your computer:

   OS Loader V3.5

   ....

   Windows NT could not start because the following file is missing or

   corrupt: \<WinRoot>\SYSTEM32\CONFIG\SYSTEM

You can attempt to repair this file by starting Windows NT Setup using the

original Setup floppy disk or CD-ROM. Select 'r' at the first screen to

start repair.

CAUSE

=====

Due to several technical issues, OS Loader V3.5 (NTLDR) only has access to

about 16 megabytes (MB) of RAM at boot time. It must load the SYSTEM

configuration file within this range. If that file exceeds the 16 MB limit,

the above error message appears.

The SYSTEM file which among other things contains share information,

achieved this size due to a problem in the Windows NT 3.5 kernel

(NTOSKRNL.EXE, NTKRNLMP.EXE) code which caused excessive fragmentation of

this file with this number of shares.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem was corrected in the latest U.S. Service Pack for Windows NT

version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory:  kbnetwork kberrmsg kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntboot

Additional reference words: prodnt 3.50


Memory Leak in LMREPL Service

Article ID: Q122838

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Advanced Server version 3.1

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

The Directory Replicator Service (LMREPL) in Windows NT Server version 3.5

and Windows NT Advanced Server version 3.1 has a memory leak, which can

slowly consume nonpaged pool resources and as a result, it can degrade

system performance.

CAUSE

=====

The leak appears to be located at the client side of LMREPL which wakes up

each 15 minutes to perform a replication, depending on the results of a

cyclic redundancy check (CRC). Each 15-minute pulse consumes approximately

1 kilobyte (K) of nonpaged pool.

WORKAROUND

==========

Periodically, the Directory Replicator can be stopped and restarted to free

the memory; this should be done at regular intervals (every two weeks or

so) until a fix is available.

To monitor this resource, use Performance Monitor to look at Object

<Process>, Instance <LMREPL>, Counter <Pool NonPaged Bytes>. The initial

value should be approximately 9860 bytes and values larger than this can

indicate a leak. Over a period of weeks, this value can grow to 3 megabytes

(MB) or more.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Advanced Server

version 3.1 and Windows NT Server version 3.5. This problem was corrected

in the latest U.S. Service Pack for Windows NT version 3.5. For information

on obtaining the Service Pack, query on the following word in the Microsoft

Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory:  kbnetwork kbbug3.10 kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntconfig ntdomain

Additional reference words: prodnt 3.50 3.10 perfmon


Error Message with Compaq Smart SCSI

Article ID: Q122903

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you run Windows NT on a Compaq machine using the SmartSCSI drive

array, and you your hard disk drive four gigabyte or larger and formatted

for Windows NT file system (NTFS), the following error message appears:

   Error writing to HarddiskX/partitionY/$mft. Some data may be lost.

where X and Y reflect the hard disk and NTFS partition.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

The Compaq product discussed here is manufactured by Compaq Computer

Corporation, a vendor independent of Microsoft; we make no warranty,

implied or otherwise, regarding this product's performance or reliability.

KBCategory: kbhw kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntfilesys

Additional reference words: prodnt 3.50 4 gb smart scsi


Print Job Stalls Printing to NEC NPDL2

Article ID: Q122961

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you connect a MIPS computer running Windows NT to a NEC PC-PR2000/4 or

NEC PC-PR4000E/4, install the appropriate printer driver, and attempt to

print TESTJ.TXT (from the floppy disk provided with the printer), the print

job stalls.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

The third-party products discussed here are manufactured by vendors

independent of Microsoft; we make no warranty, implied or otherwise,

regarding these products' performance or reliability.

KBCategory: kbprint kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntprint

Additional reference words: prodnt 3.50 npdl2 blue screen


Justified Words Printed with PostScript Driver Contain Spaces

Article ID: Q122986

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Under Windows NT version 3.5, if you format a paragraph as Justified and

print it with a PostScript driver, the words on linea with large spaces

between them may incorrectly have spaces between the letters in the word,

instead of between the words.

WORKAROUND

==========

To work around this problem on printers that are capable of both PostScript

and Hewlett-Packard (HP) PCL, use an HP PCL printer driver.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem has been corrected in the

latest U.S. Service Pack for Windows NT version 3.5. For information on

obtaining the Service Pack, query on the following word in the Microsoft

Knowledge Base (without the spaces):

   S E R V P A C K

PostScript and PCL are manufactured by Adobe Systems, Inc., and Hewlett-

Packard Company, respectively, vendors independent of Microsoft; we make no

warranty, implied or otherwise, regarding these products' performance or

reliability.

KBCategory: kbprint kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntprint

Additional reference words: prodnt 3.50 justify ps


Closing Timed-Out Applications Without Choosing End Task

Article ID: Q123058

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you log off or shutdown a Windows NT computer while 16-bit Windows-

based networking applications are running, a dialog box with the

application's name in the title bar appears stating that the Windows

application cannot respond to the End Task request. The dialog presents

three choices: Wait, End Task, and Cancel.

CAUSE

=====

This problem occurs when the application time-out due to heavy network

traffic.

RESOLUTION

==========

You can configure Windows NT so that it closes the application by default,

instead of displaying the dialog box. To do so:

1. Install the latest U.S. Service Pack for Windows NT version 3.5.

2. Add one of the following keys to the registry under the

   HKEY_CURRENT_USER subtree:

      \CONTROL PANEL\DESKTOP\HUNGAPPTIMEOUT

       After an application times-out, any you choose the Task List End

      Task button, the dialog box is displayed.

      \CONTROL PANEL\DESKTOP\WAITTOKILLAPPTIMEOUT

       After a log off or shutdown command is issued, and an application

       times-out, the dialog is displayed.

      \CONTROL PANEL\DESKTOP\AUTOENDTASKS

      Any non-zero value causes End Task to automatically be selected; the

      dialog box is not displayed.

STATUS

======

For information on obtaining the Service Pack, query on the following word

in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbfix3.50.sp2

KBSubcategory: nt16ap

Additional reference words: prodnt 3.50 logoff


Windows NT 3.5 Fails to Unlock a Record Area After Locking It

Article ID: Q123062

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Under certain conditions, Windows NT version 3.5 fails to unlock a record

area after locking it. This problem does not happen with Windows NT version

3.1.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbother kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntfilesys

Additional reference words: prodnt 3.50


Client Hangs Accessing Remote Downlevel LAN Manager Server

Article ID: Q123083

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Under certain circumstances, your Windows NT client stops responding

(hangs) when performing disk operations from the command prompt on a remote

downlevel LAN Manager server (using SMB protocol 1.0).

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbinterop kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntinterop ntnetserv

Additional reference words: prodnt 3.50


Err Msg: The Remote Computer is Not Available

Article ID: Q123155

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you attempt to establish a session from a network client to a domain

controller, the following DOS 51 error message appears:

   The remote computer is not available.

CAUSE

=====

This problem occurs when a deadlock condition occurs in NetLogon.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntdomain ntnetserv

Additional reference words: prodnt 3.50


Windows NT 3.5 Computer with Intel Neptune PCI Chip Hangs

Article ID: Q123159

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you install Windows NT version 3.5 on a computer with the Intel

Neptune 82434 PCI Cache Memory Controller (PCMC) the system stops

responding (hangs).

CAUSE

=====

The call, IoAssignResources fails if the target PCI device and the driver's

requested resource list do not request interrupt vectors and the BIOS

doesn't assign an interrupt vector.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbhw kbsetup kbbug3.50 kbfix3.50.sp2

KBSubcategory: nthw

Additional reference words: prodnt 3.50 hal PCI hang boot


Time and Date Stamp of Word 6.0 Document Updated

Article ID: Q123166

----------------------------------------------------------------------

The information in this article applies to:

- Microsoft Windows NT Server version 3.5

- Microsoft Word for Winsows version, 6.0, 6.0a, 6.0c

----------------------------------------------------------------------

SYMPTOMS

========

When you close an unmodified Microsoft Word version 6.0 document located on

a Windows NT Server version 3.5 from a Windows for Workgroups version 3.11

client computer, the time and date stamp of the document is updated.

NOTE: This behavior does not occur with a Windows NT Workstation version

3.5 as a client computer.

STATUS

======

Microsoft has confirmed this to be a problem in Microsoft Windows NT

version 3.5. This problem was corrected in the latest U.S. Service Pack for

Windows NT version 3.5. For information on obtaining the Service Pack,

query on the following word in the Microsoft Knowledge Base (without the

spaces):

   S E R V P A C K

KBCategory:  kbinterop kbbug3.50 kbfix3.50.sp2

KBSubcategory: nt16ap

Additional reference words: wfw wfwg prodnt 3.50 winword word6


Backup Incorrectly Sets Archive Bit on WFWG 3.11 Files

Article ID: Q123215

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you enable the Verify option in the Windows NT version 3.5 Backup

program to backup a Windows for Workgroups version 3.11 computer over the

network, the archive bits are set during the verification process.

Consequently, you cannot perform an incremental backup of the Windows for

Workgroups computer.

NOTE: The correct behavior is to clear the archive bits on all files, which

is done when you run Backup on a Windows NT version 3.5 computer.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem has been corrected in the

latest U.S. Service Pack for Windows NT version 3.5. For information on

obtaining the Service Pack, query on the following word in the Microsoft

Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbtool kbinterop kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntutil

Additional reference words: prodnt 3.50 wfw wfwg


Extra Keys on Brazilian Keyboard Do Not Work at Command Prompt

Article ID: Q123275

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

The additional two keys on Brazilian (ABNT) 104-key keyboards do not

generate scan codes 0x73 and 0x7E at a Windows NT command prompt.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbhw kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntdriver

Additional reference words: prodnt 3.50 non-US 102-key kbd scancodes

scancode 56 107 ? sc


SFM Performance Degrades Due to Memory Problem

Article ID: Q123338

----------------------------------------------------------------------

The information in this article applies to:

- Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you use Services for Macintosh to share files, server performance may

degrade after a number of days in a production environment. CPU use may

rise to between 85 percent and 95 percent even when no one is actively

using the server and only a few users are connected to it. Server response

time increases as the system becomes very slow.

The following events may be logged in the Event Viewer log:

   MacFile 12051: Unable to update the index database for the Macintosh-

   Accessible volume "<volume name>". There may not be enough disk space.

   MacSrv 12046: Unable to allocate paged memory resource.

CAUSE

=====

Caching and notification handling for extremely large volumes is not being

handled properly. Structures are not properly allocated and deallocated

resulting in growing memory resource demands.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Server version

3.5. This problem was corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory:  kbother kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntmac

Additional reference words: prodnt 3.50


Err Msg: STOP Message in DLC.SYS

Article ID: Q123447

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When your computer system running the DLC protocol is operating under

stress, a STOP Message may occur.

CAUSE

=====

On a heavily-used system, an attempt to allocate a packet from non-paged

pool fails. During the failure handling process, an incorrect deallocation

referencing a null pointer is performed.

RESOLUTION

==========

DLC.SYS has been corrected. The memory allocation failure is handled and

deallocation is performed correctly.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kberrmsg kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntprotocol ntstop

Additional reference words: prodnt 3.50


Multiple ISDN Adapters Cannot Be Installed

Article ID: Q123478

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you configure a Windows NT Server with two PCIMAC adapters for Remote

Access Service (RAS) dial-in, clients accessing both adapters when dialing

the number will report that one of the cards doesn't respond, while one

adapter does.

CAUSE

=====

The driver setup was not configurable during Windows NT setup using the

Network Control Panel for multiple adapters.

RESOLUTION

==========

DIGIINSTL.DLL and PCIMAC.SYS have been updated to address configuration of

multiple adapters.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntras

Additional reference words: prodnt 3.50 debugging


Administrators Permissions for a Printer Change to Read

Article ID: Q123500

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

After you upgrade a Windows NT 3.1 installation to Windows NT version 3.5

and reboot the computer several times, the permission on

HKEY_CURRENT_USERS\SOFTWARE\MICROSOFT\WINDOWSNT\DEVICE and

HKEY_CURRENT_USERS\SOFTWARE\MICROSOFT\WINDOWSNT\CURRENT VERSION\DEVICE in

change to read for the administrator.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbsetup kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntregistry ntprint ntsetup

Additional reference words: prodnt 3.50


Graphics and True Type Fonts Print Garbage on Okidata ML320

Article ID: Q123607

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Under Windows NT 3.5, if you print any type of graphics or True Type fonts

on an Okidata ML320 (using the OKI9.DLL file) dot matrix printer, the

printout may contain garbage or incorrectly formatted characters. Because

dot-matrix printers print True Type fonts as graphics, all True Type fonts

are affected.

RESOLUTION

==========

To print text correctly, use a built-in printer font, such as Courier

12CPI. There is no workaround for printing True Type fonts or graphics.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem has been corrected in the

latest U.S. Service Pack for Windows NT version 3.5. For information on

obtaining the Service Pack, query on the following word in the Microsoft

Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbprint kbbug3.50 kbfix3.50.sp2

KBSubcategory: nthw ntdriver

Additional reference words: prodnt 3.50


Changing Registry Does Not Prevent User from Changing Delay

Article ID: Q123678

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

If an administrator changing HKEY_CURRENT_USER\CONTROL PANEL\DESKTOP in the

Registry so that a user cannot change their desktop settings, the user can

still change their screen saver delay in Control Panel.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntsecurity

Additional reference words: prodnt 3.50 read privileges


CACLS.EXE Err Msg: No More Internal IDs Available

Article ID: Q123716

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you run CACLS.EXE against a three to five gigabyte directory tree, the

following error message appears when the process is about 50 percent

complete:

   NO MORE INTERNAL IDs AVAILABLE.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbtool kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntutil

Additional reference words: prodnt 3.50 3 5 3-5


Windows NT Backup Writes Incorrect Times To Log

Article ID: Q123717

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Windows NT Backup writes incorrect times (one hour late) to its log when

the time zone is not with the United States.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbtool kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntutil

Additional reference words: prodnt 3.50 USA us


STOP 0x0000001e Err Msg with NetBEUI Client/Server Applications

Article ID: Q123738

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When client/server applications send a large number of NetBEUI packets to

the server for a long period of time (for example, 30 minutes), the follow

STOP message appears:

   STOP 0x0000001e (0xC0000005 fcd45def 00000000 00000000)

   stopped at an unexpected exception: code=800000003 addr=80121575

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntstop ntprotocol

Additional reference words: prodnt 3.50 trap blue screen


Unexpected Error Accessing MS Mail Postoffice Through GSNW

Article ID: Q123740

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you run Windows for Workgroups and attempt to access a Microsoft Mail

version 3.2 postoffice on a Novell NetWare 3.12 server, an Unexpected Error

appears. This problem occurs when you attempt to access the NetWare server

through a Windows NT computer running Gateway Services for NetWare (GSNW).

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.10 kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntinterop

Additional reference words: prodnt 3.50 post office


Cannot Run RAS Programs When a Service References RASAPI32.DLL

Article ID: Q123741

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

If any service running from the local system account references

RASAPI32.DLL, no RAS programs can be run (including Remote Access

[RASPHONE.EXE]).

WORKAROUND

==========

To work around this problem, start Remote Access before your start the

service.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbtool kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntutil

Additional reference words: prodnt 3.50 ras phone rasphone


Secure Erase on Exabyte 2501 Err Msg: The Computer Has Rebooted

Article ID: Q123744

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you run Windows NT Backup and choose to Secure Erase an Exabyte 2501,

the following error appears:

   The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a

   (0x6dfcfd94, 0x00000010, 0x00000000, 0x80010ece).

The computer may also stop responding (hang).

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbtool kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntutil

Additional reference words: prodnt 3.50 tapestreamer tape streamer stream

MINIQIC.SYS


Windows NT Err Msg: No more connections to the remote...

Article ID: Q123745

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you are the second person to connect to a share on a Windows NT 3.5

server that is limited to one connection at a time, the following error

appears after:

   No more connections to the remote computer can be made at this time

   because there are already as many connections as the computer can

   accept.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntgeneral

Additional reference words: prodnt 3.50 cachedopenlimit maximum max limit

set file manager mgr shutdown shut down


Opening a File Causes the Application to Close

Article ID: Q123862

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you attempt to open a file from an application that uses common dialog

boxes, the application appears to close.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntgeneral

Additional reference words: prodnt 3.50 file/open screen disappear


Invalid User Names Causes Memory Leak

Article ID: Q123942

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

As Windows NT accepts logon requests, each request containing an invalid

user name causes a memory leak.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntsecurity

Additional reference words: prodnt 3.50 username names


Error Updating PowerPoint 4.0 File Using CSNW/GSNW

Article ID: Q123957

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

After you create and save a PowerPoint version 4.0 file to a NetWare server

using the Client Services for NetWare (CSNW) or Gateway Services for

NetWare (GSNW), you may receive the following error message when you

attempt to save changes to the file:

   x:\<filename>.ppt

   Sorry, the file or directory is write-protected.

CAUSE

=====

This problem occurs when your system is using the new NetWare redirector

(NWRDR.SYS) shipped with Windows NT version 3.5.

WORKAROUND

==========

To work around the problem:

1. Copy the file from the NetWare server to your computer and save

   changes to the PowerPoint file.

2. Remove or rename the same file on the NetWare server and copy the

   updated PowerPoint file to the NetWare server.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem was corrected in the latest U.S. Service Pack for Windows NT

version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbinterop kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntinterop ntnetserv nt16ap

Additional reference words: Novell 3.50


Server Service Hangs When Using GSNW

Article ID: Q123964

-----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Server version 3.5

-----------------------------------------------------------------------

SYMPTOMS

========

When you access a NetWare server using Gateway Services for NetWare (GSNW)

running on a Windows NT 3.5 Server installation, the Server service

may hang, disabling all network access to the Windows NT server from any

Microsoft Windows networking clients. Access to the NetWare server from the

Windows NT 3.5 server will still work. A cold boot is required to recover

from this situation.

CAUSE

=====

If two users simultaneously access the same file on a NetWare server

through the gateway service and both users try to apply a lock to an

overlapping range in the file, an unrecoverable deadlock occurs in

the server service.

This is most commonly seen when database applications such as Microsoft

Access or Microsoft FoxPro are used where the database files are located on

the NetWare server.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem was corrected in the latest U.S. Service Pack for Windows NT

version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory:  kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntprotocol

Additional reference words: 3.50 GSNW novell prodnt


Can't Get Zone Information with Compaq Netflex II TR NIC

Article ID: Q123965

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Server version 3.5

 ----------------------------------------------------------------------

SYMPTOMS

========

When using the Compaq Netflex II Token Ring (TR) network interface card

(NIC) on a Windows NT 3.5 server, you are not able to get zone information.

Macintosh clients cannot see Windows NT 3.5 servers that use this NIC from

Chooser. You cannot get zone information either when you are first

configuring zones during the installation of Services for Macintosh, or

later, after restarting the server or Services for Macintosh.

CAUSE

=====

This problem is caused by the way functional addresses (TR equivalent of a

multicast address) are added. There is no problem if the driver is written

so it completes calls synchronously. However, if a driver is written so

calls are made asynchronously, the request buffer becomes corrupted and no

routing information is passed.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem was corrected in the latest U.S. Service Pack for Windows NT

version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbhw kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntmac nthw

Additional reference words: sfm adapter prodnt 3.50


Sequential File Reads of 4K Instead of 64K Blocks

Article ID: Q123976

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

In Windows NT, sequential reads from a large file should be in blocks of

64K. Under certain circumstances, Windows NT incorrectly reads in 4K blocks

(on the ALPHA platform it is 8K) and performance is reduced.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbother kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntfilesys

Additional reference words: prodnt 3.50


CD-ROM File System Does Not De-allocate Non-paged Pool Memory

Article ID: Q124021

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

During Win32 SDK CD-ROM installation, the Windows NT CD-ROM file system,

CDFS.SYS, allocates non-paged pool memory, but does not de-allocate it.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbother kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntfilesys

Additional reference words: prodnt 3.50


Windows NT Setup Err Msg on Compaq: Stop 0x0000008B

Article ID: Q124037

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you install Windows NT on a Compaq computer that has two hard disk

drives, and the second drive is unpartitioned, the following error message

appears:

   Stop 0x0000008B

   There might be a virus on your system.

   Restart and set the recovery options in the control panel or the

   /CRASHDEBUG system start option. If this message reappears

   contact your systems administrator or your internal support group.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbsetup kb3rdparty kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntsetup

Additional reference words: prodnt 3.50 proliant 4000 w/ 1-2g 2-1g smart

controller prosignia c810 2-c710


FTP OnNet 1.1 PPP Client Hangs Windows NT 3.5 RAS Service

Article ID: Q124084

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When using FTP's OnNet version 1.1 software on Windows for Workgroups

3.11 as a dial-in PPP client to a Windows NT version 3.5 RAS server, the

hangup script used can cause the RAS services on the server to stop

responding (hang). Additionally, an unexpected disconnect, such as turning

off the modem can also cause the RAS service to hang. Event Viewer

shows event ID 20077 from source RemoteAccess. Attempts to restart the

RAS service will cause event ID 7024 - service specific error 1066.

In order to start the RAS service, the server must be rebooted.

NOTE: This problem also occurs if the client PPP product uses a Trumpet

Winsock.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem was corrected in the latest U.S. Service Pack for Windows NT

version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

OnNet is manufactured by FTP, a vendor independent of Microsoft; we make no

warranty, implied or otherwise, regarding this product's performance or

reliability.

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntras nt16ap

Additional reference words: point-to-point wfw wfwg prodnt 3.50


Event Log Service Fails to Start Due to Event Log Corruption

Article ID: Q124120

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows NT Advanced Server version 3.1

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

A dialog box describing an error with INETMIB.DLL appears. Running NET

START returns error 1722, "RPC server is unavailable." Running NET VIEW

returns the same error. SERVICES.EXE causes an access violation error when

accessing the event log at startup. A DRWATSON.LOG is created as a result.

CAUSE

=====

The event log is corrupted, but the Event Log service hangs before the

dirty bit is set. As a result, the Event Log service will not clean itself

up on reboot and will not start.

WORKAROUND

==========

Recreate the EVENTLOG.DLL by deleting it and allowing the server to restart

will correct the symptoms.

RESOLUTION

==========

EVENTLOG.DLL was rewritten to set the dirty bit even if the service fails.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT and Windows NT

Advanced Server version 3.1 and Windows NT Workstation and Windows NT

Server version 3.5. This problem was corrected in the latest U.S. Service

Pack for Windows NT version 3.5. For information on obtaining the Service

Pack, query on the following word in the Microsoft Knowledge Base (without

the spaces):

   S E R V P A C K

KBCategory: kbtool kbbug3.10 kbfix3.50.sp2

KBSubcategory: ntutil

Additional reference words: prodnt 3.50


Memory Loss During Application Process Creation

Article ID: Q124121

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

An application which periodically starts Command Prompt commands or

utilities (32-bit applications) may exhibit symptoms of a memory resource

allocation problem. To observe this problem, you can use Performance

Monitor to view nonpaged pool memory. The application in question regularly

allocates more and more nonpaged pool memory until system memory resources

are exhausted. This can result in poor system performance and disk

"thrashing" (a condition where the hard disk drive is constantly being

accessed, even in periods of little system activity).

The following error message may appear when system memory is finally

exhausted:

   {DLL Initialization Failed}

   Initialization of the dynamic link library KERNEL32.DLL failed. The

   process is terminating abnormally. [(NTSTATUS) 0xC0000142L]

NOTE: The symptoms are not evident using the same application under Windows

NT version 3.1.

CAUSE

=====

When an application spawns a process repeatedly, a new thread instance will

be created for each process but the previous instances may not be cleaned

up. This results in a significant virtual memory loss each time the process

is spawned. Executing the following Win32 calls will result in the same

memory loss symptoms listed above.

   CreateProcess(anyprocess,...,............, &pi);

   CloseHandle(pi.hProcess);

   CloseHandle(pi.hThread);

NOTE: If there is a WaitForInputIdle() call between CreateProcess() and

CloseHandle(),the problem does not occur.

RESOLUTION

==========

WINSRV.DLL was modified to correct this behavior. Even when processes are

repeatedly created by an application, WINSRV.DLL ensures that the process

and thread handles are closed upon command.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem was corrected in the latest U.S. Service Pack for Windows NT

version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbenv kbbug3.50 kbfix3.50.sp2

KBSubcategory: Nt32ap

Additional reference words: prodnt 3.50


Registry Editor Hangs When You Select a Key

Article ID: Q124142

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you run Registry Editor and select a key with the mouse and press

ENTER at the same time, the computer stops responding (hangs) or you

receive and Out of Memory error message.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbtool kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntutil

Additional reference words: prodnt 3.50 winfile.exe regedit.exe


Cannot Build VC++ Projects (.PDB & .PCH Files) on Netware Server

Article ID: Q124157

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

 - Microsoft Visual C++, 32-bit Edition, version 2.0

----------------------------------------------------------------------

SYMPTOMS

========

When you try to a build Microsoft Visual C++ project on remote NetWare

server from your Windows NT computer, one of the following error messages

appear:

   Fatal error C2308: program database file, 'filename.pdb', has an

   obsolete format, delete it and recompile.

   -or-

   Fatal error C1001: INTERNAL COMPILER ERROR

   (compiler file 'msc1.cpp', line 1056)

   Please choose the Technical Support command on the Visual C++ Help menu,

   or open the Technical Support help file for more information.

The errors do not occur if the project is on a local drive or on a remote

Windows NT server.

CAUSE

=====

Windows NT has problem passing memory mapped file I/O to the NetWare

redirector (NWRDR.SYS) and incorrectly writes the .PDB (program database)

and .PCH (precompiled headers) files to NetWare servers.

WORKAROUND

==========

To work around this problem:

You can work around Error C2308 by using the /Z7 compiler switch. This

forces the compiler to keep the debugging information in the .OBJ files and

not write it to .PDB files.

You can work around Error C1001 by turning off the compiler option for the

pre-compiled headers. To do this, select Settings from the Project menu,

select C/C++, and turn off the compiler option in the Pre-compiled Headers

dialog box.

You can also work around the problem by building the .PDB file or .PCH file

on a local drive, or by installing the latest U.S. Service Pack for Windows

NT version 3.5.

NOTE: After installing the latest U.S. Service Pack for Windows NT version

3.5, you will continue to receive error when you try to a build Microsoft

Visual C++ project on remote NetWare server until you delete the incorrect

.PDB and .PCH files.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

NetWare is manufactured by Novell, Inc., a vendor independent of Microsoft;

we make no warranty, implied or otherwise, regarding this product's

performance or reliability.

KBCategory: kbnetwork kbinterop kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntinterop ntprotocol nt32ap

Additional reference words: prodnt 3.50 VC++ plus


Forced Disconnect for Macintosh Users Not Working

Article ID: Q124242

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

In User Manager for Domains, when you select Forcibly Disconnect Remote

Users From Server When Logon Hours Expire and specify limited logon hours

for an account, the following problems occur for Macintosh accounts:

 - Users are not warned that their logon is about to expire.

 - Users are not disconnected when their logons expire.

 - Disconnects occur after the scheduled disconnect time.

CAUSE

=====

The 10 minute countdown prior to disconnect is not scheduled to run until

one minute before the disconnect time. Several timers are not started and

reset on time. This problem may be more evident for those connecting with

guest sessions.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Server version

3.5. This problem was corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

MORE INFORMATION

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

In User Manager for Domains you can limit users to certain logon hours. For

example, you can limit a user to logon between 8 AM and 5 PM, and select

Forcibly Disconnect Remote Users From Server When Logon Hours Expire in the

Account Policies dialog box.

A PC user with these logon hours will be notified with two messages stating

that they are about to be disconnected from the network and then one final

message stating that they have been disconnected from the network. If this

PC user then tries to connect to the server, access will be denied. Any

previous connections to the server will be disconnected.

Macintosh users that are connected to Macintosh volumes on the server

should be sent a message 10 minutes before being forcibly disconnected from

the server with at least one more reminder before being disconnected. If

logon hours are exceeded the Macintosh users as well as the PC users with

the restricted hours should be forcibly disconnected.

KBCategory: kbnetwork kbbug3.50 kbfix3.50 kbfix3.50.sp2

KBSubCategory: ntmac ntsecurity

Additional reference words: prodnt 3.50 mac sfm


STOP 0x00000026 when Accessing a CD Using an Indirect Path

Article ID: Q124284

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you execute the command:

   dir \\.\<x>:

where <x> specifies a CD-ROM drive, this STOP message appears:

   STOP 0x00000026 (0x000d0259,0x00000001,0x00000000,0x000000000)

   CDFS_FILE_SYSTEM

CAUSE

=====

The CD-ROM file system fails to correctly parse this specific indirect path

specification.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kberrmsg kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntfilesys ntstop

Additional reference words: 3.50 prodnt archive dec blue trap screen


Non Critical Error with IR32_32.DLL and Mitsumi IDE CD-ROM

Article ID: Q124360

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you install Windows NT version 3.5 from a Mitsumi IDE CD-ROM the

following error message appears:

   Non Critical Error

   Error unable to open file IR32_32.DLL

If you choose Continue Setup, Setup completes normally.

CAUSE

=====

This error message appears due to an incompatibility between the Mitsumi

IDE CD-ROM and the Windows NT version 3.5 ATAPI.SYS driver.

WORKAROUND

==========

To work around this problem, copy IR32_32.DLL (an Indeo codec

[compression/decompression] file used with multi-media video) from the

\I386 directory of the Windows NT version 3.5 CD to the

\%SYSTEMROOT%\SYSTEM32 directory after Windows NT version 3.5 is installed.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem has been corrected in the

latest U.S. Service Pack for Windows NT version 3.5. For information on

obtaining the Service Pack, query on the following word in the Microsoft

Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbsetup kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntdriver nthw

Additional reference words: prodnt 3.50 cdrom CRMC FX-4004X atapi 1.2


Windows NT 3.1 Computer Cannot Log On to Windows NT 3.5 Domain

Article ID: Q124374

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you attempt to log on to a domain managed by a Windows NT Server 3.5

primary domain controller (PDC) from a Windows NT version 3.1 workstation,

the following error message appears:

   The system cannot log you on (C0000224). Please try again or

   consult your system administrator.

CAUSE

=====

This problem occurs when "User Must Change Password at Next Logon" is

selected on the PDC.

WORKAROUND

==========

To work around this problem:

1. Run User Manager for Domains on the Windows NT Server PDC.

2. Edit the User account for the person receiving the error message noted

   above.

3. Clear the "User Must Change Password at Next Logon" check box.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntsecurity ntdomain

Additional reference words: prodnt 3.50 usrmgr


SFM: File Permissions Problem When Volume is Shared at Root

Article ID: Q124375

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

After you install Services for Macintosh (SFM) on a computer running

Windows NT Server version 3.5, you encounter file permission problems on

the Macintosh volume. For example, file permissions are not applied to

files dynamically on the Macintosh volume. As a result, Macintosh clients

cannot view the files.

CAUSE

=====

This problem occurs when a Macintosh volume is shared at the drive root.

WORKAROUND

==========

To work around this problem, recreate the Macintosh volume.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem was corrected in the latest U.S. Service Pack for Windows NT

version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50 kbfix3.50.sp2

KBSubcategory: ntmac

Additional reference words: prodnt 3.50 mac zone sfm


Error 33: DOSRead and DOSWrite APIs from OS/2 Application

Article ID: Q124484

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you call a DOSRead or DOSWrite API on locked ranges from an OS/2-based

application under Windows NT version 3.5, an error 33 appears.

CAUSE

=====

The OS/2 subsystem does not resolve the DOSRead and DOSWrite APIs

correctly.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem has been corrected in the

latest U.S. Service Pack for Windows NT version 3.5. For information on

obtaining the Service Pack, query on the following word in the Microsoft

Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbother kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntos2ap

Additional reference words: prodnt 3.50 OS2 OS2SRV


Service Logged On w/ User Account Able to Interact with Desktop

Article ID: Q124542

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

You start a service using the default account, LocalSystem. It interacts

with the desktop and displays windows as expected. You stop the service and

restart it using a user account. It incorrectly continues to interact with

the desktop and display windows.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbother kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntsecurity

Additional reference words: prodnt 3.50


Unable to Disable Print Event Logging in Windows NT 3.5

Article ID: Q124549

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

In Windows NT version 3.1, it was possible to disable event logging for all

printing-related events by using the following Registry entry:

   EventLog

   ========

   Disable Event logging from the Spooler (disabled by default)

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

      \Print\Providers

      Add Value: "EventLog"

      Data Type: REG_DWORD

      Set the data = 0

This same setting should work under Windows NT version 3.5, but it does

not; printing events are still written to the event log.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem has been corrected in the

latest U.S. Service Pack for Windows NT version 3.5. For information on

obtaining the Service Pack, query on the following word in the Microsoft

Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbprint kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntprint

Additional reference words: prodnt 3.50


VBApp & OLE Do Not Work If Network Components Are Not Installed

Article ID: Q124582

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you install Windows NT version 3.5 without any network components

installed, a dialog box with an exclamation mark appears when you run Excel

version 5.x and load a worksheet with Visual Basic for Applications macros

or choose Add Macro in an existing worksheet. This indicates an error has

occurred, but the dialog box does not include any text describing the

error. You are unable to load any worksheets with Visual Basic for

Applications macros or create a new module for Visual Basic for

Applications macro code.

OLE may also fail. The error message varies depending on the application.

WORKAROUND

==========

You can work around this problem by setting up a network:

1. In the Control Panel window, choose the Network icon.

2. When the dialog box appears informing you that the network components

   are not installed and asks if you want to install them, choose OK To

   Install.

3. When you are asked if you want Setup to autodetect your network card,

   choose No. You will then be presented with a list box with network card

   choices. Select the MS Loopback Adapter.

4. Choose OK for the default frame type of 802.3.

5. Choose OK for the default protocol of NWLink.

6. In the Network Configuration screen, choose OK.

7. Shut down and then restart your computer.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbinterop kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: nt16ap

Additional reference words: prodnt 3.50 insert blank


DC21040 Causes Windows NT 3.5 to Stop Responding (Hang)

Article ID: Q124648

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Network connections on your Windows NT computer are lost, new users can not

connect, and applications requiring network access stop responding (hang).

Applications running locally may continue to function, but may also

eventually hang.

CAUSE

=====

You are using the DC21040.SYS Ethernet driver. A problem with the driver

causes the protocol to run out of resources when dealing with loopback

packets. The system becomes unable to accept anymore incoming packets from

the adapter. Loopback occurs when an application is accessing a local

resource (for example, a UNC file name) rather than a local driver letter.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem has been corrected in the

latest U.S. Service Pack for Windows NT version 3.5. For information on

obtaining the Service Pack, query on the following word in the Microsoft

Knowledge Base (without the spaces):

   S E R V P A C K

The third-party products discussed here are manufactured by vendors

independent of Microsoft; we make no warranty, implied or otherwise,

regarding these products' performance or reliability.

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntdriver

Additional reference words: prodnt 3.50 DEC 2100 cpu


SFM Err Msg: The Item...Is Missing and Was Probably Deleted...

Article ID: Q124747

----------------------------------------------------------------------

The information in this article applies to:

  - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When using Macintosh Operating System 7.5 to find files on a Windows NT 3.5

Macintosh volume, the following error message appears after the query is

completed:

   The item <filename> is missing and was probably deleted. Other items may

   be affected; Checking them now.

A list of files that Macintosh file finder has found is then displayed. The

files are grayed out and inaccessible.

CAUSE

=====

On returning from the search, Find File calls AfpResolveId on ID=0. Since 0

is an invalid ID Windows NT Services for Macintosh returned ParamErr.

RESOLUTION

==========

The error code was changed to be IdNotFound which is what is returned from

real AppleShare servers.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem has been corrected in the

latest U.S. Service Pack for Windows NT version 3.5. For information on

obtaining the Service Pack, query on the following word in the Microsoft

Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kb3rdparty kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntmac

Additional reference words: prodnt sfm 3.50


DHCP Client Does Not Support Domain Name Option

Article ID: Q124796

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

The Windows NT version 3.5 dynamic host configuration protocol (DHCP)

client does not recognize the domain name sent by the Windows NT DHCP

Server.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem was corrected in the latest U.S. Service Pack for Windows NT

version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50 kbfix3.50.sp2

KBSubcategory: nttcp

Additional reference words: prodnt 3.50 option 15 dhcp


Very Large or Very Small Transfers to SCSI Printers Fail

Article ID: Q124816

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Your computer stops responding (hangs) if the SCSIPRNT driver is loaded and

a SCSI printer is connected.

CAUSE

=====

SCSIPRINT does not handle transfers correctly when they are smaller than

the maximum transfer length of the device in question. In addition, on

large transfers, it assumes that the request is either a 10-byte SCSI Read

or SCSI Write command, but SCSI printers use a 6-byte SCSI Print command.

When the 10-byte write command is issued, the SCSI printer rejects the

command as an illegal request.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem was corrected in the latest U.S. Service Pack for Windows NT

version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbother kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntdriver

Additional reference words: prodnt 3.50


STOP Message with SFMATALK.SYS

Article ID: Q124853

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Servers running Services for Macintosh may stop running and a STOP message

may appear. This appears to be most likely with MS-DOS and Windows clients

printing to Macintosh printers.

MORE INFORMATION

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

This problem can be identified in the kernel debugger by the following

(after obtaining the trap frame address):

kd> !trap fef97c84

eax=00000700 ebx=ffffff01 ecx=00000040 edx=00595b02 esi=206b7441

edi=00000001

eip=80124da9 esp=fef97cf8 ebp=fef97d34 iopl=0         nv up ei pl nz na pe

nc

cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000

efl=00010202

ErrCode = 00000000

80124da9 393438           cmp     [eax+edi],esi

kd> !kb

KD: Unable to load debug information for 0x00000524

KD: unloading "0x00000524" (deferred)

ChildEBP RetAddr  Args to Child

fef97d00 801012d4 206b7441 00000060 ffffffff NT!_ExpRemovePoolTracker+0x49

fef97d34 fc997320 ffb49768 ffb4976c fc996631 NT!_ExFreePool+0x15a

fef97d40 fc996631 ffb4976c fef97dd0 ffb49794 sfmatalk!_AtalkFreeMemory+0x21

fef97d60 fc99ad9e ffb4976c 00000000 ffac6470 sfmatalk!_AtalkDdpDeref+0xfa

fef97d78 fc99cce7 ffb4976c 00000000 00000000

 sfmatalk!_AtalkDdpCloseAddress+0x5f

fef97d98 fc9a0100 ffac630c 00000000 00000000

 sfmatalk!_AtalkAtpCloseAddress+0x84

fef97db0 fc99140b ffaac14c fc99bf79 ff0981d8

 sfmatalk!_AtalkPapCloseAddress+0x4f

fef97dd0 fc990df3 ff0981d8 ff098248 feffc0f8

 sfmatalk!_AtalkTdiCloseAddress+0x1c3

fef97dec 80107aea feffc040 ff0981d8 ff0981d8

sfmatalk!_AtalkDispatchClose+0x5

1

fef97e00 80108b7f ff095f50 ffae0140 00000000 NT!IofCallDriver+0x38

fef97e34 80147049 ffae0140 ffae010c ffae0108 NT!_IopDeleteFile+0x149

fef97e54 8010560e ffae0140 ffae0140 ffae0108

NT!_ObpRemoveObjectRoutine+0xd7

fef97e68 8010b30d fef97e98 fef97e98 fef97f14 NT!ObfDereferenceObject+0x28

fef97e8c 801385c3 00000524 801042e4 ffacdd68 NT!_NtClose+0x120

fef97e8c 8012a6d3 00000524 801042e4 ffacdd68 NT!_KiSystemService+0x83

fef97f0c 00000524 80405a50 ff04a6a8 fcae8710 NT!_ZwClose+0xb

The key points of information are:

 eax=00000700

 edi=00000001

 Top of stack=NT!_ExpRemovePoolTracker+0x49

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem has been corrected in the

latest U.S. Service Pack for Windows NT version 3.5. For information on

obtaining the Service Pack, query on the following word in the Microsoft

Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntmac

Additional reference words: prodnt sfm 3.50 ntstop blue screen trap


STOP Message 0x0A Running Performance Monitor on NEC 3360

Article ID: Q124874

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you run Performance Monitor remotely on an NCR 3360 two-processor

computer with a 3Com 3C529 network interface card (NIC), and Performance

Monitor is using default counters for all instances of NBF Bindings,

Logical Disks, Physical Disks, Network Segments, and Processors, the

following STOP message appears on the NEC 3360:

   STOP 0x0000000A (0x00000006, 0x00000002, 0x00000000, 0xfa0e08f4)

   Memory at 0x06 was referenced at IRQL2 for 0 access from 0xfa0e08f4

   Address 0xfa0e08f4 has base at 0xfa0e0000 - ndis.sys

CAUSE

=====

NSID.SYS is dequeuing NDIS send packets out of order.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem was corrected in the latest U.S. Service Pack for Windows NT

version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

The 3C529 NIC is manufactured by 3Com, a vendor independent of Microsoft;

we make no warranty, implied or otherwise, regarding this product's

performance or reliability.

KBCategory: kbnetwork kberrmsg kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntstop

Additional reference words: adapter 3.50 prodnt blue screen trap 0x0a


Problems Accessing Drive Formatted with Ontrack Disk Manager

Article ID: Q124909

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you attempt to install Windows NT on a system with a drive that has

been formatted by Ontrack System's Disk Manager, you cannot access the

drive, either during Setup or after Setup has completed.

CAUSE

=====

Windows NT version 3.5 does not recognize drives that have been formatted

using the Ontrack Disk Manager software.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem was corrected in the latest U.S. Service Pack for Windows NT

version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

Ontrack Disk Manager is manufactured by a vendor independent of Microsoft;

we make no warranty, implied or otherwise, regarding this product's

performance or reliability.

KBCategory: kb3rdparty kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntsetup

Additional reference words: prodnt 3.50


Using Ontrack Disk Manager to Support Large IDE Drives

Article ID: Q124910

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SUMMARY

=======

This article describes using Ontrack Disk Manager on an MS-DOS system to

partition and format a large (more than 540 megabytes [MB]) IDE hard disk

drive. A large IDE hard disk drive usually requires a system BIOS or

controller that supports more than 1024 cylinders. For general information

on installing Windows NT on large IDE hard disk drives, please see the

following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q124307

   TITLE     : Installing Windows NT on Large IDE Disk Drives

NOTE: To use Ontrack Disk Manager with Windows NT version 3.5, you need to

obtain an updated driver from Microsoft Product Support Services.

This updated driver (ATDISK.SYS) is included with the latest U.S. Service

Pack for Windows NT version 3.5. For information on obtaining the Service

Pack, query on the following word in the Microsoft Knowledge Base (without

the spaces):

   S E R V P A C K

MORE INFORMATION

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

Installing the Updated Driver

-----------------------------

Once you obtain the updated driver, if you are installing it on a system

already running Windows NT version 3.5, follow the installation

instructions included with the updated driver or Service Pack.

If you are attempting to install Windows NT version 3.5 on a drive that has

been formatted with Ontrack Disk Manager, installation of the updated

driver is complicated and depends upon whether you are installing from a CD

or from floppy disk.

CD Installation

---------------

Installing from a CD onto a disk formatted with Ontrack Disk Manger

requires that you boot the system under MS-DOS and access the CD. After

booting under MS-DOS, start installation from the \I386 directory on the CD

using the WINNT.EXE command. Allow the WINNT setup program to create three

boot disks and copy files to the temporary directory, $WIN_NT$.~LS. You may

also use the WINNT /B mode of Setup, which does not require the three boot

floppy disks but does require more free space on your boot partition. After

the file copy is finished, Setup asks you to reboot the system with the

boot floppy disk in drive A; do not do this. Instead, reboot to MS-DOS and

do the following:

1. Replace the ATDISK.SYS file on Setup Disk 3 with the updated file. If

   you used the /b option on Windows NT, replace ATDISK.SYS in the

   $WIN_NT$.~BT directory instead.

   NOTE: If your copy of ATDISK.SYS is compressed (ends with .SY_ instead

   of .SYS) you will need to decompress it, using the expand command,

   before replacing the copy on the installation disks.

2. Replace the ATDISK.SYS file in the directory $WIN_NT.~LS with the

   updated file.

3. Reboot the system and when Disk Manager gives you the option of starting

   from a boot floppy disk, select this option and boot from Setup Disk 1.

This should allow you to set up Windows NT version 3.5 on a drive formatted

with Ontrack Disk Manager.

Floppy Disk Installation

------------------------

Floppy installation on an Ontrack Disk Manager-formatted drive requires

that you install Windows NT on to a FAT partition, although you can convert

it to NTFS after Setup is complete. To set up, do the following:

1. Make a disk copy of Setup Disk 3.

2. Replace ATDISK.SYS on the disk copy with the updated ATDISK.SYS file.

   NOTE: If your copy of ATDISK.SYS is compressed (ends with .SY_ instead

   of .SYS) you will need to decompress it, using the expand command,

   before replacing the copy on the installation disks.

3. Reboot the system and when Disk Manager gives you the option of starting

   from a boot floppy disk, select this option and boot from the Setup boot

   disk.

4. When you reach the first reboot (at Disk 9) do not allow Setup to

   continue; instead reboot to MS-DOS (either using a bootable MS-DOS

   floppy disk or interrupting the boot menu before it loads Setup) and

   replace ATDISK.SYS in <WINNT>\SYSTEM32\DRIVERS with the updated file,

   and then reboot and allow Setup to finish.

After you finish installing Windows NT version 3.5, you can then convert

your partitions from FAT to NTFS if you want. You may experience an extra

delay in booting after you convert your boot partition to NTFS; however,

other than this delay, there are no problems with converting to NTFS.

Ontrack Disk Manager is manufactured by a vendor independent of Microsoft;

we make no warranty, implied or otherwise, regarding this product's

performance or reliability.

KBCategory: kbsetup kbhw kb3rdparty kbfix3.50.sp2

KBSubcategory: nthw ntsetup nthowto

Additional reference words: prodnt 3.50 howto hrdwr


Slow Processing with Windows NT PDC and LAN Manger BDC

Article ID: Q124912

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

 - Microsoft LAN Manager version 2.2

----------------------------------------------------------------------

SYMPTOMS

========

All networks that have Windows NT version 3.5 Domain Controllers (DCs) and

LAN Manager Backup Domain Controllers (BDCs) experience this problem. Some

symptoms of this issue can be a general slowness of the Windows NT version

3.5 DC because of the constant syncing of the LAN Manager BDCs. Symptoms

for this problem include:

 - Slow file directory enumeration from client workstations.

 - Slow printing when the printers are locally connected the client

   workstations.

CAUSE

=====

A design change in Windows NT version 3.5 causes the entire membership of

groups (containing new users) to be sent to the LAN Manager BDC. If the

total amount of this data is greater than the buffer allocated by the BDC

for the DC, it requests a larger buffer. If the second buffer is also too

small, the BDC goes into a full sync condition.

WORKAROUND

==========

To reduce the likelihood of encountering this problem, change the LAN

Manager BDC so that it initially allocates a buffer of 64K.

RESOLUTION

==========

Microsoft has changed Windows NT so it now sends a list of only the groups

that new users belong to, instead of the entire membership of the groups.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem has been corrected in the

latest U.S. Service Pack for Windows NT version 3.5. For information on

obtaining the Service Pack, query on the following word in the Microsoft

Knowledge Base (without the spaces):

   S E R V P A C K

To correct this problem on your LAN Manager BDC servers, contact Microsoft

Product Support Services to get the LAN Manager patch, CSD00.108.

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntinterop

Additional reference words: prodnt 3.50 2.20 netlogon lanman NTS LM synch

synchronization


Application in VDM May Receive Overrun Error

Article ID: Q124936

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

MS-DOS-based applications that use serial communications may receive a

serial overrun error when running in a Windows NT version 3.5 virtual DOS

machine (VDM), even though the application ran correctly under MS-DOS. In a

Basic application, this would be seen as Error 57.

This has generally been seen after several hours of heavy communications at

9600 bits per second (bps).

CAUSE

=====

Because MS-DOS-based applications running under Windows NT are subject to

CPU time-slicing; they may not execute for extended periods of time (in

Windows NT, the highest priority task that is able to run always runs). To

prevent lost characters from serial communications ports, Windows NT

virtualizes the port and presents the characters to the MS-DOS-based

application as that application receives CPU time. The virtualization

includes code to detect that an application is ignoring the serial port; a

problem in this code sometimes incorrectly reports a serial overrun error.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem was corrected in the latest U.S. Service Pack for Windows NT

version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntdosap

Additional reference words: prodnt 3.50


STOP 0x0000000A when Accessing NetWare Server

Article ID: Q124940

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

A STOP message (0x0000000A) may occur when attempting to access a NetWare

share from File Manager with Client Services for NetWare (CSNW) installed.

Below is a listing of the debug session:

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem has been corrected in the

latest U.S. Service Pack for Windows NT version 3.5. For information on

obtaining the Service Pack, query on the following word in the Microsoft

Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntstop

Additional reference words: prodnt 3.50


NTFS Integrity Problems with Large Stripe Sets

Article ID: Q124958

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you use a large hard disk drive (for example, a Seagate 9 GB) for a

stripe set with or without parity on NTFS, you may experience file

corruption and data integrity problems.

CAUSE

=====

The fault tolerance (FT) driver stripe code calculates the row for I/O

using 64-bit math. However, when building the IRP for the I/O it calculates

the byte offset from the "row" value using 32-bit math.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem has been corrected in the

latest U.S. Service Pack for Windows NT version 3.5. For information on

obtaining the Service Pack, query on the following word in the Microsoft

Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbother kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntfault ntfilesys

Additional reference words: prodnt 3.50


Event Viewer Does Not Report System Log Errors Correctly

Article ID: Q125573

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Error and warning messages are not correctly handled by the System Log.

When you attempt to view a message in Event Viewer, the following is

displayed:

   The description for event id (x) in source (XXX) could not

   be found...".

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kberrmsg kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntgeneral

Additional reference words: 3.50 prodnt


Software Compression Compatibility in Windows NT 3.5 RAS

Article ID: Q125625

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SUMMARY

=======

Several fixes were made to Windows NT Remote Access Service (RAS) that are

included in the latest U.S. Service Pack for Windows NT version 3.5. This

article provides background information on client compatibility with RAS.

MORE INFORMATION

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

NOTE: If you don't already have RAS installed, install it from your

original Windows NT installation media before applying the Service Pack.

RAS Software Compression Compatibility with Windows for Workgroups 3.11

and Windows NT 3.1

-----------------------------------------------------------------------

In addition to other fixes, the Service Pack installs files that make

Windows NT 3.5 software compression compatible with Windows for Workgroups

3.11 and Windows NT 3.1. Throughput should improve significantly unless

previously compressed files are copied. For best performance, Microsoft

suggests you configure the RAS client software on Windows for Workgroups

3.11, Windows NT 3.1, and Windows NT 3.51 (or Windows NT 3.5 with Service

Pack 2 installed) as follows:

1. In Remote Access, make sure the Disable Software Compression option in

   the Options menu is not selected.

2. Choose the Edit button, then choose the Modem button, and select the

   following:

    - Enable Hardware Flow Control

    - Enable Modem Error Control

   Clear the Enable Modem Compression check box so software compression

   and modem compression are not used at the same time (as this reduces

   throughput).

Windows NT Servers and Clients and RAS Software Compression

-----------------------------------------------------------

If you install the Service Pack on a Windows NT 3.5 RAS server, unmodified

Windows NT 3.5 RAS clients do not lose software compression compatibility

when calling the RAS server. Windows for Workgroups 3.11 and Windows NT 3.1

RAS clients can use RAS software compression without any need for new

files, except as noted below.

All copies of Windows NT 3.5 have RAS software compression built-in. Only

Windows NT 3.5 computers that are acting as RAS servers need the Service

Pack for compression compatibility with Windows NT 3.1 and Windows for

Workgroups 3.11 RAS clients. However, because of several code improvements,

Microsoft recommends that you also apply this patch to Windows NT 3.5 RAS

clients. The patch is required for RAS software compression compatibility

when you call a Windows NT 3.1 or Windows for Workgroups 3.11 RAS server

from a Windows NT 3.5 RAS client.

Software Compression in Windows for Workgroups 3.11

and Windows NT 3.1 RAS Clients

---------------------------------------------------

Software compression is available, by default, in the following RAS clients

unless you select Disable Software Compression from the Options menu, or

you purchased your copy of Windows for Workgroups 3.11 or Windows NT 3.1

after February 1994. You can tell whether or not you have RAS software

compression by using the following information:

Windows for Workgroups 3.11:

   Filename     Bytes   Compression

   --------------------------------

   RASMAC.386   49209   Yes

   RASMAC.386   27193   No

Windows NT 3.1:

   Filename       Bytes    Compression

   -----------------------------------

   ASYNCMAC.SYS   53188    Yes

   ASYNCMAC.SYS   53716    Yes

   ASYNCMAC.SYS   33732    No

NOTE: The Windows NT 3.1 and Windows for Workgroups 3.11 RAS compression

files can be obtained from the SUPPORT\RAS directory on the Windows NT 3.5

U.S. Service Pack 2 compact disc.

STATUS

======

These fixes are included in the latest Windows NT 3.5 U.S. Service Pack.

For information on obtaining the Service Pack, query on the following word

in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbug3.50 kbfix3.50.sp2

KBSubcategory: ntras

Additional reference words: prodnt 3.50


Computer with Intel Neptune PCI Chip Hangs on Warm Reboot

Article ID: Q125646

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Your single processor computer using the Intel Neptune 82434 PCI Cache

Memory Controller (PCMC) stops responding (hangs) when you perform a warm

reboot running Windows NT version 3.5.

CAUSE

=====

The BIOS incorrectly registers two CPUs.

RESOLUTION

==========

The Hardware Abstraction Layer (HAL) file, HALMPS.DLL, has been updated to

resolve this problem.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem was corrected in the latest U.S. Service Pack for Windows NT

version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbhw kbsetup kbbug3.50 kbfix3.50.sp2

KBSubcategory: nthw ntmp

Additional reference words: prodnt 3.50 hal hang boot


Windows NT3.5 Improves Performance with Intel Neptune PCI Chip

Article ID: Q125759

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SUMMARY

=======

Microsoft has developed new Windows NT version 3.5 Hardware Abstraction

Layer (HAL) Dynamic-Link Libraries (DLLs) that take advantage of Intel's

new A1 stepping of their Neptune 82434 PCI Cache Memory Controller (PCMC)

chip. These new DLLs allow your PCI-based computer with A1 or greater

stepping to achieve full operating performance.

MORE INFORMATION

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

The A0 stepping of the Neptune 82434 PCMC chip had two routines, Read-

Around-Write Enable and PCI-to-Memory Posting Enable, that did not function

according to specification. This led to data corruption in random access

files and occasionally in memory.

Because BIOS updates to correct this problem were generally unavailable at

the time of its release, Windows NT version 3.5 avoided potential data

corruption by disabling these routines. However, this workaround resulted

in a slight performance degradation.

Intel has since introduced A1 stepping for their Neptune 82434 chip which

resolves the data corruption problem. Consequently, Microsoft has modified

Windows NT HAL to only disable these routines on A0 chips. Chips with A1

and greater steppings will function normally and achieve full operating

performance.

The new HAL is available in the latest U.S. Service Pack for Windows NT

version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbhw kbbug3.50 kbfix3.50.sp2

KBSubcategory: nthw

Additional reference words: prodnt 3.50


Setup Err Msg on Intel Xpress Deskside: Inaccessible Boot...

Article ID: Q126020

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you install Windows NT on an Intel Xpress Deskside/MX 66Mhz

Dual Pentium, your computer stops responding (hangs) for about ten minutes,

after Setup reboots the computer the first time. The following error

message appears:

   INACCESSIBLE BOOT DEVICE

This problem occurs when Setup selects MPS 1.1 Multiprocessor PC as the

system type. This problem does not occur when you select Standard PC.

NOTE: Selecting MPS 1.1 Multiprocessor PC causes HALMPS.DLL to be

installed. Selecting Standard PC causes HAL.DLL to be installed.

CAUSE

=====

Older Mylex Firmware doesn't respond in the time-out period allotted during

the SCSI ENQUIRY2 command initialization.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem has been corrected in the

latest U.S. Service Pack for Windows NT version 3.5. For information on

obtaining the Service Pack, query on the following word in the Microsoft

Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory:kbsetup kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntboot ntdriver

Additional reference words: 3.50 crash install blue screen prodnt express


16-Bit Process Creation Can Result in Memory Loss

Article ID: Q126277

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

If a 16-bit Windows-based application creates another 16-bit Windows-based

applications, the WOW environment can lose memory. Continuous memory loss

can cause applications to fail.

CAUSE

=====

Thread objects are lost when on 16-bit processes creates another 16-bit

processes. Also, the Win16 GetIconInfo() function causes memory loss when

memory is not correctly de-allocated.

RESOLUTION

==========

To correct this problem, obtain and install Windows NT U.S. Service Pack 2.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem has been corrected in the

latest U.S. Service Pack for Windows NT version 3.5. For information on

obtaining the Service Pack, query on the following word in the Microsoft

Knowledge Base (without the spaces):

   S E R V P A C K

This problem was corrected in Windows NT version 3.51.

KBCategory: kbother kbbug3.50 kbfix3.50.sp2 kbfix3.51

KBSubcategory: nt16ap

Additional reference words: 3.50 prodnt loss windows on windows


Equinox Serial Driver Causes the Win16 Subsystem to Fail

Article ID: Q126429

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When using Equinox Systems intelligent serial board and driver, the Win16

subsystem fails when a 16-bit terminal application is run. Example programs

of this type are WinCim and Procomm Plus for Windows.

The following message may appear:

   Application caused an exception in the Win16 subsystem

Then, the 16-bit application and the Win16 subsystem terminate. However,

Windows NT does not fail.

CAUSE

=====

The Win16 subsystem is not correctly dealing with overlapped reads when

communicating with the COM ports.

When a ReadFile is issued, the Win16 subsystem assumes it either has

completed immediately or that it has failed (that is, it assumes that the

read is synchronous). When using the Equinox serial driver, the Win16

subsystem assumes all the reads are failing because none of the reads are

completed immediately. This situation eventually causes the Win16 subsystem

to fail.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT Workstation and

Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

The products included here are manufactured by vendors independent of

Microsoft; we make no warranty, implied or otherwise, regarding these

products' performance or reliability.

KBCategory: kb3rdparty kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntdriver nt16ap

Additional reference words: prodnt 3.50


DCs Fail to Synchronize or Validate Users Over NWLINK

Article ID: Q126752

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Windows NT Netlogon services may fail. Users may fail to be logged on and

servers may be unable to synchronize. The following errors may appear be or

reported in the system log:

   1311    There are currently no logon servers available to service the

           logon request.

   5719    No windows NT domain controller is available for domain...

   3096    The Windows NT domain controller for this domain could not be

           located.

   3210    Failed to authenticate with <computer name>, a Windows NT domain

           controller for domain <name>.

   5723    The session setup from the computer <computer name> failed to

           authenticate. The name of the account referenced in the

           security database is <name>. The following error occurred:

           Access is denied.

CAUSE

=====

When the default protocol becomes inoperable, Netlogon fails to

complete operations because it does not attempt to use other installed

protocols.

NOTE: Protocols can become inoperable when catastrophic infrastructure

problems occur involving routers or network addressing.

RESOLUTION

==========

Netlogon has been updated. When Netlogon receives an error responding to a

mailslot message from the first protocol that it attempts to use, it

responds to duplicates of the original message received by all available

protocols. Datagram mailslot messages are used by Netlogon to initiate

client logon operations and inter-domain operations including the

synchronization of domain controllers (DCs). By responding to all messages

received, Netlogon responds successfully, even if an individual protocol is

not operating properly.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem was corrected in the latest US Service Pack for Windows NT.

For information on obtaining this update, query on the following word in

the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntdomain ntprotocol

Additional reference words: 3.50 prodnt domain controller controllers

viewer network mail slot net logon


Clients Fail to Connect to Windows NT Server

Article ID: Q127818

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

You are intermittently not able to connect to Windows NT Server version 3.5

from your network client. If you attempt to connect from a Windows NT

client, a "Semaphore Time Out" error message appears, but no events are

logged in the System Log.

CAUSE

=====

The client computer is incorrectly sending a Session End frame in response

to a Receive Outstanding frame.  This appears to happen when the client

computer is in an error condition prior to the transmission.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem was corrected in the latest US Service Pack for Windows NT.

For information on obtaining this update, query on the following word in

the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntprotocol ntinterop

Additional reference words: prodnt 3.50 2.2 2.1


LMHOSTS File Generates STOP 0x00000050

Article ID: Q128565

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Windows NT provides the ability to search for LMHOSTS files located on

other systems. This is permitted for file using full path on local machine

or the UNC path across networks. If you use a #INCLUDE statement with a

driver letter in a Windows NT LMHOSTS file, the following error message

appears:

   STOP: 0x00000050

   PAGE_FAULT_IN_NONPAGED_AREA     (0x50)

For example, the following LMHOSTS file would cause the STOP message:

   #BEGIN_INCLUDE

   #INCLUDE d:\winnt\system32\drivers\etc\hosts

   #END_INCLUDE

CAUSE

=====

There is a problem in the text-parsing routines that causes an incorrect

full path to be generated for the local file.

STATUS

=======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem was corrected in the latest U.S. Service Pack for Windows NT

version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntstop

Additional reference words: prodnt 3.50 trap 0x50


Date and Time Stamp of Files Change When Copied to Netware

Article ID: Q129045

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you use File Manager to copy files from a Windows for Workgroup 3.11

client to a Netware Server (accessed through Windows NT 3.5 Server running

Gateway Services for Netware), the date and time of some files change.

WORKAROUND

==========

To work around this problem, use the copy command from a Windows for

Workgroups MS-DOS command prompt to copy the files to the NetWare Server.

STATUS

======

Microsoft has confirmed this to be a problem in Windows for Workgroup 3.11

and Windows NT Server version 3.5. This problem was corrected in the latest

U.S. Service Pack for Windows NT version 3.5. For information on obtaining

the Service Pack, query on the following word in the Microsoft Knowledge

Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.11 kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntinterop

Additional reference words: 3.11 3.50 wfw wfwg winfile


Running PKZIP Hangs WFW or Windows NT MS-DOS Command Prompt

Article ID: Q130117

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SYMPTOMS

========

When you run MS-DOS Command Prompt on a computer running Windows for

Workgroups or Windows NT, and then run PKZIP.EXE from a Windows NT read-

only network drive to compress a large file (ten megabytes or larger), your

MS-DOS Command Prompt may stop responding (hang).

CAUSE

=====

PKZIP is attempting to create a temporary file. When the MS-DOS create

unique file API is executed at a network drive with read-only privileges,

the Windows NT server service returns SMB access denied. This problem

occurs under Windows for Workgroups because the Windows NT workstation

service does not handle the SMB access denied. This problem occurs under

Windows NT because the Windows NT redirector does not correctly handle the

SMB access denied. Because of these problems, the application does not

terminate, and the API call repeatedly attempts to recreate random file

names. This loop sends request to the server infinitely.

This problem occurs only when your read-only network drive is on a computer

running Windows NT. For example, if the read-only drive is on a computer

running Windows for workgroups, the server responds in a fashion which

allows the application to return access denied to the user and the

application halts. The Windows for Workgroups server returns SMB access

denied: 2,4.

RESOLUTION

==========

To work around this problem, run PKZIP from a local or network drive that

provides both read and write privileges for the temporary files. To correct

this problem under Windows for Workgroups, install the latest US Service

Pack for Windows NT on the computer running Windows NT. To correct this

problem, install the latest US Service Pack for Windows NT.

NOTE: SRV.SYS and RDR.SYS were changed to handle the SMB access denied

return codes properly.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version

3.5. This problem was corrected in the latest US Service Pack for

Windows NT. For information on obtaining this update, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

This problem was corrected in Windows NT version 3.51.

The third-party products discussed here are manufactured by vendors

independent of Microsoft; we make no warranty, implied or otherwise,

regarding these products' performance or reliability.

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2 kbfix3.51

KBSubcategory: ntnetserv

Additional reference words: prodnt wfw wfwg 3.11 3.50 3.51 share 1,5

0xc0000022 error code


Event Error 2000 Logged Repeatedly Due to Illegal Command

Article ID: Q130120

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

Windows NT file servers may log error 2000 in the event log with the

following data:

   0000: 00040000 00540001 00000000 c00007d0

   0010: 00000000 c000000d 00000000 00000000

   0020: 00000000 00000000 00000bcd

CAUSE

=====

If a user application request is submitted illegally by a client

application, the server logs the failure. The server is failing a

SrvQueryBasicAndStandardInformation() call, with an "Invalid

Parameter" status. The following commands result in the same error:

   dir \\servername\ipc$

   dir \\servername\pipe

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version

3.5. This problem was corrected in the latest US Service Pack for

Windows NT. For information on obtaining this update, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

SRV.SYS has been modified so that these messages are no longer logged

and the smbs are discarded resulting in an application error.

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntnetserv

Additional reference words: prodnt 3.50


GSNW Share Names Displayed as DELETED with RAS Server Running

Article ID: Q130480

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

If the Gateway Service for NetWare (GSNW) and the Remote Access Service

(RAS) server is running simultaneously, the Share Name in the Configure

Gateway dialog box for GSNW displays the following:

   *DELETED*

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem was corrected in the latest US Service Pack for Windows NT.

For information on obtaining this update, query on the following word in

the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2

KBSubcategory: ntnetserv ntinterop ntras

Additional reference words: prodnt 3.50 nwc cpl


File Size and Date Reported Incorrectly On NTFS Drive

Article ID: Q125385

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

File Manager and the Windows NT Command Prompt DIR command incorrectly

report file date, time, and size information.

CAUSE

=====

This problems occurs when the file date, time, and size information stored

in the directory entry for a file is not updated from the file date, time,

and size information stored in the file record. As a result, file date,

time, and size data are not displayed correctly when a non-specific or

wildcard DIR command (one that does not explicitly specify a single file

name) is issued.

This problem only affects files on Windows NT machines which have been

modified by non-Windows NT client workstations.

WORKAROUND

==========

To work around this problem, explicitly specify the file name in a DIR

command, or open and close the file exhibiting the problem with an

application.

MORE INFORMATION

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

The NTFS file system maintains the current date, time, and size in the file

record. It also contains duplicate information in the directory entry for

quick reference by applications that do not need to access the actual file

data (such as the DIR command). This results in a substantial performance

improvement when only the file date, time, or size is being requested.

For performance reasons, when an application has a file open NTFS ignores

the directory copy of file date, time, and size information. When the file

is closed, or when an application makes an explicit request to update the

information, the directory copy of the information is updated.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbtool kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntfilesys

Additional reference words: 3.50 prodnt


Windows NT Mail Err Msg: The Network Path You Entered Could...

Article ID: Q126142

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

The following error message appears the first time you access a Microsoft

Mail postoffice on a Novell file server from the Windows NT Microsoft Mail:

   The network path you entered could not be found

CAUSE

======

The 32-bit Microsoft Mail client calls the API FindFirstFile() on the

postoffice. FindFirstFile() requires filescan trustee directory rights.

WORKAROUND

==========

To work around this problem, give filescan trustee directory rights to each

user accessing Microsoft Mail postoffices on Novell file servers.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

This problem was corrected in Windows NT version 3.51.

KBCategory: kbnetwork kb3rdparty kbbug3.50 kbfix3.50.sp3 kbfix3.51

KBSubcategory: ntgeneral nt32ap

Additional reference words: 3.10 netware post office file scan


RAS Callback Via ISDN Uses Only One Channel

Article ID: Q126383

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

-------------------------------------------------------------------------

SUMMARY

=======

If you use the callback feature of the Windows NT 3.5 Remote Access Service

(RAS) server to perform a callback through an ISDN connection, only one

channel of the ISDN line is used.

MORE INFORMATION

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

An ISDN line provides two b-channels that can be used for data transfer.

You can configure RAS to use two channels for dial-in to a Windows NT 3.5

RAS server. However, even if the RAS client is able negotiate the RAS

connection with two channels, the RAS server only uses one channel for a

callback (when the callback security feature is enabled).

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntras

Additional reference words: 3.50 prodnt


SNA Server: Windows NT Client Loses Session To Server

Article ID: Q126451

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

 - Microsoft SNA Server for Windows NT, version 2.1

----------------------------------------------------------------------

SYMPTOMS

========

When you close an SNA Server 5250 (or APPC) session on a Windows NT 3.5

computer, any other SNA applications with a connection to the server

lose their session. As a result:

 - If SNA Admin is also running on the same machine, and the 5250

   session is disconnected. SNA Admin may also lose its connection

   to SNA Server, causing an SNA Server Admin Error.

   NOTE: 5250 emulators also use the SNA Server APPC interface.

 - The Windows NT system event log includes the following error (for each

   time the user disconnected their 5250 session), if TCP/IP is being

   used:

      Event: 2012

      Source: Srv

      Description: The server has encountered a network error.

 - Within an internal SNA Server client trace, the named pipe session

   fails with rc=59 (An unexpected network error occurred).

 - Any other APPC applications with sessions against the same SNA Server

   receive the following error:

      primary return code = F003 = AP_COMM_SUBSYSTEM_ABENDED

   This error returned by SNA Server when its client-server LAN session

   is lost.

CAUSE

=====

If a Windows NT process has a pending write request on a named pipe and

then calls ExitProcess() before the write completes, all other applications

connected to the same server pipe fail with error 59 (unexpected pipe

close).

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntnetserv

Additional reference words: prodnt prodsna 2.10 3.50 rdr.sys 2012 sna f003


Can not Create NetBIOS Session Over TCP/IP

Article ID: Q126560

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you run NET VIEW or NET USE, the following error message appears:

   System error 1225 has occurred. The remote system refused the network

   connection.

A trace of network activity shows repeated pairs of the following messages:

   workstation->server:  SYN

   server->workstation:  ACK, RST

The following STOP message may also appear:

   STOP 0xc000000A

This problem occurs on servers with very heavy NetBIOS traffic over TCP/IP.

CAUSE

=====

When netbt receives a zero length message, it fails to update the number of

bytes left in the transport. As a result, when the connection is later

disconnected, it never receives disconnect indication from the transport,

leaving the connection unusable. After all connections are exhausted, new

connections are not accepted.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kberrmsg kbbug3.50 kbfix3.50.sp3

KBSubcategory: nttcp ntstop

Additional reference words: 3.50 prodnt trap blue screen


FDDI MAC Address Issue with Windows NT 3.5

Article ID: Q126652

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

-------------------------------------------------------------------------

SYMPTOMS

========

Unlike the Ethernet standard, FDDI and TokenRing are capable of using

non-canonical or canonical formatting for the MAC Address. If the MAC

address for a FDDI node is 800000000000 through FFFFFFFFFFFF, and TCP/IP is

being used as the transport protocol, you lose connectivity.

CAUSE

=====

Windows NT reads the MAC addresses in canonical format and does not

properly translate the most significant bit (MSB).

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntnetserv nttcp

Additional reference words: 3.50 prodnt token ring


NPMCA.SYS Causes STOP 0x0A in TCPIP.SYS

Article ID: Q126724

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

The following error message appears when you use TCP/IP:

   STOP 0x0A (Ox14,0x2,0x0,0xf1583318)

CAUSE

=====

NDIS set up a send request and handed the Network Peripherals FDDI network

interface card (NIC) driver the packet descriptor with a Callback

Completion routine. The NIC completed the send and called NDIS but returned

a NULL pointer to the descriptor (that ARP tries to free).

RESOLUTION

==========

To correct this problem, obtain an updated NPMCA.SYS FDDI NIC driver

from Network Peripherals Inc. at (408) 321-7300).

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kb3rdparty kbnetwork kbhw kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntdriver ntstop nttcp

Additional reference words: 3.50


STOP 0x24 Generated With NTFS

Article ID: Q126974

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

If you have large number of files in a single directory on an Windows NT

file system (NTFS) partition, the following error message appears:

   STOP: 0x00000024

CAUSE

=====

Running NTFS under heavy disk activity can create an uninitialize record

package if BitmapScb for the directory is invalid.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbenv kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntfilesys ntstop

Additional reference words: prodnt 3.50 VCN LCN trap 0x24


IBM Token Ring /A Adapter Fails To Start in Windows NT 3.5

Article ID: Q126978

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you start Windows NT version 3.5 using an IBM Token Ring /A network

adapter, it may fail and cause the following error message to appear:

   At least one service or driver failed during system startup.

   Use Event Viewer to examine the event log for details.

The following event is written to the system log of Event Viewer:

   Event: 5009

   Source: IBMTOK

   Type: Error

   Description: IBMTOKMC1: Does not support the configuration supplied.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

The IBM Token Ring network adapters discussed here are manufactured by IBM

Corporation, a vendor independent of Microsoft; we make no warranty,

implied or otherwise, regarding these products' performance or reliability.

KBCategory: kb3rdparty kbbug3.50 kbfix3.50.sp3

KBSubcategory: nthw ntdriver

Additional reference words: prodnt 3.50 nic mac


STOP 0x0A in STREAMS.SYS with DEC Pathworks Loaded

Article ID: Q127775

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you use the Windows NT version 3.5 DEC Pathworks drivers, the

following STOP message may appear:

   STOP: 0x0000000A

CAUSE

=====

STREAMS.SYS does not behave correctly when the transport takes longer to

complete a connect request than the redirector allows. In this case, the

redirector first cancels the connect IRP, then later issues a disconnect.

STREAMS.SYS erroneously accepts the disconnect and crashes.

The disconnect should be rejected since the cancel issued a disconnect to

the transport.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntprotocol

Additional reference words: 3.50 prodnt trap blue screen 0x0a crash


LAN Manager Clients Cannot See Windows NT Computers

Article ID: Q127789

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you run NET VIEW on a LAN Manager client, the list of Windows NT

workstations and servers in the domain is not available for several

minutes.

CAUSE

=====

This problem occurs due to the Windows NT broadcast design.

NOTE: To make Windows NT workstations and servers visible to LAN Manager

clients, you must configure the Windows NT computers to broadcast server

announcements to LAN Manager clients. To do this, run Control Panel, choose

Network, select Sever, choose Configure, the select "Make Browser Broadcast

to LAN Manager 2.x clients," and choose OK.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

MORE INFORMATION

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

Original Design

---------------

LAN Manager clients rely on server announcements that are broadcast over

second class mailslots. The LAN Manager clients pickup server announcements

and store them (for 1.5 times the announcement rate). If you run NET VIEW

and the stored server announcement is still valid, the server name and

server comments are displayed. If the next server announcement is not

received by the client within 1.5 times the announcement rate, the server

is dropped from the list. So if a client receives a server announcement at

one minute intervals, it is likely to drop the server from the list if it

does not receive another announcement in 1.5 minutes.

Here is a sample server announcement from USER1STA to LAN Manager clients:

   USER1STA *NETBIOS Multicast SMB C transact, File = \MAILSLOT\LANMAN

   NETBIOS: Datagram (0x08), USER1STA         -> USER1DOM       <00>

         -----

   NETBIOS: Destination Name = USER1DOM       <00>

       NETBIOS: SMB Name Type = Workstation (00)

       NETBIOS: Source Name = USER1STA

       NETBIOS: SMB Name Type = Server (20)

       NETBIOS: NetBIOS Data: Number of data bytes remaining = 115

   SMB: C transact, File = \MAILSLOT\LANMAN

      ------

   SMB: Command = C transact

      ------

   SMB: Mailslot class = Unreliable (broadcast)

           SMB: Byte count = 46

           SMB: Byte parameters

           SMB: Path name  = \MAILSLOT\LANMAN

           SMB: Transaction data

           SMB: Server announce opcode = Server announcement

           SMB: Service Flags Summary = 4097 (0x1001)

            SMB: .....................1 = Workstation service running

            SMB: ......................0. = Server service not available

           SMB: Major version = 3

           SMB: Minor version = 50

           SMB: Server announce rate = 720

           SMB: Computer name = USER1STA

           SMB: Server comment = User1's System;

NOTE: USER1STA sends a Multicast datagram to destination NetBIOS group name

USER1DOM<00>. All LAN Manager clients post a NetBIOS Receive on their own

domain, as well as other domains listed in their LANMAN.INI file, during

initialization.

The server announce rate is set is seconds. Therefore, the server announce

rate of 720 in the above example, it equates to 12 minutes. In Windows NT

3.1, the announce LAN Manager Server parameter in the registry could be

used to set the announcement interval. However, in Windows NT workstation

and Windows NT Server version 3.5, a new algorithm was developed. The

server announcements are made during the start of the server service, and

at the following approximate intervals:

   .5, 1, 1.5, 4, 8, 12, remain at 12 minutes].

For example:

   #  Time     Src         Description

   1  27.390   USER1STA    C transact, File = \MAILSLOT\LANMAN (30sec)

   2  50.303   USER1STA    C transact, File = \MAILSLOT\LANMAN (~20).

   3  79.151   USER1STA    C transact, File = \MAILSLOT\LANMAN (~30)

   4  348.700  USER1STA    C transact, File = \MAILSLOT\LANMAN (~260)

   5  861.290  USER1STA    C transact, File = \MAILSLOT\LANMAN (~520)

   6  1586.99  USER1STA    C transact, File = \MAILSLOT\LANMAN (~720)

   7  2312.10  USER1STA    C transact, File = \MAILSLOT\LANMAN (~720)

   8  3033.39  USER1STA    C transact, File = \MAILSLOT\LANMAN (~720)

   9  3758.56  USER1STA    C transact, File = \MAILSLOT\LANMAN (~720)

The announce parameter is ignored.

As a result, you may not see Windows NT workstation and server names when

you run NET VIEW on LAN Manager clients, right after you boot the computer.

The longest wait time, if you just miss a server announcement, would be 12

minutes. Once you receive the server announcement, it is valid for 18

minutes.

New Design

----------

The default initial announce frequency for LAN Manager clients is now four

minutes, and increases to once every 12 minutes.

The AnnDelta delta parameter, although adjustable, defaults to 3000

milliseconds. This parameter specifies the time by which the announcement

period can vary. This helps to prevent several servers from continuously

announcing simultaneously, thereby reducing network load peaks.

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntnetserv

Additional reference words: 3.50 browsing mail slots


Printing to WinNT Queue Attached to NetWare Queue Hangs NetWare

Article ID: Q127814

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you print to a Windows NT Server version 3.5 print queue that is

attached to a print queue on a NetWare server with a queue name that is

greater than 12 characters, the NetWare server stops responding (hangs).

The print queue is attached as shown:

   Windows NT Server (print queue)

          |

           --> NetWare Server (print queue)

                    |

                     --> NFS on NetWare Server

                                  |

                                   --> UNIX Server

                                           |

                                            --> Printer

CAUSE

=====

Windows NT does not truncate the name field in the client frame at 12

characters.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

NetWare is manufactured by Novell, Inc., a vendor independent of Microsoft;

we make no warranty, implied or otherwise, regarding this product's

performance or reliability.

KBCategory: kbprint kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntprint ntinterop

Additional reference words: prodnt 3.50


Problems Using Event Viewer from Windows for Workgroups

Article ID: Q127821

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

 - Microsoft Windows NT Server Tools

--------------------------------------------------------------------------

SYMPTOMS

========

When you use the Windows NT Server Tools version of Event Viewer to access

a backed up log file, located on a Windows NT 3.5 server, you may see the

following problems:

 - The server service, workstation service, and RPC service fail. Other

   services may also stop.

 - You cannot run Control Panel and choose Services.

 - The following message appears:

      The RPC service is unavailable.

 - The server can still be used, but all network services are stopped and

   cannot be restarted without shutting down and restarting Windows NT.

 - When you attempt to shutdown Windows NT, the computer stops

   responding (hangs).

CAUSE

=====

Two problems cause these symptoms:

- Event Viewer assumes that the user has administrator privileges when it

  tries to convert the local drive to a UNC path. If this fails, a null log

  UNC name is passed to the server.

- The server does not perform argument checking on the log UNC name.

WORKAROUND

==========

To work around this problem, run Event View from a computer running Windows

NT Workstation or Windows NT Server.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbtool kbnetwork kbbug1.00 kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntutil

Additional reference words: 3.50 prodnt compact disc cd-rom wfw wfwg log

name


Granularity Value Changes After Installing Service Pack 2

Article ID: Q127908

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

After you update Windows NT version 3.5 to Service Pack 2, the Granularity

value for Sizing Grid changes when you choose Desktop in Control Panel, log

off and log back on, and choose Desktop in Control Panel again. The

Granularity value in Desktop of Control Panel increases in increments of 8.

For example, if Granularity is set to 1, it changes to 8 the next time you

choose Desktop in Control Panel after you log off and log back on (and from

8 to 64 even though the maximum value for Granularity is 49).

CAUSE

=====

This problem only occurs if you choose Desktop in Control Panel after each

successive logon.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbenv kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntconfig

Additional reference words: prodnt 3.50


Seed Routing Not Working With C.O.P.S. LocalTalk NIC

Article ID: Q127909

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Server version 3.5

-------------------------------------------------------------------------

SYMPTOMS

========

When you run Services for the Macintosh on a computer running Windows NT

Server using an Ethernet or Token Ring network interface card (NIC) and a

C.O.P.S. LocalTalk NIC, Macintosh client computers can only view Windows NT

Servers that are using the same NIC as the default NIC for Services for

Macintosh.

For example, if you select the C.O.P.S. LocalTalk NIC as the default NIC

for Services for Macintosh, only Macintosh client computers using the

LocalTalk NIC are able to view the Windows NT Server. Enabling seed routing

has no effect.

CAUSE

=====

The LocalTalk Network Number is not sent out with the correct information

in the packet.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntmac

Additional reference words: prodnt 3.50 sfm local talk cops


Setting BDC to be WINS Proxy Agent May Cause Broadcast Storms

Article ID: Q127922

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

IP broadcast storms can occur when non-WINS clients attempt to log

on if Enable WINS Proxy Agent is selected in the Advanced configuration

dialog box on a Windows NT version 3.5 Backup Domain Controller (BDC).

CAUSE

=====

The WINS proxy code does not check to see if the datagram it receives is

from another WINS proxy agent. This allows the same datagrams to be

repeatedly forwarded.

This problem occurs only if the BDC is a WINS proxy agent.

WORKAROUND

==========

To work around this problem, configure another server to be the WINS proxy

agent.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntnetserv

Additional reference words: 3.50 internet naming service prodnt


Stop Msg: C0000218 "Unknown Hard Error" When Registry is Overrun

Article ID: Q128254

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When you add users and groups to an Windows NT version 3.5 computer using

User Manager you have the ability to overrun the registry with user and

group information. When you reboot your computer, the following stop screen

appears:

   Stop 0xc0000218 (0xe11a30e8, 0x00000000, 0x000000000, 0x00000000)

   Unknown Hard Error

CAUSE

=====

User accounts and group information are stored in a secure location in the

registry. By default, RSL (registry size limit) is 25% of the size of paged

pool. The registry charges registry quota for its memory allocations. This

is to prevent the registry from becoming too large for the available system

resources. If a piece of registry is freed up, it is deallocated from the

pool and the registry quota is returned. Although the space is still

allocated in the file, there is no memory allocated, so no quota is

charged.

If the registry becomes very fragmented, its file size may become much

larger than the charged registry quota, potentially causing the registry to

become larger than the system can accommodate at boot time. That is, the

registry file cannot fit in memory in the available paged pool.

RESOLUTION

==========

To address fragmentation, the Windows NT registry now continues to charge

quota for portions of the registry that have been deallocated from pool,

but are still allocated in the file. This prevents the size of the

registry's files from exceeding the allowable registry quota, ensuring the

file will fit in memory on the next reboot.

Additionally, a change was made that provides better coalescing of small

portions of free registry memory into larger pieces when very large

registry allocations are required.

With this change, instead of overrunning the registry with user and group

information, when the registry reaches it's maximum allocation the

following error message appears:

   Not enough server storage to process this command

For additional information, please see the following article(s) in the

Microsoft Knowledge Base:

   ARTICLE-ID: Q126401

   TITLE     : Err Msg: Not Enough Server Storage is Available to Process..

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbenv kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntregistry ntconfig

Additional reference words: prodnt 3.50

Comparison of Windows NT Network Protocols


IPX Subnet Clients Unable to Connect to Windows NT

Article ID: Q128335

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SYMPTOMS

========

When IPX clients from a subnet attempt to connect to a server, the

following error message appears:

   DOS error 53 - name not found

CAUSE

=====

This problem occurs if the connection request originates from a client

whose IPX four byte network number contains 06 in the second byte. The

server

responds with a name recognized to a FindName Query from any other network

excluding the range mentioned above.

When the NBIPX portion of the code receives the frame, it checks certain

frame properties. If the second byte in the NBIPX header is 06, it

assumes it is a session data frame. As a result, NameRecognize is not

processed.

The following is a sample FindName frame that does not get a response:

NOTE: TransmissionControl is set to 1 (indicating 1 hop). Second byte in

the NBIPX header contains 00 06. The network number in the IPX header

(x6112) is not the same in the NBIPX portion. This is a modified FindName

frame that was transmitted on the wire using Network Monitor.

USER1STA *BROADCAST NBIPX Find Name USER101        <00>

ETHERNET: 802.3 Length = 98

IPX: NetBIOS Packet - 6112.08002B314A12.455 -> 0.FFFFFFFFFFFF.455 - 1 Hops

    IPX: Checksum = 65535 (0xFFFF)

    IPX: IDP Length = 80 (0x50)

    IPX: Transport control = 1 (0x1)

    IPX: Packet type = WAN Broadcast

    IPX: Destination Address Summary 0.FFFFFFFFFFFF.455

        IPX: IPX Address = 00000000.FFFFFFFFFFFF

        IPX: Destination Net Number = 0 (0x0)

        IPX: Destination Socket Number = NetBIOS

    IPX: Source Address Summary 6112.08002B314A12.455

        IPX: IPX Address = 00006112.08002B314A12

        IPX: Source Net Number = 24850 (0x6112)

        IPX: Source Socket Number = NetBIOS

    IPX: Data: Number of data bytes remaining = 50 (0x0032)

NBIPX: Find Name USER101        <00>

    NBIPX: Routing Info

        NBIPX: Routing information = 393216 (0x60000)

        NBIPX: Routing information = 0 (0x0)

        NBIPX: Routing information = 0 (0x0)

        NBIPX: Routing information = 0 (0x0)

        NBIPX: Routing information = 0 (0x0)

        NBIPX: Routing information = 0 (0x0)

        NBIPX: Routing information = 0 (0x0)

        NBIPX: Routing information = 0 (0x0)

    NBIPX: Name type flag

        NBIPX: 0....... = Unique Name

        NBIPX: .0...... = Name not used

        NBIPX: .....0.. = Name not Registered

        NBIPX: ......0. = Name not Duplicated

        NBIPX: .......0 = Name not Deregistered

    NBIPX: Data stream type 2 = Find Name

    NBIPX: Name = USER101        <00>

    NBIPX: Data: Number of data bytes remaining = 1 (0x0001)

00000:  FF FF FF FF FF FF 08 00 2B 31 4A 12 00 54 E0 E0   ........+1J..T..

00010:  03 FF FF 00 50 01 14 00 00 00 00 FF FF FF FF FF   ....P...........

00020:  FF 04 55 00 00 61 12 08 00 2B 31 4A 12 04 55 00   ..U..a...+1J..U.

00030:  06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................

00040:  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................

00050:  01 4D 4F 48 41 4B 30 31 20 20 20 20 20 20 20 20   .USER101

00060:  00 00                                             ..

WORKAROUND

==========

To work around this problem, use an IPX network number that does not have

06 as the second byte in the network number.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntprotocol

Additional reference words: 3.50 nwlink nwnblink prodnt find name recognize


NT to LAN  Manager UAS Replication Problem after using PORTUAS

Article ID: Q128415

----------------------------------------------------------------------

The information in this article applies to:

  - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

When the user account database (UAS) is ported from a LAN Manager

server to a Windows NT 3.5 server (using PORTUAS) and later modified, UAS

replication problems may occur. The LAN Manager server's error log may

contain Error 3226, with the following two bytes in the data field:

   00 EA

These two bytes represent "ERROR_MORE_DATA." This error is the final return

code; the actual error is:

   0x57 (ERROR_INVALID_PARAMETER)

This error is not recorded in the LAN Manager server error log. The

replication process is halted and UAS replication is never successfully

completes.

CAUSE

=====

If a home directory exists for a user account that is being ported, then

PORTUAS sets a flag UF_HOMEDIR_REQUIRED FLAG (bit 3 in usri2_flags)

indicating home directory is required. If the user account is later

modified to not include a home directory, Windows NT does not reset this

bit.

When a home directory is specified for a user account that was created

using User Manager (or Net User ), UF_HOMEDIR_REQUIRED FLAG is not set.

Therefore, UAS replication works correctly.

RESOLUTION

==========

To correct this problem, clear the UF_HOMEDIR_REQUIRED FLAG when Windows NT

replicates to a LAN Manager Backup Domain controller.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbinterop kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntinterop ntnetserv prodlm2nt

Additional reference words: 3.50 NTS


Enumeration of Large NTFS Directory Takes a Long Time

Article ID: Q128447

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

-------------------------------------------------------------------------

SYMPTOMS

========

If several thousand files with long filenames exist in a shared directory

on an Windows NT file system (NTFS) partition, enumeration of the directory

takes a long time. If a network client performs the same task at the same

time, it may lose it's network connection to the shared directory.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbenv kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntfilesys

Additional reference words: prodnt 3.50 8.3 lan wfw wfwg file name names


RAS Event ID 20013: The User Connected to Port...

Article ID: Q128448

----------------------------------------------------------------------

The information in this article applies to:

- Microsoft Windows NT Workstation version 3.5

- Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

After you connect from a Remote Access Service (RAS) client to a RAS Server

in Windows NT version 3.5 and perform file transfer using the TCP/IP

protocol in heavy network traffic, the following event may appear in the

Event Viewer of the RAS Server:

   Event ID: 20013

   Source: Remote Access

   Type: Error

   Description: The user connected to port <port> has been disconnected

   due to a fatal network error on the local network.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntras nttcp

Additional reference words: prodnt 3.50 nbt


Memory Leak: MS-DOS-Based Apps Starting Non-MS-DOS-Based Apps

Article ID: Q128550

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

MS-DOS-based applications that start Windows-based, POSIX, or OS/2-based

applications under Windows NT may experience memory leaks.

CAUSE

=====

Two different memory leaks can occur. One memory leak occurs when the MS-

DOS-based application does not close a Process Object handle properly.

To observe the memory leak:

1. Run Performance Monitor.

2. From the Edit menu, choose Add to Chart.

3. From the Object list box, select Objects.

4. From the Counter list box, select Processes.

5. Choose Add and then choose Done.

A leakage of this resource will result in the gradual depletion of non-

paged pool (a vital Windows NT resource).

The other memory leak occurs when an MS-DOS-based application continuously

starts non-MS-DOS-based applications, creating a looping situation. This

results in the loss of Private Bytes associated with NTVDM.EXE running the

MS-DOS-based application.

To observe the memory leak:

1. Run Performance Monitor.

2. From the Edit menu, choose Add to Chart.

3. From the Object list box, select Process.

4. From the Instances list box, select NTVDM.

5. From the Counter list box, select Private Bytes.

6. Choose Add and then choose Done.

It may be difficult to log if there are multiple instances of NTVDM

running, as Performance Monitor will not let you distinguish between these

instances if they share the same executable name. (The Windows NT Resource

Kit describes methods to overcome this situation.) A leakage of this

resource results in the gradual consumption of Private Bytes for the

NTVDM.EXE process. Private bytes consumption is general backed by paging

file so a leak of Private Bytes will slowly consume the pagefile (a vital

Windows NT resource).

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbother kbbug3.50 kbfix3.50.sp3

KBSubcategory: nt16ap ntdosap ntos2ap ntposixap

Additional reference words: prodnt 3.50 handles batchfile page file


Periods Not Displayed in CD-ROM Disc Volume Label

Article ID: Q129054

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

If a CD-ROM disc has a period in the volume label, Windows NT 3.5 does

not show the period. This affects applications that query the volume

label to ensure the correct disc is in the CD-ROM drive. This only

affects down-level clients, not other Windows NT Servers or Workstations.

WORKAROUND

==========

To workaround this problem, share the CD-ROM from a Windows for Workgroups

version 3.11 computer.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbinterop kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntinterop

Additional reference words: prodnt 3.50 wfw wfwg cdrom


PCI Adapter Incorrectly Identified on Dual-bus Computers

Article ID: Q129111

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

-------------------------------------------------------------------------

SYMPTOMS

========

Some adapters on the second bus of a dual-bus PCI computer are not

correctly detected, causing the driver to fail to load.

CAUSE

=====

On systems with dual PCI buses, Windows NT 3.5 incorrectly reports that all

adapters on the second PCI bus (bus 1) are memory-mapped. An I/O-mapped

adapter that is installed on the second bus will be incorrectly identified

as memory-mapped. I/O-mapped adapters are correctly identified when

installed on PCI bus 0.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kb3rdparty kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntsetup ntdriver

Additional reference words: 3.50 prodnt


Systems Management Server Inventory Via RAS Causes STOP Screen

Article ID: Q129482

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Server version 3.5

 - Microsoft Systems Management Server version 1.0

----------------------------------------------------------------------

SYMPTOMS

========

When you start the Systems Management Server inventory management from a

remote computer over a Remote Access Service (RAS) connection, a STOP

message screen appears.

CAUSE

=====

The SMSLS.BAT runs INVWIN32.EXE for inventory collection. The asyncmac

driver fails to forward an I/O request packet (IRP) down the NDIS chain

correctly.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntstop ntras ntdriver

Additional reference words: prodnt prodsms 1.00 3.50 sms


Large Zeroing Operations Cause Systems To Appear Hung

Article ID: Q129600

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

-------------------------------------------------------------------------

SYMPTOMS

========

Large zeroing operations on Windows NT file system (NTFS) formatted drives

may cause Windows NT to appear to hung. The hang only affects the physical

drive on which the zeroing operation occurs. The length of the hang depend

on how much space has to be cleared and the speed of the system.

For example, if you have a 100 MB file, and an application writes one byte

at offset 200 MB. Windows NT initializes the disk space between 100 MB to

200 MB. This ensures that the space is actually available on the disk. In

addition, the space is erased so that old erased data is secure. The

zeroing operation occurs synchronously so that any attempt to access this

disk will be queued up until this action is complete.

NOTE: This information applies only to NTFS drives.

CAUSE

=====

The zeroing operations are being submitted synchronously.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbother kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntfilesys

Additional reference words: prodnt 3.50 wfw wfwg


Windows NT 3.5: STOP 0x0000000a in NETBT.SYS When Memory is Low

Article ID: Q130661

-------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

-------------------------------------------------------------------------

SYMPTOMS

========

When you run Windows NT 3.5 with TCP/IP installed on a network using the

Windows Internet Naming Service (WINS), a STOP 0x0000000a message appears.

CAUSE

=====

The Windows NT memory manager could not allocate a memory block of the

requested size and returned STATUS_INSUFFICIENT_RESOURCES to the calling

function. This occurs when your system runs low on available memory

(physical memory and page file memory). Instead of checking first whether

the pointer to the requested memory block is NULL, which it is in this

case, the code continues to use that pointer as if it was successfully

initialized. This causes the STOP 0x0000000a message.

RESOLUTION

==========

To work around this problem, install more RAM on your computer or make more

disk space available for the Windows NT page file.

To resolve this problem, upgrade to Windows NT version 3.51 or obtain

the fix mentioned below.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

This problem was corrected in Windows NT version 3.51.

DEBUGGING

=========

NT!_DbgBreakPoint

NT!_KeBugCheckEx+0x194

NT!_KiTrap0E+0x252

netbt!_QueryNameOnNet+0x6a

netbt!_RegOrQueryFromNet+0x7c

netbt!_DgramHndlrNotOs+0x63d

netbt!_TdiRcvDatagramHandler+0x44

tcpip!_UDPDeliver+0x138

tcpip!_UDPRcv+0x177

tcpip!_BCastRcv+0x5a

tcpip!_DeliverToUser+0x6a

tcpip!_IPRcv+0x22e

tcpip!_ARPRcv+0xe0

NDIS!_EthFilterDprIndicateReceive+0x111

ee16!_ee16ProcessReceiveInterrupts+0x222

ee16!_ee16HandleInterrupt+0x4a

NDIS!_NdisMDpc+0x71

NT!_KiDispatchInterrupt+0x45

hal!_HalBeginSystemInterrupt+0x106

NT!_MiAllocatePoolPages+0x18a

kd> !trap fe4396b0

eax=00000002 ebx=c000009a ecx=00000000 edx=00000000 esi=00000000

edi=ff69bd50

eip=fe57369a esp=fe439724 ebp=00000000 iopl=3      nv up ei ng nz na po nc

cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000

efl=00013286

ErrCode = 00000002

fe57369a 894120           mov     [ecx+0x20],eax

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp3 kbfix3.51

KBSubcategory: nttcp

Additional reference words: prodnt 3.50 3.51 crash trap blue screen


Frame Corruption in Retransmitted IPX Packet

Article ID: Q130901

------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

------------------------------------------------------------

SYMPTOMS

========

When you use the Windows NT IPX/SPX Compatible Transport protocol (NWLink),

frame corruption may occur. This results in a lost connection between a

client and a server. A network trace reveals that the IPX packet is corrupt

(which is why the client does not receive the data). This problem can occur

on both Ethernet and Token Ring networks.

The following conditions must exist for the problem to occur:

 - The Windows NT server is running NWLink IPX.

 - The client sends a request to Windows NT server and the server responds.

 - The original frame gets lost on the network.

A slow WAN may be more prone to encounter this problem because they often

drop frames. The problem only occurs during frame re-transmission.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntnetserv

Additional reference words: 3.50 prodnt


STOP Msg: 0x0000000A or 0X0000001E Dis/Reconnecting to WfWG Svr

Article ID: Q131339

------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

------------------------------------------------------------------

SYMPTOMS

========

From your Windows NT Workstation, when you disconnect and reconnect to two

network shares with the same password on a Windows for Workgroups 3.11

computer running the NetWatcher utility, the following STOP Message appears

(on your Windows NT Workstation client):

   STOP: 0x0000000A

When you do the same from your Windows NT Server, the following STOP

Message appears (on your Windows NT Server client):

  STOP: 0X0000001E

  KMODE_EXCEPTION_NOT_HANDLED

CAUSE

=====

The Windows NT network redirector, RDR.SYS, confuses the security entries

for the two connections. It tries to assign a security entry to the wrong

share and causes an access violation.

RESOLUTION

==========

Changes have been made to RDR.SYS that correct this problem.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

This problem was corrected in Windows NT version 3.51.

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp3 kbfix3.51

KBSubcategory: ntstop ntnetserv

Additional reference words: prodnt 3.50 redirection connect confuse cross


Unable to Change Printer Settings From Windows Applications

Article ID: Q131479

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT Workstation version 3.5

 - Microsoft Windows NT Server version 3.5

----------------------------------------------------------------------

SYMPTOMS

========

After you change postscript printer settings from default to another

setting from a Windows-based application, Windows NT 3.5 Print Manager

keeps the default settings.

STATUS

======

Microsoft has confirmed this to be a problem in Windows NT version 3.5.

This problem has been corrected in the latest U.S. Service Pack for Windows

NT version 3.5. For information on obtaining the Service Pack, query on the

following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

KBCategory: kbprint kbbug3.50 kbfix3.50.sp3

KBSubcategory: ntprint

Additional reference words: prodnt 3.50