95 Jahr 2000 Kompatibilitšt
|Windows 95 - all
Versions to OSR 2.1, 4.00.1111 (German) - 32-Bit Win
|Product: Windows 95
Operating System: 32-Bit Win
||Release Date: N/A
1980 - 31 Dec 2035
||Windows 95 year 2000 software update - 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, 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.
Operational Range for Data: 1980-2035
To learn how to check your version of Windows 95, see KnowledgeBase article from
Microsoft's Support site - Q158238.
Microsoft has released a software update for Windows 95 that addresses the known issues
To download/install, please click here:
W95Y2K.EXE - Tech. details
(self extracting exe-file 2,19MB, 16.7.1999 , download or open to install)
receive the Year 2000 Resource Center CD from Microsoft, please contact your local
subsidiary. For local contact information please check Microsoft
Windows 95 shipped with various versions of Internet Explorer. It is recommended to be
on Internet Explorer 4.01 Service Pack 1 or greater, including any software updates which
are applicable. Please check the Year 2000 Product Guide for the version
of Internet Explorer you have.
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 by
the updated version of COMMAND.COM.
Also, since 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 API's are
not affected by this.
Product Issues resolved by Windows 95 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
- 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".
and OSR 1: SHELL32.DLL - The
"Find File" or "Folders Dialog" Date tab displays the year in YY
format. This format results in non-numeric displays for years greater than 2000. For
example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the
search. When searching for files changed within a certain date range, enter a 2-digit or
4-digit date and the search will be performed based on the dates entered.
- 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.
- 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.
- Phone Dialer applet - The show call log option does not 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.
- 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.
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
- 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 two 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
- 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 1900s (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
|Legend of Symbols:
||Indicates 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.
||Indicates the product is compliant,
with acceptable deviations from Microsoft's standard of compliance. An acceptable
deviation does not affect the core functionality (ex: data integrity) or stability (ex:
reliability) of the product.
||Indicates the product is compliant,
with pending software updates. Future maintenance actions will be recommended shortly.
ratings given for each product assume that all recommended actions have been taken.