| Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| Internet Explorer (32-bit) 4.0x (Turkish) - 32-Bit Win
| Product Summary |
Product: Internet Explorer (32-bit)
Version: 4.0x |
Category: Compliant*
Operating System: 32-Bit Win |
| Language: Turkish |
Release Date: 01 Sep 1997 |
| Operational Range: |
- |
| Prerequisites: |
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 |
| Product Dependencies: |
Windows 95, or Windows NT4 Service Pack 3 |
| Clock Dependencies: |
Clock, DCOM, COMCTL, OLEAUT32 |
| Last Updated: |
07 Sep 1999 | |
| Product Details |
|
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:
- If a web site uses a cookie with a 2-digit year of "00", Internet Explorer recognized the cookie as expired. Cookies with 4-digit expiration dates, or expiration dates before and after the year 2000 are not affected.
- If a web server communicates a 2-digit year of "00" in its HTTP/1.0 header, Internet Explorer will recognize pages on that site as expired and not cache them locally. Browsing the site will work normally while connected, but will not be available for offline browsing. HTTP/1.1 headers, headers with a 4-digit year, or headers containing 2-digit years before and after the year 2000 are not affected.
- If Microsoft Wallet is installed (an optional add-on for Internet Explorer configured via the "Content" tab of Internet Options), Internet Explorer will not allow the addition of a credit card with an expiration date in or beyond the year 2000. Wallet will also not allow users to add or edit their credit card information if the system date is in or beyond the year 2000.
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.
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 is less than 60,
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,
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.).
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 MS Data Access Components Year 2000 Product Guide.
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. To resolve this issue, install Microsoft Wallet 2.1.1383 or later from http://www.microsoft.com/wallet.
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.
- Authentication: If you use a secured site and/or SSL connections, verify proper authentication of authorized users, denial of others, and proper operation. Note: If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired.
- Code Download: Download of digitally signed code includes a signature with an expiration date. Verify download, installation, and operation of required ActiveX controls, and proper handling of Authenticode signatures on downloaded code. If you are testing certificates in Internet Explorer that are not yet valid, Internet Explorer displays an incorrect message that they are expired.
- File Download: Verify proper download of files referred to by your site.
- Search: Verify that search bar works for your preferred search provider.
- History: Internet Explorer organizes sites you have recently visited by "today", "yesterday", and previous weeks.
- Subscriptions: Internet Explorer 4 provides for publisher-scheduled updates and expiration for channel content. Verify proper update of subscribed sites.
- Autoconfiguration: The Internet Explorer Administration Kit (IEAK) allows for downloading of new settings and restrictions maintained by an administrator on a server. Options for auto-configuration include updating settings by date and by a timeout value.
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.
| |
Return to Search Screen
| Legend of Symbols: |
| * |
The product is compliant with recommended customer action. This indicates a prerequisite action is recommended which may include loading a software update or reading a document. |
| # |
The product is compliant with an acceptable deviations from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability, or reliability of the product. |
| + |
The product is compliant with pending Year 2000 software updates. Future maintenance actions will be recommended shortly. See Product Guide for further details. |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
If after reviewing this information you have additional questions related to this product, click here.
YEAR 2000 READINESS DISCLOSURE
ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFT'S YEAR 2000 WEBSITE LOCATED AT http://www.microsoft.com/year2000/ (the "Y2K WEBSITE"). EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED PURSUANT TO THE TERMS HEREOF, THE TERMS OF THE Y2K WEBSITE, AND THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT FOR THE SOLE PURPOSE OF ASSISTING THE PLANNING FOR THE TRANSITION TO THE YEAR 2000. EACH MICROSOFT YEAR 2000 STATEMENT CONTAINS INFORMATION CURRENTLY AVAILABLE AND IS UPDATED REGULARLY AND SUBJECT TO CHANGE. MICROSOFT THEREFORE RECOMMENDS THAT YOU CHECK THE Y2K WEBSITE REGULARLY FOR ANY CHANGES TO ANY MICROSOFT YEAR 2000 STATEMENT. EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. CONSEQUENTLY, MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, MICROSOFT DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF ANY MICROSOFT YEAR 2000 STATEMENT IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY MICROSOFT OR ITS AUTHORIZED REPRESENTATIVES SHALL CREATE A WARRANTY OR IN ANY WAY DECREASE THE SCOPE OF THIS WARRANTY DISCLAIMER. IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER REGARDING ANY MICROSOFT YEAR 2000 STATEMENT INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, PUNITIVE OR SPECIAL DAMAGES, EVEN IF MICROSOFT OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE FOREGOING LIMITATION MAY NOT APPLY TO YOU. THE INFORMATION CONTAINED IN EACH MICROSOFT YEAR 2000 STATEMENT IS FOUND AT THE Y2K WEBSITE AND IS INTENDED TO BE READ IN CONJUNCTION WITH OTHER INFORMATION LOCATED AT THE Y2K WEBSITE, INCLUDING BUT NOT LIMITED TO MICROSOFT'S YEAR 2000 COMPLIANCE STATEMENT, THE DESCRIPTION OF THE CATEGORIES OF COMPLIANCE INTO WHICH MICROSOFT HAS CLASSIFIED ITS PRODUCTS IN ITS YEAR 2000 PRODUCT GUIDE, AND THE MICROSOFT YEAR 2000 TEST CRITERIA.
ANY MICROSOFT YEAR 2000 STATEMENTS MADE TO YOU IN THE COURSE OF PROVIDING YEAR 2000 RELATED UPDATES, YEAR 2000 DIAGNOSTIC TOOLS, OR REMEDIATION SERVICES (IF ANY) ARE SUBJECT TO THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT (112 STAT. 2386). IN CASE OF A DISPUTE, THIS ACT MAY REDUCE YOUR LEGAL RIGHTS REGARDING THE USE OF ANY SUCH STATEMENTS, UNLESS OTHERWISE SPECIFIED BY YOUR CONTRACT OR TARIFF.
|
