- | ||
None | ||
None | ||
None | ||
18 Aug 1999 | ||
Platform(s): 32-bit Win, WinNT Operational Range for Data: Not Applicable Microsoft Golf 1999 Edition does not handle dates or perform two-digit shortcut interpretations. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1980 - 31 Dec 2037 | ||
None | ||
Internet Explorer Version 5, Works 2000 Calendars and Reminders, Month Calendar Control from the Common Control Library | ||
None | ||
03 Sep 1999 | ||
This information applies to all Retail, OEM, CD, and DVD versions of the following: Greetings 2000 Home Publishing 2000 Home Publishing Express 2000 How the product handles dates: The product allows users to create week, month, year, and 12-page year calendars. The user is allowed to set the start date for these projects through the date range of 1980 – 2037. The user is also allowed to set reminders for specific events such as birthdays and anniversaries. Two-digit shortcut handling: This product does not perform two-digit shortcut interpretations. Testing guidelines and recommendations: Create calendars and reminders for the years 2000 through 2037.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1980 - 31 Dec 2037 | ||
None | ||
Internet Explorer Version 5, Works 2000 Calendars and Reminders, Month Calendar Control from the Common Control Library | ||
None | ||
03 Sep 1999 | ||
This information applies to all Retail, OEM, CD, and DVD versions of the following: Greetings 2000 Home Publishing 2000 Home Publishing Express 2000 How the product handles dates: The product allows users to create week, month, year, and 12-page year calendars. The user is allowed to set the start date for these projects through the date range of 1980 – 2037. The user is also allowed to set reminders for specific events such as birthdays and anniversaries. Two-digit shortcut handling: This product does not perform two-digit shortcut interpretations. Testing guidelines and recommendations: Create calendars and reminders for the years 2000 through 2037.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2035 | ||
None | ||
Product requires Windows 95, Windows 98 or Windows NT 4.0 or later. | ||
None | ||
03 Apr 1999 | ||
How the product handles dates: The Greetings 99 (U.S. English & International English) products allow users to create paper based monthly and yearly calendars for any month or year between January 1970 and December 2035. After the user chooses the appropriate date for the calendar, the applications create a document with an appropriately filled out calendar grid or grids. The products also have the capability to issue messages to remind users of upcoming holidays or user-defined special events such as birthdays, anniversaries or appointments that fall on dates within the aforementioned range. To create a reminder message, users specify the reminder message text and choose the time period for the message to appear in advance of the event. A reminder scanner application executing on the system will display the reminder message to the user when the specified time has been reached. Dates for calendars, pre-set and user-defined reminders are stored on disk and in memory as unique values with a 4-digit representation of the year. None of the operating system requirements impact permitted date ranges or date handling behavior. Two-digit shortcut handling: Not Applicable.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2035 | ||
None | ||
Product requires Windows 95, Windows 98 or Windows NT 4.0 or later. | ||
None | ||
03 Apr 1999 | ||
How the product handles dates: The Greetings 99 (U.S. English & International English) products allow users to create paper based monthly and yearly calendars for any month or year between January 1970 and December 2035. After the user chooses the appropriate date for the calendar, the applications create a document with an appropriately filled out calendar grid or grids. The products also have the capability to issue messages to remind users of upcoming holidays or user-defined special events such as birthdays, anniversaries or appointments that fall on dates within the aforementioned range. To create a reminder message, users specify the reminder message text and choose the time period for the message to appear in advance of the event. A reminder scanner application executing on the system will display the reminder message to the user when the specified time has been reached. Dates for calendars, pre-set and user-defined reminders are stored on disk and in memory as unique values with a 4-digit representation of the year. None of the operating system requirements impact permitted date ranges or date handling behavior. Two-digit shortcut handling: Not Applicable.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2035 | ||
None | ||
Product requires Windows 95, Windows 98 or Windows NT 4.0 or later. | ||
None | ||
30 Mar 1999 | ||
How the product handles dates: The Greetings 99 (U.S. English & International English) products allow users to create paper based monthly and yearly calendars for any month or year between January 1970 and December 2035. After the user chooses the appropriate date for the calendar, the applications create a document with an appropriately filled out calendar grid or grids. The products also have the capability to issue messages to remind users of upcoming holidays or user-defined special events such as birthdays, anniversaries or appointments that fall on dates within the aforementioned range. To create a reminder message, users specify the reminder message text and choose the time period for the message to appear in advance of the event. A reminder scanner application executing on the system will display the reminder message to the user when the specified time has been reached. Dates for calendars, pre-set and user-defined reminders are stored on disk and in memory as unique values with a 4-digit representation of the year. None of the operating system requirements impact permitted date ranges or date handling behavior. Two-digit shortcut handling: Not Applicable.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2035 | ||
None | ||
Product requires Windows 95, Windows 98 or NT4.0 or later. None of these operating system requirements impact date range or behavior. | ||
None. | ||
07 Jul 1999 | ||
How the product handles dates: The Greetings Workshop 2.0 and Greetings Workshop Deluxe 2.0 (U.S. English & International English) products allow users to create paper based monthly and yearly calendars for dates between January 1, 1970 and December 31, 2035. After choosing the appropriate month and/or year for the calendar, the application will create a document with an appropriately filled out calendar grid or grids. The products also allow users to enter reminders for special events (e.g. birthdays, anniversaries, appointments, etc.) that fall on any date within this same range. Users are able to select from a list of predefined time periods before the actual date of the event in which to receive a reminder for the event. A small reminder scanner application executes on the user’s system and will show a reminder message to the user when the time period has elapsed even though the Greetings Workshop application may not be running at the time. A known problem with the reminder scanner application is that it will fail to show pop up reminder messages for any events if the machine time where the scanner is running is later than January 1, 2000. This bug was caused by a problem in copy of an early COLEDateTime() routine used by the reminder scanner application. This problem only affects the ability of the reminder scanner to show reminder messages on machines where system time is later than January 1, 2000. The problem does not affect a user’s ability to create month or year calendars or to create reminders for holidays or special events. Date values for both calendar and reminder features in the product are calculated via the COleDateTime() class and stored in a Jet/Access 97database in date/time fields There are no known date storage or conversion issues in Access 97 that affect Greetings Workshop. Two-digit shortcut handling: N/A |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2035 | ||
None | ||
Product requires Windows 95, Windows 98 or NT4.0 or later. None of these operating system requirements impact date range or behavior. | ||
None | ||
07 Jul 1999 | ||
How the product handles dates: The Greetings Workshop 2.0 and Greetings Workshop Deluxe 2.0 (U.S. English & International English) products allow users to create paper based monthly and yearly calendars for dates between January 1, 1970 and December 31, 2035. After choosing the appropriate month and/or year for the calendar, the application will create a document with an appropriately filled out calendar grid or grids. The products also allow users to enter reminders for special events (e.g. birthdays, anniversaries, appointments, etc.) that fall on any date within this same range. Users are able to select from a list of predefined time periods before the actual date of the event in which to receive a reminder for the event. A small reminder scanner application executes on the user’s system and will show a reminder message to the user when the time period has elapsed even though the Greetings Workshop application may not be running at the time. A known problem with the reminder scanner application is that it will fail to show pop up reminder messages for any events if the machine time where the scanner is running is later than January 1, 2000. This bug was caused by a problem in copy of an early COLEDateTime() routine used by the reminder scanner application. This problem only affects the ability of the reminder scanner to show reminder messages on machines where system time is later than January 1, 2000. The problem does not affect a user’s ability to create month or year calendars or to create reminders for holidays or special events. Date values for both calendar and reminder features in the product are calculated via the COleDateTime() class and stored in a Jet/Access 97database in date/time fields There are no known date storage or conversion issues in Access 97 that affect Greetings Workshop. Two-digit shortcut handling: N/A |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2035 | ||
None | ||
Product requires Windows 95, Windows 98 or NT4.0 or later. None of these operating system requirements impact date range or behavior. | ||
None | ||
07 Jul 1999 | ||
How the product handles dates: The Greetings Workshop 2.0 and Greetings Workshop Deluxe 2.0 (U.S. English & International English) products allow users to create paper based monthly and yearly calendars for dates between January 1, 1970 and December 31, 2035. After choosing the appropriate month and/or year for the calendar, the application will create a document with an appropriately filled out calendar grid or grids. The products also allow users to enter reminders for special events (e.g. birthdays, anniversaries, appointments, etc.) that fall on any date within this same range. Users are able to select from a list of predefined time periods before the actual date of the event in which to receive a reminder for the event. A small reminder scanner application executes on the user’s system and will show a reminder message to the user when the time period has elapsed even though the Greetings Workshop application may not be running at the time. A known problem with the reminder scanner application is that it will fail to show pop up reminder messages for any events if the machine time where the scanner is running is later than January 1, 2000. This bug was caused by a problem in copy of an early COLEDateTime() routine used by the reminder scanner application. This problem only affects the ability of the reminder scanner to show reminder messages on machines where system time is later than January 1, 2000. The problem does not affect a user’s ability to create month or year calendars or to create reminders for holidays or special events. Date values for both calendar and reminder features in the product are calculated via the COleDateTime() class and stored in a Jet/Access 97database in date/time fields There are no known date storage or conversion issues in Access 97 that affect Greetings Workshop. Two-digit shortcut handling: N/A |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2035 | ||
None | ||
Product requires Windows 95, Windows 98 or NT4.0 or later. None of these operating system requirements impact date range or behavior. | ||
None | ||
07 Jul 1999 | ||
How the product handles dates: The Greetings Workshop 2.0 and Greetings Workshop Deluxe 2.0 (U.S. English & International English) products allow users to create paper based monthly and yearly calendars for dates between January 1, 1970 and December 31, 2035. After choosing the appropriate month and/or year for the calendar, the application will create a document with an appropriately filled out calendar grid or grids. The products also allow users to enter reminders for special events (e.g. birthdays, anniversaries, appointments, etc.) that fall on any date within this same range. Users are able to select from a list of predefined time periods before the actual date of the event in which to receive a reminder for the event. A small reminder scanner application executes on the user’s system and will show a reminder message to the user when the time period has elapsed even though the Greetings Workshop application may not be running at the time. A known problem with the reminder scanner application is that it will fail to show pop up reminder messages for any events if the machine time where the scanner is running is later than January 1, 2000. This bug was caused by a problem in copy of an early COLEDateTime() routine used by the reminder scanner application. This problem only affects the ability of the reminder scanner to show reminder messages on machines where system time is later than January 1, 2000. The problem does not affect a user’s ability to create month or year calendars or to create reminders for holidays or special events. Date values for both calendar and reminder features in the product are calculated via the COleDateTime() class and stored in a Jet/Access 97database in date/time fields There are no known date storage or conversion issues in Access 97 that affect Greetings Workshop. Two-digit shortcut handling: N/A |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
18 Jan 1980 - 18 Jan 2038 | ||
None | ||
Windows 95, Windows 98 or Windows NT 4.0 SP3 or higher | ||
System Clock | ||
16 Jul 1999 | ||
Note: To install the Hagaki Studio 1.0 on Windows 98, you need to download the update module from http://www.asia.microsoft.com/japan/office/officefreestuff/hagakistudio/mshs15up/
How the product handles dates:
Two-digit shortcut handling: Data Entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Hagaki Studio interprets 2-digit-year entries as between 1930 and 2029. On the Windows 98 operating system, Hagaki Studio respects the year range setting specified by the user on the Data tab in Regional Settings. As a result, Hagaki Studio interprets 2-digit year entries as a year in the specified range.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
18 Jan 1980 - 18 Jan 2038 | ||
None | ||
Windows 95, Windows 98 or Windows NT 4.0 SP3 or higher | ||
System Clock | ||
16 Jul 1999 | ||
How the product handles dates:
Two-digit shortcut handling: Data Entry fields parse and accept 2-digiti year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating system, Hagaki Studio interprets 2-digit-year entries between 1930 and 2029. On the Windows 98 operating system, Hagaki Studio respects the year range setting specified by the user on the Data tab in Regional Settings. As a result, Hagaki Studio interprets 2-digit year entries as a year in the specified range.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
18 Jan 1980 - 18 Jan 2038 | ||
None | ||
Windows 95, Windows 98 or Windows NT 4.0 SP3, Internet Explorer 4.01 Service Pack 1 or higher | ||
System Clock | ||
16 Jul 1999 | ||
How the product handles dates:
Two-digit shortcut handling: Data Entry fields parse and accept 2-digiti year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating system, Hagaki Studio interprets 2-digit-year entries as between 1930 and 2029. On the Windows 98 operating system, Hagaki Studio respects the year range setting specified by the user on the Data tab in Regional Settings. As a result. Hagaki Studio interprets 2-digit year entries as a year in the specified range. Recommendations to meet compliance: Hagaki Studio 2 setup Disk contains Internet Explorer 4.0 Service Pack 1. Users need to install Internet Explorer 4.0 Service Pack 2 or install COMCTL32.DLL V4.72 or higher that is distributed individually.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
18 Jan 1980 - 18 Jan 2038 | ||
None | ||
Windows 95, Windows 98 or Windows NT 4.0 SP4 or higher | ||
System Clock | ||
09 Nov 1999 | ||
How the product handles dates:
Two-digit shortcut handling: Data Entry fields parse and accept 2-digit-year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating system, Hagaki Studio interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Hagaki Studio respects the year range setting specified by the user on the Data tab in Regional Settings. Hagaki Studio interprets 2-digit year entries as a year in the specified range.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||
DOS 5.0, Win 3.1 | ||
System Clock | ||
02 Nov 1999 | ||
How the product handles dates: No date handling or two-digit shortcut interpretation is performed. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||
Macintosh Operating System | ||
System Clock | ||
02 Nov 1999 | ||
How the product handles dates: No date handling or two-digit shortcut interpretation is performed. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||
Macintosh System 7 or above, Windows 95, Windows 98, or Windows NT 4.0 Service Pack 4 or later running Internet Explorer version 3.02 or greater or Netscape Navigator 3.x or greater | ||
System Clock | ||
07 Oct 1999 | ||
Home Advisor can be found at: http://www.homeadvisor.msn.com/ie/ How the product handles dates: Loan Validation Tool (LVT) –Inbound loan data is processed through the LVT, which checks for 4-digit date format on the date fields. This is intended to prevent invalid dates from entering the HomeAdvisor database. Cookie processing – session cookies are deleted upon browser exit and no date related calculations are performed using session cookies. Two-digit shortcut handling: Not applicable. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 - 03 Jun 2079 | ||||||||||
See individual compliance documents | ||||||||||
Windows 95 or Windows NT 4.0 | ||||||||||
System clock | ||||||||||
28 Jul 1999 | ||||||||||
Home Essentials 98 is composed of individual components. There is no cross-product functionality to be tested for compliance. For more information, see the compliance documents for the individual components in Home Essentials 98: http://www.microsoft.com/services/technet/topics/year2k/product/product.htm.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 - 03 Jun 2079 | ||||||||||
See individual compliance documents | ||||||||||
Windows 95 or Windows NT 4.0 | ||||||||||
System Clock | ||||||||||
28 Jul 1999 | ||||||||||
Home Essentials 98 is composed of individual components. There is no cross-product functionality to be tested for compliance. For more information, see the compliance documents for the individual components in Home Essentials 98: http://www.microsoft.com/technet/year2k/product/product.asp.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 - 03 Jun 2079 | ||||||||||
See individual compliance documents | ||||||||||
Windows 95 or Windows NT 4.0 | ||||||||||
System Clock | ||||||||||
28 Jul 1999 | ||||||||||
Home Essentials 98 is composed of individual components. There is no cross-product functionality to be tested for compliance. For more information, see the compliance documents for the individual components in Home Essentials 98: http://www.microsoft.com/technet/year2k/product/product.asp.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 - 03 Jun 2079 | ||||||||||
See individual compliance documents | ||||||||||
Windows 95 or Windows NT 4.0 | ||||||||||
System Clock | ||||||||||
28 Jul 1999 | ||||||||||
Home Essentials 98 is composed of individual components. There is no cross-product functionality to be tested for compliance. For more information, see the compliance documents for the individual components in Home Essentials 98: http://www.microsoft.com/technet/year2k/product/product.asp.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 - 03 Jun 2079 | ||||||||||
See individual compliance documents | ||||||||||
Windows 95 or Windows NT 4.0 | ||||||||||
System Clock | ||||||||||
28 Jul 1999 | ||||||||||
Home Essentials 98 is composed of individual components. There is no cross-product functionality to be tested for compliance. For more information, see the compliance documents for the individual components in Home Essentials 98: http://www.microsoft.com/technet/year2k/product/product.asp.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 - 03 Jun 2079 | ||||||||||
See individual compliance documents | ||||||||||
Windows 95 or Windows NT 4.0 | ||||||||||
System Clock | ||||||||||
28 Jul 1999 | ||||||||||
Home Essentials 98 is composed of individual components. There is no cross-product functionality to be tested for compliance. For more information, see the compliance documents for the individual components in Home Essentials 98: http://www.microsoft.com/technet/year2k/product/product.asp.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 - 03 Jun 2079 | ||||||||||
See individual compliance documents | ||||||||||
Windows 95 or Windows NT 4.0 | ||||||||||
System Clock | ||||||||||
28 Jul 1999 | ||||||||||
Home Essentials 98 is composed of individual components. There is no cross-product functionality to be tested for compliance. For more information, see the compliance documents for the individual components in Home Essentials 98: http://www.microsoft.com/technet/year2k/product/product.asp.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 - 03 Jun 2079 | ||||||||||
See individual compliance documents | ||||||||||
Windows 95 or Windows NT 4.0 | ||||||||||
System Clock | ||||||||||
28 Jul 1999 | ||||||||||
Home Essentials 98 is composed of individual components. There is no cross-product functionality to be tested for compliance. For more information, see the compliance documents for the individual components in Home Essentials 98: http://www.microsoft.com/technet/year2k/product/product.asp.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 - 03 Jun 2079 | ||||||||||
See individual compliance documents | ||||||||||
Windows 95 or Windows NT 4.0 | ||||||||||
System Clock | ||||||||||
28 Jul 1999 | ||||||||||
Home Essentials 98 is composed of individual components. There is no cross-product functionality to be tested for compliance. For more information, see the compliance documents for the individual components in Home Essentials 98: http://www.microsoft.com/technet/year2k/product/product.asp.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 - 03 Jun 2079 | ||||||||||
See individual compliance documents | ||||||||||
Windows 95 or Windows NT 4.0 | ||||||||||
System Clock | ||||||||||
28 Jul 1999 | ||||||||||
Home Essentials 98 is composed of individual components. There is no cross-product functionality to be tested for compliance. For more information, see the compliance documents for the individual components in Home Essentials 98: http://www.microsoft.com/technet/year2k/product/product.asp.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1980 - 31 Dec 2037 | ||
None | ||
Internet Explorer Version 5, Works 2000 Calendars and Reminders, Month Calendar Control from the Common Control Library | ||
None | ||
21 Sep 1999 | ||
This information applies to all Retail, OEM, CD, and DVD versions of the following: Greetings 2000 Home Publishing 2000 Home Publishing Express 2000 Home Publishing Suite 2000 How the product handles dates: The product allows users to create week, month, year, and 12-page year calendars. The user is allowed to set the start date for these projects through the date range of 1980 – 2037. The user is also allowed to set reminders for specific events such as birthdays and anniversaries. Two-digit shortcut handling: This product does not perform two-digit shortcut interpretations. Testing guidelines and recommendations: Create calendars and reminders for the years 2000 through 2037.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1980 - 31 Dec 2037 | ||
None | ||
Internet Explorer Version 5, Works 2000 Calendars and Reminders, Month Calendar Control from the Common Control Library | ||
None | ||
21 Sep 1999 | ||
This information applies to all Retail, OEM, CD, and DVD versions of the following: Greetings 2000 Home Publishing 2000 Home Publishing Express 2000 Home Publishing Suite 2000 How the product handles dates: The product allows users to create week, month, year, and 12-page year calendars. The user is allowed to set the start date for these projects through the date range of 1980 – 2037. The user is also allowed to set reminders for specific events such as birthdays and anniversaries. Two-digit shortcut handling: This product does not perform two-digit shortcut interpretations. Testing guidelines and recommendations: Create calendars and reminders for the years 2000 through 2037.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2035 | ||
None | ||
None | ||
None | ||
15 Sep 1999 | ||
This report applies to: Home Publishing Home Publishing Suite How the product handles dates: The Home Publishing 99 (U.S. English & International English) products allow users to create paper based monthly and yearly calendars for any month or year between January 1970 and December 2035. After the user chooses the appropriate date for the calendar, the applications create a document with an appropriately filled out calendar grid or grids. The products also have the capability to issue messages to remind users of upcoming holidays or user-defined special events such as birthdays, anniversaries or appointments that fall on dates within the aforementioned range. To create a reminder message, users specify the reminder message text and choose the time period for the message to appear in advance of the event. A reminder scanner application executing on the system will display the reminder message to the user when the specified time has been reached.
Dates for calendars, pre-set and user-defined reminders are stored on disk and in memory as unique values with a 4-digit representation of the year. None of the operating system requirements impact permitted date ranges or date handling behavior. Two-digit shortcut handling: Not Applicable.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2035 | ||
None | ||
None | ||
None | ||
15 Sep 1999 | ||
This report applies to: Home Publishing Home Publishing Suite How the product handles dates: The Home Publishing 99 (U.S. English & International English) products allow users to create paper based monthly and yearly calendars for any month or year between January 1970 and December 2035. After the user chooses the appropriate date for the calendar, the applications create a document with an appropriately filled out calendar grid or grids. The products also have the capability to issue messages to remind users of upcoming holidays or user-defined special events such as birthdays, anniversaries or appointments that fall on dates within the aforementioned range. To create a reminder message, users specify the reminder message text and choose the time period for the message to appear in advance of the event. A reminder scanner application executing on the system will display the reminder message to the user when the specified time has been reached.
Dates for calendars, pre-set and user-defined reminders are stored on disk and in memory as unique values with a 4-digit representation of the year. None of the operating system requirements impact permitted date ranges or date handling behavior. Two-digit shortcut handling: Not Applicable.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2035 | ||
None | ||
None | ||
None | ||
15 Sep 1999 | ||
This report applies to: Home Publishing Home Publishing Suite How the product handles dates: The Home Publishing 99 (U.S. English & International English) products allow users to create paper based monthly and yearly calendars for any month or year between January 1970 and December 2035. After the user chooses the appropriate date for the calendar, the applications create a document with an appropriately filled out calendar grid or grids. The products also have the capability to issue messages to remind users of upcoming holidays or user-defined special events such as birthdays, anniversaries or appointments that fall on dates within the aforementioned range. To create a reminder message, users specify the reminder message text and choose the time period for the message to appear in advance of the event. A reminder scanner application executing on the system will display the reminder message to the user when the specified time has been reached.
Dates for calendars, pre-set and user-defined reminders are stored on disk and in memory as unique values with a 4-digit representation of the year. None of the operating system requirements impact permitted date ranges or date handling behavior. Two-digit shortcut handling: Not Applicable.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1980 - 31 Dec 2037 | ||
None | ||
Internet Explorer Version 5, Works 2000 Calendars and Reminders, Month Calendar Control from the Common Control Library | ||
None | ||
03 Sep 1999 | ||
This information applies to all Retail, OEM, CD, and DVD versions of the following: Greetings 2000 Home Publishing 2000 Home Publishing Express 2000 How the product handles dates: The product allows users to create week, month, year, and 12-page year calendars. The user is allowed to set the start date for these projects through the date range of 1980 – 2037. The user is also allowed to set reminders for specific events such as birthdays and anniversaries. Two-digit shortcut handling: This product does not perform two-digit shortcut interpretations. Testing guidelines and recommendations: Create calendars and reminders for the years 2000 through 2037.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1980 - 31 Dec 2037 | ||
None | ||
Internet Explorer Version 5, Works 2000 Calendars and Reminders, Month Calendar Control from the Common Control Library | ||
None | ||
03 Sep 1999 | ||
This information applies to all Retail, OEM, CD, and DVD versions of the following: Greetings 2000 Home Publishing 2000 Home Publishing Express 2000 How the product handles dates: The product allows users to create week, month, year, and 12-page year calendars. The user is allowed to set the start date for these projects through the date range of 1980 – 2037. The user is also allowed to set reminders for specific events such as birthdays and anniversaries. Two-digit shortcut handling: This product does not perform two-digit shortcut interpretations. Testing guidelines and recommendations: Create calendars and reminders for the years 2000 through 2037.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.00 with the Year 2000 software update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer | ||
None | ||
14 Sep 1999 | ||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.0 with the Year 2000 Update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer 3.0x or later | ||
None | ||
14 Sep 1999 | ||
Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliance, Microsoft recommends using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 100 - 31 Dec 9999 | ||
none | ||
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 (no specific Service Pack is required, though Service Pack 3 is recommended) | ||
Operating System Clock | ||
02 Nov 1998 | ||
Description of how dates are handled in the product: Image Composer uses the System dates in the following manner: When saving in the *.mic format, Image Composer uses the operating system dates. Does the product support 2 digit shortcuts for date representation? See discussion below. Conversion of 2-digit shortcut dates assumes a date window of 1930 through 2029. What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation?
Are there some common pitfalls for use or testing of this product that may have caused the customer to use the product in a non-compliant fashion? Sprite and composition properties store dates in the annotations. The dates stored are entered by the user, so the user could choose to enter a date in 2-digit 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 100 - 31 Dec 9999 | ||
none | ||
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 (no specific Service Pack is required, though Service Pack 3 is recommended) | ||
Operating System Clock | ||
02 Nov 1998 | ||
Description of how dates are handled in the product: Image Composer uses the System dates in the following manner: When saving in the *.mic format, Image Composer uses the operating system dates. Does the product support 2 digit shortcuts for date representation? See discussion below. Conversion of 2-digit shortcut dates assumes a date window of 1930 through 2029. What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation?
Are there some common pitfalls for use or testing of this product that may have caused the customer to use the product in a non-compliant fashion? Sprite and composition properties store dates in the annotations. The dates stored are entered by the user, so the user could choose to enter a date in 2-digit 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 100 - 31 Dec 9999 | ||
none | ||
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 (no specific Service Pack is required, though Service Pack 3 is recommended) | ||
Operating System Clock | ||
02 Nov 1998 | ||
Description of how dates are handled in the product: Image Composer uses the System dates in the following manner: When saving in the *.mic format, Image Composer uses the operating system dates. Does the product support 2 digit shortcuts for date representation? See discussion below. Conversion of 2-digit shortcut dates assumes a date window of 1930 through 2029. What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation?
Are there some common pitfalls for use or testing of this product that may have caused the customer to use the product in a non-compliant fashion? Sprite and composition properties store dates in the annotations. The dates stored are entered by the user, so the user could choose to enter a date in 2-digit 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. |
- | ||
Internet Explorer 3.0 with the Year 2000 Update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer 3.0x or later | ||
None | ||
10 Sep 1999 | ||
(InfoViewer 5.0 is also known as Visual Studio 97 Documentation Viewer) Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliancy, we recommend using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.0 with the Year 2000 Update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer 3.0x or later | ||
None | ||
10 Sep 1999 | ||
(InfoViewer 5.0 is also known as Visual Studio 97 Documentation Viewer) Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliancy, we recommend using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Internet Explorer 3.0 with the Year 2000 Update | ||
Windows NT 4.0, Windows 95, Windows 98 with Internet Explorer 3.0x or later | ||
None | ||
10 Sep 1999 | ||
(InfoViewer 5.0 is also known as Visual Studio 97 Documentation Viewer) Operational Range for Data: System Dependent How the product runtime handles dates: There is no User Interface for entering dates. A 64-bit file time stamp value is stored in the compiled help title to represent the date and time it was built. This time value has no known date related issues. Two-digit shortcut handling: Does not apply. Recommended practices to develop year 2000 compliant applications: For Year 2000 compliancy, we recommend using an Internet browser that is year 2000 compliant. Some versions of Microsoft Internet Explorer may have issues related to the year 2000. Please refer to the Microsoft Year 2000 Product Guide for more information on specific versions of Internet Explorer.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
None | ||
Windows 95 | ||
System Clock | ||
15 Jul 1999 | ||
Operational Range: Operating System dependent How the product handles dates:Storage. Microsoft Input Message Editor 95 does not store any date/time. It just passes the data through to applications. String date parsing . Microsoft IME 95 does not parse dates or time. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Windows 95, or Windows NT 4 | ||
Operating System dependent | ||
15 Jul 1999 | ||
How the product handles dates:
Storage. Microsoft Input Message Editor 97 does not store any date/time. It just passes the data through to applications. String date parsing . Microsoft IME 97 does not parse dates or time.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Windows 95, Windows 98, Windows NT 4 | ||
System clock | ||
15 Jul 1999 | ||
String date parsing . Microsoft Input Message Editor 98 supports date and time input with the software keyboard of an IMEpad applet, but does not parse dates or time. It accepts the bottom "date" or "time" and just inputs the string to the application. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Mac Operating Systems 8.5.1 or later | ||
System Clock | ||
13 Oct 1999 | ||
How the product handles dates: This version of IntelliPoint does not process dates. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Mac Operating Systems 8.5.1 or later | ||
System Clock | ||
13 Oct 1999 | ||
How the product handles dates: This version of IntelliPoint does not process dates. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Mac Operating Systems 8.5.1 or later | ||
System Clock | ||
13 Oct 1999 | ||
How the product handles dates: This version of IntelliPoint does not process dates. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Mac Operating Systems 8.5.1 or later | ||
System Clock | ||
13 Oct 1999 | ||
How the product handles dates: This version of IntelliPoint does not process dates. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Mac Operating Systems 8.5.1 or later | ||
System Clock | ||
13 Oct 1999 | ||
How the product handles dates: This version of IntelliPoint does not process dates. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Mac Operating Systems 8.5.1 or later | ||
System Clock | ||
25 Oct 1999 | ||
How the product handles dates: This version of IntelliPoint does not process dates. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Mac Operating Systems 8.5.1 or later | ||
System Clock | ||
13 Oct 1999 | ||
How the product handles dates: This version of IntelliPoint does not process dates. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1853 - 31 Dec 2107 | ||
NONE | ||
MS-DOS 3.1, Windows 3.1, Windows 95 & all OEM Service Releases, Windows NT 3.51 & all Service Packs. | ||
Operating System Clock | ||
30 Jul 1999 | ||
How dates are handled in the product: The IntelliPoint 1.x software for two-button mice performs only one date operation. Its Setup program utilizes a Date field as part of the PID verification. This software stores the entire date in a WORD as an offset of +/-127 from 1980. This results in support for years: 1853-2107. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 1853 - 31 Dec 2107 | ||
NONE | ||
MS-DOS 3.1, Windows 3.1, Windows 95 & all OEM Service Releases, Windows NT 3.51 & all Service Packs. | ||
Operating System Clock | ||
30 Jul 1999 | ||
How dates are handled in the product: The IntelliPoint 1.x software for two-button mice performs only one date operation. Its Setup program utilizes a Date field as part of the PID verification. This software stores the entire date in a WORD as an offset of +/-127 from 1980. This results in support for years: 1853-2107. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 1853 - 31 Dec 2107 | ||
None | ||
MS-DOS 3.1, Windows 3.1, Windows 95 & all OEM Service Releases, Windows NT 3.51 & all Service Packs. | ||
Operating System Clock | ||
30 Jul 1999 | ||
How dates are handled in the product: The IntelliPoint 1.x software for two-button mice performs only one date operation. Its Setup program utilizes a Date field as part of the PID verification. This software stores the entire date in a WORD as an offset of +/-127 from 1980. This results in support for years: 1853-2107. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, .2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, .2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1970 - 31 Dec 2037 | ||
NONE | ||
Windows 95, Windows NT 4.0, all OEM Service Releases, all Service Packs, and greater. | ||
Operating System Clock | ||
30 Jul 1999 | ||
This document is applicable to versions 2.0, 2.0a, 2.1, 2.2. Release Date: 10/3/96 (2.0), 3/5/97 (2.0a), 8/8/97 (2.1), 3/31/98 (2.2) How dates are handled in the product: The IntelliPoint 2.x software for wheel mice and trackballs performs only one date operation. The Odometer feature software stores a Date field to show the user the length of time since the Odometer feature was reset. This Date field is stored in a WORD as an offset in seconds from the year 1970. This results in support for years: 1970-2038. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
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. |