---------------------------------------------------------------------------
              Microsoft Windows NT 3.51 Workstation and Server
                            U.S. Service Pack 2
---------------------------------------------------------------------------


Contents
--------
1.0  Introduction
2.0  Installation Instructions for the Windows NT 3.51 U.S. Service Pack 2
2.1  User Notes
2.2  List of Bugs Fixed in Windows NT 3.51 U.S. Service Pack 2

1.0  Introduction
-----------------
This release of Microsoft(R) Windows NT(TM) 3.51 U.S. Service Pack 2 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, ALPHA, or PPC directory (depending upon whether
    you have an Intel(TM), MIPS(R), ALPHA AXP(TM) or PowerPC(R) 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
---------------
*** New ROUTE.EXE Command Line Argument

A new command line argument for ROUTE.EXE has been added in Service Pack 2. 
The new parameter is METRIC, and is described below:

ROUTE [-f] [command [destination] [MASK netmask] [gateway] [METRIC metric]]

METRIC
   The metric option is used to associate a cost/hop count for the 
   destination specified by the route entry. Generally this specifies the 
   distance in number of hops from the destination. If not specified, the 
   metric is set to 1 by default.


*** 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 2, 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 2 .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).


*** Verifying the proper Firmware for Powerized ES and MX PowerPC systems

To install Service Pack #2 on your Powerized ES or MX PowerPC system, you
should first verify your Firmware is up-to-date.  Your Firmware should
have a date of September 15, 1995.  You may use the fw-title command in
the Firmware to verify this.  If you have an earlier ROM date, contact
your hardware manufacturer to get the latest release of the Firmware.


2.2  List of Bugs Fixed in Windows NT 3.51 U.S. Service Pack 2
-------------------------------------------------------------
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.

Service Pack 1
--------------
Q128453: Windows NT 3.51 Hangs (Memory Access Violation) Running Exchange
Q128454: Windows NT 3.51 Hangs with Office 95 (Word) Help File Wizard
Q130093: Err Msg: Incorrect Response from the Network
Q130292: Windows NT Win16 Subsystem Crashes Printing from Quicken 4.0
Q130677: TCP/IP Generates Frames with Loopback Address as Source Address
Q131343:  "Invalid Page Fault" Running Office 95 Help Wizard
Q131427: Windows NT 3.51 TCP/IP System Network Interface Hang
Q131683: Help File Opens Very Slowly with Office 95 Applications
Q131779: Help Fails for VB Modules in Excel
Q131865: SMC Elite Ultra NIC Causes UNIX Computers to Disconnect TCP/IP
Q132470: STOP Msg: 0x0000000A or 0x0000001E When Using PING
Q132858: PowerStack with Cirrus Video Adapter Hangs During Startup
Q132198: Middle Mouse Button Does Not Work Under Windows NT 3.51
Q132466: Problems Printing From DCA IRMA Workstation for NT 1.1

Service Pack 2
--------------
Q112665: UPDATE.EXE Starts Setup Help If Space Exists in Directory Path
Q128567: Landscape Orientation Reversed With Postscript Driver
Q129670: GSNW Not Releasing Session to NetWare Server
Q129724: Macintosh Client Has Slow Access to Windows NT 3.5x SFM Volume
Q130226: Banner Always Printed When Using GSNW Print Gateway
Q130783: STOP Msg: 0x0000003F NO_MORE_SYSTEMS_PTES Repetitive I/O on MIPS
Q130932: Desktop Remains Active At Logoff
Q130979: User Environment Variables Set Before Default Home Directory
Q131073: Datagram Sends Fail if Route is Not in IPX Cache
Q131241: FTPSVC Orphans Connections, Uses Up Virtual Memory
Q131428: DHCPADMN Reports Error 14 After You Select Local Machine
Q131689: Postscript Jobs Do Not Print Correctly Over SFM and AppleTalk
Q132085: Applications Hang When Opening Files when CSNW is Installed
Q132394: Streaming Mode NPMCA.SYS NIC Sleeps on Transmit.
Q132511: Windows NT 3.51 Hangs on Shutdown With Some S3 Based Video Cards
Q132722: Server Instability After Reboot Caused by NDIS Driver Problem
Q132896: FTP Client Scripts Terminate Without Completing
Q132903: Err Msg Using NetBIOS over TCP/IP (NETBT.SYS): STOP 0x0000000A
Q133112: NetWkstaSetUid2 API Returns Access Denied
Q133128: Printing From Windows NT 3.51 to an HP4 at 600 DPI is Slow
Q133252: Windows NT 3.51 GSNW Help Reports The File Is Corrupted
Q133280: FTPSVC: Delay Receiving FTP Directory Annotation and Prompt
Q133303: WINFILE.EXE Application Error When Associating a Searched File
Q133306: Maximum Disk Space of 1.99 GB Displayed for NetWare Volume
Q133384: Event ID 2019: Nonpaged Memory Pool Empty
Q133410: The Breakpoint "{,<filename>,} .<line>" Cannot Be Set
Q133488: LPR Printing Fails After Setting Up Security
Q133701: Forward Slash May Be Ignored As A Path Delimiter In 3.51
Q133757: Performance Monitor SQLServer-Log Object Corrupted
Q134250: No Compaq Netflex Drivers in Windows NT 3.51 for RISC Platforms
Q134285: STOP Msg: 0x0000007B or "0x4,0,0,0 Error" in WinNT 3.51 Setup
Q134286: Windows NT 3.51 LsarLookupSids errors from Big Endian Servers
Q134386: Computers Using QVision Display Driver Lock Up
Q134427: Dr. Watson Access Violation Occurs Sending Mail Attachments
Q134701: Uninitialized Pointers in DHCPSSVC.DLL Cause Access Violation
Q134765: Unknown Software Exception When Application Calls OpenGL
Q134959: Cannot copy Icons From a Common Group to a Personal Group
Q134968: NetWare Connections Remain Connected After You Log
Q134969: Faxing from 16-bit Program Using Separate Memory Space Fails
Q134985: Browsing & Other Traffic Incur High Costs over ISDN Routers
Q134988: Access Violation in glsbCreateAndDuplicateSection API on PowerPC
Q135065: Windows NT 3.51 Hangs on Shutdown
Q135275: Windows NT Backup : Incorrect Date in "Tape Name" Text
Q135277: WINS Records of Multi-homed Computers Do Not Replicate
Q135291: Print Manager: Owner Appears as System Printing from Macintosh
Q135308: Disk Administrator Corrupts Partitions
Q135471: Cannot Reconnect to OS/2 Name Space Resources on NetWare Server
Q135548: PIF Editor Reserve Shortcut Keys Settings May Be Ineffective
Q135553: IOCTL_NDIS_QUERY_ALL_STATS Causes STOP Msg in Windows NT 3.51
Q135621: NetWare Transaction Tracking System (TTS) Not Detected
Q135667: STOP 1E When Using File Manager and Services for Macintosh (SFM)
Q135692: "List Name From" List Box Shows Only 20 Trusted Domains
Q135724: Deleted Disk Space Not Released on Converted NTFS Volume
Q135774: Performance Monitor Counters Produce Unlikely Results
Q135777: Unable to Connect Using Cabletron EISA F70XX FDDI NIC
Q135856: RIP Table Does Not Update When New RIPX Response Is Received
Q136023: Batch Files Stop Executing with Windows NT version 3.51
Q136024: Tape Hardware Data Compression Disabled After Running NTBackup
Q136334: Access Violation in LSASS.EXE During User Password Change
Q136336: Windows NT Fails Because of an Access Violation in WINLOGON
Q136375: NTFS directory corruption with more than 100,000 files
Q136402: IniFileMapping for 16-Bit Windows Apps Fail in Windows NT 3.51
Q136472: NE3200 NIC Driver Can Lose Locally Administered Address
Q136627: Layered Drivers Never See WINSOCK IRPs for the TCP/IP Device
Q136780: WinFax Pro Software Causes 16-bit Applications To Hang
Q136782: Unable To Connect To AT&T Advanced Server For UNIX Printer Share
