| Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| Windows 95 4.00.950r-7 (Hebrew) - 32-Bit Win
| Product Summary |
Product: Windows 95
Version: 4.00.950r-7 |
Category: Compliant*
Operating System: 32-Bit Win |
| Language: Hebrew |
Release Date: N/A |
| Operational Range: |
01 Jan 1980 - 31 Dec 2035 |
| Prerequisites: |
Windows 95 year 2000 Software Update, Internet Explorer 5 |
| Product Dependencies: |
None |
| Clock Dependencies: |
PC BIOS |
| Last Updated: |
30 Jun 1999 | |
| Product Details |
|
This document also applies to Hebrew (enabled).
Product Details
Microsoft has released a software update for Windows 95 that addresses the known issues described below.
- To download, please click Windows 95 year 2000 software update
- To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International
- Windows 95 shipped with various versions of Internet Explorer. It is recommended to be on Internet Explorer 5, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer that is installed.
How the product handles dates:
Storage: Dates are stored internally as 4-digit year dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980.
Two-digit shortcut handling: MS-DOS DATE command will not accept 2-digit year date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit year date will result in an "invalid date" message. This issue is fixed by the updated version of COMMAND.COM.
Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this.
Product Issues:
WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows:
- January 1, 2000 would appear as 1/1/;1
- February 3, 2023 would appear as 2/3/>3
- March 5, 2036 would appear as 3/5/=6
COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date".
COMCTL32.DLL û When Regional Settings from Control Panel is set to use two digits for years, the Date/Time Picker function may not return the proper date. To ensure proper handling of dates: set Regional Settings to 4-digit date handling,
VDHCP.386 - Winipcfg/all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date.
TIMEDATE.CPL ûTime and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back.
DIALER.EXE - Phone Dialer applet - The show call log option doesnÆt display date correctly after successful completion of telephone call. If date is adjusted to the year 2000, the date will display as 100, 101, 102, etc.
MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon.
Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see http://msdn.microsoft.com/visualc/headlines/2001.asp
OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the userÆs century window settings in Control Panel\Regional Settings\Date tab. This fix moves the 2-digit year cutoff from 1999 to 2029.
XCOPY.EXE û When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 20th century (02/05/01 is seen as 02/05/1901).
Testing guidelines and recommendations:
Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock article in the white paper section of this product guide for further information.
| |
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 an 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.
|
