Windows NT 4.0 build 1381.4 (RC 1.52)

From BetaWiki
Jump to navigation Jump to search

4.0.1381.4 (RC 1.52)
Build of Windows NT 4.0
4.0.1381.4 (RC 1.52)
OS family
Architecturex86, Alpha
Compiled1997-02-20
Timebomb
Works in
About
1381.4 pre-release winver.png
SKUs
Server
Workstation

Windows NT 4.0 build 1381.4 (RC 1.52) is a Service Pack 3 beta build of Windows NT 4.0. The installer is named UPDATE.EXE, located in the i386 folder of the CD.

Setup[edit | edit source]

Unlike most Windows NT 4.0 Service Pack updates that are usually available in only executable forms, the installer for this build - as mentioned above - is located in the i386 folder of the CD. Not only that there are files for Service Pack 3, but there are more files included, including a driver pack and a HP Jetadmin installer.

Documentation[edit | edit source]

Inside the CD, there is also a text document called README.TXT. It contains information about this pre-release version of Service Pack 3 for Windows NT 4.0, such as the phasing out of PowerPC support and installation instructions.

The README's contents:

-----------------------------------------------------------------------  
             Microsoft Windows NT 4.0 Workstation 
                       and Windows NT 4.0 Server
                            Service Pack 3 Beta
-----------------------------------------------------------------------

Contents
--------
1.0  Introduction
1.1  What's New in Service Pack 3 Beta
1.2  Support for PowerPC platform
2.0  Installation Instructions for the Windows NT 4.0 Service Pack 3 Beta
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 3 Beta
5.0  Notes for Users of the 128-bit North American Version of Windows NT 4.0

1.0  Introduction
-----------------
This release of Microsoft Windows NT 4.0 Service Pack 3 Beta 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, and any new fixes made to the system.

1.1  What's New in Service Pack 3
---------------------------------
RPC Transport

This service pack includes new versions of the remote procedure call (RPC) run-time dynamic-link library (DLL), the RPC subsystem service (Rpcss.exe), the Microsoft Interface Definition Language (MIDL) compiler (Midl.exe), and several new RPC header files. These changes provide enhanced support for RPC message queuing, which is a feature of the upcoming Microsoft Message Queue Server (MSMQ). In order to use message-queuing in an RPC client/server application on Windows NT 4.0 you must have Service Pack 3 Beta installed on both the client machine and the server machine. 

If you are developing RPC applications that support MSMQ, you need the new RPC run-time DLL, the new RPC subsystem service, the new header files, and the new MIDL compiler. Also, RPC applications must support message queuing in order to use the following new features:

The MIDL [message] attribute.

The ncadg_mq protocol sequence.

The RPC_C_MQ_* endpoint flags in the RPC_POLICY data structure.

The RpcBindingInqOption and RpcBindingSetOption functions.

For more information on using message queuing in your RPC applications, see RPC Message Queuing in the Windows NT 4.0 Help or refer to the documentation in the upcoming MSMQ software development kit (SDK).

CAPI 2.0

The Microsoft Cryptography application programming interface (CAPI) provides developers with core cryptographic and certificate functions. CAPI 1.0 supports public-key and symmetric-key operations, such as key generation, key management, key exchange, encryption, decryption, hashing, digital signatures, and verification of signatures. CAPI 2.0 (the upgrade contained in this service pack) includes this core cryptographic functionality as well as certificate-based functionality, which is required for developers who want to use certificates with these public-key operations and perform the necessary encapsulations and encoding to apply certificates within their applications. 

CAPI 2.0 uses a service-provider model in which cryptography is provided by Cryptographic Service Providers (CSPs). This model allows developers to easily adapt their applications to evolving cryptographic technologies and government export policies. One CSP is provided with this service pack (the Microsoft RSA Base Provider), which gives users and developers access to exportable cryptography. 

CAPI 2.0 supports existing standards, such as X.509 v.3 certificate formats, ASN.1 encoding, and both PKCS #7 and  #10 for encapsulation. This allows applications using CAPI to interoperate with other certificate-based systems that adhere to these standards.

The release version of CAPI 2.0 includes several updates to the developers release version of 9/96, including both parameter changes and naming changes.  These changes are reflected in the Crypt32.dll and Wincrypt.h files. Please consult the CAPI 2.0 documentation for details.

Microsoft NetMeeting 2.0 Beta 3 

Microsoft NetMeeting 2.0 enables real-time communications and collaboration over the Internet or a corporate intranet, providing standards-based audio, video, and multipoint data conferencing support. From a Windows 95 or Windows NT 4.0 desktop, users can communicate over a network with real-time voice and video technology. They can share data and information through true application sharing, electronic whiteboard, text-based chat, and file transfer features. 

NetMeeting 2.0 Beta 3 is the first version of NetMeeting for Windows NT to fully support application sharing. This functionality requires Windows NT 4.0 Service Pack 3 Beta. It is important that you install the Service Pack before installing NetMeeting 2.0 Beta 3. If you use NetMeeting 2.0 Beta 3 on a computer that does not have Service Pack 3 beta installed, you will be able to view and control applications shared by other NetMeeting users, but you will not be able to share applications from your computer. NetMeeting 2.0 Beta 3 is identical to NetMeeting 2.0 Beta 2 in all areas other than application sharing. For more information on NetMeeting 2.0, please refer to Netmeet.txt, which is located in the NetMeeting directory on the enclosed compact disc.

This product will not be included with the final release version of Service Pack 3 for Windows NT 4.0. It is included here to facilitate beta testing. When Net Meeting 2.0 is released, it will be available at http://www.microsoft.com/netmeeting/. 


DirectX 3.0

Service Pack 3 Beta provides support for DirectX 3.0 with the exception of Direct 3D hardware acceleration. Direct 3D software emulation is supported. 

ODBC 3.0

This service pack includes the latest version of Microsoft's Open Database Connectivity (ODBC) API. ODBC 3.0 provides an updated ODBC Control Panel and ODBC Administrator interface that uses tabbed controls and provides more information about the ODBC components installed and in use on your system. It also introduces the concept of a file data source that can be shared or placed on a central server and used by any user who has the appropriate drivers installed. This new version of ODBC is fully aligned with both the American National Standards Institute (ANSI) and the International Standards Organization (ISO). It is also backwards compatible with previous versions of the ODBC API. For more information on ODBC 3.0, see ODBC in the online Help for Windows NT 4.0 Server or refer to the documentation included with the ODBC 3.0 SDK.

Fortezza Support

Service Pack 3 Beta provides client-side and server-side SSL support for Fortezza via the SChannel DLL.  When used in conjunction with a Fortezza cryptographic service provider (CSP), SChannel enables Fortezza data integrity, user authentication, and data confidentiality.  Fortezza CSPs can be obtained from Fortezza technology vendors.

1.2 Support for PowerPC-Based Systems

Microsoft is in the process of phasing out all Windows NT-related development for the PowerPC architecture. Because of this, there are no PowerPC files included in Service Pack 3 for Windows NT 4.0. Microsoft plans to continue providing technical support for customers who use Windows NT 4.0 on the PowerPC architecture.

2.0  Installation Instructions for the Windows NT Service Pack 3 Beta
-------------------------------------------------------------------
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 appears, in which you can choose to cancel the installation or to skip the file copy.  We recommend you choose to cancel and run the update program selecting the uninstall option.  Close active sessions on the system and rerun Update.exe to install the Service Pack.

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

To install the Service Pack from a compact disc:
1.  Insert the Service Pack compact disc into the CD-ROM drive.
2.  At the Command Prompt, change to the drive letter associated with the CD-ROM drive.
3.  Change directory to i386 or ALPHA (depending upon whether you have an Intel or ALPHA CPU), and type UPDATE.
4.  Follow the instructions that appear on the screen.

To install the Service Pack from a network drive:
1.  At the 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.  
3.  Change directory to i386 or ALPHA (depending upon whether you have an Intel or ALPHA CPU), and then type UPDATE.
4.  Follow the instructions that appear on the screen.

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

To enable the uninstall option, you must create an uninstall directory the first time you run Update.exe. To do this, when prompted, click "Yes, I want to create an Uninstall directory."  A subdirectory in your Windows NT directory will be created; this requires at least 60 MB of free space on the drive on which Windows NT is installed.

To uninstall the Service Pack, run Update.exe and click "Uninstall a previously installed Service Pack."  After your system has rebooted, the Update.exe program 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 3 was installed.

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


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 4.0 setup.  After the repair has completed, simply follow the Installation Instructions (section 2.0 above) 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 need to reapply the Service Pack.  This is because the files taken from the original Windows NT 4.0 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 3 Beta, 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 Beta .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 4.0 Workstation Resource Kit.


3.4 Remote Access Service PPP CHAP MD5 Authenticator Support

Service Pack 3 Beta provides limited PPP MD5-CHAP authenticator support to the Remote Access Server, which 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 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 removed.

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 box.  This feature is disabled by default.

Address conflicts are indicated by the replacement of the machine name with "BAD_ADDRESS."  If a Unique Identifier is specified for the address in the Client Properties dialog box, 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 use the Access Resolution Protocol (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 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, using the command:

NET STOP DHCPSERVER

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

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

3.6 Manually Updating OEM Drivers

OEM drivers supplied on the CD-ROM are not automatically updated by the Service Pack installation process. You must manually copy these updated drivers into the drivers directory of your machine.  The Service Pack media contains a DRVLIB directory, with subdiretories for various components.  If you determine the file is already installed on your system, you should make a backup copy of the file and then copy the updated file from the appropriate directory to the directory where it is installed on your system.  The following updated drivers are available in this Service Pack:

Network Adapter Drivers

Compaq NetFlex-3 and Netelligent: from drvlib\netcard\netflx3\i386\netflx3.sys
Intel E100B (and clones): from drvlib\netcard\e100b\i386\e100b.sys
3Com 3C590,3C592,3C595,3C597: from drvlib\netcard\3c59x\i386\el59x.sys


4.0  List of Bugs Fixed in Windows NT 4.0 Service Pack 3 Beta
--------------------------------------------------------------
NOTE: Use the Qxxxxxx number that precedes the title of the bug fix to
query the Microsoft Knowledge Base to find an article about a specific bug.

Service Pack 1
--------------
 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

Service Pack 2
--------------
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 Violation 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

Service Pack 3 Beta
-------------
Q135707: Programs Run at Priority Level 15 May Cause Computer to Hang
Q141189: BUG: Wrong Error Code on NetBIOS Call When Using NWNBLNK
Q141239: Stop 0xA Errors May Occur After Installing Service Pack 2
Q154939: CreateQueueJobAndFile Fails w/ Queues Other Than Print Queue
Q158433: Recreating Admin Shares from Server Manager Causes Exception Error
Q158548: Sysdiff Changes Dates on Files It Applies to WinNT
Q159330: MAP.EXE Does Not Set Environment Variable Correctly
Q161035: GetAddressByName API Cause SAP Broadcast
Q161038: Winsock Apps Fail on First Attempt at NetBIOS Name Resolution
Q161368: Service Pack 2 May Cause Loss of Connectivity in Remote Access
Q161432: WINS Static Entries Overwritten by Duplicate Group Names
Q161644: STOP 0x0000000A Sfmsrv.sys When Copying File to Mac Volume
Q161714: IPX Doesn't Function Correctly over Token Ring Source Routing
Q161830: Message from Unix Using Smbclient with Long Username Crashes
Q161838: Programs That Lock 0 Bytes at Byte 0 Lock Entire File
Q161991: Stop 0x0A With Virus Protection Software After Applying SP2
Q162077: Stop: 0x0000000A When Selecting NDS Map Objects
Q162096: SET: Drivers Fail to Load When I/O Address Is Above 0xFFF
Q162189: Macintosh Clients May Hang Temporarily with Multiple Mac Volumes
Q162616: Extra FF When Using PASSTHROUGH Functions To TXTONLY Driver
Q162657: Choosing Default Domain Name for RAS Client Authentication


5.0 Notes for Users of the 128-bit North American Version of Windows NT 4.0
-------------------------------------------------------------------

All encryption-related components in this version of Service Pack 3 Beta are limited to exportable 40-bit cryptography. During installation, you will be prompted when an existing component on your system containing 128-bit encryption is about to be replaced by an updated component with 40-bit encryption. If you require 128-bit support, you should click "Skip" when prompted during Service Pack Setup. A 128-bit version of this Service Pack Beta is not available. We recommend that you install this beta on a computer that has 40-bit encryption.

Bugs[edit | edit source]

  • In winver, the version string is cut off at the RC 1.52 part because it's too long.
  • There is an additional empty line on the bootscreen because the version string is too long.

Gallery[edit | edit source]