- | ||
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. |
- | ||
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 Hebrew Internet Explorer version 4.01. Product Details 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 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 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. |
- | ||
Internet Explorer Service Pack 2 OR Internet Explorer 4.01 Service Pack 1, Updated MSDADC.dll, Microsoft Wallet 2.1.1383 or later, Updated comctl32.dll 4.70.3110.9 or later, Updated Microsoft Virtual Machine | ||
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 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 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 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. |
- | ||
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 Thai Internet Explorer version 4.01. Product Details Prerequisite Update wallet or 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. |
- | ||
Internet Explorer 4.01 Service Pack 1, Updated MSDADC.dll, Microsoft Wallet 2.1.1383 or later, Updated comctl32.dll 4.70.3110.9 or later, Updated Microsoft Virtual Machine | ||
Windows 95, or Windows NT4 Service Pack 3 | ||
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. |
01 Jan 1980 - 31 Dec 2035 | ||
None | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Hebrew you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/EW/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLLs to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
- | ||
None | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher, MFC40.DLL | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
None | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
None | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1980 - 31 Dec 2035 | ||
none | ||
Windows 95 or higher, Windows NT Service Pack 3 or higher | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
01 Nov 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Depending on the installation options you select, some system components may not be updated when you install Internet Explorer 5 and Internet Tools. To minimize download size, Internet Explorer only upgrades certain components when they are explicitly selected. For example, if you select a minimal installation option for Internet Explorer 5 over a system with Internet Explorer 4, then the Microsoft Virtual Machine, NetMeeting, and Outlook Express are not updated and remain the Internet Explorer 4 versions. To ensure that all components have been updated, select the Full installation option when you install Internet Explorer 5. For more information, please consult this Knowledge Base Article.Release Date: March 1999 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 5.0 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:
To get updated versions of MFC40.DLL/MFC40U.DLL: If you are running Windows 95 - the software update for MFC40.DLL is included in the Windows 95 Year 2000 update which is available If are running Windows 98 - http://windowsupdate.microsoft.com. Select Windows 98 Year 2000 Update for the appropriate language version.If you are running Windows NT Workstation, localized versions of this software update are available for download off the FTP site. Choose your language, then choose /nt40/hotfixes-postSP4/y2kupd/. For example, to download the update for Brazilian Portuguese you would go to ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/bra/nt40/hotfixes-postSP4/y2kupd/. Please see the Readme file for an index of 3 letter language abbreviations.
Description of MFC40.DLL issue: MFC40.DLL Causes Programs to Display Wrong Date after 01/01/2000. ( Q218877)MFC40.DLL and MFC40U.DLL: Programs using one of these DLL's to represent dates may interpret a year 2000 and later date incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document that will be posting soon. 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 onward. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. 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. Note that 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 servers 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. |
01 Jan 1904 - 31 Dec 2035 | ||
none | ||
Macintosh operating system 7.1 or higher | ||
System Clock | ||
18 Sep 1999 | ||
How the product handles dates: All dates are stored internally as a 32bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: 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. Microsoft Internet Explorer 3.01 for Mac interprets dates entered with a two-digit shortcut in the following way:
How is the product not compliant?
JavaScript:
Recommendations to meet compliance: Upgrade to Internet Explorer 4.01 http://www.microsoft.com/msdownload/iebuild/ie401_mac/en/ie401_mac.htmCommon 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 the year 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. 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. For example, some web and proxy servers 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 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. |
01 Jan 1904 - 31 Dec 2035 | ||
none | ||
Macintosh operating system 7.1 or higher | ||
System Clock | ||
18 Sep 1999 | ||
How the product handles dates: All dates are stored internally as a 32bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: 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. Microsoft Internet Explorer 3.01 for Mac interprets dates entered with a two-digit shortcut in the following way:
How is the product not compliant?
JavaScript:
Recommendations to meet compliance: Upgrade to Internet Explorer 4.01 http://www.microsoft.com/msdownload/iebuild/ie401_mac/en/ie401_mac.htmCommon 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 the year 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. 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. For example, some web and proxy servers 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 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. |
01 Jan 1904 - 31 Dec 2035 | ||
none | ||
Macintosh operating system 7.1 or higher | ||
System Clock | ||
18 Sep 1999 | ||
How the product handles dates: All dates are stored internally as a 32bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: 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. Microsoft Internet Explorer 3.01 for Mac interprets dates entered with a two-digit shortcut in the following way:
How is the product not compliant?
JavaScript:
Recommendations to meet compliance: Upgrade to Internet Explorer 4.01 http://www.microsoft.com/msdownload/iebuild/ie401_mac/en/ie401_mac.htmCommon 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 the year 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. 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. For example, some web and proxy servers 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 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. |
01 Jan 1904 - 31 Dec 2035 | ||
none | ||
Macintosh operating system 7.1 or higher | ||
System Clock | ||
18 Sep 1999 | ||
How the product handles dates: All dates are stored internally as a 32bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: 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. Microsoft Internet Explorer 3.01 for Mac interprets dates entered with a two-digit shortcut in the following way:
How is the product not compliant?
JavaScript:
Recommendations to meet compliance: Upgrade to Internet Explorer 4.01 http://www.microsoft.com/msdownload/iebuild/ie401_mac/en/ie401_mac.htmCommon 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 the year 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. 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. For example, some web and proxy servers 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 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. |
01 Jan 1904 - 31 Dec 2035 | ||
none | ||
Macintosh operating system 7.1 or higher | ||
System Clock | ||
18 Sep 1999 | ||
How the product handles dates: All dates are stored internally as a 32bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: 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. Microsoft Internet Explorer 3.01 for Mac interprets dates entered with a two-digit shortcut in the following way:
How is the product not compliant?
JavaScript:
Recommendations to meet compliance: Upgrade to Internet Explorer 4.01 http://www.microsoft.com/msdownload/iebuild/ie401_mac/en/ie401_mac.htmCommon 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 the year 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. 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. For example, some web and proxy servers 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 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. |
01 Jan 1904 - 31 Dec 2035 | ||
none | ||
Macintosh operating system 7.1 or higher | ||
System Clock | ||
18 Sep 1999 | ||
How the product handles dates: All dates are stored internally as a 32bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: 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. Microsoft Internet Explorer 3.01 for Mac interprets dates entered with a two-digit shortcut in the following way:
How is the product not compliant?
JavaScript:
Recommendations to meet compliance: Upgrade to Internet Explorer 4.01 http://www.microsoft.com/msdownload/iebuild/ie401_mac/en/ie401_mac.htmCommon 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 the year 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. 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. For example, some web and proxy servers 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 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. |
01 Jan 1904 - 31 Dec 2035 | ||
none | ||
Macintosh operating system 7.1 or higher | ||
System Clock | ||
18 Sep 1999 | ||
How the product handles dates: All dates are stored internally as a 32bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: 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. Microsoft Internet Explorer 3.01 for Mac interprets dates entered with a two-digit shortcut in the following way:
How is the product not compliant?
JavaScript:
Recommendations to meet compliance: Upgrade to Internet Explorer 4.01 http://www.microsoft.com/msdownload/iebuild/ie401_mac/en/ie401_mac.htmCommon 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 the year 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. 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. For example, some web and proxy servers 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 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. |
01 Jan 1904 - 31 Dec 2035 | ||
none | ||
Macintosh operating system 7.1 or higher | ||
System Clock | ||
18 Sep 1999 | ||
How the product handles dates: All dates are stored internally as a 32bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: 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. Microsoft Internet Explorer 3.01 for Mac interprets dates entered with a two-digit shortcut in the following way:
How is the product not compliant?
JavaScript:
Recommendations to meet compliance: Upgrade to Internet Explorer 4.01 http://www.microsoft.com/msdownload/iebuild/ie401_mac/en/ie401_mac.htmCommon 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 the year 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. 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. For example, some web and proxy servers 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 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. |
01 Jan 1904 - 31 Dec 2035 | ||
none | ||
Macintosh operating system 7.1 or higher | ||
System Clock | ||
18 Sep 1999 | ||
How the product handles dates: All dates are stored internally as a 32bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: 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. Microsoft Internet Explorer 3.01 for Mac interprets dates entered with a two-digit shortcut in the following way:
How is the product not compliant?
JavaScript:
Recommendations to meet compliance: Upgrade to Internet Explorer 4.01 http://www.microsoft.com/msdownload/iebuild/ie401_mac/en/ie401_mac.htmCommon 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 the year 2000. Web authors can use the method .getFullYear(), which always returns 4-digit dates. 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. For example, some web and proxy servers 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 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. |
01 Jan 1904 - 31 Dec 2035 | ||
none | ||
Macintosh Operating System, 7.1 or higher | ||
System Clock | ||
19 Oct 1999 | ||
How the product handles dates: Dates are stored internally as a 32-bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 for Mac interprets dates entered with a 2-digit shortcut to mean the in the following way: Any value less than 50 will be interpreted as 20XX and 50 or greater as 19XX. 1/1/00 through 12/31/49 are interpreted as 1/1/2000 through 12/31/2049 1/1/50 through 12/31/99 are interpreted as 1/1/1950 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4-digit representation to the server. If the server requires 2-digit representation, Internet Explorer will send it in 2-digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described above. 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. 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. 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 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. |
01 Jan 1904 - 31 Dec 2035 | ||
none | ||
Macintosh Operating System, 7.1 or higher | ||
System Clock | ||
19 Oct 1999 | ||
How the product handles dates: Dates are stored internally as a 32-bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 for Mac interprets dates entered with a 2-digit shortcut to mean the in the following way: Any value less than 50 will be interpreted as 20XX and 50 or greater as 19XX. 1/1/00 through 12/31/49 are interpreted as 1/1/2000 through 12/31/2049 1/1/50 through 12/31/99 are interpreted as 1/1/1950 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4-digit representation to the server. If the server requires 2-digit representation, Internet Explorer will send it in 2-digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described above. 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. 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. 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 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. |
01 Jan 1904 - 31 Dec 2035 | ||
none | ||
Macintosh Operating System, 7.1 or higher | ||
System clock | ||
19 Oct 1999 | ||
How the product handles dates: Dates are stored internally as a 32-bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 for Mac interprets dates entered with a 2-digit shortcut to mean the in the following way: Any value less than 50 will be interpreted as 20XX and 50 or greater as 19XX. 1/1/00 through 12/31/49 are interpreted as 1/1/2000 through 12/31/2049 1/1/50 through 12/31/99 are interpreted as 1/1/1950 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4-digit representation to the server. If the server requires 2-digit representation, Internet Explorer will send it in 2-digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described above. 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. 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. 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 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. |
01 Jan 1904 - 31 Dec 2035 | ||
none | ||
Macintosh Operating System, 7.1 or higher | ||
System Clock | ||
19 Oct 1999 | ||
How the product handles dates: Dates are stored internally as a 32-bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 for Mac interprets dates entered with a 2-digit shortcut to mean the in the following way: Any value less than 50 will be interpreted as 20XX and 50 or greater as 19XX. 1/1/00 through 12/31/49 are interpreted as 1/1/2000 through 12/31/2049 1/1/50 through 12/31/99 are interpreted as 1/1/1950 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4-digit representation to the server. If the server requires 2-digit representation, Internet Explorer will send it in 2-digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described above. 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. 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. 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 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. |
01 Jan 1904 - 31 Dec 2035 | ||
none | ||
Macintosh Operating System, 7.1 or higher | ||
System Clock | ||
19 Oct 1999 | ||
How the product handles dates: Dates are stored internally as a 32-bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 for Mac interprets dates entered with a 2-digit shortcut to mean the in the following way: Any value less than 50 will be interpreted as 20XX and 50 or greater as 19XX. 1/1/00 through 12/31/49 are interpreted as 1/1/2000 through 12/31/2049 1/1/50 through 12/31/99 are interpreted as 1/1/1950 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4-digit representation to the server. If the server requires 2-digit representation, Internet Explorer will send it in 2-digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described above. 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. 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. 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 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. |
01 Jan 1904 - 31 Dec 2035 | ||
none | ||
Macintosh Operating System, 7.1 or higher | ||
System clock | ||
19 Oct 1999 | ||
How the product handles dates: Dates are stored internally as a 32-bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 for Mac interprets dates entered with a 2-digit shortcut to mean the in the following way: Any value less than 50 will be interpreted as 20XX and 50 or greater as 19XX. 1/1/00 through 12/31/49 are interpreted as 1/1/2000 through 12/31/2049 1/1/50 through 12/31/99 are interpreted as 1/1/1950 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4-digit representation to the server. If the server requires 2-digit representation, Internet Explorer will send it in 2-digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described above. 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. 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. 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 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. |
01 Jan 1904 - 31 Dec 2035 | ||
none | ||
Macintosh Operating System, 7.1 or higher | ||
System clock | ||
18 Sep 1999 | ||
How the product handles dates: Dates are stored internally as a 32-bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 for Mac interprets dates entered with a 2-digit shortcut to mean the in the following way: Any value less than 50 will be interpreted as 20XX and 50 or greater as 19XX. 1/1/00 through 12/31/49 are interpreted as 1/1/2000 through 12/31/2049 1/1/50 through 12/31/99 are interpreted as 1/1/1950 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4-digit representation to the server. If the server requires 2-digit representation, Internet Explorer will send it in 2-digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described above. 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. 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. 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 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. |
01 Jan 1904 - 31 Dec 2035 | ||
none | ||
Macintosh Operating System, 7.1 or higher | ||
System clock | ||
19 Oct 1999 | ||
How the product handles dates: Dates are stored internally as a 32-bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 for Mac interprets dates entered with a 2-digit shortcut to mean the in the following way: Any value less than 50 will be interpreted as 20XX and 50 or greater as 19XX. 1/1/00 through 12/31/49 are interpreted as 1/1/2000 through 12/31/2049 1/1/50 through 12/31/99 are interpreted as 1/1/1950 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4-digit representation to the server. If the server requires 2-digit representation, Internet Explorer will send it in 2-digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described above. 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. 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. 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 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. |
01 Jan 1904 - 31 Dec 2035 | ||
none | ||
Macintosh Operating System, 7.1 or higher | ||
System clock | ||
19 Oct 1999 | ||
How the product handles dates: Dates are stored internally as a 32-bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: Microsoft Internet Explorer 4.0/4.01 for Mac interprets dates entered with a 2-digit shortcut to mean the in the following way: Any value less than 50 will be interpreted as 20XX and 50 or greater as 19XX. 1/1/00 through 12/31/49 are interpreted as 1/1/2000 through 12/31/2049 1/1/50 through 12/31/99 are interpreted as 1/1/1950 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4-digit representation to the server. If the server requires 2-digit representation, Internet Explorer will send it in 2-digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described above. 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. 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. 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 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. |
01 Jan 1904 - 31 Dec 2035 | ||
none | ||
Mac OS, 7.1 or higher | ||
System Clock | ||
18 Sep 1999 | ||
Description of how the product handles dates: All dates are stored internally as a 32bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. 2-digit shortcut handling: Microsoft Internet Explorer 4.0 for Mac interprets dates entered with a 2-digit shortcut to mean the in the following way: Any value less than 50 will be interpreted as 20XX and greater than 50 as 19XX. 1/1/00 through 12/31/49 are interpreted as 1/1/2000 through 12/31/2049 1/1/50 through 12/31/99 are interpreted as 1/1/1950 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4 digit representation to the server. If the server requires 2 digit representation, Internet Explorer will send it in 2 digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described 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. 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. 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. 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 1904 - 31 Dec 2035 | ||
none | ||
Mac OS, 7.1 or higher | ||
System Clock | ||
18 Sep 1999 | ||
Description of how the product handles dates: All dates are stored internally as a 32bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. 2-digit shortcut handling: Microsoft Internet Explorer 4.0 for Mac interprets dates entered with a 2-digit shortcut to mean the in the following way: Any value less than 50 will be interpreted as 20XX and greater than 50 as 19XX. 1/1/00 through 12/31/49 are interpreted as 1/1/2000 through 12/31/2049 1/1/50 through 12/31/99 are interpreted as 1/1/1950 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4 digit representation to the server. If the server requires 2 digit representation, Internet Explorer will send it in 2 digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described 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. 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. 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. 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 1904 - 31 Dec 2035 | ||
none | ||
Mac OS, 7.1 or higher | ||
System Clock | ||
18 Sep 1999 | ||
Description of how the product handles dates: All dates are stored internally as a 32bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. 2-digit shortcut handling: Microsoft Internet Explorer 4.0 for Mac interprets dates entered with a 2-digit shortcut to mean the in the following way: Any value less than 50 will be interpreted as 20XX and greater than 50 as 19XX. 1/1/00 through 12/31/49 are interpreted as 1/1/2000 through 12/31/2049 1/1/50 through 12/31/99 are interpreted as 1/1/1950 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4 digit representation to the server. If the server requires 2 digit representation, Internet Explorer will send it in 2 digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described 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. 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. 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. 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 1904 - 31 Dec 2035 | ||
none | ||
Mac OS, 7.1 or higher | ||
System Clock | ||
18 Sep 1999 | ||
Description of how the product handles dates: All dates are stored internally as a 32bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. 2-digit shortcut handling: Microsoft Internet Explorer 4.0 for Mac interprets dates entered with a 2-digit shortcut to mean the in the following way: Any value less than 50 will be interpreted as 20XX and greater than 50 as 19XX. 1/1/00 through 12/31/49 are interpreted as 1/1/2000 through 12/31/2049 1/1/50 through 12/31/99 are interpreted as 1/1/1950 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4 digit representation to the server. If the server requires 2 digit representation, Internet Explorer will send it in 2 digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described 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. 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. 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. 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 1904 - 31 Dec 2035 | ||
none | ||
Mac OS, 7.1 or higher | ||
System Clock | ||
18 Sep 1999 | ||
Description of how the product handles dates: All dates are stored internally as a 32bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. 2-digit shortcut handling: Microsoft Internet Explorer 4.0 for Mac interprets dates entered with a 2-digit shortcut to mean the in the following way: Any value less than 50 will be interpreted as 20XX and greater than 50 as 19XX. 1/1/00 through 12/31/49 are interpreted as 1/1/2000 through 12/31/2049 1/1/50 through 12/31/99 are interpreted as 1/1/1950 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4 digit representation to the server. If the server requires 2 digit representation, Internet Explorer will send it in 2 digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described 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. 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. 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. 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 1904 - 31 Dec 2035 | ||
none | ||
Mac OS, 7.1 or higher | ||
System Clock | ||
18 Sep 1999 | ||
Description of how the product handles dates: All dates are stored internally as a 32bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. 2-digit shortcut handling: Microsoft Internet Explorer 4.0 for Mac interprets dates entered with a 2-digit shortcut to mean the in the following way: Any value less than 50 will be interpreted as 20XX and greater than 50 as 19XX. 1/1/00 through 12/31/49 are interpreted as 1/1/2000 through 12/31/2049 1/1/50 through 12/31/99 are interpreted as 1/1/1950 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4 digit representation to the server. If the server requires 2 digit representation, Internet Explorer will send it in 2 digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described 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. 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. 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. 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 1904 - 31 Dec 2035 | ||
none | ||
Mac OS, 7.1 or higher | ||
System Clock | ||
18 Sep 1999 | ||
Description of how the product handles dates: All dates are stored internally as a 32bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. 2-digit shortcut handling: Microsoft Internet Explorer 4.0 for Mac interprets dates entered with a 2-digit shortcut to mean the in the following way: Any value less than 50 will be interpreted as 20XX and greater than 50 as 19XX. 1/1/00 through 12/31/49 are interpreted as 1/1/2000 through 12/31/2049 1/1/50 through 12/31/99 are interpreted as 1/1/1950 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4 digit representation to the server. If the server requires 2 digit representation, Internet Explorer will send it in 2 digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described 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. 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. 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. 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 1904 - 31 Dec 2035 | ||
none | ||
Mac OS, 7.1 or higher | ||
System Clock | ||
18 Sep 1999 | ||
Description of how the product handles dates: All dates are stored internally as a 32bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. 2-digit shortcut handling: Microsoft Internet Explorer 4.0 for Mac interprets dates entered with a 2-digit shortcut to mean the in the following way: Any value less than 50 will be interpreted as 20XX and greater than 50 as 19XX. 1/1/00 through 12/31/49 are interpreted as 1/1/2000 through 12/31/2049 1/1/50 through 12/31/99 are interpreted as 1/1/1950 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4 digit representation to the server. If the server requires 2 digit representation, Internet Explorer will send it in 2 digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described 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. 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. 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. 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 1904 - 31 Dec 2035 | ||
none | ||
Mac OS, 7.1 or higher | ||
System Clock | ||
18 Sep 1999 | ||
Description of how the product handles dates: All dates are stored internally as a 32bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. 2-digit shortcut handling: Microsoft Internet Explorer 4.0 for Mac interprets dates entered with a 2-digit shortcut to mean the in the following way: Any value less than 50 will be interpreted as 20XX and greater than 50 as 19XX. 1/1/00 through 12/31/49 are interpreted as 1/1/2000 through 12/31/2049 1/1/50 through 12/31/99 are interpreted as 1/1/1950 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4 digit representation to the server. If the server requires 2 digit representation, Internet Explorer will send it in 2 digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described 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. 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. 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. 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 1904 - 31 Dec 2035 | ||
none | ||
Mac OS, 7.1 or higher | ||
System Clock | ||
18 Sep 1999 | ||
Description of how the product handles dates: All dates are stored internally as a 32bit integer in Mac OS time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. 2-digit shortcut handling: Microsoft Internet Explorer 4.0 for Mac interprets dates entered with a 2-digit shortcut to mean the in the following way: Any value less than 50 will be interpreted as 20XX and greater than 50 as 19XX. 1/1/00 through 12/31/49 are interpreted as 1/1/2000 through 12/31/2049 1/1/50 through 12/31/99 are interpreted as 1/1/1950 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4 digit representation to the server. If the server requires 2 digit representation, Internet Explorer will send it in 2 digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described 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. 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. 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. 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 1904 - 31 Dec 2035 | ||
None | ||
Macintosh Operating System 7.5 or higher | ||
System Clock | ||
23 Sep 1999 | ||
How the product handles dates: Dates are stored internally as a 32-bit integer in Macintosh operating system time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: Microsoft Internet Explorer 4.5 for Macintosh interprets dates entered with a 2-digit shortcut to mean the in the following way: Two-Digit years 00 through 49 are interpreted as 2000 through 2049. Two-Digit years 50 through 99 are interpreted as 1950 through 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4-digit representation to the server. If the server requires 2-digit representation, Internet Explorer will send it in 2-digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described above. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, server certificates, 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. The X.509 specification for certificates requires the valid date range to be described using two-digit years through the year 2049. Four-digit year format is not to be used until 2050 and later. These issues, combined with the fact than many secure certificates are set to expire at midnight, December 31, 1999 should be considered by web site administrators to prevent interruption of service to their customers. 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. 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 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, server certificates, 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 1904 - 31 Dec 2035 | ||
None | ||
Macintosh Operating System 7.5 or higher | ||
System Clock | ||
23 Sep 1999 | ||
How the product handles dates: Dates are stored internally as a 32-bit integer in Macintosh operating system time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: Microsoft Internet Explorer 4.5 for Macintosh interprets dates entered with a 2-digit shortcut to mean the in the following way: Two-Digit years 00 through 49 are interpreted as 2000 through 2049. Two-Digit years 50 through 99 are interpreted as 1950 through 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4-digit representation to the server. If the server requires 2-digit representation, Internet Explorer will send it in 2-digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described above. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, server certificates, 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. The X.509 specification for certificates requires the valid date range to be described using two-digit years through the year 2049. Four-digit year format is not to be used until 2050 and later. These issues, combined with the fact than many secure certificates are set to expire at midnight, December 31, 1999 should be considered by web site administrators to prevent interruption of service to their customers. 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. 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 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, server certificates, 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 1904 - 31 Dec 2035 | ||
None | ||
Macintosh Operating System 7.5 or higher | ||
System Clock | ||
23 Sep 1999 | ||
How the product handles dates: Dates are stored internally as a 32-bit integer in Macintosh operating system time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: Microsoft Internet Explorer 4.5 for Macintosh interprets dates entered with a 2-digit shortcut to mean the in the following way: Two-Digit years 00 through 49 are interpreted as 2000 through 2049. Two-Digit years 50 through 99 are interpreted as 1950 through 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4-digit representation to the server. If the server requires 2-digit representation, Internet Explorer will send it in 2-digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described above. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, server certificates, 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. The X.509 specification for certificates requires the valid date range to be described using two-digit years through the year 2049. Four-digit year format is not to be used until 2050 and later. These issues, combined with the fact than many secure certificates are set to expire at midnight, December 31, 1999 should be considered by web site administrators to prevent interruption of service to their customers. 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. 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 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, server certificates, 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 1904 - 31 Dec 2035 | ||
None | ||
Macintosh Operating System 7.5 or higher | ||
System Clock | ||
23 Sep 1999 | ||
How the product handles dates: Dates are stored internally as a 32-bit integer in Macintosh operating system time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: Microsoft Internet Explorer 4.5 for Macintosh interprets dates entered with a 2-digit shortcut to mean the in the following way: Two-Digit years 00 through 49 are interpreted as 2000 through 2049. Two-Digit years 50 through 99 are interpreted as 1950 through 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4-digit representation to the server. If the server requires 2-digit representation, Internet Explorer will send it in 2-digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described above. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, server certificates, 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. The X.509 specification for certificates requires the valid date range to be described using two-digit years through the year 2049. Four-digit year format is not to be used until 2050 and later. These issues, combined with the fact than many secure certificates are set to expire at midnight, December 31, 1999 should be considered by web site administrators to prevent interruption of service to their customers. 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. 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 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, server certificates, 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 1904 - 31 Dec 2035 | ||
None | ||
Macintosh Operating System 7.5 or higher | ||
System clock | ||
23 Sep 1999 | ||
How the product handles dates: Dates are stored internally as a 32-bit integer in Macintosh operating system time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: Microsoft Internet Explorer 4.5 for Macintosh interprets dates entered with a 2-digit shortcut to mean the in the following way: Two-Digit years 00 through 49 are interpreted as 2000 through 2049. Two-Digit years 50 through 99 are interpreted as 1950 through 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4-digit representation to the server. If the server requires 2-digit representation, Internet Explorer will send it in 2-digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described above. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, server certificates, 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. The X.509 specification for certificates requires the valid date range to be described using two-digit years through the year 2049. Four-digit year format is not to be used until 2050 and later. These issues, combined with the fact than many secure certificates are set to expire at midnight, December 31, 1999 should be considered by web site administrators to prevent interruption of service to their customers. 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. 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 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, server certificates, 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 1904 - 31 Dec 2035 | ||
None | ||
Macintosh Operating System 7.5 or higher | ||
System clock | ||
23 Sep 1999 | ||
How the product handles dates: Dates are stored internally as a 32-bit integer in Macintosh operating system time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: Microsoft Internet Explorer 4.5 for Macintosh interprets dates entered with a 2-digit shortcut to mean the in the following way: Two-Digit years 00 through 49 are interpreted as 2000 through 2049. Two-Digit years 50 through 99 are interpreted as 1950 through 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4-digit representation to the server. If the server requires 2-digit representation, Internet Explorer will send it in 2-digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described above. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, server certificates, 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. The X.509 specification for certificates requires the valid date range to be described using two-digit years through the year 2049. Four-digit year format is not to be used until 2050 and later. These issues, combined with the fact than many secure certificates are set to expire at midnight, December 31, 1999 should be considered by web site administrators to prevent interruption of service to their customers. 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. 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 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, server certificates, 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 1904 - 31 Dec 2035 | ||
None | ||
Macintosh Operating System 7.5 or higher | ||
System clock | ||
23 Sep 1999 | ||
How the product handles dates: Dates are stored internally as a 32-bit integer in Macintosh operating system time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: Microsoft Internet Explorer 4.5 for Macintosh interprets dates entered with a 2-digit shortcut to mean the in the following way: Two-Digit years 00 through 49 are interpreted as 2000 through 2049. Two-Digit years 50 through 99 are interpreted as 1950 through 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4-digit representation to the server. If the server requires 2-digit representation, Internet Explorer will send it in 2-digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described above. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, server certificates, 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. The X.509 specification for certificates requires the valid date range to be described using two-digit years through the year 2049. Four-digit year format is not to be used until 2050 and later. These issues, combined with the fact than many secure certificates are set to expire at midnight, December 31, 1999 should be considered by web site administrators to prevent interruption of service to their customers. 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. 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 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, server certificates, 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 1904 - 31 Dec 2035 | ||
None | ||
Macintosh Operating System 7.5 or higher | ||
System clock | ||
23 Sep 1999 | ||
How the product handles dates: Dates are stored internally as a 32-bit integer in Macintosh operating system time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: Microsoft Internet Explorer 4.5 for Macintosh interprets dates entered with a 2-digit shortcut to mean the in the following way: Two-Digit years 00 through 49 are interpreted as 2000 through 2049. Two-Digit years 50 through 99 are interpreted as 1950 through 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4-digit representation to the server. If the server requires 2-digit representation, Internet Explorer will send it in 2-digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described above. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, server certificates, 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. The X.509 specification for certificates requires the valid date range to be described using two-digit years through the year 2049. Four-digit year format is not to be used until 2050 and later. These issues, combined with the fact than many secure certificates are set to expire at midnight, December 31, 1999 should be considered by web site administrators to prevent interruption of service to their customers. 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. 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 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, server certificates, 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 1904 - 31 Dec 2035 | ||
None | ||
Macintosh Operating System 7.5 or higher | ||
System clock | ||
23 Sep 1999 | ||
How the product handles dates: Dates are stored internally as a 32-bit integer in Macintosh operating system time. The structure is a 32-bit value that represents the number of seconds since January 1, 1904. Two-digit shortcut handling: Microsoft Internet Explorer 4.5 for Macintosh interprets dates entered with a 2-digit shortcut to mean the in the following way: Two-Digit years 00 through 49 are interpreted as 2000 through 2049. Two-Digit years 50 through 99 are interpreted as 1950 through 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. Internal representation of the date range is 1904 to year 2035. If a web server communicates a 2-digit year in its HTTP/1.0 header, Internet Explorer will interpret it as mentioned above and will return the 4-digit representation to the server. If the server requires 2-digit representation, Internet Explorer will send it in 2-digit representation. Headers with a 4-digit year, or headers containing 2-digit years will be interpreted in accordance with the rules described above. Common date usage errors: Independent of Internet Explorer’s handling of dates, web page HTML content, server certificates, 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. The X.509 specification for certificates requires the valid date range to be described using two-digit years through the year 2049. Four-digit year format is not to be used until 2050 and later. These issues, combined with the fact than many secure certificates are set to expire at midnight, December 31, 1999 should be considered by web site administrators to prevent interruption of service to their customers. 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. 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 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, server certificates, 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 1970 - 31 Dec 2137 | ||
none | ||
Sun Solaris 2.5, 2.5.1, or 2.6 | ||
System Clock | ||
27 Oct 1999 | ||
Description of how the product handles dates: All 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. When making operating system calls, dates are converted to and from the UNIX time_t format. The time_t format is a 32-bit value representing the number of seconds since January 1, 1970, 00:00 UTC. 2-digit shortcut handling: Microsoft Internet Explorer for UNIX 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 for UNIX’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. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have Internet Explorer for UNIX, the web server, and if applicable, proxy server, all transition to and 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 teams have 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 1970 - 31 Dec 2137 | ||
None | ||
Hewlett-Packard UX 10.2 or 11.0 | ||
System Clock | ||
27 Oct 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Internet Explorer 5 HP-UNIX as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.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. When making operating system calls, dates are converted to and from the UNIX time_t format. The time_t format is a 32-bit value representing the number of seconds since January 1, 1970, 00:00 UTC. Two-digit shortcut handling: Microsoft Internet Explorer for HP-UX ("IE") interprets dates entered with a 2-digit shortcut to mean the following: 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. Microsoft Outlook Express for HP-UX ("OE") does not generate 2-digit shortcuts for date representation. OE inter-operates with other e-mail clients and newsreaders. Some of these older clients may not be year 2000-aware and send messages with dates in a "dd/mm/yy" format. OE will assume that 50 – 99 are 1950 to 1999 and 00 – 49 are 2000 to 2049 Common date usage errors: Independent of IE’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. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have IE, the web server, and if applicable, proxy server, transition to and 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. Tests of mail servers for the year 2000 need to have OE and the mail server (IMAP or POP3 and SMTP), transition to operate in the year 2000. For example, some servers may use a 2-digit year in message headers. While the IE and OE teams have tested operation with some popular mail servers, proxy servers & web servers, verification of IE & OE should include testing of the below items within your computing environment.
In addition, contact your web server, proxy server, mail server and third party Java Virtual Machine 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 1970 - 31 Dec 2137 | ||
None | ||
Sun Solaris 2.5, 2.5.1, 2.6 or 2.7 (SPARC versions) | ||
System Clock | ||
27 Oct 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Product Version SP# as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.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. When making operating system calls, dates are converted to and from the UNIX time_t format. The time_t format is a 32-bit value representing the number of seconds since January 1, 1970, 00:00 UTC. Two-digit shortcut handling: Microsoft Internet Explorer for Solaris ("IE") interprets dates entered with a 2-digit shortcut to mean the following: 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. Microsoft Outlook Express for Solaris ("OE") does not generate 2-digit shortcuts for date representation. OE inter-operates with other email clients and newsreaders. Some of these older clients may not be year 2000-aware and send messages with dates in a "dd/mm/yy" format. OE will assume that 50 – 99 are 1950 to 1999 and 00 – 49 are 2000 to 2049 Common date usage errors: Independent of IE’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. Testing guidelines and recommendations: Tests of web sites or web-based applications for the year 2000 need to have IE, the web server, and if applicable, proxy server, transition to and 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. Tests of mail servers for the year 2000 need to have OE and the mail server (IMAP or POP3 and SMTP), transition to operate in the year 2000. For example, some servers may use a 2-digit year in message headers. While the IE and OE teams have tested operation with some popular mail servers, proxy servers & web servers, verification of IE & OE should include testing of the below items within your computing environment.
In addition, contact your web server, proxy server, mail server and third party Java Virtual Machine 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 | ||
none | ||
Internet Explorer 4.0 or greater | ||
System Clock | ||
21 Oct 1999 | ||
How the product handles dates: All dates are stored internally as Win32 SYSTEMTIME structures. The SYSTEMTIME structure represents a date and time using individual members for the month, day, year, weekday, hour, minute, second, and millisecond. Two-digit shortcut handling: The Internet Explorer Administration Kit does not use 2-digit dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and 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 teams have tested operation with popular web servers and proxy servers, verification of the IEAK 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. |
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 1980 - 31 Dec 2035 | ||
none | ||
Internet Explorer 5 | ||
System Clock | ||
21 Jul 1999 | ||
This document pertains to Internet Explorer Administration Kit (IEAK) version 5. 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: The Internet Explorer Administration Kit does not use 2-digit Dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and 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 teams have tested operation with popular web servers and proxy servers, verification of the IEAK 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.
|
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 1980 - 31 Dec 2035 | ||
none | ||
Internet Explorer 5 | ||
System Clock | ||
21 Jul 1999 | ||
This document pertains to Internet Explorer Administration Kit (IEAK) version 5. 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: The Internet Explorer Administration Kit does not use 2-digit Dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and 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 teams have tested operation with popular web servers and proxy servers, verification of the IEAK 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.
|
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 1980 - 31 Dec 2035 | ||
none | ||
Internet Explorer 5 | ||
System Clock | ||
21 Jul 1999 | ||
This document pertains to Internet Explorer Administration Kit (IEAK) version 5. 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: The Internet Explorer Administration Kit does not use 2-digit Dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and 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 teams have tested operation with popular web servers and proxy servers, verification of the IEAK 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.
|
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 1980 - 31 Dec 2035 | ||
none | ||
Internet Explorer 5 | ||
System Clock | ||
21 Jul 1999 | ||
This document pertains to Internet Explorer Administration Kit (IEAK) version 5. 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: The Internet Explorer Administration Kit does not use 2-digit Dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and 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 teams have tested operation with popular web servers and proxy servers, verification of the IEAK 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.
|
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 1980 - 31 Dec 2035 | ||
none | ||
Internet Explorer 5 | ||
System Clock | ||
21 Jul 1999 | ||
This document pertains to Internet Explorer Administration Kit (IEAK) version 5. 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: The Internet Explorer Administration Kit does not use 2-digit Dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and 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 teams have tested operation with popular web servers and proxy servers, verification of the IEAK 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.
|
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 1980 - 31 Dec 2035 | ||
none | ||
Internet Explorer 5 | ||
System Clock | ||
22 Jul 1999 | ||
This document pertains to Internet Explorer Administration Kit (IEAK) version 5. 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: The Internet Explorer Administration Kit does not use 2-digit Dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and 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 teams have tested operation with popular web servers and proxy servers, verification of the IEAK 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.
|
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 1980 - 31 Dec 2035 | ||
none | ||
Internet Explorer 5 | ||
System Clock | ||
21 Jul 1999 | ||
This document pertains to Internet Explorer Administration Kit (IEAK) version 5. 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: The Internet Explorer Administration Kit does not use 2-digit Dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and 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 teams have tested operation with popular web servers and proxy servers, verification of the IEAK 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.
|
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 1980 - 31 Dec 2035 | ||
none | ||
Internet Explorer 5 | ||
System Clock | ||
21 Jul 1999 | ||
This document pertains to Internet Explorer Administration Kit (IEAK) version 5. 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: The Internet Explorer Administration Kit does not use 2-digit Dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and 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 teams have tested operation with popular web servers and proxy servers, verification of the IEAK 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.
|
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 1980 - 31 Dec 2035 | ||
none | ||
Internet Explorer 5 | ||
System Clock | ||
21 Jul 1999 | ||
This document pertains to Internet Explorer Administration Kit (IEAK) version 5. 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: The Internet Explorer Administration Kit does not use 2-digit Dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and 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 teams have tested operation with popular web servers and proxy servers, verification of the IEAK 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.
|
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 1980 - 31 Dec 2035 | ||
none | ||
Internet Explorer 5 | ||
System Clock | ||
21 Jul 1999 | ||
This document pertains to Internet Explorer Administration Kit (IEAK) version 5. 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: The Internet Explorer Administration Kit does not use 2-digit Dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and 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 teams have tested operation with popular web servers and proxy servers, verification of the IEAK 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.
|
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 1980 - 31 Dec 2035 | ||
none | ||
Internet Explorer 5 | ||
System Clock | ||
21 Jul 1999 | ||
This document pertains to Internet Explorer Administration Kit (IEAK) version 5. 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: The Internet Explorer Administration Kit does not use 2-digit Dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and 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 teams have tested operation with popular web servers and proxy servers, verification of the IEAK 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.
|
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 1980 - 31 Dec 2035 | ||
none | ||
Internet Explorer 5 | ||
System Clock | ||
21 Jul 1999 | ||
This document pertains to Internet Explorer Administration Kit (IEAK) version 5. 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: The Internet Explorer Administration Kit does not use 2-digit Dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and 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 teams have tested operation with popular web servers and proxy servers, verification of the IEAK 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.
|
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 1980 - 31 Dec 2035 | ||
none | ||
Internet Explorer 5 | ||
System Clock | ||
21 Jul 1999 | ||
This document pertains to Internet Explorer Administration Kit (IEAK) version 5. 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: The Internet Explorer Administration Kit does not use 2-digit Dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and 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 teams have tested operation with popular web servers and proxy servers, verification of the IEAK 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.
|
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 1980 - 31 Dec 2035 | ||
none | ||
Internet Explorer 5 | ||
System Clock | ||
21 Jul 1999 | ||
This document pertains to Internet Explorer Administration Kit (IEAK) version 5. 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: The Internet Explorer Administration Kit does not use 2-digit Dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and 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 teams have tested operation with popular web servers and proxy servers, verification of the IEAK 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.
|
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 1980 - 31 Dec 2035 | ||
none | ||
Internet Explorer 5 | ||
System Clock | ||
21 Jul 1999 | ||
This document pertains to Internet Explorer Administration Kit (IEAK) version 5. 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: The Internet Explorer Administration Kit does not use 2-digit Dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and 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 teams have tested operation with popular web servers and proxy servers, verification of the IEAK 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.
|
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 1980 - 31 Dec 2035 | ||
none | ||
Internet Explorer 5 | ||
System Clock | ||
21 Jul 1999 | ||
This document pertains to Internet Explorer Administration Kit (IEAK) version 5. 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: The Internet Explorer Administration Kit does not use 2-digit Dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and 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 teams have tested operation with popular web servers and proxy servers, verification of the IEAK 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.
|
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 1980 - 31 Dec 2035 | ||
none | ||
Internet Explorer 5 | ||
System Clock | ||
21 Jul 1999 | ||
This document pertains to Internet Explorer Administration Kit (IEAK) version 5. 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: The Internet Explorer Administration Kit does not use 2-digit Dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and 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 teams have tested operation with popular web servers and proxy servers, verification of the IEAK 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.
|
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. |