01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, SP3, SP4, SP5, Windows 98, SE | ||
System Clock | ||
13 Oct 1999 | ||
How the product handles dates: This version of IntelliPoint does not process dates |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, SP3, SP4, SP5, Windows 98, SE | ||
System Clock | ||
13 Oct 1999 | ||
How the product handles dates: This version of IntelliPoint does not process dates |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, SP3, SP4, SP5, Windows 98, SE | ||
System Clock | ||
13 Oct 1999 | ||
How the product handles dates: This version of IntelliPoint does not process dates |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, SP3, SP4, SP5, Windows 98, SE | ||
System Clock | ||
13 Oct 1999 | ||
How the product handles dates: This version of IntelliPoint does not process dates |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, SP3, SP4, SP5, Windows 98, SE | ||
System Clock | ||
13 Oct 1999 | ||
How the product handles dates: This version of IntelliPoint does not process dates |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, SP3, SP4, SP5, Windows 98, SE | ||
System Clock | ||
13 Oct 1999 | ||
How the product handles dates: This version of IntelliPoint does not process dates |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, SP3, SP4, SP5, Windows 98, SE | ||
System Clock | ||
13 Oct 1999 | ||
How the product handles dates: This version of IntelliPoint does not process dates |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, SP3, SP4, SP5, Windows 98, SE | ||
System Clock | ||
13 Oct 1999 | ||
How the product handles dates: This version of IntelliPoint does not process dates |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, SP3, SP4, SP5, Windows 98, SE | ||
System Clock | ||
25 Oct 1999 | ||
How the product handles dates: This version of IntelliPoint does not process dates |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, SP3, SP4, SP5, Windows 98, SE | ||
System Clock | ||
13 Oct 1999 | ||
How the product handles dates: This version of IntelliPoint does not process dates |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
None | ||
None | ||
None | ||
30 Aug 1999 | ||
How the product handles dates: International Football 2000 does not handle dates or perform two-digit shortcut interpretations. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
None | ||
None | ||
None | ||
30 Aug 1999 | ||
How the product handles dates: International Football 2000 does not handle dates or perform two-digit shortcut interpretations. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
None | ||
None | ||
None | ||
30 Aug 1999 | ||
How the product handles dates: International Football 2000 does not handle dates or perform two-digit shortcut interpretations. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
None | ||
None | ||
None | ||
30 Aug 1999 | ||
How the product handles dates: International Football 2000 does not handle dates or perform two-digit shortcut interpretations. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
None | ||
None | ||
None | ||
30 Aug 1999 | ||
How the product handles dates: International Football 2000 does not handle dates or perform two-digit shortcut interpretations. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
None | ||
None | ||
None | ||
30 Aug 1999 | ||
How the product handles dates: International Football 2000 does not handle dates or perform two-digit shortcut interpretations. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
None | ||
None | ||
None | ||
30 Aug 1999 | ||
How the product handles dates: International Football 2000 does not handle dates or perform two-digit shortcut interpretations. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
None | ||
None | ||
None | ||
30 Aug 1999 | ||
How the product handles dates: International Soccer 2000 does not handle dates or perform two-digit shortcut interpretations. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
None | ||
None | ||
None | ||
30 Aug 1999 | ||
How the product handles dates: International Soccer 2000 does not handle dates or perform two-digit shortcut interpretations. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
None | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP5 | ||
System Clock | ||
28 Oct 1999 | ||
How the product handles dates: Dates stored internally use the C Run-Time Library. Two-digit shortcut handling: Some web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for the expiration date of cookie data. Issues Contributing To Non-Compliance Rating:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls may have potential Year 2000 issues. Also note: when viewing dates in Internet Explorer for history, true web integration, the display of 4-digit years in Windows or Windows NT needs to be enabled through the regional settings in control panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Microsoft has tested operation with popular web servers and proxy servers, it is recommended your verification of Internet Explorer include testing of the items below within your computing environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. Microsoft recommends you ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
None | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP5 | ||
System Clock | ||
28 Oct 1999 | ||
How the product handles dates: Dates stored internally use the C Run-Time Library. Two-digit shortcut handling: Some web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for the expiration date of cookie data. Issues Contributing To Non-Compliance Rating:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls may have potential Year 2000 issues. Also note: when viewing dates in Internet Explorer for history, true web integration, the display of 4-digit years in Windows or Windows NT needs to be enabled through the regional settings in control panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Microsoft has tested operation with popular web servers and proxy servers, it is recommended your verification of Internet Explorer include testing of the items below within your computing environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. Microsoft recommends you ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
None | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP5 | ||
System Clock | ||
28 Oct 1999 | ||
How the product handles dates: Dates stored internally use the C Run-Time Library. Two-digit shortcut handling: Some web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for the expiration date of cookie data. Issues Contributing To Non-Compliance Rating:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls may have potential Year 2000 issues. Also note: when viewing dates in Internet Explorer for history, true web integration, the display of 4-digit years in Windows or Windows NT needs to be enabled through the regional settings in control panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Microsoft has tested operation with popular web servers and proxy servers, it is recommended your verification of Internet Explorer include testing of the items below within your computing environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. Microsoft recommends you ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
Internet Explorer 3.03 Service Pack 1 | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP5 | ||
System Clock | ||
28 Oct 1999 | ||
Product Maintenance This document pertains to Internet Explorer version 3.03 (16bit). Earlier versions of Internet Explorer 3.0x will have the same issues as noted in this document, but do not have a software update available. If you are on one of the earlier versions of IE 3.0x, it is recommended to move to the latest version of Internet Explorer. What are the prerequisites? The user needs to install Service Pack 1 for Internet Explorer 3.03. The Service Pack can be found at: http://www.microsoft.com/msdownload/iebuild/ie3sp1_win16/en/ie3sp1_win16.htm this is available in English, French, Italian, and Spanish. Description of how the product handles dates: All dates are stored internally use the C Run-Time Library. 2-digit shortcut handling: Some web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. With Internet Explorer 3.03 Service Pack 1, Internet Explorer will assume that 80 - 99 are 1980 to 1999 and 00 - 35 are 2000 to 2035. Issues addressed by Service Pack 1:
Recommendations: IE 3.03 Service Pack 1 (for English, French, Italian, and Spanish) version is available as listed above. Common date usage errors: Independent of Internet Explorer's handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. Also note: when viewing dates in Internet Explorer for history, true web integration, the display of four digit years in Windows or Windows NT needs to be enabled through the regional settings in control panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
Internet Explorer 3.03 Service Pack 1 | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
Product Maintenance This document pertains to Internet Explorer version 3.03 (16bit). Earlier versions of Internet Explorer 3.0x will have the same issues as noted in this document, but do not have a software update available. If you are on one of the earlier versions of IE 3.0x, it is recommended to move to the latest version of Internet Explorer. What are the prerequisites? The user needs to install Service Pack 1 for Internet Explorer 3.03. The Service Pack can be found at: http://www.microsoft.com/msdownload/iebuild/ie3sp1_win16/en/ie3sp1_win16.htm this is available in English, French, Italian, and Spanish. Description of how the product handles dates: All dates are stored internally use the C Run-Time Library. 2-digit shortcut handling: Some web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. With Internet Explorer 3.03 Service Pack 1, Internet Explorer will assume that 80 - 99 are 1980 to 1999 and 00 - 35 are 2000 to 2035. Issues addressed by Service Pack 1:
Recommendations: IE 3.03 Service Pack 1 (for English, French, Italian, and Spanish) version is available as listed above. Common date usage errors: Independent of Internet Explorer's handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. Also note: when viewing dates in Internet Explorer for history, true web integration, the display of four digit years in Windows or Windows NT needs to be enabled through the regional settings in control panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
None | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP5 | ||
System Clock | ||
28 Oct 1999 | ||
How the product handles dates: Dates stored internally use the C Run-Time Library. Two-digit shortcut handling: Some web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for the expiration date of cookie data. Issues Contributing To Non-Compliance Rating:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls may have potential Year 2000 issues. Also note: when viewing dates in Internet Explorer for history, true web integration, the display of 4-digit years in Windows or Windows NT needs to be enabled through the regional settings in control panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Microsoft has tested operation with popular web servers and proxy servers, it is recommended your verification of Internet Explorer include testing of the items below within your computing environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. Microsoft recommends you ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
Internet Explorer 3.03 Service Pack 1 | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
Product Maintenance This document pertains to Internet Explorer version 3.03 (16bit). Earlier versions of Internet Explorer 3.0x will have the same issues as noted in this document, but do not have a software update available. If you are on one of the earlier versions of IE 3.0x, it is recommended to move to the latest version of Internet Explorer. What are the prerequisites? The user needs to install Service Pack 1 for Internet Explorer 3.03. The Service Pack can be found at: http://www.microsoft.com/msdownload/iebuild/ie3sp1_win16/en/ie3sp1_win16.htm this is available in English, French, Italian, and Spanish. Description of how the product handles dates: All dates are stored internally use the C Run-Time Library. 2-digit shortcut handling: Some web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. With Internet Explorer 3.03 Service Pack 1, Internet Explorer will assume that 80 - 99 are 1980 to 1999 and 00 - 35 are 2000 to 2035. Issues addressed by Service Pack 1:
Recommendations: IE 3.03 Service Pack 1 (for English, French, Italian, and Spanish) version is available as listed above. Common date usage errors: Independent of Internet Explorer's handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. Also note: when viewing dates in Internet Explorer for history, true web integration, the display of four digit years in Windows or Windows NT needs to be enabled through the regional settings in control panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
None | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP5 | ||
System Clock | ||
28 Oct 1999 | ||
How the product handles dates: Dates stored internally use the C Run-Time Library. Two-digit shortcut handling: Some web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for the expiration date of cookie data. Issues Contributing To Non-Compliance Rating:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls may have potential Year 2000 issues. Also note: when viewing dates in Internet Explorer for history, true web integration, the display of 4-digit years in Windows or Windows NT needs to be enabled through the regional settings in control panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Microsoft has tested operation with popular web servers and proxy servers, it is recommended your verification of Internet Explorer include testing of the items below within your computing environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. Microsoft recommends you ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
None | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP5 | ||
System Clock | ||
28 Oct 1999 | ||
How the product handles dates: Dates stored internally use the C Run-Time Library. Two-digit shortcut handling: Some web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for the expiration date of cookie data. Issues Contributing To Non-Compliance Rating:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls may have potential Year 2000 issues. Also note: when viewing dates in Internet Explorer for history, true web integration, the display of 4-digit years in Windows or Windows NT needs to be enabled through the regional settings in control panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Microsoft has tested operation with popular web servers and proxy servers, it is recommended your verification of Internet Explorer include testing of the items below within your computing environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. Microsoft recommends you ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
None | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP5 | ||
System Clock | ||
28 Oct 1999 | ||
How the product handles dates: Dates stored internally use the C Run-Time Library. Two-digit shortcut handling: Some web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for the expiration date of cookie data. Issues Contributing To Non-Compliance Rating:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls may have potential Year 2000 issues. Also note: when viewing dates in Internet Explorer for history, true web integration, the display of 4-digit years in Windows or Windows NT needs to be enabled through the regional settings in control panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Microsoft has tested operation with popular web servers and proxy servers, it is recommended your verification of Internet Explorer include testing of the items below within your computing environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. Microsoft recommends you ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
None | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP5 | ||
System Clock | ||
28 Oct 1999 | ||
How the product handles dates: Dates stored internally use the C Run-Time Library. Two-digit shortcut handling: Some web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for the expiration date of cookie data. Issues Contributing To Non-Compliance Rating:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls may have potential Year 2000 issues. Also note: when viewing dates in Internet Explorer for history, true web integration, the display of 4-digit years in Windows or Windows NT needs to be enabled through the regional settings in control panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Microsoft has tested operation with popular web servers and proxy servers, it is recommended your verification of Internet Explorer include testing of the items below within your computing environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. Microsoft recommends you ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
Internet Explorer 3.03 Service Pack 1 | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
What are the prerequisites? The user needs to install Service Pack 1 for Internet Explorer 3.03. The Service Pack can be found at: http://www.microsoft.com/msdownload/iebuild/ie3sp1_win16/en/ie3sp1_win16.htm this is available in English, French, Italian, and Spanish.Description of how the product handles dates: All dates are stored internally use the C Run-Time Library. 2-digit shortcut handling: Some web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. With Internet Explorer 3.03 Service Pack 1, Internet Explorer will assume that 80 - 99 are 1980 to 1999 and 00 - 35 are 2000 to 2035. Issues addressed by Service Pack 1:
Recommendations: IE 3.03 Service Pack 1 (for English, French, Italian, and Spanish) version is available as listed above. Common date usage errors: Independent of Internet Explorer's handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. Also note: when viewing dates in Internet Explorer for history, true web integration, the display of four digit years in Windows or Windows NT needs to be enabled through the regional settings in control panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
None | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP5 | ||
System Clock | ||
28 Oct 1999 | ||
How the product handles dates: Dates stored internally use the C Run-Time Library. Two-digit shortcut handling: Some web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for the expiration date of cookie data. Issues Contributing To Non-Compliance Rating:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls may have potential Year 2000 issues. Also note: when viewing dates in Internet Explorer for history, true web integration, the display of 4-digit years in Windows or Windows NT needs to be enabled through the regional settings in control panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Microsoft has tested operation with popular web servers and proxy servers, it is recommended your verification of Internet Explorer include testing of the items below within your computing environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. Microsoft recommends you ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
none | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
Description of how the product handles dates: All dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. 2-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a two-digit string for years within the operational range up to 1999. The method returns a four-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server, all transition to operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
none | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
Description of how the product handles dates: All dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. 2-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a two-digit string for years within the operational range up to 1999. The method returns a four-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server, all transition to operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
none | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
Description of how the product handles dates: All dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. 2-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a two-digit string for years within the operational range up to 1999. The method returns a four-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server, all transition to operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
none | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
Description of how the product handles dates: All dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. 2-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a two-digit string for years within the operational range up to 1999. The method returns a four-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server, all transition to operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
none | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
Description of how the product handles dates: All dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. 2-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a two-digit string for years within the operational range up to 1999. The method returns a four-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server, all transition to operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
Internet Explorer 4.01 & Outlook Express 4.01 Year 2000 Software Update | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
Description of how the product handles dates: Dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. 2-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 interprets dates entered with a 2-digit shortcut in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a two-digit string for years within the operational range up to 1999. The method returns a four-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired.
Outlook Express Issue (software update is not part of Internet Explorer 4.01) If Outlook Express (OE) 4.01 receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than 99, OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as 97, then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year 99 is received and the current year is a multiple of 100 (e.g. 2000), the year will be interpreted as the current year plus 98 (e.g. 2098). For more information and the software update for this issue, please review Knowledge Base Articles Q237823 or Q237824.A software update is available for this issue. (There is a separate update if you are running Outlook Express 5.0.) The software update for OE 4.01 is found here.Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server, all transition to operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
none | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
Description of how the product handles dates: All dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. 2-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a two-digit string for years within the operational range up to 1999. The method returns a four-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server, all transition to operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
none | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
Description of how the product handles dates: All dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. 2-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a two-digit string for years within the operational range up to 1999. The method returns a four-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server, all transition to operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
none | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
Description of how the product handles dates: All dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. 2-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a two-digit string for years within the operational range up to 1999. The method returns a four-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server, all transition to operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
none | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
Description of how the product handles dates: All dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. 2-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a two-digit string for years within the operational range up to 1999. The method returns a four-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server, all transition to operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
none | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
Description of how the product handles dates: All dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. 2-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a two-digit string for years within the operational range up to 1999. The method returns a four-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server, all transition to operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
None | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
Description of how the product handles dates: All dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. 2-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a two-digit string for years within the operational range up to 1999. The method returns a four-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server, all transition to operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
none | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
Description of how the product handles dates: All dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. 2-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a two-digit string for years within the operational range up to 1999. The method returns a four-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server, all transition to operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
none | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
Description of how the product handles dates: All dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. 2-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a two-digit string for years within the operational range up to 1999. The method returns a four-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server, all transition to operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
none | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
Description of how the product handles dates: All dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. 2-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a two-digit string for years within the operational range up to 1999. The method returns a four-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server, all transition to operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
none | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
Description of how the product handles dates: All dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. 2-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a two-digit string for years within the operational range up to 1999. The method returns a four-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server, all transition to operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
none | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
Description of how the product handles dates: All dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. 2-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a two-digit string for years within the operational range up to 1999. The method returns a four-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server, all transition to operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
none | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
Description of how the product handles dates: All dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. 2-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a two-digit string for years within the operational range up to 1999. The method returns a four-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server, all transition to operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
None | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 5 | ||
System Clock | ||
28 Oct 1999 | ||
Description of how the product handles dates: All dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. 2-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a two-digit string for years within the operational range up to 1999. The method returns a four-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server, all transition to operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
None | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 4 | ||
System Clock | ||
03 Nov 1999 | ||
The expected release date for the Internet Explorer 5.0 16-bit Win Year 2000 software update is November 12, 1999. How the product handles dates: Dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. Two-digit shortcut handling: Some web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Internet Explorer assumes that 80 – 99 are 1980 to 1999 and 00 – 35 are 2000 to 2035 and 36 – 70 are 2035. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls may have potential year 2000 issues. Also note: when viewing dates in Internet Explorer for history, true web integration, the display of 4-digit years in Windows or Windows NT needs to be enabled through the regional settings in control panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays a message that they are expired.
Testing guidelines and recommendations: Web sites or web-based applications need to have Internet Explorer, the web server, and if applicable, proxy server test all transition to and operate in the year 2000. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While Internet Explorer has been tested operation with popular web servers and proxy servers, verification of Internet Explorer should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Also, some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
Internet Explorer 5.0 & Outlook Express 5.0 Year 2000 Software Update | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 4 | ||
System Clock | ||
03 Nov 1999 | ||
The expected release date for the Internet Explorer 5.0 16-bit Win Year 2000 software update is November 12, 1999. How the product handles dates: Dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. Two-digit shortcut handling: Some web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Internet Explorer assumes that 80 – 99 are 1980 to 1999 and 00 – 35 are 2000 to 2035 and 36 – 70 are 2035. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls may have potential year 2000 issues. Also note: when viewing dates in Internet Explorer for history, true web integration, the display of 4-digit years in Windows or Windows NT needs to be enabled through the regional settings in control panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays a message that they are expired.
Outlook Express Issue (software update is not part of Internet Explorer 4.01) If Outlook Express (OE) 4.01 receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than 99, OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as 97, then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year 99 is received and the current year is a multiple of 100 (e.g. 2000), the year will be interpreted as the current year plus 98 (e.g. 2098). For more information and the software update for this issue, please review Knowledge Base Articles Q237823 or Q237824.A software update is available for this issue. (There is a separate update if you are running Outlook Express 4.01.) The software update is found here.Testing guidelines and recommendations: Web sites or web-based applications need to have Internet Explorer, the web server, and if applicable, proxy server test all transition to and operate in the year 2000. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While Internet Explorer has been tested operation with popular web servers and proxy servers, verification of Internet Explorer should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Also, some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
None | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 4 | ||
System Clock | ||
03 Nov 1999 | ||
The expected release date for the Internet Explorer 5.0 16-bit Win Year 2000 software update is November 12, 1999. How the product handles dates: Dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. Two-digit shortcut handling: Some web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Internet Explorer assumes that 80 – 99 are 1980 to 1999 and 00 – 35 are 2000 to 2035 and 36 – 70 are 2035. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls may have potential year 2000 issues. Also note: when viewing dates in Internet Explorer for history, true web integration, the display of 4-digit years in Windows or Windows NT needs to be enabled through the regional settings in control panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays a message that they are expired.
Testing guidelines and recommendations: Web sites or web-based applications need to have Internet Explorer, the web server, and if applicable, proxy server test all transition to and operate in the year 2000. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While Internet Explorer has been tested operation with popular web servers and proxy servers, verification of Internet Explorer should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Also, some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
None | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 4 | ||
System Clock | ||
03 Nov 1999 | ||
The expected release date for the Internet Explorer 5.0 16-bit Win Year 2000 software update is November 12, 1999. How the product handles dates: Dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. Two-digit shortcut handling: Some web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Internet Explorer assumes that 80 – 99 are 1980 to 1999 and 00 – 35 are 2000 to 2035 and 36 – 70 are 2035. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls may have potential year 2000 issues. Also note: when viewing dates in Internet Explorer for history, true web integration, the display of 4-digit years in Windows or Windows NT needs to be enabled through the regional settings in control panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays a message that they are expired.
Testing guidelines and recommendations: Web sites or web-based applications need to have Internet Explorer, the web server, and if applicable, proxy server test all transition to and operate in the year 2000. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While Internet Explorer has been tested operation with popular web servers and proxy servers, verification of Internet Explorer should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Also, some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
None | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 4 | ||
System Clock | ||
03 Nov 1999 | ||
The expected release date for the Internet Explorer 5.0 16-bit Win Year 2000 software update is November 12, 1999. How the product handles dates: Dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. Two-digit shortcut handling: Some web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Internet Explorer assumes that 80 – 99 are 1980 to 1999 and 00 – 35 are 2000 to 2035 and 36 – 70 are 2035. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls may have potential year 2000 issues. Also note: when viewing dates in Internet Explorer for history, true web integration, the display of 4-digit years in Windows or Windows NT needs to be enabled through the regional settings in control panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays a message that they are expired.
Testing guidelines and recommendations: Web sites or web-based applications need to have Internet Explorer, the web server, and if applicable, proxy server test all transition to and operate in the year 2000. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While Internet Explorer has been tested operation with popular web servers and proxy servers, verification of Internet Explorer should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Also, some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
None | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 4 | ||
System Clock | ||
03 Nov 1999 | ||
The expected release date for the Internet Explorer 5.0 16-bit Win Year 2000 software update is November 12, 1999. How the product handles dates: Dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. Two-digit shortcut handling: Some web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Internet Explorer assumes that 80 – 99 are 1980 to 1999 and 00 – 35 are 2000 to 2035 and 36 – 70 are 2035. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls may have potential year 2000 issues. Also note: when viewing dates in Internet Explorer for history, true web integration, the display of 4-digit years in Windows or Windows NT needs to be enabled through the regional settings in control panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays a message that they are expired.
Testing guidelines and recommendations: Web sites or web-based applications need to have Internet Explorer, the web server, and if applicable, proxy server test all transition to and operate in the year 2000. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While Internet Explorer has been tested operation with popular web servers and proxy servers, verification of Internet Explorer should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Also, some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
None | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 4 | ||
System Clock | ||
03 Nov 1999 | ||
The expected release date for the Internet Explorer 5.0 16-bit Win Year 2000 software update is November 12, 1999. How the product handles dates: Dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. Two-digit shortcut handling: Some web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Internet Explorer assumes that 80 – 99 are 1980 to 1999 and 00 – 35 are 2000 to 2035 and 36 – 70 are 2035. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls may have potential year 2000 issues. Also note: when viewing dates in Internet Explorer for history, true web integration, the display of 4-digit years in Windows or Windows NT needs to be enabled through the regional settings in control panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays a message that they are expired.
Testing guidelines and recommendations: Web sites or web-based applications need to have Internet Explorer, the web server, and if applicable, proxy server test all transition to and operate in the year 2000. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While Internet Explorer has been tested operation with popular web servers and proxy servers, verification of Internet Explorer should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Also, some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
None | ||
MS-DOS, Windows 3.1x, or Windows NT 3.51 SP 4 | ||
System Clock | ||
03 Nov 1999 | ||
The expected release date for the Internet Explorer 5.0 16-bit Win Year 2000 software update is November 12, 1999. How the product handles dates: Dates are stored internally the same as they are for the Win32 FILETIME structures. The FILETIME structure is a 64-bit value. Two-digit shortcut handling: Some web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. Internet Explorer assumes that 80 – 99 are 1980 to 1999 and 00 – 35 are 2000 to 2035 and 36 – 70 are 2035. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, java applets, server scripts, or controls may have potential year 2000 issues. Also note: when viewing dates in Internet Explorer for history, true web integration, the display of 4-digit years in Windows or Windows NT needs to be enabled through the regional settings in control panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays a message that they are expired.
Testing guidelines and recommendations: Web sites or web-based applications need to have Internet Explorer, the web server, and if applicable, proxy server test all transition to and operate in the year 2000. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While Internet Explorer has been tested operation with popular web servers and proxy servers, verification of Internet Explorer should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Also, some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | |||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | |||
Windows 95, or Windows NT4 SP 4 | |||
System Clock, DCOM, COMCTL, OLEAUT32 | |||
07 Oct 1999 | |||
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 4 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
07 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 4 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
07 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 4 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 4 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 4 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
07 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 4 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
07 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 4 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 4 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
07 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 4 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
07 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 4 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
07 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | |||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | |||
Windows 95, or Windows NT4 SP 4 | |||
System Clock, DCOM, COMCTL, OLEAUT32 | |||
07 Oct 1999 | |||
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 4 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 4 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
07 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 4 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
07 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 4 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 4 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 3 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
07 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 3 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
07 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 4 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 4 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 4 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
07 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 4 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
07 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 4 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
07 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000. The update is approximately .5 MB. It will be available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit shortcut in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2049 | ||
Year 2000 Update for IE 3.02, Microsoft Virtual Machine (Build 1520), New Certificates | ||
Windows 95, or Windows NT4 SP 4 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Oct 1999 | ||
What are the Prerequisites for compliance? Users of Internet Explorer 3.02 should install IE 3.02 Year 2000 . The update is approximately .5 MB. It is available at: http://www.microsoft.com/msdownload/iebuild/ie3y2k_win32/en/ie3y2k_win32.htmTo update the Microsoft Virtual Machine to the latest version that fixes the 2-digit issue, please download the Microsoft Virtual Machine.Certificates in IE 3.02 will expire on 12/31/99 disabling Authenticode functionality. To populate your IE 3.02 browser with new certificates, please navigate to http://www.microsoft.com/windows/Ie/security/authenticode.asp. Once the new certificates are installed, code that is signed after 12/31/99 and/or code that is not timed stamped before 12/31/99 will continue to work as expected. The new certificates will expire 12/31/05.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 3 interprets dates entered with a 2-digit in the following way:
Some web sites using older web servers may use HTTP/1.0 headers that have a 2-digit date representation for the year. Web authors may also use a 2-digit year representation for expiration date of cookie data. There is an Issue with the Microsoft Virtual Machine's compliance included with Internet Explorer 3.02:
Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls all may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 2-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. Also note: When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server all transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer team has tested operation with popular web servers and proxy servers, verification of IE should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Update wallet and virtual machine | ||
Windows 95, or Windows NT4 Service Pack 3 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
18 Aug 1999 | ||
Operational Range for Data: 1980-2079 Release Date: September 1997 This document pertains to Arabic Internet Explorer version 4.01. Prerequisites Update wallet and virtual machine How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 4.01 interprets dates entered with a 2-digit shortcut in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Product Issues:
Windows 95 users: Download Windows 95 year 2000 software update. When prompted for "updating IE files as well, go to custom setup and select Wallet. Windows 98 users: To get the wallet update, download Windows 98 year 2000 software update. Windows NT 4.0 Users: Service Pack 5 for Windows NT includes IE wallet 5.0. Make a custom setup of IE5.0 and select Wallet.
Year 2000 issues have been reported in connection with 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 year dates incorrectly. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit year dates. When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While Microsoft has tested operation with popular web servers and proxy servers, verification of Internet Explorer should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
IE 4.01 SP2 & Outlook Express 4.01 year 2000 software update OR IE 4.01 SP1 & additional IE 4.01 SP1 year 2000 software updates listed below & Outlook Express 4.01 year 2000 software update | ||
Windows 95, or Windows NT4 Service Pack 3 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
28 Oct 1999 | ||
Product Maintenance: Microsoft intends to maintain Internet Explorer 4.01 Service Pack 1 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 document pertains to Internet Explorer version 4.01. Internet Explorer 4.0 has date related issues that are resolved by installing Internet Explorer 4.01 from the Internet Explorer download area in addition to the updates recommended below.To determine the version of Internet Explorer that you are currently running, please see Knowledge Base Article Q164539 entitled "Determining which Version of Internet Explorer you are Using".Updated information An issue was identified June 1999 with Outlook Express 4.01. Outlook Express is installed in a standard Internet Explorer Service Pack 1 and Service Pack 2 setup. A software update is available for this issue. Details on the issue can be found below. To address the known year 2000 issues: Install Internet Explorer 4.01 Service Pack 1 with additional updates listed below (#2-5, plus Outlook Express Issue)or Install Internet Explorer 4.01 Service Pack 2* plus with the Outlook Express issue.* SP2 includes updates from SP1 and issues identified below (#2-5)
Product Issues: 1. Issues Resolved by Service Pack 1 Service Pack 1 for Internet Explorer 4.01 resolves the following acceptable deviations with Internet Explorer 4.01:
Other issues with Internet Explorer Individual software Updates for each issue are available as noted – or as part of SP2) 2. MDAC Data Coercion Library (MSDADC.DLL): For older versions of msdadc.dll, the following issue exists: If coding to ADO, AND the ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. THEN Data Convert (msdadc.dll) may translate the date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01 a.m.). If coding directly to OLE DB, the same case exists: If the user is converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98), AND the specified year less than 60, Microsoft recommends going to the latest version of MDAC (version 2.1 Service Pack 1 (2.1.1.3711.11) or higher). An update is available in Internet Explorer 4.01 Service Pack 2 or you can download the latest version MDAC. For more information and to download the latest version of MDAC please go to 3. Microsoft Wallet. 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 1 of the current year. This behavior is changed in Wallet in version 2.1.1383 and later. Note that the Microsoft Wallet product is now known as Microsoft Passport. To resolve this issue, install Microsoft Passport from http://www.passport.com/ and follow the instructions for Get a Free Passport. 4. Date/Time Picker (comctl32.dll). When Regional Settings from Control Panel are set to use 2 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, or use the calendar to choose the date, or update comctl32.dll to the latest version from the location described in the Recommendations section below. Install the latest version of comctl32.dll or update comctl32.dll to the latest version from http://www.microsoft.com/msdownload/ieplatform/ie/comctrlx86.asp. If running Windows NT Alpha download, download the latest version of comctl32.dll from http://www.microsoft.com/msdownload/ieplatform/ie/comctrlalpha.asp. 5. Microsoft Virtual Machine Many versions of the Microsoft Virtual Machine Version, including the VM that ships with Service Pack 1, have year 2000 date related issues. Please refer to the Microsoft Virtual Machine Year 2000 Product Guide Microsoft Virtual Machine for details and recommendations to address issues. Year 2000 issues have been reported in connection with 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. Additional Issues Outlook Express Issue (software update is not part of Internet Explorer 4.01 Service Pack 1 or Service Pack 2) If Outlook Express (OE) 4.01 (SP1 or SP2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than '99', OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as '97', then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year "99" is received and the current year is a multiple of 100 (e.g. 2000), the year will be interpreted as the current year plus 98 (e.g. 2098). For More information, please review Knowledge Base Articles Q234680 or Q234681.A software update is available for this issue. There is a separate update if you are running Outlook Express 4.01 SP1 or Outlook Express 4.01 SP2. The software update is found here.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 4.01 interprets dates entered with a 2-digit shortcut in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired.
Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While Microsoft has tested operation with popular web servers and proxy servers, verification of Internet Explorer should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
IE 4.01 SP2 & Outlook Express 4.01 year 2000 software update OR IE 4.01 SP1 & additional IE 4.01 SP1 year 2000 software updates listed below & Outlook Express 4.01 year 2000 software update | ||
Windows 95, or Windows NT4 Service Pack 3 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
28 Oct 1999 | ||
Product Maintenance: Microsoft intends to maintain Internet Explorer 4.01 Service Pack 1 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 document pertains to Internet Explorer version 4.01. Internet Explorer 4.0 has date related issues that are resolved by installing Internet Explorer 4.01 from the Internet Explorer download area in addition to the updates recommended below.To determine the version of Internet Explorer that you are currently running, please see Knowledge Base Article Q164539 entitled "Determining which Version of Internet Explorer you are Using".Updated information An issue was identified June 1999 with Outlook Express 4.01. Outlook Express is installed in a standard Internet Explorer Service Pack 1 and Service Pack 2 setup. A software update is available for this issue. Details on the issue can be found below. To address the known year 2000 issues: Install Internet Explorer 4.01 Service Pack 1 with additional updates listed below (#2-5, plus Outlook Express Issue)or Install Internet Explorer 4.01 Service Pack 2* plus with the Outlook Express issue.* SP2 includes updates from SP1 and issues identified below (#2-5)
Product Issues: 1. Issues Resolved by Service Pack 1 Service Pack 1 for Internet Explorer 4.01 resolves the following acceptable deviations with Internet Explorer 4.01:
Other issues with Internet Explorer Individual software Updates for each issue are available as noted – or as part of SP2) 2. MDAC Data Coercion Library (MSDADC.DLL): For older versions of msdadc.dll, the following issue exists: If coding to ADO, AND the ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. THEN Data Convert (msdadc.dll) may translate the date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01 a.m.). If coding directly to OLE DB, the same case exists: If the user is converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98), AND the specified year less than 60, Microsoft recommends going to the latest version of MDAC (version 2.1 Service Pack 1 (2.1.1.3711.11) or higher). An update is available in Internet Explorer 4.01 Service Pack 2 or you can download the latest version MDAC. For more information and to download the latest version of MDAC please go to 3. Microsoft Wallet. 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 1 of the current year. This behavior is changed in Wallet in version 2.1.1383 and later. Note that the Microsoft Wallet product is now known as Microsoft Passport. To resolve this issue, install Microsoft Passport from http://www.passport.com/ and follow the instructions for Get a Free Passport. 4. Date/Time Picker (comctl32.dll). When Regional Settings from Control Panel are set to use 2 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, or use the calendar to choose the date, or update comctl32.dll to the latest version from the location described in the Recommendations section below. Install the latest version of comctl32.dll or update comctl32.dll to the latest version from http://www.microsoft.com/msdownload/ieplatform/ie/comctrlx86.asp. If running Windows NT Alpha download, download the latest version of comctl32.dll from http://www.microsoft.com/msdownload/ieplatform/ie/comctrlalpha.asp. 5. Microsoft Virtual Machine Many versions of the Microsoft Virtual Machine Version, including the VM that ships with Service Pack 1, have year 2000 date related issues. Please refer to the Microsoft Virtual Machine Year 2000 Product Guide Microsoft Virtual Machine for details and recommendations to address issues. Year 2000 issues have been reported in connection with 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. Additional Issues Outlook Express Issue (software update is not part of Internet Explorer 4.01 Service Pack 1 or Service Pack 2) If Outlook Express (OE) 4.01 (SP1 or SP2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than '99', OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as '97', then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year "99" is received and the current year is a multiple of 100 (e.g. 2000), the year will be interpreted as the current year plus 98 (e.g. 2098). For More information, please review Knowledge Base Articles Q234680 or Q234681.A software update is available for this issue. There is a separate update if you are running Outlook Express 4.01 SP1 or Outlook Express 4.01 SP2. The software update is found here.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 4.01 interprets dates entered with a 2-digit shortcut in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired.
Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While Microsoft has tested operation with popular web servers and proxy servers, verification of Internet Explorer should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
IE 4.01 SP2 & Outlook Express 4.01 year 2000 software update OR IE 4.01 SP1 & additional IE 4.01 SP1 year 2000 software updates listed below & Outlook Express 4.01 year 2000 software update | ||
Windows 95, or Windows NT4 Service Pack 3 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
28 Oct 1999 | ||
Product Maintenance Microsoft intends to maintain Internet Explorer 4.01 Service Pack 1 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 document pertains to Internet Explorer version 4.01. Internet Explorer 4.0 has date related issues that are resolved by installing Internet Explorer 4.01 from the Internet Explorer download area in addition to the updates recommended below.To determine the version of Internet Explorer that you are currently running, please see Knowledge Base Article Q164539 entitled "Determining which Version of Internet Explorer you are Using".Updated information An issue was identified June 1999 with Outlook Express 4.01. Outlook Express is installed in a standard Internet Explorer SP1 and SP2 setup. A software update is available for this issue. Details on the issue can be found below. To address the known year 2000 issues: Install Internet Explorer 4.01 Service Pack 1 with additional updates listed below (#2-5, plus Outlook Express Issue)or Install Internet Explorer 4.01 Service Pack 2* plus with the Outlook Express issue.* SP2 includes updates from SP1 and issues identified below (#2-5)
Product Issues: 1. Issues Resolved by Service Pack 1 Service Pack 1 for Internet Explorer 4.01 resolves the following acceptable deviations with Internet Explorer 4.01:
Other issues with Internet Explorer Individual software Updates for each issue are available as noted – or as part of SP2) 2. MDAC Data Coercion Library (MSDADC.DLL): For older versions of msdadc.dll, the following issue exists: If coding to ADO, AND the ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. THEN Data Convert (msdadc.dll) may translate the date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01 a.m.). If coding directly to OLE DB, the same case exists: If the user is converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98), AND the specified year less than 60, Microsoft recommends going to the latest version of MDAC (version 2.1 Service Pack 1 (2.1.1.3711.11) or higher). An update is available in Internet Explorer 4.01 Service Pack 2 or you can download the latest version MDAC. For more information and to download the latest version of MDAC please go to 3. Microsoft Wallet. 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 1 of the current year. This behavior is changed in Wallet in version 2.1.1383 and later. Note that the Microsoft Wallet product is now known as Microsoft Passport. To resolve this issue, install Microsoft Passport from http://www.passport.com/ and follow the instructions for Get a Free Passport. 4. Date/Time Picker (comctl32.dll). When Regional Settings from Control Panel are set to use 2 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, or use the calendar to choose the date, or update comctl32.dll to the latest version from the location described in the Recommendations section below. Install the latest version of comctl32.dll or update comctl32.dll to the latest version from http://www.microsoft.com/msdownload/ieplatform/ie/comctrlx86.asp. If running Windows NT Alpha download, download the latest version of comctl32.dll from http://www.microsoft.com/msdownload/ieplatform/ie/comctrlalpha.asp. 5. Microsoft Virtual Machine Many versions of the Microsoft Virtual Machine Version, including the VM that ships with Service Pack 1, have year 2000 date related issues. Please refer to the Microsoft Virtual Machine Year 2000 Product Guide Microsoft Virtual Machine for details and recommendations to address issues. Year 2000 issues have been reported in connection with 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. Additional Issues Outlook Express Issue (software update is not part of IE 4.01 SP1 or SP2) If Outlook Express (OE) 4.01 (SP1 or SP2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than '99', OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as '97', then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year "99" is received and the current year is a multiple of 100 (e.g. 2000), the year will be interpreted as the current year plus 98 (e.g. 2098). For More information, please review Knowledge Base Articles Q234680 or Q234681.When available, the software update will be found here. There is a separate update if you are running Outlook Express 4.01 SP1 or Outlook Express 4.01 SP2.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 4.01 interprets dates entered with a 2-digit shortcut in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired.
Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While Microsoft has tested operation with popular web servers and proxy servers, verification of Internet Explorer should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
IE 4.01 SP2 & Outlook Express 4.01 year 2000 software update OR IE 4.01 SP1 & additional IE 4.01 SP1 year 2000 software updates listed below & Outlook Express 4.01 year 2000 software update | ||
Windows 95, or Windows NT4 Service Pack 3 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
28 Oct 1999 | ||
Product Maintenance Microsoft intends to maintain Internet Explorer 4.01 Service Pack 1 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 document pertains to Internet Explorer version 4.01. Internet Explorer 4.0 has date related issues that are resolved by installing Internet Explorer 4.01 from the Internet Explorer download area in addition to the updates recommended below.To determine the version of Internet Explorer that you are currently running, please see Knowledge Base Article Q164539 entitled "Determining which Version of Internet Explorer you are Using".Updated information An issue was identified June 1999 with Outlook Express 4.01. Outlook Express is installed in a standard Internet Explorer SP1 and SP2 setup. A software update is available for this issue. Details on the issue can be found below. To address the known year 2000 issues: Install Internet Explorer 4.01 Service Pack 1 with additional updates listed below (#2-5, plus Outlook Express Issue)or Install Internet Explorer 4.01 Service Pack 2* plus with the Outlook Express issue.* SP2 includes updates from SP1 and issues identified below (#2-5)
Product Issues: 1. Issues Resolved by Service Pack 1 Service Pack 1 for Internet Explorer 4.01 resolves the following acceptable deviations with Internet Explorer 4.01:
Other issues with Internet Explorer Individual software Updates for each issue are available as noted – or as part of SP2) 2. MDAC Data Coercion Library (MSDADC.DLL): For older versions of msdadc.dll, the following issue exists: If coding to ADO, AND the ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. THEN Data Convert (msdadc.dll) may translate the date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01 a.m.). If coding directly to OLE DB, the same case exists: If the user is converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98), AND the specified year less than 60, Microsoft recommends going to the latest version of MDAC (version 2.1 Service Pack 1 (2.1.1.3711.11) or higher). An update is available in Internet Explorer 4.01 Service Pack 2 or you can download the latest version MDAC. For more information and to download the latest version of MDAC please go to 3. Microsoft Wallet. 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 1 of the current year. This behavior is changed in Wallet in version 2.1.1383 and later. Note that the Microsoft Wallet product is now known as Microsoft Passport. To resolve this issue, install Microsoft Passport from http://www.passport.com/ and follow the instructions for Get a Free Passport. 4. Date/Time Picker (comctl32.dll). When Regional Settings from Control Panel are set to use 2 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, or use the calendar to choose the date, or update comctl32.dll to the latest version from the location described in the Recommendations section below. Install the latest version of comctl32.dll or update comctl32.dll to the latest version from http://www.microsoft.com/msdownload/ieplatform/ie/comctrlx86.asp. If running Windows NT Alpha download, download the latest version of comctl32.dll from http://www.microsoft.com/msdownload/ieplatform/ie/comctrlalpha.asp. 5. Microsoft Virtual Machine Many versions of the Microsoft Virtual Machine Version, including the VM that ships with Service Pack 1, have year 2000 date related issues. Please refer to the Microsoft Virtual Machine Year 2000 Product Guide Microsoft Virtual Machine for details and recommendations to address issues. Year 2000 issues have been reported in connection with 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. Additional Issues Outlook Express Issue (software update is not part of IE 4.01 SP1 or SP2) If Outlook Express (OE) 4.01 (SP1 or SP2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than '99', OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as '97', then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year "99" is received and the current year is a multiple of 100 (e.g. 2000), the year will be interpreted as the current year plus 98 (e.g. 2098). For More information, please review Knowledge Base Articles Q234680 or Q234681.When available, the software update will be found here. There is a separate update if you are running Outlook Express 4.01 SP1 or Outlook Express 4.01 SP2.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 4.01 interprets dates entered with a 2-digit shortcut in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired.
Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While Microsoft has tested operation with popular web servers and proxy servers, verification of Internet Explorer should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
IE 4.01 SP2 & Outlook Express 4.01 year 2000 software update OR IE 4.01 SP1 & additional IE 4.01 SP1 year 2000 software updates listed below & Outlook Express 4.01 year 2000 software update | ||
Windows 95, or Windows NT4 Service Pack 3 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
28 Oct 1999 | ||
Product Maintenance Microsoft intends to maintain Internet Explorer 4.01 Service Pack 1 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 document pertains to Internet Explorer version 4.01. Internet Explorer 4.0 has date related issues that are resolved by installing Internet Explorer 4.01 from the Internet Explorer download area in addition to the updates recommended below.To determine the version of Internet Explorer that you are currently running, please see Knowledge Base Article Q164539 entitled "Determining which Version of Internet Explorer you are Using".Updated information An issue was identified June 1999 with Outlook Express 4.01. Outlook Express is installed in a standard Internet Explorer SP1 and SP2 setup. A software update is available for this issue. Details on the issue can be found below. To address the known year 2000 issues: Install Internet Explorer 4.01 Service Pack 1 with additional updates listed below (#2-5, plus Outlook Express Issue)or Install Internet Explorer 4.01 Service Pack 2* plus with the Outlook Express issue.* SP2 includes updates from SP1 and issues identified below (#2-5)
Product Issues: 1. Issues Resolved by Service Pack 1 Service Pack 1 for Internet Explorer 4.01 resolves the following acceptable deviations with Internet Explorer 4.01:
Other issues with Internet Explorer Individual software Updates for each issue are available as noted – or as part of SP2) 2. MDAC Data Coercion Library (MSDADC.DLL): For older versions of msdadc.dll, the following issue exists: If coding to ADO, AND the ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. THEN Data Convert (msdadc.dll) may translate the date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01 a.m.). If coding directly to OLE DB, the same case exists: If the user is converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98), AND the specified year less than 60, Microsoft recommends going to the latest version of MDAC (version 2.1 Service Pack 1 (2.1.1.3711.11) or higher). An update is available in Internet Explorer 4.01 Service Pack 2 or you can download the latest version MDAC. For more information and to download the latest version of MDAC please go to 3. Microsoft Wallet. 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 1 of the current year. This behavior is changed in Wallet in version 2.1.1383 and later. Note that the Microsoft Wallet product is now known as Microsoft Passport. To resolve this issue, install Microsoft Passport from http://www.passport.com/ and follow the instructions for Get a Free Passport. 4. Date/Time Picker (comctl32.dll). When Regional Settings from Control Panel are set to use 2 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, or use the calendar to choose the date, or update comctl32.dll to the latest version from the location described in the Recommendations section below. Install the latest version of comctl32.dll or update comctl32.dll to the latest version from http://www.microsoft.com/msdownload/ieplatform/ie/comctrlx86.asp. If running Windows NT Alpha download, download the latest version of comctl32.dll from http://www.microsoft.com/msdownload/ieplatform/ie/comctrlalpha.asp. 5. Microsoft Virtual Machine Many versions of the Microsoft Virtual Machine Version, including the VM that ships with Service Pack 1, have year 2000 date related issues. Please refer to the Microsoft Virtual Machine Year 2000 Product Guide Microsoft Virtual Machine for details and recommendations to address issues. Year 2000 issues have been reported in connection with 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. Additional Issues Outlook Express Issue (software update is not part of IE 4.01 SP1 or SP2) If Outlook Express (OE) 4.01 (SP1 or SP2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than '99', OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as '97', then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year "99" is received and the current year is a multiple of 100 (e.g. 2000), the year will be interpreted as the current year plus 98 (e.g. 2098). For More information, please review Knowledge Base Articles Q234680 or Q234681.When available, the software update will be found here. There is a separate update if you are running Outlook Express 4.01 SP1 or Outlook Express 4.01 SP2.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 4.01 interprets dates entered with a 2-digit shortcut in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired.
Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While Microsoft has tested operation with popular web servers and proxy servers, verification of Internet Explorer should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
IE 4.01 SP2 & Outlook Express 4.01 year 2000 software update OR IE 4.01 SP1 & additional IE 4.01 SP1 year 2000 software updates listed below & Outlook Express 4.01 year 2000 software update | ||
Windows 95, or Windows NT4 Service Pack 3 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
28 Oct 1999 | ||
Product Maintenance: Microsoft intends to maintain Internet Explorer 4.01 Service Pack 1 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 document pertains to Internet Explorer version 4.01. Internet Explorer 4.0 has date related issues that are resolved by installing Internet Explorer 4.01 from the Internet Explorer download area in addition to the updates recommended below.To determine the version of Internet Explorer that you are currently running, please see Knowledge Base Article Q164539 entitled "Determining which Version of Internet Explorer you are Using".Updated information An issue was identified June 1999 with Outlook Express 4.01. Outlook Express is installed in a standard Internet Explorer Service Pack 1 and Service Pack 2 setup. A software update is available for this issue. Details on the issue can be found below. To address the known year 2000 issues: Install Internet Explorer 4.01 Service Pack 1 with additional updates listed below (#2-5, plus Outlook Express Issue)or Install Internet Explorer 4.01 Service Pack 2* plus with the Outlook Express issue.* SP2 includes updates from SP1 and issues identified below (#2-5)
Product Issues: 1. Issues Resolved by Service Pack 1 Service Pack 1 for Internet Explorer 4.01 resolves the following acceptable deviations with Internet Explorer 4.01:
Other issues with Internet Explorer Individual software Updates for each issue are available as noted – or as part of SP2) 2. MDAC Data Coercion Library (MSDADC.DLL): For older versions of msdadc.dll, the following issue exists: If coding to ADO, AND the ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. THEN Data Convert (msdadc.dll) may translate the date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01 a.m.). If coding directly to OLE DB, the same case exists: If the user is converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98), AND the specified year less than 60, Microsoft recommends going to the latest version of MDAC (version 2.1 Service Pack 1 (2.1.1.3711.11) or higher). An update is available in Internet Explorer 4.01 Service Pack 2 or you can download the latest version MDAC. For more information and to download the latest version of MDAC please go to 3. Microsoft Wallet. 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 1 of the current year. This behavior is changed in Wallet in version 2.1.1383 and later. Note that the Microsoft Wallet product is now known as Microsoft Passport. To resolve this issue, install Microsoft Passport from http://www.passport.com/ and follow the instructions for Get a Free Passport. 4. Date/Time Picker (comctl32.dll). When Regional Settings from Control Panel are set to use 2 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, or use the calendar to choose the date, or update comctl32.dll to the latest version from the location described in the Recommendations section below. Install the latest version of comctl32.dll or update comctl32.dll to the latest version from http://www.microsoft.com/msdownload/ieplatform/ie/comctrlx86.asp. If running Windows NT Alpha download, download the latest version of comctl32.dll from http://www.microsoft.com/msdownload/ieplatform/ie/comctrlalpha.asp. 5. Microsoft Virtual Machine Many versions of the Microsoft Virtual Machine Version, including the VM that ships with Service Pack 1, have year 2000 date related issues. Please refer to the Microsoft Virtual Machine Year 2000 Product Guide Microsoft Virtual Machine for details and recommendations to address issues. Year 2000 issues have been reported in connection with 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. Additional Issues Outlook Express Issue (software update is not part of Internet Explorer 4.01 Service Pack 1 or Service Pack 2) If Outlook Express (OE) 4.01 (SP1 or SP2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than '99', OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as '97', then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year "99" is received and the current year is a multiple of 100 (e.g. 2000), the year will be interpreted as the current year plus 98 (e.g. 2098). For More information, please review Knowledge Base Articles Q234680 or Q234681.A software update is available for this issue. There is a separate update if you are running Outlook Express 4.01 SP1 or Outlook Express 4.01 SP2. The software update is found here.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 4.01 interprets dates entered with a 2-digit shortcut in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired.
Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While Microsoft has tested operation with popular web servers and proxy servers, verification of Internet Explorer should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
IE 4.01 SP2 & Outlook Express 4.01 year 2000 software update OR IE 4.01 SP1 & additional IE 4.01 SP1 year 2000 software updates listed below & Outlook Express 4.01 year 2000 software update | ||
Windows 95, or Windows NT4 Service Pack 3 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
28 Oct 1999 | ||
Product Maintenance: Microsoft intends to maintain Internet Explorer 4.01 Service Pack 1 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 document pertains to Internet Explorer version 4.01. Internet Explorer 4.0 has date related issues that are resolved by installing Internet Explorer 4.01 from the Internet Explorer download area in addition to the updates recommended below.To determine the version of Internet Explorer that you are currently running, please see Knowledge Base Article Q164539 entitled "Determining which Version of Internet Explorer you are Using".Updated information An issue was identified June 1999 with Outlook Express 4.01. Outlook Express is installed in a standard Internet Explorer Service Pack 1 and Service Pack 2 setup. A software update is available for this issue. Details on the issue can be found below. To address the known year 2000 issues: Install Internet Explorer 4.01 Service Pack 1 with additional updates listed below (#2-5, plus Outlook Express Issue)or Install Internet Explorer 4.01 Service Pack 2* plus with the Outlook Express issue.* SP2 includes updates from SP1 and issues identified below (#2-5)
Product Issues: 1. Issues Resolved by Service Pack 1 Service Pack 1 for Internet Explorer 4.01 resolves the following acceptable deviations with Internet Explorer 4.01:
Other issues with Internet Explorer Individual software Updates for each issue are available as noted – or as part of SP2) 2. MDAC Data Coercion Library (MSDADC.DLL): For older versions of msdadc.dll, the following issue exists: If coding to ADO, AND the ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. THEN Data Convert (msdadc.dll) may translate the date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01 a.m.). If coding directly to OLE DB, the same case exists: If the user is converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98), AND the specified year less than 60, Microsoft recommends going to the latest version of MDAC (version 2.1 Service Pack 1 (2.1.1.3711.11) or higher). An update is available in Internet Explorer 4.01 Service Pack 2 or you can download the latest version MDAC. For more information and to download the latest version of MDAC please go to 3. Microsoft Wallet. 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 1 of the current year. This behavior is changed in Wallet in version 2.1.1383 and later. Note that the Microsoft Wallet product is now known as Microsoft Passport. To resolve this issue, install Microsoft Passport from http://www.passport.com/ and follow the instructions for Get a Free Passport. 4. Date/Time Picker (comctl32.dll). When Regional Settings from Control Panel are set to use 2 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, or use the calendar to choose the date, or update comctl32.dll to the latest version from the location described in the Recommendations section below. Install the latest version of comctl32.dll or update comctl32.dll to the latest version from http://www.microsoft.com/msdownload/ieplatform/ie/comctrlx86.asp. If running Windows NT Alpha download, download the latest version of comctl32.dll from http://www.microsoft.com/msdownload/ieplatform/ie/comctrlalpha.asp. 5. Microsoft Virtual Machine Many versions of the Microsoft Virtual Machine Version, including the VM that ships with Service Pack 1, have year 2000 date related issues. Please refer to the Microsoft Virtual Machine Year 2000 Product Guide Microsoft Virtual Machine for details and recommendations to address issues. Year 2000 issues have been reported in connection with 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. Additional Issues Outlook Express Issue (software update is not part of Internet Explorer 4.01 Service Pack 1 or Service Pack 2) If Outlook Express (OE) 4.01 (SP1 or SP2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than '99', OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as '97', then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year "99" is received and the current year is a multiple of 100 (e.g. 2000), the year will be interpreted as the current year plus 98 (e.g. 2098). For More information, please review Knowledge Base Articles Q234680 or Q234681.A software update is available for this issue. There is a separate update if you are running Outlook Express 4.01 SP1 or Outlook Express 4.01 SP2. The software update is found here.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 4.01 interprets dates entered with a 2-digit shortcut in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired.
Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While Microsoft has tested operation with popular web servers and proxy servers, verification of Internet Explorer should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
IE 4.01 SP2 & Outlook Express 4.01 year 2000 software update OR IE 4.01 SP1 & additional IE 4.01 SP1 year 2000 software updates listed below & Outlook Express 4.01 year 2000 software update | ||
Windows 95, or Windows NT4 Service Pack 3 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
28 Oct 1999 | ||
Product Maintenance Microsoft intends to maintain Internet Explorer 4.01 Service Pack 1 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 document pertains to Internet Explorer version 4.01. Internet Explorer 4.0 has date related issues that are resolved by installing Internet Explorer 4.01 from the Internet Explorer download area in addition to the updates recommended below.To determine the version of Internet Explorer that you are currently running, please see Knowledge Base Article Q164539 entitled "Determining which Version of Internet Explorer you are Using".Updated information An issue was identified June 1999 with Outlook Express 4.01. Outlook Express is installed in a standard Internet Explorer SP1 and SP2 setup. A software update is available for this issue. Details on the issue can be found below. To address the known year 2000 issues: Install Internet Explorer 4.01 Service Pack 1 with additional updates listed below (#2-5, plus Outlook Express Issue)or Install Internet Explorer 4.01 Service Pack 2* plus with the Outlook Express issue.* SP2 includes updates from SP1 and issues identified below (#2-5)
Product Issues: 1. Issues Resolved by Service Pack 1 Service Pack 1 for Internet Explorer 4.01 resolves the following acceptable deviations with Internet Explorer 4.01:
Other issues with Internet Explorer Individual software Updates for each issue are available as noted – or as part of SP2) 2. MDAC Data Coercion Library (MSDADC.DLL): For older versions of msdadc.dll, the following issue exists: If coding to ADO, AND the ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. THEN Data Convert (msdadc.dll) may translate the date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01 a.m.). If coding directly to OLE DB, the same case exists: If the user is converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98), AND the specified year less than 60, Microsoft recommends going to the latest version of MDAC (version 2.1 Service Pack 1 (2.1.1.3711.11) or higher). An update is available in Internet Explorer 4.01 Service Pack 2 or you can download the latest version MDAC. For more information and to download the latest version of MDAC please go to 3. Microsoft Wallet. 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 1 of the current year. This behavior is changed in Wallet in version 2.1.1383 and later. Note that the Microsoft Wallet product is now known as Microsoft Passport. To resolve this issue, install Microsoft Passport from http://www.passport.com/ and follow the instructions for Get a Free Passport. 4. Date/Time Picker (comctl32.dll). When Regional Settings from Control Panel are set to use 2 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, or use the calendar to choose the date, or update comctl32.dll to the latest version from the location described in the Recommendations section below. Install the latest version of comctl32.dll or update comctl32.dll to the latest version from http://www.microsoft.com/msdownload/ieplatform/ie/comctrlx86.asp. If running Windows NT Alpha download, download the latest version of comctl32.dll from http://www.microsoft.com/msdownload/ieplatform/ie/comctrlalpha.asp. 5. Microsoft Virtual Machine Many versions of the Microsoft Virtual Machine Version, including the VM that ships with Service Pack 1, have year 2000 date related issues. Please refer to the Microsoft Virtual Machine Year 2000 Product Guide Microsoft Virtual Machine for details and recommendations to address issues. Year 2000 issues have been reported in connection with 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. Additional Issues Outlook Express Issue (software update is not part of IE 4.01 SP1 or SP2) If Outlook Express (OE) 4.01 (SP1 or SP2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than '99', OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as '97', then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year "99" is received and the current year is a multiple of 100 (e.g. 2000), the year will be interpreted as the current year plus 98 (e.g. 2098). For More information, please review Knowledge Base Articles Q234680 or Q234681.When available, the software update will be found here. There is a separate update if you are running Outlook Express 4.01 SP1 or Outlook Express 4.01 SP2.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 4.01 interprets dates entered with a 2-digit shortcut in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired.
Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While Microsoft has tested operation with popular web servers and proxy servers, verification of Internet Explorer should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
IE 4.01 SP2 & Outlook Express 4.01 year 2000 software update OR IE 4.01 SP1 & additional IE 4.01 SP1 year 2000 software updates listed below & Outlook Express 4.01 year 2000 software update | ||
Windows 95, or Windows NT4 Service Pack 3 | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
28 Oct 1999 | ||
Product Maintenance Microsoft intends to maintain Internet Explorer 4.01 Service Pack 1 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 document pertains to Internet Explorer version 4.01. Internet Explorer 4.0 has date related issues that are resolved by installing Internet Explorer 4.01 from the Internet Explorer download area in addition to the updates recommended below.To determine the version of Internet Explorer that you are currently running, please see Knowledge Base Article Q164539 entitled "Determining which Version of Internet Explorer you are Using".Updated information An issue was identified June 1999 with Outlook Express 4.01. Outlook Express is installed in a standard Internet Explorer SP1 and SP2 setup. A software update is available for this issue. Details on the issue can be found below. To address the known year 2000 issues: Install Internet Explorer 4.01 Service Pack 1 with additional updates listed below (#2-5, plus Outlook Express Issue)or Install Internet Explorer 4.01 Service Pack 2* plus with the Outlook Express issue.* SP2 includes updates from SP1 and issues identified below (#2-5)
Product Issues: 1. Issues Resolved by Service Pack 1 Service Pack 1 for Internet Explorer 4.01 resolves the following acceptable deviations with Internet Explorer 4.01:
Other issues with Internet Explorer Individual software Updates for each issue are available as noted – or as part of SP2) 2. MDAC Data Coercion Library (MSDADC.DLL): For older versions of msdadc.dll, the following issue exists: If coding to ADO, AND the ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. THEN Data Convert (msdadc.dll) may translate the date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01 a.m.). If coding directly to OLE DB, the same case exists: If the user is converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98), AND the specified year less than 60, Microsoft recommends going to the latest version of MDAC (version 2.1 Service Pack 1 (2.1.1.3711.11) or higher). An update is available in Internet Explorer 4.01 Service Pack 2 or you can download the latest version MDAC. For more information and to download the latest version of MDAC please go to 3. Microsoft Wallet. 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 1 of the current year. This behavior is changed in Wallet in version 2.1.1383 and later. Note that the Microsoft Wallet product is now known as Microsoft Passport. To resolve this issue, install Microsoft Passport from http://www.passport.com/ and follow the instructions for Get a Free Passport. 4. Date/Time Picker (comctl32.dll). When Regional Settings from Control Panel are set to use 2 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, or use the calendar to choose the date, or update comctl32.dll to the latest version from the location described in the Recommendations section below. Install the latest version of comctl32.dll or update comctl32.dll to the latest version from http://www.microsoft.com/msdownload/ieplatform/ie/comctrlx86.asp. If running Windows NT Alpha download, download the latest version of comctl32.dll from http://www.microsoft.com/msdownload/ieplatform/ie/comctrlalpha.asp. 5. Microsoft Virtual Machine Many versions of the Microsoft Virtual Machine Version, including the VM that ships with Service Pack 1, have year 2000 date related issues. Please refer to the Microsoft Virtual Machine Year 2000 Product Guide Microsoft Virtual Machine for details and recommendations to address issues. Year 2000 issues have been reported in connection with 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. Additional Issues Outlook Express Issue (software update is not part of IE 4.01 SP1 or SP2) If Outlook Express (OE) 4.01 (SP1 or SP2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than '99', OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as '97', then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year "99" is received and the current year is a multiple of 100 (e.g. 2000), the year will be interpreted as the current year plus 98 (e.g. 2098). For More information, please review Knowledge Base Articles Q234680 or Q234681.When available, the software update will be found here. There is a separate update if you are running Outlook Express 4.01 SP1 or Outlook Express 4.01 SP2.How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: Microsoft Internet Explorer 4.01 interprets dates entered with a 2-digit shortcut in the following way: 1/1/00 through 12/31/79 are interpreted as 1/1/2000 through 12/31/2079 1/1/80 through 12/31/99 are interpreted as 1/1/1980 through 12/31/1999 Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, JSCRIPT, Java applets, server scripts, or controls may have potential Year 2000 issues. The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. When viewing dates in Internet Explorer for history, the display of 4-digit years in Windows or Windows NT needs to be enabled through the Regional Settings in Control Panel. If testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired.
Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer, the web server, and if applicable, proxy server transition to operate in the year 2000 under testing. For example, some web and proxy server may use a 2-digit year in its HTTP/1.0 headers. While Microsoft has tested operation with popular web servers and proxy servers, verification of Internet Explorer should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their Year 2000 status and recommendations. Some potential year 2000 issues may be content-specific. You should ensure that interactive sites can handle the year 2000 in their web page HTML content, cookies, JSCRIPT, Java applets, server scripts, or controls.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
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://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.
|
||
Wednesday, November 17, 1999 © 1999 Microsoft Corporation. All rights reserved. Terms of use. This site is being designated as a Year 2000 Readiness Disclosure and the information contained herein is provided pursuant to the terms hereof and the Year 2000 Information and Readiness Disclosure Act. |