| Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| Windows NT Server 3.51 (Japanese) - Win NT
| Product Summary |
Product: Windows NT Server
Version: 3.51 |
Category: Compliant*
Operating System: Win NT |
| Language: Japanese |
Release Date: 30 May 1995 |
| Operational Range: |
01 Jan 1996- - 31 Dec 2036 |
| Prerequisites: |
Windows NT 3.51 Service Pack 5 and hot fix |
| Product Dependencies: |
None |
| Clock Dependencies: |
System clock |
| Last Updated: |
30 Sep 1999 | |
| Product Details |
|
What are the prerequisites for compliance?
Windows NT 3.51 is compliant with the following software installed:
1) Microsoft Windows NT Service Pack 5 (SP5) for Windows NT 3.51
2) A software update for known compliance issues for Windows NT Server Version 3.51 Service Pack 5.
Brazilian
Chinese Simplified
Chinese Traditional Dutch
French
English
German
Japanese
Korean
Norwegian
Spanish
Swedish
The software update addresses the following issues:
|
1. Simulated RTC presents the century byte with 19 instead of 20 (Microsoft Knowledge Base Article Q193376). The simulated Real Time Clock (RTC) will present the century byte representing 19 instead of 20 in the 21st Century. This causes MS-DOS-based programs that access the Real Time Clock to receive the wrong date. For example, the year 2000 is interpreted as the year 1900. |
|
2. File and Print Services for NetWare (FPNW) Logout.exe incorrectly reports Year after Jan. 1, 2000 (Microsoft Knowledge Base Article Q186669). The File and Print Services for NetWare (FPNW) service Logout.exe program may report the year incorrectly for files created on or after January 1, 2000. |
|
3. Date of Print Job may be displayed incorrectly in print queue (Microsoft Knowledge Base Article Q191768). When you view a print job spooled on another print server, such as Windows 9x or LAN Manager, from a Windows NT client, the date displayed in the print queue may be incorrect and possibly off by one year. |
|
4. WINS/DHCP Admin show expiration dates 2000 - 2009 with one digit (Microsoft Knowledge Base Article Q193371). Windows Internet Name Service (WINS) Admin and Dynamic Host Configuration Protocol (DCHP) Service Admin display the expiration dates 2000 through 2009 with one digit (for example, 1/1/2000 is displayed as 1/1/0 instead of 1/1/00). |
|
5. User Manager does not recognize February 2000 as a leap year (Microsoft Knowledge Base Article Q175093). When you set an account to expire on February 29, 2000, User Manager displays the following message: "February only has 28 days in this year." |
|
6. Last Day of the Month reverts back to first day of same month (Microsoft Knowledge Base Article Q193422). As the Date/Time utility attempts to change the date from the last day of the month to the first day of the following month, it displays the first day of the current month instead. For example, instead of displaying February 1, 2000, one day after the date was January 31, 2000, the Date/Time utility reports the date as January 1, 2000. |
|
7. Migration changes NetWare accounts expiration date (Microsoft Knowledge Base Article Q193434). Novell NetWare accounts with an expiration date January 1, 2000, or later are migrated to Windows NT with the incorrect expiration date. |
|
8. Problems in Date/Time after choosing Feb 29 in leap year (Microsoft Knowledge Base Article Q193461). You may experience one or more of the following issues in Windows NT Version 3.51: 1) Using the Date/Time tool in Control Panel, if you select February 29 in a leap year, select a non-leap year, and then click Cancel, the system date is set to a random year. 2) Using the Date/Time tool in Control Panel, if you are editing any field other than the seconds field and the time passes midnight, clicking Cancel sets the date to a seemingly random values. |
|
9. FTP File Service displays incorrect file date for Year 2000 (Microsoft Knowledge Base Article Q182597). The FTP service in Windows NT 3.51 may report the year incorrectly for files created on or after Jan 1, 2000. For example, January 1, 2000 is displayed as 01/01/100. |
Latest Year 2000 Updates:
NET USER /TIME Command does not work in Year 2000 (Q240195) The /TIMES function can be used to set the valid logon times of Windows NT user accounts via the command line utility NET USER. The Year 2000 issue causes the /TIMES function to cease functioning in years 2000 or greater. The User Manager GUI application is not affected and can be used to effectively set account valid logon times in the year 2000 and beyond.
Internet Information Server:
For reasons of Year 2000 Compliance, Internet Information Server (IIS) is considered to be part of the Windows NT 3.51 SP5 Operating System. This applies to versions 1.0(x) of IIS. Following the updates prescribed above, these versions of IIS are Year 2000 Compliant. For other versions of IIS, consult the Windows NT 4.0 Compliance Documents.
Description of how dates are handled in the product:
|
Time Data Structures. The system has two data structures exposed to Win32 programs: FILETIME and SYSTEMTIME. FILETIME returns the number of 100 nanoseconds intervals since January 1, 1601 in a 64-bit value. SYSTEMTIME returns the year in a 16-bit value. FAT file systems store dates starting in 1980 in a field with valid input up to 2127.
Event Log. The event log record header saves the date encoded in seconds since Jan. 1, 1970. This will only be a problem after the year 2100.
Protocol Stack. There are no known date issues in the network protocol stacks. |
What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation?
The Control Panel Regional Settings applet under the Date tab controls the format of short dates. The operating system uses this format when displaying dates. Examples of use may be seen in the Shell (view details on files), the DIR command and in notepad (when printing dates in headers). Win32 applications may also use this format. If you change the short date format to be one that shows 4-digit years, you should test your Win32 applications to make sure they have allocated enough space for the extra digits.
Testing guidelines and recommendations:
Device drivers in general should not be affected by year 2000 problems. However, drivers do have access to the BIOS code on the card and may look at the BIOS date to change behavior. Most BIOS dates are stored in 2-digit year format, so there is a chance that a driver may not work correctly with cards that have BIOS dates in the next century. Microsoft is not aware of any drivers that are currently doing this check. Most look for revision numbers to change behavior. When manufacturers start offering cards with these BIOS dates, you should test the drivers that run on them to make sure they continue to work as expected.
| |
Return to Search Screen
| Legend of Symbols: |
| * |
The product is compliant with recommended customer action. This indicates a prerequisite action is recommended which may include loading a software update or reading a document. |
| # |
The product is compliant with acceptable deviations from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability, or reliability of the product. |
| + |
The product is compliant with pending Year 2000 software updates. Future maintenance actions will be recommended shortly. See Product Guide for further details. |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
If after reviewing this information you have additional questions related to this product, click here.
YEAR 2000 READINESS DISCLOSURE
ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFT'S YEAR 2000 WEBSITE LOCATED AT http://www.microsoft.com/year2000/ (the "Y2K WEBSITE"). EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED PURSUANT TO THE TERMS HEREOF, THE TERMS OF THE Y2K WEBSITE, AND THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT FOR THE SOLE PURPOSE OF ASSISTING THE PLANNING FOR THE TRANSITION TO THE YEAR 2000. EACH MICROSOFT YEAR 2000 STATEMENT CONTAINS INFORMATION CURRENTLY AVAILABLE AND IS UPDATED REGULARLY AND SUBJECT TO CHANGE. MICROSOFT THEREFORE RECOMMENDS THAT YOU CHECK THE Y2K WEBSITE REGULARLY FOR ANY CHANGES TO ANY MICROSOFT YEAR 2000 STATEMENT. EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. CONSEQUENTLY, MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, MICROSOFT DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF ANY MICROSOFT YEAR 2000 STATEMENT IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY MICROSOFT OR ITS AUTHORIZED REPRESENTATIVES SHALL CREATE A WARRANTY OR IN ANY WAY DECREASE THE SCOPE OF THIS WARRANTY DISCLAIMER. IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER REGARDING ANY MICROSOFT YEAR 2000 STATEMENT INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, PUNITIVE OR SPECIAL DAMAGES, EVEN IF MICROSOFT 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 FOREGOING LIMITATION MAY NOT APPLY TO YOU. THE INFORMATION CONTAINED IN EACH MICROSOFT YEAR 2000 STATEMENT IS FOUND AT THE Y2K WEBSITE AND IS INTENDED TO BE READ IN CONJUNCTION WITH OTHER INFORMATION LOCATED AT THE Y2K WEBSITE, INCLUDING BUT NOT LIMITED TO MICROSOFT'S YEAR 2000 COMPLIANCE STATEMENT, THE DESCRIPTION OF THE CATEGORIES OF COMPLIANCE INTO WHICH MICROSOFT HAS CLASSIFIED ITS PRODUCTS IN ITS YEAR 2000 PRODUCT GUIDE, AND THE MICROSOFT YEAR 2000 TEST CRITERIA.
ANY MICROSOFT YEAR 2000 STATEMENTS MADE TO YOU IN THE COURSE OF PROVIDING YEAR 2000 RELATED UPDATES, YEAR 2000 DIAGNOSTIC TOOLS, OR REMEDIATION SERVICES (IF ANY) ARE SUBJECT TO THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT (112 STAT. 2386). IN CASE OF A DISPUTE, THIS ACT MAY REDUCE YOUR LEGAL RIGHTS REGARDING THE USE OF ANY SUCH STATEMENTS, UNLESS OTHERWISE SPECIFIED BY YOUR CONTRACT OR TARIFF.
|
