- | ||
None | ||
None | ||
operating system clock and OLEAUT32 | ||
21 Sep 1999 | ||
Operational Range for Data: OEM dependent.
How the product handles dates: Windows CE stores a compressed year in the OEM Adaptation Layer, which is controlled by an OEM. It is up to the OEM to store this data with most specifying a 100-year range (i.e. 1950 – 2049). 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 any such conversion logic but OLE does. OLE converts a 2-digit date to a 4-digit date using the following rules: Two-digit years 00-29 are converted to 2000-2029 Two-digit years 30-99 are converted to 1930-1999 OLE programmatically uses 4-Digit dates. The only place that this conversion is used is when an application is supplied a 2-digit string representing a year and OLE is required to convert it. The operating system itself does not rely of this conversion. Common date usage errors: Windows CE is dependent upon the OEM and their implementation of the OEM’s real-time clock APIs. The OEM must provide the correct information in their OAL/hardware to maintain proper date handling. Testing guidelines and recommendations: We recommend OEMs call GetSystemTime, SetSystemTime, and CeSetUserNotification to ensure the system clock is correct. These APIs will in turn call the OEM real-time clock functions that need to be tested for compliance. The testing would consist of trying to set various dates and then checking the result of these attempts. The OEM functions that will be exercised are OEMSetRealTime, OEMGetRealTime and OEMSetAlarmTime. |
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 1997 - 31 Dec 2070 | ||
None | ||
Windows CE 2.0, Lernout & Hauspie Text-To-Speech engine, directions data provider | ||
original equipment manufacturer hardware | ||
06 Oct 1999 | ||
How the product handles dates: Dates are stored using the 64-bit UTC (Coordinated Universal Time), which represents the amount of time in 100 nano-second increments since January 1, 1601. Two-digit shortcut handling: The product does not support user input of two-digit shortcuts. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted.
Date usage across the product: Radio: N/A. No date information is used. CD Player: N/A. No date information is used. Directions: Uses date from data disc, to determine road closures for specific times of year. This information is contained on the data CD provided by your Directions data provider. Address Book: Date information is displayed for Birthday and Anniversary, but is not editable. These dates are entered into the Address Book by sending contacts that contain this information using IR and a Hand-held or Palm-Sized PC. Audio: N/A. No date information is used. Setup: Uses "combo boxes" which allow the user to set the date. The selectable range for the year is from 1997 to 2070. Messages: Displays date and time that messages were received. Date and time are also read via Text-to-speech. Sorting in the main view is done via date, and is sorted in reverse chronological order. Clock Screen: Displays current time and date. Date is in fixed format of DDDDDDDDD, MMM DD, YYYY. Power Off Screen: Displays current time and date. Date is in fixed format of DDDDDDDDD, MMM DD, YYYY. Text-to-Speech (TTS) engine: Reads text that can include a year that is 2 or 4 digits. Text-to-speech makes no assumptions for 2-digit years, other than that the year 00 will be read as "Two-thousand." A year of 01 will be read as "One".
Speech Recognition (SR) engine: N/A. No date information is used. Shell: Relies on system time, current time zone, and DST setting to determine if the time should be adjusted for DST. Windows CE operating system: Storage: Windows CE for the Auto PC stores a compressed year in the OEM Adaptation Layer, (OAL) which is controlled by an OEM. The date range is therefore hardware specific and is determined by the OEM. OEMs receive sample drivers from Microsoft that contain the default date range (1970-2069). This date range is only for the real-time clock and does not effect date ranges for Windows CE applications. Windows CE for the Auto PC takes and returns a 4-digit year except in the OAL layer that talks directly to the hardware. External interfaces for the operating system support 4-digit years.
|
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 CE 2.12, Lernout & Hauspie Text-To-Speech engine, directions data provider, OEM Real time clock settings. | ||
OEM hardware | ||
06 Oct 1999 | ||
Operational Range for Data: OEM Specific Release Date: July 1999 How the product handles dates: Dates are stored using the 64-bit UTC (Coordinated Universal Time), which represents the amount of time in 100 nano-second increments since January 1, 1601. Storage: Windows CE for the Auto PC stores a compressed year in the OEM Adaptation Layer, (OAL) which is controlled by an OEM. The date range is therefore hardware specific and is determined by the OEM. OEMs receive sample drivers from Microsoft that contain the default date range (1970-2069). This date range is only for the real-time clock and does not effect date ranges for Windows CE applications. Windows CE for the Auto PC takes and returns a 4-digit year except in the OAL layer that talks directly to the hardware. External interfaces for the operating system support 4-digit years. Two-digit shortcut handling: The product does not support user input of two-digit shortcuts. Testing guidelines and recommendations:
Date usage across the product: Radio: Not Applicable. No date information used. CD Player: Not Applicable. No date information used. Directions: Uses date from data disc to determine road closures for specific times of year. This information is contained on the data CD provided by the directions data publisher. Address Book: Not Applicable. Date information is displayed for Birthday and Anniversary, but are not editable. These dates are entered into the Address Book by sending contacts that contain this information using Infrared and a Hand-held or Palm-Sized PC. Audio: Not Applicable. No date information used. Setup: Uses "combo boxes" which allow the user to set the date. The selectable range for the year is from 1998 to 2069. Messages: Displays date and time that messages were received. Date and time are also read via Text-to-speech. Sorting in the main view is done via date, and is sorted in reverse chronological order. Clock Screen: Displays current time and date. Date is in fixed format of Day, MMM DD, YYYY. Power Off Screen: Displays current time and date. Date is always in fixed format of Day, MMM DD, YYYY. This is adjustable by our OEMs. Text-to-Speech (TTS) engine: Reads text that can include a year that is 2 or 4 digits. Text-to-speech makes no assumptions for 2-digit years, other than that the year 00 will be read as "Two-thousand". A year of 01 will be read as "One". Speech Recognition (SR) engine: Not Applicable. No date information used. Shell: Relies on system time, current time zone, and DST setting to determine if the time should be adjusted for DST. Hardware Platform Specific: SH3 and SH4 processor platforms use a 2-digit year and a base year of 1996, while the X86 processor platform uses a 2-digit year and a base year of 1970. |
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 CE 2.12, Lernout & Hauspie Text-To-Speech engine, directions data provider, OEM Real time clock settings. | ||
OEM Hardware | ||
06 Oct 1999 | ||
Operational Range for Data: OEM Specific How the product handles dates: Dates are stored using the 64-bit UTC (Coordinated Universal Time), which represents the amount of time in 100 nano-second increments since January 1, 1601. Windows CE Operating System: Storage: Windows CE for the Auto PC stores a compressed year in the OEM Adaptation Layer, (OAL) which is controlled by an OEM. The date range is therefore hardware specific and is determined by the OEM. OEMs receive sample drivers from Microsoft that contain the default date range (1970-2069). This date range is only for the real-time clock and does not effect date ranges for Windows CE applications. Windows CE for the Auto PC takes and returns a 4-digit year except in the OAL layer that talks directly to the hardware. External interfaces for the operating system support 4-digit years. Two-digit shortcut handling: The product does not support user input of two-digit shortcuts.
Testing guidelines and recommendations:
Date usage across the product: Radio: Not Applicable. No date information used. CD Player: Not Applicable. No date information used. Directions: Uses date from data disc to determine road closures for specific times of year. This information is contained on the data CD provided by the directions data publisher. Address Book: Not Applicable. Date information is displayed for Birthday and Anniversary, but are not editable. These dates are entered into the Address Book by sending contacts that contain this information using Infrared and a Hand-held or Palm-Sized PC.Audio: Not Applicable. No date information used. Setup: Uses "combo boxes" which allow the user to set the date. The selectable range for the year is from 1998 to 2069. Messages: Displays date and time that messages were received. Date and time are also read via Text-to-speech. Sorting in the main view is done via date, and is sorted in reverse chronological order. Clock Screen: Displays current time and date. Date is in fixed format of Day, MMM DD, YYYY. Power Off Screen: Displays current time and date. Date is always in fixed format of Day, MMM DD, YYYY. This is adjustable by our OEMs. Text-to-Speech (TTS) engine: Reads text that can include a year that is 2 or 4 digits. Text-to-speech makes no assumptions for 2-digit years, other than that the year 00 will be read as "Two-thousand". A year of 01 will be read as "One". Speech Recognition (SR) engine: Not Applicable. No date information used. Shell: Relies on system time, current time zone, and DST setting to determine if the time should be adjusted for DST. Hardware Platform Specific: SH3 and SH4 processor platforms use a 2-digit year and a base year of 1996, while the X86 processor platform uses a 2-digit year and a base year of 1970. |
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 CE 2.12, Lernout & Hauspie Text-To-Speech engine, directions data provider, OEM Real time clock settings. | ||
OEM Hardware | ||
06 Oct 1999 | ||
Operational Range for Data: OEM Specific How the product handles dates: Dates are stored using the 64-bit UTC (Coordinated Universal Time), which represents the amount of time in 100 nano-second increments since January 1, 1601. Windows CE Operating System: Storage: Windows CE for the Auto PC stores a compressed year in the OEM Adaptation Layer, (OAL) which is controlled by an OEM. The date range is therefore hardware specific and is determined by the OEM. OEMs receive sample drivers from Microsoft that contain the default date range (1970-2069). This date range is only for the real-time clock and does not effect date ranges for Windows CE applications. Windows CE for the Auto PC takes and returns a 4-digit year except in the OAL layer that talks directly to the hardware. External interfaces for the operating system support 4-digit years. Two-digit shortcut handling: The product does not support user input of two-digit shortcuts.
Testing guidelines and recommendations:
Date usage across the product: Radio: Not Applicable. No date information used. CD Player: Not Applicable. No date information used. Directions: Uses date from data disc to determine road closures for specific times of year. This information is contained on the data CD provided by the directions data publisher. Address Book: Not Applicable. Date information is displayed for Birthday and Anniversary, but are not editable. These dates are entered into the Address Book by sending contacts that contain this information using Infrared and a Hand-held or Palm-Sized PC.Audio: Not Applicable. No date information used. Setup: Uses "combo boxes" which allow the user to set the date. The selectable range for the year is from 1998 to 2069. Messages: Displays date and time that messages were received. Date and time are also read via Text-to-speech. Sorting in the main view is done via date, and is sorted in reverse chronological order. Clock Screen: Displays current time and date. Date is in fixed format of Day, MMM DD, YYYY. Power Off Screen: Displays current time and date. Date is always in fixed format of Day, MMM DD, YYYY. This is adjustable by our OEMs. Text-to-Speech (TTS) engine: Reads text that can include a year that is 2 or 4 digits. Text-to-speech makes no assumptions for 2-digit years, other than that the year 00 will be read as "Two-thousand". A year of 01 will be read as "One". Speech Recognition (SR) engine: Not Applicable. No date information used. Shell: Relies on system time, current time zone, and DST setting to determine if the time should be adjusted for DST. Hardware Platform Specific: SH3 and SH4 processor platforms use a 2-digit year and a base year of 1996, while the X86 processor platform uses a 2-digit year and a base year of 1970. |
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 CE 2.12, Lernout & Hauspie Text-To-Speech engine, directions data provider, OEM Real time clock settings. | ||
OEM Hardware | ||
06 Oct 1999 | ||
Operational Range for Data: OEM Specific How the product handles dates: Dates are stored using the 64-bit UTC (Coordinated Universal Time), which represents the amount of time in 100 nano-second increments since January 1, 1601. Windows CE Operating System: Storage: Windows CE for the Auto PC stores a compressed year in the OEM Adaptation Layer, (OAL) which is controlled by an OEM. The date range is therefore hardware specific and is determined by the OEM. OEMs receive sample drivers from Microsoft that contain the default date range (1970-2069). This date range is only for the real-time clock and does not effect date ranges for Windows CE applications. Windows CE for the Auto PC takes and returns a 4-digit year except in the OAL layer that talks directly to the hardware. External interfaces for the operating system support 4-digit years. Two-digit shortcut handling: The product does not support user input of two-digit shortcuts.
Testing guidelines and recommendations:
Date usage across the product: Radio: Not Applicable. No date information used. CD Player: Not Applicable. No date information used. Directions: Uses date from data disc to determine road closures for specific times of year. This information is contained on the data CD provided by the directions data publisher. Address Book: Not Applicable. Date information is displayed for Birthday and Anniversary, but are not editable. These dates are entered into the Address Book by sending contacts that contain this information using Infrared and a Hand-held or Palm-Sized PC.Audio: Not Applicable. No date information used. Setup: Uses "combo boxes" which allow the user to set the date. The selectable range for the year is from 1998 to 2069. Messages: Displays date and time that messages were received. Date and time are also read via Text-to-speech. Sorting in the main view is done via date, and is sorted in reverse chronological order. Clock Screen: Displays current time and date. Date is in fixed format of Day, MMM DD, YYYY. Power Off Screen: Displays current time and date. Date is always in fixed format of Day, MMM DD, YYYY. This is adjustable by our OEMs. Text-to-Speech (TTS) engine: Reads text that can include a year that is 2 or 4 digits. Text-to-speech makes no assumptions for 2-digit years, other than that the year 00 will be read as "Two-thousand". A year of 01 will be read as "One". Speech Recognition (SR) engine: Not Applicable. No date information used. Shell: Relies on system time, current time zone, and DST setting to determine if the time should be adjusted for DST. Hardware Platform Specific: SH3 and SH4 processor platforms use a 2-digit year and a base year of 1996, while the X86 processor platform uses a 2-digit year and a base year of 1970. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||||||||||||
none | ||||||||||||
none | ||||||||||||
Operating system clock and OLEAUT32 | ||||||||||||
06 Oct 1999 | ||||||||||||
Operational Range for Data: OEM dependent for OSDescription of how the product handles dates: Windows CE Operating System: Storage: Windows CE for the Handheld PC stores a compressed year in the OEM Adaptation Layer, (OAL) which is controlled by an OEM. The date range is therefore hardware specific and is determined by the OEM. OEMs receive sample drivers from Microsoft that contain the default date range (1970-2069). This date range is only for the real-time clock and does not effect date ranges for Windows CE applications. Windows CE for the Handheld PC takes and returns a 4-digit year except in the OAL layer that talks directly to the hardware. External interfaces for the operating system support 4-digit years .* See separate listing for "Windows CE 2.0" for additional Windows CE information
Pocket Excel:
Pocket Word:
Pocket PowerPoint:
Inbox:
Pocket Internet Explorer: Storage: All dates are stored internally as Win32 FILETIME structures. There are three main areas where Pocket Internet Explorer receives dates from the outside world: Cookies, FTP listings, and Security Certificates. A two-digit year that is less than 79 is interpreted as 20XX. A two-digit year that is greater than or equal to 80 is interpreted as 19XX.
2-digit shortcut handling: Windows CE operating system: Windows CE does not contain 2-digit conversion logic but OLE does. OLE converts a 2-digit date to a 4-digit date using the following rules: 00 - 29 converts to 2000 - 2029 30 - 99 converts to 1930 - 1999
Common date usage errors: Windows CE:
Four-digit year formats for these locales will not be available in some applications, such as Calendar Day View, Tasks, Inbox, and Shell Browser. * See separate listing for "Windows CE 2.0" for additional Windows CE information Pocket Excel:
Inbox:
Calendar:
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||||||||||||
none | ||||||||||||
none | ||||||||||||
Operating system clock and OLEAUT32 | ||||||||||||
06 Oct 1999 | ||||||||||||
Operational Range for Data: OEM dependent for OSDescription of how the product handles dates: Windows CE Operating System: Storage: Windows CE for the Handheld PC stores a compressed year in the OEM Adaptation Layer, (OAL) which is controlled by an OEM. The date range is therefore hardware specific and is determined by the OEM. OEMs receive sample drivers from Microsoft that contain the default date range (1970-2069). This date range is only for the real-time clock and does not effect date ranges for Windows CE applications. Windows CE for the Handheld PC takes and returns a 4-digit year except in the OAL layer that talks directly to the hardware. External interfaces for the operating system support 4-digit years .* See separate listing for "Windows CE 2.0" for additional Windows CE information
Pocket Excel:
Pocket Word:
Pocket PowerPoint:
Inbox:
Pocket Internet Explorer: Storage: All dates are stored internally as Win32 FILETIME structures. There are three main areas where Pocket Internet Explorer receives dates from the outside world: Cookies, FTP listings, and Security Certificates. A two-digit year that is less than 79 is interpreted as 20XX. A two-digit year that is greater than or equal to 80 is interpreted as 19XX.
2-digit shortcut handling: Windows CE operating system: Windows CE does not contain 2-digit conversion logic but OLE does. OLE converts a 2-digit date to a 4-digit date using the following rules: 00 - 29 converts to 2000 - 2029 30 - 99 converts to 1930 - 1999
Common date usage errors: Windows CE:
Four-digit year formats for these locales will not be available in some applications, such as Calendar Day View, Tasks, Inbox, and Shell Browser. * See separate listing for "Windows CE 2.0" for additional Windows CE information Pocket Excel:
Inbox:
Calendar:
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||||||||||||
none | ||||||||||||
none | ||||||||||||
Operating system clock and OLEAUT32 | ||||||||||||
06 Oct 1999 | ||||||||||||
Operational Range for Data: OEM dependent for OSDescription of how the product handles dates: Windows CE Operating System: Storage: Windows CE for the Handheld PC stores a compressed year in the OEM Adaptation Layer, (OAL) which is controlled by an OEM. The date range is therefore hardware specific and is determined by the OEM. OEMs receive sample drivers from Microsoft that contain the default date range (1970-2069). This date range is only for the real-time clock and does not effect date ranges for Windows CE applications. Windows CE for the Handheld PC takes and returns a 4-digit year except in the OAL layer that talks directly to the hardware. External interfaces for the operating system support 4-digit years .* See separate listing for "Windows CE 2.0" for additional Windows CE information
Pocket Excel:
Pocket Word:
Pocket PowerPoint:
Inbox:
Pocket Internet Explorer: Storage: All dates are stored internally as Win32 FILETIME structures. There are three main areas where Pocket Internet Explorer receives dates from the outside world: Cookies, FTP listings, and Security Certificates. A two-digit year that is less than 79 is interpreted as 20XX. A two-digit year that is greater than or equal to 80 is interpreted as 19XX.
2-digit shortcut handling: Windows CE operating system: Windows CE does not contain 2-digit conversion logic but OLE does. OLE converts a 2-digit date to a 4-digit date using the following rules: 00 - 29 converts to 2000 - 2029 30 - 99 converts to 1930 - 1999
Common date usage errors: Windows CE:
Four-digit year formats for these locales will not be available in some applications, such as Calendar Day View, Tasks, Inbox, and Shell Browser. * See separate listing for "Windows CE 2.0" for additional Windows CE information Pocket Excel:
Inbox:
Calendar:
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||||||||||||
none | ||||||||||||
none | ||||||||||||
Operating system clock and OLEAUT32 | ||||||||||||
06 Oct 1999 | ||||||||||||
Operational Range for Data: OEM dependent for OSDescription of how the product handles dates: Windows CE Operating System: Storage: Windows CE for the Handheld PC stores a compressed year in the OEM Adaptation Layer, (OAL) which is controlled by an OEM. The date range is therefore hardware specific and is determined by the OEM. OEMs receive sample drivers from Microsoft that contain the default date range (1970-2069). This date range is only for the real-time clock and does not effect date ranges for Windows CE applications. Windows CE for the Handheld PC takes and returns a 4-digit year except in the OAL layer that talks directly to the hardware. External interfaces for the operating system support 4-digit years .* See separate listing for "Windows CE 2.0" for additional Windows CE information
Pocket Excel:
Pocket Word:
Pocket PowerPoint:
Inbox:
Pocket Internet Explorer: Storage: All dates are stored internally as Win32 FILETIME structures. There are three main areas where Pocket Internet Explorer receives dates from the outside world: Cookies, FTP listings, and Security Certificates. A two-digit year that is less than 79 is interpreted as 20XX. A two-digit year that is greater than or equal to 80 is interpreted as 19XX.
2-digit shortcut handling: Windows CE operating system: Windows CE does not contain 2-digit conversion logic but OLE does. OLE converts a 2-digit date to a 4-digit date using the following rules: 00 - 29 converts to 2000 - 2029 30 - 99 converts to 1930 - 1999
Common date usage errors: Windows CE:
Four-digit year formats for these locales will not be available in some applications, such as Calendar Day View, Tasks, Inbox, and Shell Browser. * See separate listing for "Windows CE 2.0" for additional Windows CE information Pocket Excel:
Inbox:
Calendar:
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||||||||||||
None | ||||||||||||
None | ||||||||||||
Operating system clock and OLEAUT32 | ||||||||||||
06 Oct 1999 | ||||||||||||
Operational Range for Data: OEM dependent for OSDescription of how the product handles dates: Windows CE Operating System: Storage: Windows CE for the Handheld PC stores a compressed year in the OEM Adaptation Layer, (OAL) which is controlled by an OEM. The date range is therefore hardware specific and is determined by the OEM. OEMs receive sample drivers from Microsoft that contain the default date range (1970-2069). This date range is only for the real-time clock and does not effect date ranges for Windows CE applications. Windows CE for the Handheld PC takes and returns a 4-digit year except in the OAL layer that talks directly to the hardware. External interfaces for the operating system support 4-digit years .* See separate listing for "Windows CE 2.0" for additional Windows CE information
Pocket Excel:
Pocket Word:
Pocket PowerPoint:
Inbox:
Pocket Internet Explorer: Storage: All dates are stored internally as Win32 FILETIME structures. There are three main areas where Pocket Internet Explorer receives dates from the outside world: Cookies, FTP listings, and Security Certificates. A two-digit year that is less than 79 is interpreted as 20XX. A two-digit year that is greater than or equal to 80 is interpreted as 19XX.
2-digit shortcut handling: Windows CE operating system: Windows CE does not contain 2-digit conversion logic but OLE does. OLE converts a 2-digit date to a 4-digit date using the following rules: 00 - 29 converts to 2000 - 2029 30 - 99 converts to 1930 - 1999
Common date usage errors: Windows CE:
Four-digit year formats for these locales will not be available in some applications, such as Calendar Day View, Tasks, Inbox, and Shell Browser. * See separate listing for "Windows CE 2.0" for additional Windows CE information Pocket Excel:
Inbox:
Calendar:
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||||||||||||
none | ||||||||||||
none | ||||||||||||
Operating system clock and OLEAUT32 | ||||||||||||
06 Oct 1999 | ||||||||||||
Operational Range for Data: OEM dependent for OSDescription of how the product handles dates: Windows CE Operating System: Storage: Windows CE for the Handheld PC stores a compressed year in the OEM Adaptation Layer, (OAL) which is controlled by an OEM. The date range is therefore hardware specific and is determined by the OEM. OEMs receive sample drivers from Microsoft that contain the default date range (1970-2069). This date range is only for the real-time clock and does not effect date ranges for Windows CE applications. Windows CE for the Handheld PC takes and returns a 4-digit year except in the OAL layer that talks directly to the hardware. External interfaces for the operating system support 4-digit years .* See separate listing for "Windows CE 2.0" for additional Windows CE information
Pocket Excel:
Pocket Word:
Pocket PowerPoint:
Inbox:
Pocket Internet Explorer: Storage: All dates are stored internally as Win32 FILETIME structures. There are three main areas where Pocket Internet Explorer receives dates from the outside world: Cookies, FTP listings, and Security Certificates. A two-digit year that is less than 79 is interpreted as 20XX. A two-digit year that is greater than or equal to 80 is interpreted as 19XX.
2-digit shortcut handling: Windows CE operating system: Windows CE does not contain 2-digit conversion logic but OLE does. OLE converts a 2-digit date to a 4-digit date using the following rules: 00 - 29 converts to 2000 - 2029 30 - 99 converts to 1930 - 1999
Common date usage errors: Windows CE:
Four-digit year formats for these locales will not be available in some applications, such as Calendar Day View, Tasks, Inbox, and Shell Browser. * See separate listing for "Windows CE 2.0" for additional Windows CE information Pocket Excel:
Inbox:
Calendar:
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||||||||||||
none | ||||||||||||
none | ||||||||||||
Operating system clock and OLEAUT32 | ||||||||||||
06 Oct 1999 | ||||||||||||
Operational Range for Data: OEM dependent for OSDescription of how the product handles dates: Windows CE Operating System: Storage: Windows CE for the Handheld PC stores a compressed year in the OEM Adaptation Layer, (OAL) which is controlled by an OEM. The date range is therefore hardware specific and is determined by the OEM. OEMs receive sample drivers from Microsoft that contain the default date range (1970-2069). This date range is only for the real-time clock and does not effect date ranges for Windows CE applications. Windows CE for the Handheld PC takes and returns a 4-digit year except in the OAL layer that talks directly to the hardware. External interfaces for the operating system support 4-digit years .* See separate listing for "Windows CE 2.0" for additional Windows CE information
Pocket Excel:
Pocket Word:
Pocket PowerPoint:
Inbox:
Pocket Internet Explorer: Storage: All dates are stored internally as Win32 FILETIME structures. There are three main areas where Pocket Internet Explorer receives dates from the outside world: Cookies, FTP listings, and Security Certificates. A two-digit year that is less than 79 is interpreted as 20XX. A two-digit year that is greater than or equal to 80 is interpreted as 19XX.
2-digit shortcut handling: Windows CE operating system: Windows CE does not contain 2-digit conversion logic but OLE does. OLE converts a 2-digit date to a 4-digit date using the following rules: 00 - 29 converts to 2000 - 2029 30 - 99 converts to 1930 - 1999
Common date usage errors: Windows CE:
Four-digit year formats for these locales will not be available in some applications, such as Calendar Day View, Tasks, Inbox, and Shell Browser. * See separate listing for "Windows CE 2.0" for additional Windows CE information Pocket Excel:
Inbox:
Calendar:
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||||||||||||
None | ||||||||||||
None | ||||||||||||
Operating system clock and OLEAUT32 | ||||||||||||
06 Oct 1999 | ||||||||||||
This information applies to Windows CE for Handheld PC Professional Edition 3.0. Operational Range for Data: OEM dependent for Operating System. How the product handles dates: Windows CE Operating System:
Pocket Excel:
Pocket Word:
Pocket PowerPoint:
Pocket Access
Dates are stored internally as Win32 FILETIME structures.
2-digit shortcut in the following way. 1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029 Inbox:
Pocket Internet Explorer:
PIM:
2-digit shortcut handling: Windows CE operating system:
00 - 29 converts to 2000 - 2029 30 - 99 converts to 1930 - 1999
See
Common date usage errors: Windows CE:
Pocket Excel:
Issues to be aware of when developing applications for Windows CE for Handheld PC Professional Edition:
The LOCAL_ICENTURY value for the current short date format is not updated to reflect the current century information if:
In both cases the value returned for LOCALE_ICENTURY is the same as before the date format was changed. To compensate for this an application can retrieve the short date format and count the number of ‘y’s that are in the year format. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||||||||||||
None | ||||||||||||
None | ||||||||||||
Operating system clock and OLEAUT32 | ||||||||||||
06 Oct 1999 | ||||||||||||
This information applies to Windows CE for Handheld PC Professional Edition 3.0. Operational Range for Data: OEM dependent for Operating System. How the product handles dates: Windows CE Operating System:
Pocket Excel:
Pocket Word:
Pocket PowerPoint:
Pocket Access
Dates are stored internally as Win32 FILETIME structures.
2-digit shortcut in the following way. 1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029 Inbox:
Pocket Internet Explorer:
PIM:
2-digit shortcut handling: Windows CE operating system:
00 - 29 converts to 2000 - 2029 30 - 99 converts to 1930 - 1999
See
Common date usage errors: Windows CE:
Pocket Excel:
Issues to be aware of when developing applications for Windows CE for Handheld PC Professional Edition:
The LOCAL_ICENTURY value for the current short date format is not updated to reflect the current century information if:
In both cases the value returned for LOCALE_ICENTURY is the same as before the date format was changed. To compensate for this an application can retrieve the short date format and count the number of ‘y’s that are in the year format. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||||||||||||
None | ||||||||||||
None | ||||||||||||
Operating system clock and OLEAUT32 | ||||||||||||
06 Oct 1999 | ||||||||||||
This information applies to Windows CE for Handheld PC Professional Edition 3.0. Operational Range for Data: OEM dependent for Operating System. How the product handles dates: Windows CE Operating System:
Pocket Excel:
Pocket Word:
Pocket PowerPoint:
Pocket Access
Dates are stored internally as Win32 FILETIME structures.
2-digit shortcut in the following way. 1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029 Inbox:
Pocket Internet Explorer:
PIM:
2-digit shortcut handling: Windows CE operating system:
00 - 29 converts to 2000 - 2029 30 - 99 converts to 1930 - 1999
See
Common date usage errors: Windows CE:
Pocket Excel:
Issues to be aware of when developing applications for Windows CE for Handheld PC Professional Edition:
The LOCAL_ICENTURY value for the current short date format is not updated to reflect the current century information if:
In both cases the value returned for LOCALE_ICENTURY is the same as before the date format was changed. To compensate for this an application can retrieve the short date format and count the number of ‘y’s that are in the year format. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||||||||||||
None | ||||||||||||
None | ||||||||||||
Operating system clock and OLEAUT32 | ||||||||||||
06 Oct 1999 | ||||||||||||
This information applies to Windows CE for Handheld PC Professional Edition 3.0. Operational Range for Data: OEM dependent for Operating System. How the product handles dates: Windows CE Operating System:
Pocket Excel:
Pocket Word:
Pocket PowerPoint:
Pocket Access
Dates are stored internally as Win32 FILETIME structures.
2-digit shortcut in the following way. 1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029 Inbox:
Pocket Internet Explorer:
PIM:
2-digit shortcut handling: Windows CE operating system:
00 - 29 converts to 2000 - 2029 30 - 99 converts to 1930 - 1999
See
Common date usage errors: Windows CE:
Pocket Excel:
Issues to be aware of when developing applications for Windows CE for Handheld PC Professional Edition:
The LOCAL_ICENTURY value for the current short date format is not updated to reflect the current century information if:
In both cases the value returned for LOCALE_ICENTURY is the same as before the date format was changed. To compensate for this an application can retrieve the short date format and count the number of ‘y’s that are in the year format. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||||||||||||
None | ||||||||||||
None | ||||||||||||
Operating system clock and OLEAUT32 | ||||||||||||
06 Oct 1999 | ||||||||||||
This information applies to Windows CE for Handheld PC Professional Edition 3.0. Operational Range for Data: OEM dependent for Operating System. How the product handles dates: Windows CE Operating System:
Pocket Excel:
Pocket Word:
Pocket PowerPoint:
Pocket Access
Dates are stored internally as Win32 FILETIME structures.
2-digit shortcut in the following way. 1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029 Inbox:
Pocket Internet Explorer:
PIM:
2-digit shortcut handling: Windows CE operating system:
00 - 29 converts to 2000 - 2029 30 - 99 converts to 1930 - 1999
See
Common date usage errors: Windows CE:
Pocket Excel:
Issues to be aware of when developing applications for Windows CE for Handheld PC Professional Edition:
The LOCAL_ICENTURY value for the current short date format is not updated to reflect the current century information if:
In both cases the value returned for LOCALE_ICENTURY is the same as before the date format was changed. To compensate for this an application can retrieve the short date format and count the number of ‘y’s that are in the year format. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||||||||||||
None | ||||||||||||
None | ||||||||||||
Operating system clock and OLEAUT32 | ||||||||||||
06 Oct 1999 | ||||||||||||
This information applies to Windows CE for Handheld PC Professional Edition 3.0. Operational Range for Data: OEM dependent for Operating System. How the product handles dates: Windows CE Operating System:
Pocket Excel:
Pocket Word:
Pocket PowerPoint:
Pocket Access
Dates are stored internally as Win32 FILETIME structures.
2-digit shortcut in the following way. 1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029 Inbox:
Pocket Internet Explorer:
PIM:
2-digit shortcut handling: Windows CE operating system:
00 - 29 converts to 2000 - 2029 30 - 99 converts to 1930 - 1999
See
Common date usage errors: Windows CE:
Pocket Excel:
Issues to be aware of when developing applications for Windows CE for Handheld PC Professional Edition:
The LOCAL_ICENTURY value for the current short date format is not updated to reflect the current century information if:
In both cases the value returned for LOCALE_ICENTURY is the same as before the date format was changed. To compensate for this an application can retrieve the short date format and count the number of ‘y’s that are in the year format. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
None | ||
None | ||
Operating system clock and OLEAUT32 | ||
29 Jul 1999 | ||
Operational Range for Data: OEM dependent.
How the product handles dates: Windows CE Operating System:
Pocket Excel:
Note: If a user enters a date that can be interpreted in both "mm/dd/yy" and "yy/mm/dd" formats, then the date will default to the "yy/mm/dd" format. To avoid ambiguity, enter dates in a YYYY/MM/DD format so the date can be clearly understood.
Pocket Word:
Pocket PowerPoint:
Pocket Access
Dates are stored internally as Win32 FILETIME structures.
2-digit shortcut in the following way. 1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029 Inbox:
Pocket Internet Explorer:
PIM:
2-digit shortcut handling: Windows CE operating system:
00-29 convert to 2000-2029 30-99 convert to 1930-1999 See the
Common date usage errors: Windows CE:
Pocket Excel:
Issues to be aware of when developing applications for Windows CE for Handheld PC Professional Edition:
The LOCAL_ICENTURY value for the current short date format is not updated to reflect the current century information if:
In both cases the value returned for LOCALE_ICENTURY is the same as before the date format was changed. To compensate for this an application can retrieve the short date format and count the number of ‘y’s that are in the year format.
|
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 2999 | ||
none | ||
Windows CE operating system version 2.0 | ||
Hardware must support 4 bit date storage | ||
08 Dec 1998 | ||
How the product handles dates: Windows CE for Palm-size PC Devices clock and calendar apps and other applications make a call to the Operating System for the current date. The Operating System makes a hardware call to the OEM hardware registers for the time data. Two-digit shortcut handling: Month and Year are always displayed in four digit long format. There is no 2 digit date format display Common date usage errors: Windows CE Operating System
Four-digit year formats for these locales will not be available in some applications, such as Calendar Day View, Tasks, Inbox, and Shell Browser. Inbox:
Testing guidelines 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 1900 - 31 Dec 2999 | ||
none | ||
Windows CE operating system version 2.0 | ||
Hardware must support 4 bit date storage | ||
08 Dec 1998 | ||
How the product handles dates: Windows CE for Palm-size PC Devices clock and calendar apps and other applications make a call to the Operating System for the current date. The Operating System makes a hardware call to the OEM hardware registers for the time data. Two-digit shortcut handling: Month and Year are always displayed in four digit long format. There is no 2 digit date format display Common date usage errors: Windows CE Operating System
Four-digit year formats for these locales will not be available in some applications, such as Calendar Day View, Tasks, Inbox, and Shell Browser. Inbox:
Testing guidelines 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 1900 - 31 Dec 2999 | ||
none | ||
Windows CE operating system version 2.0 | ||
Hardware must support 4 bit date storage | ||
08 Dec 1998 | ||
How the product handles dates: Windows CE for Palm-size PC Devices clock and calendar apps and other applications make a call to the Operating System for the current date. The Operating System makes a hardware call to the OEM hardware registers for the time data. Two-digit shortcut handling: Month and Year are always displayed in four digit long format. There is no 2 digit date format display Common date usage errors: Windows CE Operating System
Four-digit year formats for these locales will not be available in some applications, such as Calendar Day View, Tasks, Inbox, and Shell Browser. Inbox:
Testing guidelines 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 1900 - 31 Dec 2999 | ||
none | ||
Windows CE operating system version 2.0 | ||
Hardware must support 4 bit date storage | ||
08 Dec 1998 | ||
How the product handles dates: Windows CE for Palm-size PC Devices clock and calendar apps and other applications make a call to the Operating System for the current date. The Operating System makes a hardware call to the OEM hardware registers for the time data. Two-digit shortcut handling: Month and Year are always displayed in four digit long format. There is no 2 digit date format display Common date usage errors: Windows CE Operating System
Four-digit year formats for these locales will not be available in some applications, such as Calendar Day View, Tasks, Inbox, and Shell Browser. Inbox:
Testing guidelines 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 1900 - 31 Dec 2999 | ||
none | ||
Windows CE operating system version 2.0 | ||
Hardware must support 4 bit date storage | ||
08 Dec 1998 | ||
How the product handles dates: Windows CE for Palm-size PC Devices clock and calendar apps and other applications make a call to the Operating System for the current date. The Operating System makes a hardware call to the OEM hardware registers for the time data. Two-digit shortcut handling: Month and Year are always displayed in four digit long format. There is no 2 digit date format display Common date usage errors: Windows CE Operating System
Four-digit year formats for these locales will not be available in some applications, such as Calendar Day View, Tasks, Inbox, and Shell Browser. Inbox:
Testing guidelines 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 1900 - 31 Dec 2999 | ||
none | ||
Windows CE operating system version 2.0 | ||
Hardware must support 4 bit date storage | ||
08 Dec 1998 | ||
How the product handles dates: Windows CE for Palm-size PC Devices clock and calendar apps and other applications make a call to the Operating System for the current date. The Operating System makes a hardware call to the OEM hardware registers for the time data. Two-digit shortcut handling: Month and Year are always displayed in four digit long format. There is no 2 digit date format display Common date usage errors: Windows CE Operating System
Four-digit year formats for these locales will not be available in some applications, such as Calendar Day View, Tasks, Inbox, and Shell Browser. Inbox:
Testing guidelines 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 1900 - 31 Dec 2999 | ||
none | ||
Windows CE operating system version 2.1 | ||
Hardware must support 4 bit date storage | ||
25 Oct 1999 | ||
How the product handles dates: Windows CE for Palm-size PC Devices clock and calendar apps and other applications make a call to the Operating System for the current date. The Operating System makes a hardware call to the OEM hardware registers for the time data. Two-digit shortcut handling: Month and Year are always displayed in four digit long format. There is no 2 digit date format display Common date usage errors: Windows CE Operating System
Four-digit year formats for these locales will not be available in some applications, such as Calendar Day View, Tasks, Inbox, and Shell Browser. Inbox:
Testing guidelines 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 1900 - 31 Dec 2999 | ||
none | ||
Windows CE operating system version 2.1 | ||
Hardware must support 4 bit date storage | ||
25 Oct 1999 | ||
How the product handles dates: Windows CE for Palm-size PC Devices clock and calendar apps and other applications make a call to the Operating System for the current date. The Operating System makes a hardware call to the OEM hardware registers for the time data. Two-digit shortcut handling: Month and Year are always displayed in four digit long format. There is no 2 digit date format display Common date usage errors: Windows CE Operating System
Four-digit year formats for these locales will not be available in some applications, such as Calendar Day View, Tasks, Inbox, and Shell Browser. Inbox:
Testing guidelines 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 1900 - 31 Dec 2999 | ||
none | ||
Windows CE operating system version 2.1 | ||
Hardware must support 4 bit date storage | ||
25 Oct 1999 | ||
How the product handles dates: Windows CE for Palm-size PC Devices clock and calendar apps and other applications make a call to the Operating System for the current date. The Operating System makes a hardware call to the OEM hardware registers for the time data. Two-digit shortcut handling: Month and Year are always displayed in four digit long format. There is no 2 digit date format display Common date usage errors: Windows CE Operating System
Four-digit year formats for these locales will not be available in some applications, such as Calendar Day View, Tasks, Inbox, and Shell Browser. Inbox:
Testing guidelines 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 1900 - 31 Dec 2999 | ||
none | ||
Windows CE operating system version 2.1 | ||
Hardware must support 4 bit date storage | ||
25 Oct 1999 | ||
How the product handles dates: Windows CE for Palm-size PC Devices clock and calendar apps and other applications make a call to the Operating System for the current date. The Operating System makes a hardware call to the OEM hardware registers for the time data. Two-digit shortcut handling: Month and Year are always displayed in four digit long format. There is no 2 digit date format display Common date usage errors: Windows CE Operating System
Four-digit year formats for these locales will not be available in some applications, such as Calendar Day View, Tasks, Inbox, and Shell Browser. Inbox:
Testing guidelines 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 1900 - 31 Dec 2999 | ||
none | ||
Windows CE operating system version 2.1 | ||
Hardware must support 4 bit date storage | ||
25 Oct 1999 | ||
How the product handles dates: Windows CE for Palm-size PC Devices clock and calendar apps and other applications make a call to the Operating System for the current date. The Operating System makes a hardware call to the OEM hardware registers for the time data. Two-digit shortcut handling: Month and Year are always displayed in four digit long format. There is no 2 digit date format display Common date usage errors: Windows CE Operating System
Four-digit year formats for these locales will not be available in some applications, such as Calendar Day View, Tasks, Inbox, and Shell Browser. Inbox:
Testing guidelines 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 1900 - 31 Dec 2999 | ||
none | ||
Windows CE operating system version 2.1 | ||
Hardware must support 4 bit date storage | ||
25 Oct 1999 | ||
How the product handles dates: Windows CE for Palm-size PC Devices clock and calendar apps and other applications make a call to the Operating System for the current date. The Operating System makes a hardware call to the OEM hardware registers for the time data. Two-digit shortcut handling: Month and Year are always displayed in four digit long format. There is no 2 digit date format display Common date usage errors: Windows CE Operating System
Four-digit year formats for these locales will not be available in some applications, such as Calendar Day View, Tasks, Inbox, and Shell Browser. Inbox:
Testing guidelines 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. |
- | ||
none | ||
Outlook 97, 98, and/or Schedule + 7.0, The Pcs operating System- Windows 95, Windows 98, or Windows NT 4.0 w/ Service Pack 3Windows CE Device | ||
none | ||
19 Nov 1998 | ||
Operational Range for Data: Dependent on PC operating system and PIM software.How the product handles dates: Windows CE Services synchronizes data between the desktop machine and the Windows CE devices. All dates are stored and manipulated as full 4-digit dates. All data is entered via the PC’s PIM software or with the applications on the Windows CE device. There is no way to directly manipulate this data via the Windows CE Services interface. Windows CE services is dependent on the operating system, the calendaring/e-mail software, and the Windows CE device for date handling. Two-digit shortcut handling: Windows CE Services does not contain any method for entering two-digit shortcuts. Recommendations to meet compliance: Ensure that any products Windows CE Services interacts with have been tested for year 2000 compliance. Common date usage errors: None.
Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. |
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 | ||
Outlook 97, 98, and/or Schedule + 7.0, The Pcs operating System- Windows 95, Windows 98, or Windows NT 4.0 w/ Service Pack 3Windows CE Device | ||
none | ||
19 Nov 1998 | ||
Operational Range for Data: Dependent on PC operating system and PIM software.How the product handles dates: Windows CE Services synchronizes data between the desktop machine and the Windows CE devices. All dates are stored and manipulated as full 4-digit dates. All data is entered via the PC’s PIM software or with the applications on the Windows CE device. There is no way to directly manipulate this data via the Windows CE Services interface. Windows CE services is dependent on the operating system, the calendaring/e-mail software, and the Windows CE device for date handling. Two-digit shortcut handling: Windows CE Services does not contain any method for entering two-digit shortcuts. Recommendations to meet compliance: Ensure that any products Windows CE Services interacts with have been tested for year 2000 compliance. Common date usage errors: None.
Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. |
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 | ||
Outlook 97, 98, and/or Schedule + 7.0, The Pcs operating System- Windows 95, Windows 98, or Windows NT 4.0 w/ Service Pack 3Windows CE Device | ||
none | ||
19 Nov 1998 | ||
Operational Range for Data: Dependent on PC operating system and PIM software.How the product handles dates: Windows CE Services synchronizes data between the desktop machine and the Windows CE devices. All dates are stored and manipulated as full 4-digit dates. All data is entered via the PC’s PIM software or with the applications on the Windows CE device. There is no way to directly manipulate this data via the Windows CE Services interface. Windows CE services is dependent on the operating system, the calendaring/e-mail software, and the Windows CE device for date handling. Two-digit shortcut handling: Windows CE Services does not contain any method for entering two-digit shortcuts. Recommendations to meet compliance: Ensure that any products Windows CE Services interacts with have been tested for year 2000 compliance. Common date usage errors: None.
Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. |
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 | ||
Outlook 97, 98, and/or Schedule + 7.0, The Pcs operating System- Windows 95, Windows 98, or Windows NT 4.0 w/ Service Pack 3Windows CE Device | ||
none | ||
19 Nov 1998 | ||
Operational Range for Data: Dependent on PC operating system and PIM software.How the product handles dates: Windows CE Services synchronizes data between the desktop machine and the Windows CE devices. All dates are stored and manipulated as full 4-digit dates. All data is entered via the PC’s PIM software or with the applications on the Windows CE device. There is no way to directly manipulate this data via the Windows CE Services interface. Windows CE services is dependent on the operating system, the calendaring/e-mail software, and the Windows CE device for date handling. Two-digit shortcut handling: Windows CE Services does not contain any method for entering two-digit shortcuts. Recommendations to meet compliance: Ensure that any products Windows CE Services interacts with have been tested for year 2000 compliance. Common date usage errors: None.
Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. |
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 | ||
Outlook 97, 98, and/or Schedule + 7.0, The Pcs operating System- Windows 95, Windows 98, or Windows NT 4.0 w/ Service Pack 3Windows CE Device | ||
none | ||
19 Nov 1998 | ||
Operational Range for Data: Dependent on PC operating system and PIM software.How the product handles dates: Windows CE Services synchronizes data between the desktop machine and the Windows CE devices. All dates are stored and manipulated as full 4-digit dates. All data is entered via the PC’s PIM software or with the applications on the Windows CE device. There is no way to directly manipulate this data via the Windows CE Services interface. Windows CE services is dependent on the operating system, the calendaring/e-mail software, and the Windows CE device for date handling. Two-digit shortcut handling: Windows CE Services does not contain any method for entering two-digit shortcuts. Recommendations to meet compliance: Ensure that any products Windows CE Services interacts with have been tested for year 2000 compliance. Common date usage errors: None.
Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. |
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 | ||
Outlook 97, 98, and/or Schedule + 7.0, The Pcs operating System- Windows 95, Windows 98, or Windows NT 4.0 w/ Service Pack 3Windows CE Device | ||
none | ||
19 Nov 1998 | ||
Operational Range for Data: Dependent on PC operating system and PIM software.How the product handles dates: Windows CE Services synchronizes data between the desktop machine and the Windows CE devices. All dates are stored and manipulated as full 4-digit dates. All data is entered via the PC’s PIM software or with the applications on the Windows CE device. There is no way to directly manipulate this data via the Windows CE Services interface. Windows CE services is dependent on the operating system, the calendaring/e-mail software, and the Windows CE device for date handling. Two-digit shortcut handling: Windows CE Services does not contain any method for entering two-digit shortcuts. Recommendations to meet compliance: Ensure that any products Windows CE Services interacts with have been tested for year 2000 compliance. Common date usage errors: None.
Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. |
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 | ||
Outlook 97, 98, and/or Schedule + 7.0, The Pcs operating System- Windows 95, Windows 98, or Windows NT 4.0 w/ Service Pack 3Windows CE Device | ||
none | ||
19 Nov 1998 | ||
Operational Range for Data: Dependent on PC operating system and PIM software.How the product handles dates: Windows CE Services synchronizes data between the desktop machine and the Windows CE devices. All dates are stored and manipulated as full 4-digit dates. All data is entered via the PC’s PIM software or with the applications on the Windows CE device. There is no way to directly manipulate this data via the Windows CE Services interface. Windows CE services is dependent on the operating system, the calendaring/e-mail software, and the Windows CE device for date handling. Two-digit shortcut handling: Windows CE Services does not contain any method for entering two-digit shortcuts. Recommendations to meet compliance: Ensure that any products Windows CE Services interacts with have been tested for year 2000 compliance. Common date usage errors: None.
Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. |
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 | ||
Outlook 97, Outlook 98, Schedule+ 7.0a, or Schedule+ 7.5The PC’s Operating System: Windows 95, Windows 98, or Windows NT 4.0 A Windows CE device | ||
Operating system clock | ||
25 Mar 1999 | ||
Operational Range for Data: Dependent on Operating System and Personal Information Management software.How the product handles dates: Windows CE Services synchronizes data between the desktop machine and the Windows CE devices. Dates are stored and manipulated as 4-digit dates. Data is entered via the PC’s PIM software or with the applications on the Windows CE device. Direct manipulation of this data is not done via the Windows CE Services interface. Windows CE Services has dependencies on the operating system, the calendaring/e-mail software, Internet Explorer for channel sync, and the Windows CE device for year 2000 compliance. As such, it is recommended users assess and remediate each of these dependencies as indicated in their respective compliance documents. Two-digit shortcut handling: Windows CE Services does not contain any method for entering 2-digit shortcuts. Recommendations to meet compliance: Ensure that any products Windows CE Services interacts with are fully year 2000 compliant. Common date usage errors: None. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.
|
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 | ||
Outlook 97, Outlook 98, Schedule+ 7.0a, or Schedule+ 7.5The PC’s Operating System: Windows 95, Windows 98, or Windows NT 4.0 A Windows CE device | ||
Operating system clock | ||
25 Mar 1999 | ||
Operational Range for Data: Dependent on Operating System and Personal Information Management software.How the product handles dates: Windows CE Services synchronizes data between the desktop machine and the Windows CE devices. Dates are stored and manipulated as 4-digit dates. Data is entered via the PC’s PIM software or with the applications on the Windows CE device. Direct manipulation of this data is not done via the Windows CE Services interface. Windows CE Services has dependencies on the operating system, the calendaring/e-mail software, Internet Explorer for channel sync, and the Windows CE device for year 2000 compliance. As such, it is recommended users assess and remediate each of these dependencies as indicated in their respective compliance documents. Two-digit shortcut handling: Windows CE Services does not contain any method for entering 2-digit shortcuts. Recommendations to meet compliance: Ensure that any products Windows CE Services interacts with are fully year 2000 compliant. Common date usage errors: None. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.
|
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 | ||
Outlook 97, Outlook 98, Schedule+ 7.0a, or Schedule+ 7.5The PC’s Operating System: Windows 95, Windows 98, or Windows NT 4.0 A Windows CE device | ||
Operating system clock | ||
25 Mar 1999 | ||
Operational Range for Data: Dependent on Operating System and Personal Information Management software.How the product handles dates: Windows CE Services synchronizes data between the desktop machine and the Windows CE devices. Dates are stored and manipulated as 4-digit dates. Data is entered via the PC’s PIM software or with the applications on the Windows CE device. Direct manipulation of this data is not done via the Windows CE Services interface. Windows CE Services has dependencies on the operating system, the calendaring/e-mail software, Internet Explorer for channel sync, and the Windows CE device for year 2000 compliance. As such, it is recommended users assess and remediate each of these dependencies as indicated in their respective compliance documents. Two-digit shortcut handling: Windows CE Services does not contain any method for entering 2-digit shortcuts. Recommendations to meet compliance: Ensure that any products Windows CE Services interacts with are fully year 2000 compliant. Common date usage errors: None. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.
|
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 | ||
Outlook 97, Outlook 98, Schedule+ 7.0a, or Schedule+ 7.5The PC’s Operating System: Windows 95, Windows 98, or Windows NT 4.0 A Windows CE device | ||
Operating system clock | ||
25 Mar 1999 | ||
Operational Range for Data: Dependent on Operating System and Personal Information Management software.How the product handles dates: Windows CE Services synchronizes data between the desktop machine and the Windows CE devices. Dates are stored and manipulated as 4-digit dates. Data is entered via the PC’s PIM software or with the applications on the Windows CE device. Direct manipulation of this data is not done via the Windows CE Services interface. Windows CE Services has dependencies on the operating system, the calendaring/e-mail software, Internet Explorer for channel sync, and the Windows CE device for year 2000 compliance. As such, it is recommended users assess and remediate each of these dependencies as indicated in their respective compliance documents. Two-digit shortcut handling: Windows CE Services does not contain any method for entering 2-digit shortcuts. Recommendations to meet compliance: Ensure that any products Windows CE Services interacts with are fully year 2000 compliant. Common date usage errors: None. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.
|
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 | ||
Outlook 97, Outlook 98, Schedule+ 7.0a, or Schedule+ 7.5The PC’s Operating System: Windows 95, Windows 98, or Windows NT 4.0 A Windows CE device | ||
Operating system clock | ||
25 Mar 1999 | ||
Operational Range for Data: Dependent on Operating System and Personal Information Management software.How the product handles dates: Windows CE Services synchronizes data between the desktop machine and the Windows CE devices. Dates are stored and manipulated as 4-digit dates. Data is entered via the PC’s PIM software or with the applications on the Windows CE device. Direct manipulation of this data is not done via the Windows CE Services interface. Windows CE Services has dependencies on the operating system, the calendaring/e-mail software, Internet Explorer for channel sync, and the Windows CE device for year 2000 compliance. As such, it is recommended users assess and remediate each of these dependencies as indicated in their respective compliance documents. Two-digit shortcut handling: Windows CE Services does not contain any method for entering 2-digit shortcuts. Recommendations to meet compliance: Ensure that any products Windows CE Services interacts with are fully year 2000 compliant. Common date usage errors: None. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.
|
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 | ||
Outlook 97, Outlook 98, Schedule+ 7.0a, or Schedule+ 7.5The PC’s Operating System: Windows 95, Windows 98, or Windows NT 4.0 A Windows CE device | ||
Operating system clock | ||
25 Mar 1999 | ||
Operational Range for Data: Dependent on Operating System and Personal Information Management software.How the product handles dates: Windows CE Services synchronizes data between the desktop machine and the Windows CE devices. Dates are stored and manipulated as 4-digit dates. Data is entered via the PC’s PIM software or with the applications on the Windows CE device. Direct manipulation of this data is not done via the Windows CE Services interface. Windows CE Services has dependencies on the operating system, the calendaring/e-mail software, Internet Explorer for channel sync, and the Windows CE device for year 2000 compliance. As such, it is recommended users assess and remediate each of these dependencies as indicated in their respective compliance documents. Two-digit shortcut handling: Windows CE Services does not contain any method for entering 2-digit shortcuts. Recommendations to meet compliance: Ensure that any products Windows CE Services interacts with are fully year 2000 compliant. Common date usage errors: None. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.
|
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 | ||
Outlook 97, Outlook 98, Schedule+ 7.0a, or Schedule+ 7.5The PC’s Operating System: Windows 95, Windows 98, or Windows NT 4.0 A Windows CE device | ||
Operating system clock | ||
25 Mar 1999 | ||
Operational Range for Data: Dependent on Operating System and Personal Information Management software.How the product handles dates: Windows CE Services synchronizes data between the desktop machine and the Windows CE devices. Dates are stored and manipulated as 4-digit dates. Data is entered via the PC’s PIM software or with the applications on the Windows CE device. Direct manipulation of this data is not done via the Windows CE Services interface. Windows CE Services has dependencies on the operating system, the calendaring/e-mail software, Internet Explorer for channel sync, and the Windows CE device for year 2000 compliance. As such, it is recommended users assess and remediate each of these dependencies as indicated in their respective compliance documents. Two-digit shortcut handling: Windows CE Services does not contain any method for entering 2-digit shortcuts. Recommendations to meet compliance: Ensure that any products Windows CE Services interacts with are fully year 2000 compliant. Common date usage errors: None. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.
|
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 | ||
Outlook 97, Outlook 98, Schedule+ 7.0a, or Schedule+ 7.5The PC’s Operating System: Windows 95, Windows 98, or Windows NT 4.0 A Windows CE device | ||
Operating system clock | ||
25 Mar 1999 | ||
Operational Range for Data: Dependent on Operating System and Personal Information Management software.How the product handles dates: Windows CE Services synchronizes data between the desktop machine and the Windows CE devices. Dates are stored and manipulated as 4-digit dates. Data is entered via the PC’s PIM software or with the applications on the Windows CE device. Direct manipulation of this data is not done via the Windows CE Services interface. Windows CE Services has dependencies on the operating system, the calendaring/e-mail software, Internet Explorer for channel sync, and the Windows CE device for year 2000 compliance. As such, it is recommended users assess and remediate each of these dependencies as indicated in their respective compliance documents. Two-digit shortcut handling: Windows CE Services does not contain any method for entering 2-digit shortcuts. Recommendations to meet compliance: Ensure that any products Windows CE Services interacts with are fully year 2000 compliant. Common date usage errors: None. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.
|
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 | ||
Outlook 97, Outlook 98, Schedule+ 7.0a, or Schedule+ 7.5The PC’s Operating System: Windows 95, Windows 98, or Windows NT 4.0 A Windows CE device | ||
Operating system clock | ||
25 Mar 1999 | ||
Operational Range for Data: Dependent on Operating System and Personal Information Management software.How the product handles dates: Windows CE Services synchronizes data between the desktop machine and the Windows CE devices. Dates are stored and manipulated as 4-digit dates. Data is entered via the PC’s PIM software or with the applications on the Windows CE device. Direct manipulation of this data is not done via the Windows CE Services interface. Windows CE Services has dependencies on the operating system, the calendaring/e-mail software, Internet Explorer for channel sync, and the Windows CE device for year 2000 compliance. As such, it is recommended users assess and remediate each of these dependencies as indicated in their respective compliance documents. Two-digit shortcut handling: Windows CE Services does not contain any method for entering 2-digit shortcuts. Recommendations to meet compliance: Ensure that any products Windows CE Services interacts with are fully year 2000 compliant. Common date usage errors: None. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.
|
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 | ||
Outlook 97, Outlook 98, Schedule+ 7.0a, or Schedule+ 7.5The PC’s Operating System: Windows 95, Windows 98, or Windows NT 4.0 A Windows CE device | ||
Operating system clock | ||
25 Mar 1999 | ||
Operational Range for Data: Dependent on Operating System and Personal Information Management software.How the product handles dates: Windows CE Services synchronizes data between the desktop machine and the Windows CE devices. Dates are stored and manipulated as 4-digit dates. Data is entered via the PC’s PIM software or with the applications on the Windows CE device. Direct manipulation of this data is not done via the Windows CE Services interface. Windows CE Services has dependencies on the operating system, the calendaring/e-mail software, Internet Explorer for channel sync, and the Windows CE device for year 2000 compliance. As such, it is recommended users assess and remediate each of these dependencies as indicated in their respective compliance documents. Two-digit shortcut handling: Windows CE Services does not contain any method for entering 2-digit shortcuts. Recommendations to meet compliance: Ensure that any products Windows CE Services interacts with are fully year 2000 compliant. Common date usage errors: None. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.
|
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 | ||
Outlook 97, Outlook 98, Schedule+ 7.0a, or Schedule+ 7.5The PC’s Operating System: Windows 95, Windows 98, or Windows NT 4.0 A Windows CE device | ||
Operating system clock | ||
25 Mar 1999 | ||
Operational Range for Data: Dependent on Operating System and Personal Information Management software.How the product handles dates: Windows CE Services synchronizes data between the desktop machine and the Windows CE devices. Dates are stored and manipulated as 4-digit dates. Data is entered via the PC’s PIM software or with the applications on the Windows CE device. Direct manipulation of this data is not done via the Windows CE Services interface. Windows CE Services has dependencies on the operating system, the calendaring/e-mail software, Internet Explorer for channel sync, and the Windows CE device for year 2000 compliance. As such, it is recommended users assess and remediate each of these dependencies as indicated in their respective compliance documents. Two-digit shortcut handling: Windows CE Services does not contain any method for entering 2-digit shortcuts. Recommendations to meet compliance: Ensure that any products Windows CE Services interacts with are fully year 2000 compliant. Common date usage errors: None. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.
|
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 1999 - 31 Dec 2037 | |||||||||||||||||||||||||||||||||||||||||
Consult the Windows NT Embedded 4.0 compliance document for any issues or updates. Consult Windows NT Server 4.0 SP5 compliance document for post-SP5 updates. | |||||||||||||||||||||||||||||||||||||||||
Windows NT Embedded 4.0, Proxy Server 2.0 | |||||||||||||||||||||||||||||||||||||||||
System Clock | |||||||||||||||||||||||||||||||||||||||||
01 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||
Windows for Express Networks 1.0 is a server appliance embedded system for small business, which is based on a Windows NT Embedded 4.0. Please consult the Windows NT Embedded 4.0 compliance document for any issues or updates related to relevant Windows NT Embedded 4.0 platform technology. The Windows for Express Networks server and client components do not have known Year 2000 issues.How the product handles dates: Please consult the Windows NT Embedded 4.0 compliance document for date handling.Two-digit shortcut handling: Please consult the Windows NT Embedded 4.0 compliance document for 2-digit year shortcut handling.
Testing guidelines and recommendations:
It is recommended that you verify the year 2000 readiness of all components that are included as part of an server appliance configuration. The following tables enumerate the technologies included in the Windows for Express Networks 1.0 product: Table 1: Included Microsoft technology
Table 2: Windows for Express Network 1.0 – features
|
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 1999 - 31 Dec 2037 | |||||||||||||||||||||||||||||||||||||||||
Consult the Windows NT Embedded 4.0 compliance document for any issues or updates. Consult Windows NT Server 4.0 SP5 compliance document for post-SP5 updates. | |||||||||||||||||||||||||||||||||||||||||
Windows NT Embedded 4.0, Proxy Server 2.0 | |||||||||||||||||||||||||||||||||||||||||
System Clock | |||||||||||||||||||||||||||||||||||||||||
01 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||
Windows for Express Networks 1.0 is a server appliance embedded system for small business, which is based on a Windows NT Embedded 4.0. Please consult the Windows NT Embedded 4.0 compliance document for any issues or updates related to relevant Windows NT Embedded 4.0 platform technology. The Windows for Express Networks server and client components do not have known Year 2000 issues.How the product handles dates: Please consult the Windows NT Embedded 4.0 compliance document for date handling.Two-digit shortcut handling: Please consult the Windows NT Embedded 4.0 compliance document for 2-digit year shortcut handling.
Testing guidelines and recommendations:
It is recommended that you verify the year 2000 readiness of all components that are included as part of an server appliance configuration. The following tables enumerate the technologies included in the Windows for Express Networks 1.0 product: Table 1: Included Microsoft technology
Table 2: Windows for Express Network 1.0 – features
|
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 1999 - 31 Dec 2037 | |||||||||||||||||||||||||||||||||||||||||
Consult the Windows NT Embedded 4.0 compliance document for any issues or updates. Consult Windows NT Server 4.0 SP5 compliance document for post-SP5 updates. | |||||||||||||||||||||||||||||||||||||||||
Windows NT Embedded 4.0, Proxy Server 2.0 | |||||||||||||||||||||||||||||||||||||||||
System Clock | |||||||||||||||||||||||||||||||||||||||||
01 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||
Windows for Express Networks 1.0 is a server appliance embedded system for small business, which is based on a Windows NT Embedded 4.0. Please consult the Windows NT Embedded 4.0 compliance document for any issues or updates related to relevant Windows NT Embedded 4.0 platform technology. The Windows for Express Networks server and client components do not have known Year 2000 issues.How the product handles dates: Please consult the Windows NT Embedded 4.0 compliance document for date handling.Two-digit shortcut handling: Please consult the Windows NT Embedded 4.0 compliance document for 2-digit year shortcut handling.
Testing guidelines and recommendations:
It is recommended that you verify the year 2000 readiness of all components that are included as part of an server appliance configuration. The following tables enumerate the technologies included in the Windows for Express Networks 1.0 product: Table 1: Included Microsoft technology
Table 2: Windows for Express Network 1.0 – features
|
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 1999 - 31 Dec 2037 | |||||||||||||||||||||||||||||||||||||||||
Consult the Windows NT Embedded 4.0 compliance document for any issues or updates. Consult Windows NT Server 4.0 SP5 compliance document for post-SP5 updates. | |||||||||||||||||||||||||||||||||||||||||
Windows NT Embedded 4.0, Proxy Server 2.0 | |||||||||||||||||||||||||||||||||||||||||
System Clock | |||||||||||||||||||||||||||||||||||||||||
01 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||
Windows for Express Networks 1.0 is a server appliance embedded system for small business, which is based on a Windows NT Embedded 4.0. Please consult the Windows NT Embedded 4.0 compliance document for any issues or updates related to relevant Windows NT Embedded 4.0 platform technology. The Windows for Express Networks server and client components do not have known Year 2000 issues.How the product handles dates: Please consult the Windows NT Embedded 4.0 compliance document for date handling.Two-digit shortcut handling: Please consult the Windows NT Embedded 4.0 compliance document for 2-digit year shortcut handling.
Testing guidelines and recommendations:
It is recommended that you verify the year 2000 readiness of all components that are included as part of an server appliance configuration. The following tables enumerate the technologies included in the Windows for Express Networks 1.0 product: Table 1: Included Microsoft technology
Table 2: Windows for Express Network 1.0 – features
|
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. |
04 Jan 1980 - 31 Dec 2035 | |||
None | |||
Microsoft DOS version 6.22 | |||
System Clock | |||
16 Nov 1999 | |||
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates:
Product issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this issue, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Microsoft Operating System Interactions with BIOS and Real Time Clock article in the whitepaper section of this product guide for further information.
|
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. |
04 Jan 1980 - 31 Dec 2035 | |||
None | |||
Microsoft DOS version 5.0 or greater | |||
System Clock | |||
21 Sep 1999 | |||
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS file system API’s are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS operating system. More information on MS-DOS issues:
Product issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this issue, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Microsoft Operating System Interactions with BIOS and Real Time Clock article in the whitepaper section of this product guide for further information. |
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. |
04 Jan 1980 - 31 Dec 2035 | |||
Microsoft DOS version 5.0 or later | |||
System Clock | |||
21 Sep 1999 | |||
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS file system API’s are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS operating system. More information on MS-DOS issues:
Product issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this issue, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Microsoft Operating System Interactions with BIOS and Real Time Clock article in the whitepaper section of this product guide for further information. |
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. |
04 Jan 1980 - 31 Dec 2035 | |||
Microsoft DOS version 5.0 or later | |||
System Clock | |||
21 Sep 1999 | |||
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS file system API’s are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS operating system. More information on MS-DOS issues:
Product issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this issue, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Microsoft Operating System Interactions with BIOS and Real Time Clock article in the whitepaper section of this product guide for further information. |
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. |
04 Jan 1980 - 31 Dec 2035 | |||
Microsoft DOS version 5.0 or later | |||
System Clock | |||
21 Sep 1999 | |||
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS file system API’s are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS operating system. More information on MS-DOS issues:
Product issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this issue, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Microsoft Operating System Interactions with BIOS and Real Time Clock article in the whitepaper section of this product guide for further information. |
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. |
04 Jan 1980 - 31 Dec 2035 | ||||
Microsoft DOS version 5.0 or later | ||||
System Clock | ||||
21 Sep 1999 | ||||
Description of how the product handles dates: Storage: All dates are stored internally as 4-digit dates. MS-DOS file system API’s are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows:
2-digit shortcut handling:
Product issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: |
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. |
04 Jan 1980 - 31 Dec 2035 | |||
Microsoft DOS version 5.0 or later | |||
System Clock | |||
21 Sep 1999 | |||
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS file system API’s are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS operating system. More information on MS-DOS issues:
Product issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this issue, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Microsoft Operating System Interactions with BIOS and Real Time Clock article in the whitepaper section of this product guide for further information. |
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. |
04 Jan 1980 - 31 Dec 2035 | |||
Microsoft DOS version 5.0 or later | |||
System Clock | |||
21 Sep 1999 | |||
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS file system API’s are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS operating system. More information on MS-DOS issues:
Product issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this issue, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Microsoft Operating System Interactions with BIOS and Real Time Clock article in the whitepaper section of this product guide for further information. |
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. |
04 Jan 1980 - 31 Dec 2035 | |||
None | |||
Microsoft DOS version 6.22 | |||
System Clock | |||
21 Sep 1999 | |||
Updates- There is an updated version of WINFILE.EXE. For more information see Knowledge Base article at http://www.microsoft.com/intlkb/germany/support/kb/d34/d34672.htm.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remain Compliant# with or without this update. Description of how the product handles dates:
Product issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this issue, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Microsoft Operating System Interactions with BIOS and Real Time Clock article in the whitepaper section of this product guide for further information.
|
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. |
04 Jan 1980 - 31 Dec 2035 | |||
Microsoft DOS version 5.0 or greater | |||
System Clock | |||
21 Sep 1999 | |||
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS file system API’s are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS operating system. More information on MS-DOS issues:
Product issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this issue, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Microsoft Operating System Interactions with BIOS and Real Time Clock article in the whitepaper section of this product guide for further information. |
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. |
04 Jan 1980 - 31 Dec 2035 | |||
Microsoft DOS version 5.0 or later | |||
System Clock | |||
21 Sep 1999 | |||
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS file system API’s are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS operating system. More information on MS-DOS issues:
Product issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this issue, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Microsoft Operating System Interactions with BIOS and Real Time Clock article in the whitepaper section of this product guide for further information. |
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. |
04 Jan 1980 - 31 Dec 2035 | |||
Microsoft DOS version 5.0 or later | |||
System Clock | |||
21 Sep 1999 | |||
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS file system API’s are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS operating system. More information on MS-DOS issues:
Product issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this issue, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Microsoft Operating System Interactions with BIOS and Real Time Clock article in the whitepaper section of this product guide for further information. |
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. |
04 Jan 1980 - 31 Dec 2035 | |||
Microsoft DOS version 5.0 or later | |||
System Clock | |||
21 Sep 1999 | |||
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS file system API’s are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS operating system. More information on MS-DOS issues:
Product issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this issue, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Microsoft Operating System Interactions with BIOS and Real Time Clock article in the whitepaper section of this product guide for further information. |
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. |
04 Jan 1980 - 31 Dec 2035 | |||
None | |||
Microsoft DOS version 6.22 | |||
System Clock | |||
21 Sep 1999 | |||
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS file system API’s are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS operating system. More information on MS-DOS issues:
Product issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this issue, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Microsoft Operating System Interactions with BIOS and Real Time Clock article in the whitepaper section of this product guide for further information. |
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. |
04 Jan 1980 - 31 Dec 2035 | |||
Microsoft DOS version 5.0 or later | |||
System Clock | |||
21 Sep 1999 | |||
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS file system API’s are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS operating system. More information on MS-DOS issues:
Product issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this issue, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Microsoft Operating System Interactions with BIOS and Real Time Clock article in the whitepaper section of this product guide for further information. |
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. |
04 Jan 1980 - 31 Dec 2035 | |||
Microsoft DOS version 5.0 or later | |||
System Clock | |||
21 Sep 1999 | |||
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS file system API’s are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS operating system. More information on MS-DOS issues:
Product issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this issue, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Microsoft Operating System Interactions with BIOS and Real Time Clock article in the whitepaper section of this product guide for further information. |
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. |
04 Jan 1980 - 31 Dec 2035 | |||
Microsoft DOS version 5.0 or later | |||
System Clock | |||
21 Sep 1999 | |||
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS file system API’s are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS operating system. More information on MS-DOS issues:
Product issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this issue, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Microsoft Operating System Interactions with BIOS and Real Time Clock article in the whitepaper section of this product guide for further information. |
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. |
04 Jan 1980 - 31 Dec 2035 | |||
Microsoft DOS version 5.0 or later | |||
System Clock | |||
21 Sep 1999 | |||
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS file system API’s are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS operating system. More information on MS-DOS issues:
Product issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this issue, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Microsoft Operating System Interactions with BIOS and Real Time Clock article in the whitepaper section of this product guide for further information. |
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. |
04 Jan 1980 - 31 Dec 2035 | |||
Microsoft DOS version 5.0 or later | |||
System Clock | |||
21 Sep 1999 | |||
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS file system API’s are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS operating system. More information on MS-DOS issues:
Product issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this issue, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Microsoft Operating System Interactions with BIOS and Real Time Clock article in the whitepaper section of this product guide for further information. |
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. |
04 Jan 1980 - 31 Dec 2035 | |||
Microsoft DOS version 5.0 or later | |||
System Clock | |||
21 Sep 1999 | |||
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS file system API’s are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS operating system. More information on MS-DOS issues:
Product issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this issue, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Microsoft Operating System Interactions with BIOS and Real Time Clock article in the whitepaper section of this product guide for further information. |
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. |
04 Jan 1980 - 31 Dec 2035 | |||
Microsoft DOS version 5.0 or later | |||
System Clock | |||
21 Sep 1999 | |||
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS file system API’s are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS operating system. More information on MS-DOS issues:
Product issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Testing guidelines and recommendations: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this issue, Microsoft recommends executing the tests on a "test-bed" machine rather than a production machine. Please see the Microsoft Operating System Interactions with BIOS and Real Time Clock article in the whitepaper section of this product guide for further information. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more detail. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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 1900 - 31 Dec 2035 | ||
DirectX 3.0 Runtime, Active X 3.01 Runtime | ||
None | ||
None | ||
02 Nov 1999 | ||
Note: There have been no known Internationalization concerns to test, additionally. Thus this product is not dependent on an English language platform for compliance. How the product handles dates: The only place that the Windows Media Player is known to handle dates is the reporting of the creationDate of a media file that is currently being played back. This is a read-only property; i.e. the user cannot set dates using this property. The authoring date is entered into the file by the authoring tools, which is likely the system date on which it was authored. Two-digit shortcut handling: Not applicable. Recommendations to meet compliance: Windows Media Player ships the Internet Explorer 3.0 redistribution package, which has a compliance issue. Installing any Year 2000 Compliant version of Internet Explorer will resolve this issue. See Internet Explorer compliance documents for more details. http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430Testing guidelines 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. |