| Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| Windows 95 OSR 2.5, 4.00.1111 (German) - 32-Bit Win
| Product Summary |
Product: Windows 95
Version: OSR 2.5, 4.00.1111 |
Category: Compliant*
Operating System: 32-Bit Win |
| Language: German |
Release Date: N/A |
| Operational Range: |
01 Jan 1980 - 31 Dec 2035 |
| Prerequisites: |
Windows 95 year 2000 Software Update; Outlook Express 4.01 Software Update; Updated Microsoft Virtual Machine |
| Product Dependencies: |
None |
| Clock Dependencies: |
PC BIOS |
| Last Updated: |
13 Oct 1999 | |
| Product Details |
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Windows 95 version OSR 2.x, 4.00.1111 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.
To learn how to check your version of Windows 95, see Knowledge Base article from Microsoft's Support site - Q158238.
Product Details
Microsoft has released a software update for Windows 95 that addresses the known issues described below.
To download the Windows 95 year 2000 Software Update, please click here.
To receive the Year 2000 Resource Center CD from Microsoft that will include this update, please click here, or in the US call 1-888-MSFT Y2k.
Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here.
Additional Information
Windows 95 Year 2000 Update may not update VDHCP.386: If the Dial Up Networking 1.3 or the Winsock2 Updates for Windows 95 have been installed on the Windows 95 machine prior to installing Windows 95 year 2000 Software Update, the Windows 95 year 2000 software update will not update VDHCP.386. For more information, please see the Knowledge Base Article Q230173.
To determine if you have either Dial Up Networking or Winsock installed, check Control Panel/ Add/Remove Programs. If either update has been installed, it will be on the list of installed products.
The year 2000 software update for Dial Up Networking 1.3 and Winsock 2 is available at Dial Up Networking 1.3 and Winsock 2 Year 2000 Update.
Corporate Customers
A Windows 95 Corporate Year 2000 Companion is available for corporations to address Year 2000 Update deployment issues and to ease administration. This Corporate Year 2000 Companion is recommended for corporate customers after they have installed the Windows 95 year 2000 update released in April 1999. The Corporate Year 2000 Companion incorporates: 1) deployment and maintenance features requested by corporate customers, and 2) the Dial Up Networking 1.3 and Winsock 2 year 2000 software update. An English version is available at Windows 95 Corporate Year 2000 Companion.
To determine which Year 2000 updates have been applied to your Windows 95 system, install the Windows 95 Corporate Companion available from the Windows 95 download site or Windows Update. Run the Update Information Tool (QFECHECK.EXE) that is installed with the Corporate Companion to view which Y2K updates are deployed on the system.
How the product handles dates:
Storage: Dates are stored internally as 4-digit 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 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 date will result in an "invalid date" message. This issue is fixed (see below) 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 fixed in the Windows 95 year 2000 Software Update:
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".
MSWALLET - When entering credit card information in versions of Microsoft Wallet before 2.1.1383, users must enter month, day, and year for expiration dates beyond 2000. Otherwise, information may be parsed incorrectly. For example, entering a credit card with expiration 5/01 will be parsed as May 1st of the current year.
COMCTL32.DLL - When Regional Settings from Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to 4-digit date display.
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.
MICROSOFT VIRTUAL MACHINE - Year 2000 issues have been reported in connection with Java virtual machines based on the Sun Microsystems Java Development Kit (versions 1.1.1-1.1.5). Applications written in Java that make use of the java.txt.SimpleDateFormat class library may parse 4-digit dates incorrectly. The latest update for Java VM may download at http://www.microsoft.com/java/vm/dl_vm32.htm.
OLE DB Year 2000 issues for data coercion library are:
If coded to ADO,
AND the ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp.
AND a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98)
AND a year specified is less than 60,
THEN Data Convert (msdadc.dll) will translate the date as a time. For example, 01.01.01 (January 1st, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01 a.m.).
If coded directly to OLE DB, the same case exists:
If converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as:
DBTYPE_DATE
DBTYPE_DBDATE
DBTYPE_DBTIME
DBTYPE_FILETIME
DBTYPE_DBTIMESTAMP
AND using a European format for dates,
AND specify a year less than 60,
THEN Data Convert (msdadc.dll) will translate the date as a time. For example, 01.01.01 (January 1st, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01 a.m.).
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 does not display date correctly after successful completion of telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc.
MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's 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.
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:
Microsoft Jet Database Engine 3.0 and Microsoft Office 95
When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Service Release from the Microsoft Web site at http://www.officeupdate.microsoft.com/
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 testing 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 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.
|
