| Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| WinCE ETK for VC++ 5.0 EP 2.1 (English) - Win CE
| Product Summary |
Product: WinCE ETK for VC++ 5.0 EP
Version: 2.1 |
Category: Compliant
Operating System: Win CE |
| Language: English |
Release Date: 17 Apr 1997 |
| Operational Range: |
- |
| Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes |
| Prerequisites: |
None |
| Product Dependencies: |
None |
| Clock Dependencies: |
Operating System clock and OLEAUT32 |
| Last Updated: |
10 May 1999 | |
| Product Details |
|
Windows CE Embedded Toolkit for Visual C++ 5.0 EP 2.1
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement?
Yes.
Operational Range for Data: Original Equipment Manufacturer Dependent
How the product runtime handles dates:
Windows CE stores a compressed year in the OAL (HAL) layer which is controlled by the Original Equipment Manufacturer (OEM). It is up to the OEM to store this data. Most specify a 100-year range (i.e. 1950 û 2050). Windows CE takes and returns a 4-digit year except in the OAL layer that talks directly to the hardware. External interfaces for Windows CE are 4-digit years.
Two-digit shortcut handling:
Windows CE does not have two-digit conversion logic but OLE does. OLE converts a 2-digit date to a 4-digit date using the following rules:
|
2-Digit |
4-Digit |
|
00-29 |
2000-2029 |
|
30-99 |
1930-1999 |
OLE programmatically uses 4-Digit dates. The place that this conversion is used is when an application is supplied a 2-digit string representing a year and OLE is required to interpret/convert it. The operating system itself does not rely of this conversion.
Common development errors dealing with year 2000 date issues:
The OEM develops the real-time clock unless it is provided on the CPU. The OEM also implements real-time clock functions. Windows CE is dependent upon the OEM and their implementation of the OEM real-time clock APIs. The OEM is to provide the correct information in their OAL/hardware to maintain proper date handling. The documentation and sample files provided to OEMs show (the OEM) how to provide proper date handling.
Testing guidelines and recommendations:
Microsoft recommends that OEMs call GetSystemTime and SetSystemTime to ensure the system clock is correct. These APIs in turn call the OEM real-time clock functions that need to be tested for their date-handling characteristics. The testing would consist of trying to set various dates and then checking the result of these attempts.
Locale Date formats for SSHORTDATE
The Locale tables that ship with Windows CE 2.01 do not contain 4-digit date formats for all locales. To supplement the date formats for a locale, an OEM can supply a date format to the GetDateFormat() API or use a format specified by SLONGDATE. An OEM is not encouraged to change the locale data files but instead add a system applet to enable date format overrides.
Locales not supporting 4-digit SSHORTDATE as of posting
Catalan - Spain
German - Switzerland
German - Liechtenstein
English - United Kingdom
English - Australia
English - Canada
English - New Zealand
English - Ireland
English - South Africa
English - Caribbean
Spanish - Spain (Traditional Sort)
Spanish - Mexico
Spanish - Spain (Modern Sort)
French - Belgium
French - Canada
French - Switzerland
Hebrew - Israel
Italian - Switzerland
Dutch - Netherlands
Dutch - Belgium
Polish - Poland
Russian - Russia
Serbian - Serbia (Latin)
Serbian - Serbia (Cyrillic)
Albanian - Albania
Indonesian - Indonesia
Ukrainian - Ukraine
Belarussian - Belarus
Estonian - Estonia
Latvian - Latvia
Vietnamese - Viet Nam
Basque - Spain
Macedonian - Republic of Macedonia
Afrikaans - South Africa
Faeroese - Faeroe Islands
Malay - Malaysia
Malay - Brunei Darussalam
| |
Return to Search Screen
| Legend of Symbols: |
| * |
The product is compliant with recommended customer action. This indicates a prerequisite action is recommended which may include loading a software update or reading a document. |
| # |
The product is compliant with acceptable deviations from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability, or reliability of the product. |
| + |
The product is compliant with pending Year 2000 software updates. Future maintenance actions will be recommended shortly. See Product Guide for further details. |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
If after reviewing this information you have additional questions related to this product, click here.
YEAR 2000 READINESS DISCLOSURE
ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFT'S YEAR 2000 WEBSITE LOCATED AT http://www.microsoft.com/year2000/ (the "Y2K WEBSITE"). EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED PURSUANT TO THE TERMS HEREOF, THE TERMS OF THE Y2K WEBSITE, AND THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT FOR THE SOLE PURPOSE OF ASSISTING THE PLANNING FOR THE TRANSITION TO THE YEAR 2000. EACH MICROSOFT YEAR 2000 STATEMENT CONTAINS INFORMATION CURRENTLY AVAILABLE AND IS UPDATED REGULARLY AND SUBJECT TO CHANGE. MICROSOFT THEREFORE RECOMMENDS THAT YOU CHECK THE Y2K WEBSITE REGULARLY FOR ANY CHANGES TO ANY MICROSOFT YEAR 2000 STATEMENT. EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. CONSEQUENTLY, MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, MICROSOFT DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF ANY MICROSOFT YEAR 2000 STATEMENT IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY MICROSOFT OR ITS AUTHORIZED REPRESENTATIVES SHALL CREATE A WARRANTY OR IN ANY WAY DECREASE THE SCOPE OF THIS WARRANTY DISCLAIMER. IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER REGARDING ANY MICROSOFT YEAR 2000 STATEMENT INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, PUNITIVE OR SPECIAL DAMAGES, EVEN IF MICROSOFT OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE FOREGOING LIMITATION MAY NOT APPLY TO YOU. THE INFORMATION CONTAINED IN EACH MICROSOFT YEAR 2000 STATEMENT IS FOUND AT THE Y2K WEBSITE AND IS INTENDED TO BE READ IN CONJUNCTION WITH OTHER INFORMATION LOCATED AT THE Y2K WEBSITE, INCLUDING BUT NOT LIMITED TO MICROSOFT'S YEAR 2000 COMPLIANCE STATEMENT, THE DESCRIPTION OF THE CATEGORIES OF COMPLIANCE INTO WHICH MICROSOFT HAS CLASSIFIED ITS PRODUCTS IN ITS YEAR 2000 PRODUCT GUIDE, AND THE MICROSOFT YEAR 2000 TEST CRITERIA.
ANY MICROSOFT YEAR 2000 STATEMENTS MADE TO YOU IN THE COURSE OF PROVIDING YEAR 2000 RELATED UPDATES, YEAR 2000 DIAGNOSTIC TOOLS, OR REMEDIATION SERVICES (IF ANY) ARE SUBJECT TO THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT (112 STAT. 2386). IN CASE OF A DISPUTE, THIS ACT MAY REDUCE YOUR LEGAL RIGHTS REGARDING THE USE OF ANY SUCH STATEMENTS, UNLESS OTHERWISE SPECIFIED BY YOUR CONTRACT OR TARIFF.
|
