-----------------------------------------------------------------------  
             Microsoft Windows NT 4.0 Workstation and Server
                            Service Pack 2
-----------------------------------------------------------------------

Contents
--------
1.0  Introduction
2.0  Installation Instructions for the Windows NT 4.0 Service 
     Pack 2
2.1  Service Pack Uninstall
3.0  User Notes
	3.1 Emergency Repair Disk
	3.2 Adding New Components to the System
	3.3 Installing Symbol Files from the compact disc
	3.4 Remote Access Service PPP CHAP MD5 authenticator support
	3.5 Microsoft DHCP Server                      
4.0  List of Bugs Fixed in Windows NT 4.0 Service Pack 2
5.0  How to obtain the North American version of this service pack (128 bit version)

1.0  Introduction
-----------------
This release of Microsoft(R) Windows NT(TM) 4.0 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 Service Pack
-------------------------------------------------------------------
Before Installing the Service Pack

Please close active debugging sessions before installing this Service 
Pack, otherwise the update program will be unable to replace system files 
in use.  If a file is in use, a dialog box will allow you to choose to 
abort the installation or skip the file copy.  We recommend you choose to 
abort and run the update program selecting the uninstall option.  Close 
active sessions on the system and rerun update.exe to install the Service 
Pack.  

Installing the Service Pack from a compact disc:
1.  Insert the Service Pack compact disc into the CD-ROM drive.
2.  At the Windows NT Command Prompt, change to the drive letter 
    associated with the CD-ROM drive.  Change directory to i386, 
    ALPHA, or PPC (depending upon whether you have an Intel(TM), 
    ALPHA(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 the drive letter to that network drive.  Change directory to i386, 
    ALPHA, or PPC directory (depending upon whether you have an Intel(TM), 
    ALPHA(TM) or PowerPC(R) CPU), and then type UPDATE.
3.  Follow the instructions given on the screen.

2.1  Service Pack Uninstall
---------------------------
This Service Pack contains an uninstall feature that can be used to remove
the Service Pack from your system.  It will restore your system to its previous
state; for example, if you install Service Pack 2 on top of Service Pack 1,
when you uninstall Service Pack 2, you will have Service Pack 1 left on your
system.

To enable the uninstall option, you must create an uninstall directory when
running UPDATE.EXE the first time.  To do this, check the "Yes, I want to create 
an Uninstall directory" button.  A subdirectory in your Windows NT directory will
be created and this requires that you have at least 60M of free space on the 
drive you have Windows NT installed on.

To uninstall the Service Pack, run UPDATE.EXE and check the "Uninstall a previously 
installed Service Pack" button.  After your system has rebooted, UPDATE will have 
replaced the files updated by the Service Pack with the files from the previous 
installation, and will have returned your registry settings to what they were before 
the Service Pack was installed.

If you install any applications that require Service Pack 2, or have bug fixes
contained in Service Pack 2, performing an uninstall could adversely affect 
those applications.

Also, it is recommended that you run the Emergency Repair Disk before updating 
your system with a Service Pack.


3.0  User Notes
---------------
3.1 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 reapply 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.


3.2 Adding New Components to the System

If you change or add new software or hardware components to your 
system after you have applied the Service Pack, you will need to 
reapply the Service Pack.  This is because the files taken from the
original Windows NT disk set may not be the same as the files on the 
Service Pack disk set.  You cannot install new components 
directly from the Service Pack media (such as a new keyboard or printer 
driver).  You must install new components from the original product media.


3.3 Installing Symbol Files from the compact disc

Each program file in Windows NT has a corresponding symbol file that is used to 
find the cause of kernel STOP errors. 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).

For more information about debugging on Windows NT, see chapter 39, 'Windows NT 
Debugger," in the Microsoft Windows NT Workstation Resource Kit.


3.4 Remote Access Service PPP CHAP MD5 authenticator support

SP2 provides limited PPP MD5-CHAP authenticator support to the Remote Access 
Server that may be useful for small user-count environments using 
non-Microsoft PPP dial-in clients. The support is local to a given RAS 
server.  The MD5 account information is stored in the RAS server's 
registry and is not integrated or synchronized with the User Manager 
account database.  Integrated support will appear in a later release, 
at which time this limited support may be deprecated.

The local MD5-CHAP authenticator is enabled by creating the MD5 key below 
and adding "account" subkeys of the form [<domain>:]<user>, with subvalue 
"Pw" containing the account password.  The ":" notation is used instead of 
"\" due to the syntax rules of registry keys.  The 'domain:' is optional 
and typically omitted.  MD5-CHAP will not be negotiated (old behavior) when 
the MD5 key does not exist (default).

HKLM\SYSTEM\CurrentControlSet\Services\RasMan\PPP\CHAP\MD5
	[<domain>:]<user>
		(REG_SZ)Pw


3.5  Microsoft DHCP Server

This version of the Microsoft DHCP Server modifies the format of the dhcp 
database.  You should back up the contents of your %windir%\system32\dhcp 
directory prior to upgrading.

The address conflict detection feature can limit the throughput of Microsoft 
DHCP Server.  For improved performance, reduce the number of ping retries in 
the Server Properties dialog.  This feature is disabled by default.

Address conflicts are indicated by replacing the machine name with 
"BAD_ADDRESS".  If a Unique Identifier is specified for the address in the 
Client Properties dialog, then the address was declined by the client.  If 
the Unique Identifier is not specified then the address conflict was detected 
by the DHCP Server.

Microsoft DHCP server can be configured to set a client's default gateway 
equal to its IP address.  This causes the client to arp for all IP addresses 
on the local subnet, and is useful for routerless networks.  To enable this 
feature for all clients in a scope, add the following value to the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DHCPServer\Subnets\a.b.c.d\SwitchedNetworkFlag=1 (REG_DWORD)

This version of Microsoft DHCP Server supports BOOTP clients.  BOOTP addresses 
currently must be reserved in advance by creating an IP address reservation.  
Future versions of Microsoft DHCP Server will be capable of leasing dynamic 
addresses to BOOTP clients.

BOOTP clients that do not specify the parameter request list option ( 55 ) can 
still retrieve the following options from this release of Microsoft DHCP Server:

1	Subnet Mask
3	Router
5	Name Server
12	Host Name
15	Domain Name
44	NetBIOS over TCP/IP Name Server
45	NetBIOS over TCP/IP Datagram Distribution Server
46	NetBIOS over TCP/IP Node Type
47	NetBIOS over TCP/IP Scope
48	X Window System Font Server
49	X Window System Display Manager
69	SMTP Server
70	POP3 Server
9	LPR Server
17	Root Path
42	NTP Servers
4	Time Server

In order to obtain other options the client must specify option 55 in the 
BOOTP request.  DHCP Server will return the options in the order listed 
above.  DHCP Server will return as many options as will fit in in response 
packet.

The activity log feature creates a text log file of all DHCP Server activity.  
The file is located at %windir%\system32\dhcp\dhcpsrv.log.  When the activity 
log feature is enabled this file will be kept open by DHCP Server while the 
Server is running.  To delete the activity log file you must first stop DHCP 
Server:

NET STOP DHCPSERVER

If available disk space becomes low the activity log will pause until sufficient
disk space becomes available to continue.

You must also stop and restart the DHCP Service after enabling or disabling
Logging, Superscope, or DHCP Decline support.


4.0  List of Bugs Fixed in Windows NT 4.0 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 2
--------------
 Q78303: Intermittent File Corruption Problem
Q142653: STOP Message Occurs Calling GetThreadContext/SetThreadContext
Q142654: Winsock Memory Access Violation in Ws2help.dll Or Msafd.dll
Q142655: Stop Message Appears After Deleting ProductOption Registry Key
Q142656: Internet Explorer 3.0 on RISC Computer Cannot Connect to Host
Q142657: Data Corruption on Windows NT 4.0
Q142658: Internet Information Server Runs Out of Memory
Q142659: Internet Explorer 2.0 Fails To Check the Country Code/Language
Q149903: File Manager Performs a Move Instead of a Copy
Q156832: STOP Message when IBM Warp Client Connects to Windows NT 4.0
Q102477: Draw Can't Leave Data in Clipboard After Closing Application    
Q102710: MFX Draw: 16-Bit Device Drivers Incompatible with Windows NT    
Q106503: FIX: SQL Server FixList for Version 4.20aK11                    
Q107422: Windows NT Resource Kit Vol. 1 - 3.5 Inch Disk Contents         
Q108144: FIX: SQL Server FixList for Version 4.20b                       
Q136032: Systems Management Server Sender Packet Size Computation        
Q140955: XCLN: Error When Opening Attachment in Client for Windows 3.x   
Q142625: NETBIOS Defaults To 16 Sessions on Windows NT                   
Q142634: Multiple Processes Are Able to Open the Same Winsock Port       
Q142641: Internet Server Unavailable Because of Malicious SYN Attacks    
Q142648: STOP 0x00000024 in Ntfs.sys                                     
Q142661: Cacls.exe May Report Errors when Handling Extended Characters   
Q142671: Backup Fails on Certain Directories Due to Lack of Permissions  
Q142675: CSNW Sends Packets Greater Than Negotiated Maximum Packet Size  
Q142687: Windows NT 4.0 Not Able to Read Some Compact Discs              
Q151989: Novell 32-bit Client for Win95/WinNT Doesn't See FPNW Volume    
Q152273: DHCP Server May Give Out Duplicate IP Addresses                 
Q152346: Some DEC TLZ06 4MM DAT Tape Drives Not Recognized by Windows NT 
Q153665: SPX Data Stream Type Header May Reset Unexpectedly              
Q154784: Windows NT Operating System SNMP OID Incorrect                  
Q155117: Shutdown And Power Off Does Not Appear on Shut Down Menu        
Q155883: NT 4.0 Breaks SNA Server 2.x Server Communication Over IP       
Q156091: Access Violation with Long NDS Context in CSNW/GSNW             
Q156095: Replace Command with Space Character in the Path Does Not Work  
Q156276: Cmd.exe Does Not Support UNC Names as the Current Directory     
Q156324: Device Failure Message with Microchannel Network Adapter        
Q156520: Logon Validation Fails Using Domain Name Server (DNS)           
Q156524: HP PaintJet XL 300 Does Not Print Colors, Only Black            
Q156608: Err Msg: Account Unknown--Account Deleted                      
Q156735: WOW Applications Stack Fault When Launched by a Service         
Q156750: AddGroupNameResponse Frame from WinNT May Cause WFWG to Hang    
Q156884: Problems Saving Event Viewer Log from Windows NT 4.0 to 3.51    
Q156931: STOP 0x0000001E in Nwrdr.sys                                    
Q156958: Serial Service Won't Stop with Serial Printer Installed         
Q156989: Multiple Processes Are Able to Open the Same Winsock Port       
Q157279: Nwrdr.sys Fails Reading File with Execute Only Attribute        
Q157289: Memory Leak Using RegConnectRegistry API                        
Q157621: Personal Groups Not Visible If %Systemroot% Is Read-Only        
Q157673: Policy Not Updated on Workstation                               
Q157979: NT/RDR: "Access Denied" with Windows NT 4.0 Ntbackup            
Q158142: WM_DDE_EXECUTE API Causes a Memory Leak in the WOW Subsystem    
Q159075: Compression is not supported on Quantum 4000DLT                 
Q158994: NT 4.0 Fails to Replicate to Backup Domain Controllers          
Q158387: RAS Server Cannot Use DHCP to Assign Addresses w/ PPTP Filtering
Q158587: 16-Bit Named Pipe File Open Leads to WOW Access Violation       
Q158682: Shortcuts Embed Admin$ in .lnk File                             
Q158706: Shortcuts Embed Admin$ In .LNK File                             
Q158707: DDE Destroy Window Code may Stop 0x0000001e in Windows NT 4.0   
Q108261: Windows NT Hangs on Shutdown with Certain PCMCIA Devices        
Q158981: IBM Thinkpads 760ED and 760ELD May Hang During Shutdown         
Q159066: A Client Crash May Prevent an NTFS Volume Dismount              
Q159071: NTFS Does Not Prevent a File Deletion During Rename             
Q159075: Compression is not supported on Quantum 4000DLT                 
Q158796: MAC Clients Connected to an NT Server May Intermittently Appear 
Q149817: STOP 0x0000000A and STOP 0x0000001E in Isotp.sys                
Q141375: Winstone 97 May Fail on Windows NT 4.0                          
Q141708: RAS Client IP Addresses Not Returned to Static Address Pool     
Q142686: First Line of Print Job Lost When Printing Using Lpdsvc         
Q142847: Bugcheck 0x1e Caused by Isotp.sys Driver                        
Q142872: Length of PDC Name May Affect Performance on a Domain           
Q157494: PPC 4.0 Cirrus Driver Fails to Redraw & Fill Objects Correctly  
Q148602: Running SNA Server 2.11 on the Windows NT 4.0                   
Q156746: Print Jobs Are Deleted When Printer Is Resumed After Restart    
Q150815: Windows NT May Fail to Boot on Toshiba Portable Computers       
Q152455: File Manager Can Only See 32 Volumes of NetWare/FPNW            
Q152474: Window Socket Application Failure with Connection Reset Event   
Q154556: Delegation Requires a Stop and Restart of the DNS Server Service
Q156578: Cannot Cancel Print Job on Windows NT 3.51 Shared Printer       
Q159107: Access Violaion in Addatom Inside KERNEL32.DLL                  
Q142903: Windows NT Ndis.sys and Netflx3.sys Performance Improvement     
Q160583: Windows NT 4.0 With More Than 4 Processors May Stall and Reboot 
Q159971: SetTimer() API causes Memory leak in the WOW subsystem          
Q159972: WinNT 4.0 May not Return a Valid Response for SMB Search Command
Q160015: 2D Vector Performance on WinNT 4.0 Slower Than on 3.51          
Q160055: Warning Event ID 4010 Generated on Windows NT LPD Server        
Q160189: CSNW can't see more than 32 volumes per server                  
Q159095: STOP 0x0000001E in Win32k.sys When Exiting Applications         
Q160328: Internet Explorer 3.0 causes NT 4.0 to Blue Screen              
Q159449: DNS Server Glue data gets deleted                               
Q160601: Bad Parameters Sent to WIN32K.SYS May Blue Screen Windows NT    
Q160603: No Output from DBMON Using OutputDebugString While Debugging    
Q160604: Access violation in security!SspQueryContextAttributesW         
Q160606: Performance enhancements for SQL Server under Windows NT        
Q160610: READ_REGISTER_ULONG Doesn't Preserve ULONG Semantics on Alpha   
Q160653: NTFS Fails Assertion Under High Stress During Transfer          
Q160190: RasSetEntryProperties does not save a full path script name     
Q159205: HOTFIX: SFM file Type and Creator properties invalid            
Q160657: 16 Bit Version of VB4 May Hang Windows NT 4.0                   
Q159108: SMP Full Duplex Adapter Configuration May Cause Blue Screen     
Q159109: ExitWindowsEx Does Not Work With NEC Power Switch Service       
Q159110: CDFS Does Not Complete IRPs Correctly                           
Q159111: Multiprocessor Machine Hangs Under Stress Using HALSP.DLL       
Q159129: OpenGL Access Violates with Invalid OpenGL Context              
Q159910: Memory Corruption on a Windows NT Alpha platform                
Q159204: HOTFIX: IoCompletionPort causes blue screen crash               
Q159594: Missing EE FontSubstitutes in Registry                          
Q159206: HOTFIX: Reactivation of paused print queues deletes print jobs  
Q159311: NT4.0 RAS not releasing static IP Addresses                     
Q159315: NT 4.0 RAS Server does not release static IP addresses          
Q159347: Using NetBEUI for RAS Connector on Windows NT 4.0               
Q159447: HOTFIX: Applications testing for directory existence fail       
Q159098: NT 4.0 resource Kit utility "Remote Console" client fails       
Q159203: HOTFIX: Unattended install prompts for new IP if zero in address

For the latest information see:
Q150734  	List of Fixed Bugs in Windows NT Version 4.0

5.0  How to obtain the North American version of this Service Pack (128 bit version)
------------------------------------------------------------------------------
The North American (128-bit) version of Service Pack 2 is intended for 
distribution only in the United States and Canada.  Export of the North American
version of this service pack from the United States is regulated by the 
International Traffic in Arms Regulations (ITAR, 22 CFR 120-130) of the 
U.S. State Department, Office of Defense Trade Controls.  A State Department 
license is required to export the North American version of Service Pack 2 outside 
the United States or Canada.   

Microsoft will distribute the North American (128-bit) version of Service Pack 2
to U.S. or Canadian companies or persons for end-use in the U.S. or Canada only.  

Ordering Information and Availability:
Customers in the 50 United States and Canada can order the North American (128-bit) 
version of Service Pack 2 effective 12/15/96 for US $14.95 (CDN $20.95) plus 
customer service and handling charges of US $5 (CDN $7.50). Customers can order the 
product by phone or mail. 

By Phone or Fax: Call (800) 370-8758 or Fax to (716) 873-0906 US, (905) 374-3855 
Canada. The 800 number is for customers calling in the U.S. and Canada. 

By mail in the 50 United States:
Microsoft Service Pack 2
PO Box 810
Buffalo, NY 14207-0810 

By mail in Canada:
Microsoft Service Pack 2
PO Box 643
Fort Erie, ON 
L2A 6M1 Canada 

Be sure to request Part Number 236-00711. The product will be delivered within four weeks.
