Product Summary
Product: MS-DOS	Version: 6.0	Category:Compliant#
Language: Korean	OS: DOS	Release Date: N/A
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC Bios
Last Updated:	28 Oct 1999
Product Details
How the product handles dates: MS-DOS is aware of dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOS® DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date" upon entry of 2-digit dates in this range. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. Product compliance issues:        MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. External commands with switches that use a date parameter require years beyond 2000 to be entered using all 4 digits. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.0 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006),   MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.0 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Similarly, when MSBACKUP is backing up, restoring, or comparing files with dates greater than 1999 the file date is not displayed correctly. This is strictly a limitation of the MSBACKUP user interface and does not prevent MSBACKUP from properly backing up, restoring, or comparing files. Recommendations: There are no patches available at this time and no plans to develop any patches. The commands described above are infrequently used and easily worked around. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.0	Category:Compliant#
Language: Norwegian	OS: DOS	Release Date: 10 Mar 1993
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC Bios
Last Updated:	28 Oct 1999
Product Details
How the product handles dates: MS-DOS is aware of dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOS® DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date" upon entry of 2-digit dates in this range. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. Product compliance issues:        MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. External commands with switches that use a date parameter require years beyond 2000 to be entered using all 4 digits. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.0 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006),   MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.0 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Similarly, when MSBACKUP is backing up, restoring, or comparing files with dates greater than 1999 the file date is not displayed correctly. This is strictly a limitation of the MSBACKUP user interface and does not prevent MSBACKUP from properly backing up, restoring, or comparing files. Recommendations: There are no patches available at this time and no plans to develop any patches. The commands described above are infrequently used and easily worked around. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.0	Category:Compliant#
Language: Portuguese (Brazil)	OS: DOS	Release Date: 10 Mar 1993
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC Bios
Last Updated:	28 Oct 1999
Product Details
How the product handles dates: MS-DOS is aware of dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOS® DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date" upon entry of 2-digit dates in this range. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. Product compliance issues:        MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. External commands with switches that use a date parameter require years beyond 2000 to be entered using all 4 digits. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.0 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006),   MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.0 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Similarly, when MSBACKUP is backing up, restoring, or comparing files with dates greater than 1999 the file date is not displayed correctly. This is strictly a limitation of the MSBACKUP user interface and does not prevent MSBACKUP from properly backing up, restoring, or comparing files. Recommendations: There are no patches available at this time and no plans to develop any patches. The commands described above are infrequently used and easily worked around. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.0	Category:Compliant#
Language: Russian	OS: DOS	Release Date: 10 Mar 1993
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC Bios
Last Updated:	28 Oct 1999
Product Details
How the product handles dates: MS-DOS is aware of dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOS® DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date" upon entry of 2-digit dates in this range. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. Product compliance issues:        MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. External commands with switches that use a date parameter require years beyond 2000 to be entered using all 4 digits. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.0 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006),   MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.0 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Similarly, when MSBACKUP is backing up, restoring, or comparing files with dates greater than 1999 the file date is not displayed correctly. This is strictly a limitation of the MSBACKUP user interface and does not prevent MSBACKUP from properly backing up, restoring, or comparing files. Recommendations: There are no patches available at this time and no plans to develop any patches. The commands described above are infrequently used and easily worked around. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.0	Category:Compliant#
Language: Spanish	OS: DOS	Release Date: 10 Mar 1993
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC Bios
Last Updated:	28 Oct 1999
Product Details
How the product handles dates: MS-DOS is aware of dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOS® DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date" upon entry of 2-digit dates in this range. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. Product compliance issues:        MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. External commands with switches that use a date parameter require years beyond 2000 to be entered using all 4 digits. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.0 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006),   MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.0 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Similarly, when MSBACKUP is backing up, restoring, or comparing files with dates greater than 1999 the file date is not displayed correctly. This is strictly a limitation of the MSBACKUP user interface and does not prevent MSBACKUP from properly backing up, restoring, or comparing files. Recommendations: There are no patches available at this time and no plans to develop any patches. The commands described above are infrequently used and easily worked around. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.0	Category:Compliant#
Language: Swedish	OS: DOS	Release Date: 10 Mar 1993
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC Bios
Last Updated:	28 Oct 1999
Product Details
How the product handles dates: MS-DOS is aware of dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOS® DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date" upon entry of 2-digit dates in this range. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. Product compliance issues:        MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. External commands with switches that use a date parameter require years beyond 2000 to be entered using all 4 digits. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.0 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006),   MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.0 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Similarly, when MSBACKUP is backing up, restoring, or comparing files with dates greater than 1999 the file date is not displayed correctly. This is strictly a limitation of the MSBACKUP user interface and does not prevent MSBACKUP from properly backing up, restoring, or comparing files. Recommendations: There are no patches available at this time and no plans to develop any patches. The commands described above are infrequently used and easily worked around. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.2	Category:Compliant#
Language: Danish	OS: DOS	Release Date: 30 Sep 1993
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS is aware of dates beyond the year 2000. It does not display the full year, but will sort files correctly. 2-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOS® DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date" upon entry of 2-digit date in this range. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. Product compliance issues:        MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. External commands with switches that use a date parameter require years beyond 2000 to be entered using all 4 digits. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.2 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.2 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Similarly, when MSBACKUP is backing up, restoring, or comparing files with dates greater than 1999 the file date is not displayed correctly. This is strictly a limitation of the MSBACKUP user interface and does not prevent MSBACKUP from properly backing up, restoring, or comparing files. Recommendations: There are no patches available at this time and no plans to develop any patches. The commands described above are infrequently used and easily worked around. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.2	Category:Compliant#
Language: Dutch	OS: DOS	Release Date: 30 Sep 1993
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS is aware of dates beyond the year 2000. It does not display the full year, but will sort files correctly. 2-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOS® DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date" upon entry of 2-digit date in this range. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. Product compliance issues:        MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. External commands with switches that use a date parameter require years beyond 2000 to be entered using all 4 digits. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.2 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.2 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Similarly, when MSBACKUP is backing up, restoring, or comparing files with dates greater than 1999 the file date is not displayed correctly. This is strictly a limitation of the MSBACKUP user interface and does not prevent MSBACKUP from properly backing up, restoring, or comparing files. Recommendations: There are no patches available at this time and no plans to develop any patches. The commands described above are infrequently used and easily worked around. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.2	Category:Compliant#
Language: English	OS: DOS	Release Date: 30 Sep 1993
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS is aware of dates beyond the year 2000. It does not display the full year, but will sort files correctly. 2-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOS® DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date" upon entry of 2-digit date in this range. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. Product compliance issues:        MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. External commands with switches that use a date parameter require years beyond 2000 to be entered using all 4 digits. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.2 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.2 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Similarly, when MSBACKUP is backing up, restoring, or comparing files with dates greater than 1999 the file date is not displayed correctly. This is strictly a limitation of the MSBACKUP user interface and does not prevent MSBACKUP from properly backing up, restoring, or comparing files. Recommendations: There are no patches available at this time and no plans to develop any patches. The commands described above are infrequently used and easily worked around. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.2	Category:Compliant#
Language: Finnish	OS: DOS	Release Date: 30 Sep 1993
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS is aware of dates beyond the year 2000. It does not display the full year, but will sort files correctly. 2-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOS® DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date" upon entry of 2-digit date in this range. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. Product compliance issues:        MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. External commands with switches that use a date parameter require years beyond 2000 to be entered using all 4 digits. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.2 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.2 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Similarly, when MSBACKUP is backing up, restoring, or comparing files with dates greater than 1999 the file date is not displayed correctly. This is strictly a limitation of the MSBACKUP user interface and does not prevent MSBACKUP from properly backing up, restoring, or comparing files. Recommendations: There are no patches available at this time and no plans to develop any patches. The commands described above are infrequently used and easily worked around. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.2	Category:Compliant#
Language: French	OS: DOS	Release Date: 30 Sep 1993
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS is aware of dates beyond the year 2000. It does not display the full year, but will sort files correctly. 2-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOS® DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date" upon entry of 2-digit date in this range. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. Product compliance issues:        MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. External commands with switches that use a date parameter require years beyond 2000 to be entered using all 4 digits. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.2 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.2 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Similarly, when MSBACKUP is backing up, restoring, or comparing files with dates greater than 1999 the file date is not displayed correctly. This is strictly a limitation of the MSBACKUP user interface and does not prevent MSBACKUP from properly backing up, restoring, or comparing files. Recommendations: There are no patches available at this time and no plans to develop any patches. The commands described above are infrequently used and easily worked around. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.2	Category:Compliant#
Language: German	OS: DOS	Release Date: 31 May 1994
Operational Range:	-
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Operational Range for Data: 2035 Description of how the product handles dates: MS-DOS recognizes dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOSÒ DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date." Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOSÒ DATE command is the only operating system command that accepts dates. See the note above for the 2-digit year logic. MS-DOSÒ file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOSÒ API the program must add 1980. Product compliance issues: MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.22 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.22 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Recommendations: There are no patches available at this time. The commands described above are infrequently used and easily worked around. This date issue does not constitute a significant threat to the stability and/or functionality of the product as a whole. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.2	Category:Compliant#
Language: Italian	OS: DOS	Release Date: 30 Sep 1993
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS is aware of dates beyond the year 2000. It does not display the full year, but will sort files correctly. 2-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOS® DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date" upon entry of 2-digit date in this range. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. Product compliance issues:        MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. External commands with switches that use a date parameter require years beyond 2000 to be entered using all 4 digits. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.2 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.2 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Similarly, when MSBACKUP is backing up, restoring, or comparing files with dates greater than 1999 the file date is not displayed correctly. This is strictly a limitation of the MSBACKUP user interface and does not prevent MSBACKUP from properly backing up, restoring, or comparing files. Recommendations: There are no patches available at this time and no plans to develop any patches. The commands described above are infrequently used and easily worked around. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.2	Category:Compliant#
Language: Japanese	OS: DOS	Release Date: 31 May 1994
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	none
Product Dependencies:	none
Clock Dependencies:	PC Bios
Last Updated:	28 Oct 1999
Product Details
This information applies to the NEC version of MS-DOS 6.2. Description of how the product handles dates: MS-DOS is aware of dates beyond the year 2000. It does not display the full year, but will sort files correctly. 2-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOS® DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date" upon entry of 2-digit date in this range. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. Product compliance issues:        MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. External commands with switches that use a date parameter require years beyond 2000 to be entered using all 4 digits. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.2 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.2 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Similarly, when MSBACKUP is backing up, restoring, or comparing files with dates greater than 1999 the file date is not displayed correctly. This is strictly a limitation of the MSBACKUP user interface and does not prevent MSBACKUP from properly backing up, restoring, or comparing files. Recommendations: There are no patches available at this time and no plans to develop any patches. The commands described above are infrequently used and easily worked around. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.2	Category:Compliant#
Language: Korean	OS: DOS	Release Date: N/A
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	none
Product Dependencies:	none
Clock Dependencies:	PC Bios
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS is aware of dates beyond the year 2000. It does not display the full year, but will sort files correctly. 2-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOS® DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date" upon entry of 2-digit date in this range. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. Product compliance issues:        MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. External commands with switches that use a date parameter require years beyond 2000 to be entered using all 4 digits. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.2 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.2 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Similarly, when MSBACKUP is backing up, restoring, or comparing files with dates greater than 1999 the file date is not displayed correctly. This is strictly a limitation of the MSBACKUP user interface and does not prevent MSBACKUP from properly backing up, restoring, or comparing files. Recommendations: There are no patches available at this time and no plans to develop any patches. The commands described above are infrequently used and easily worked around. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.2	Category:Compliant#
Language: Norwegian	OS: DOS	Release Date: 30 Sep 1993
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS is aware of dates beyond the year 2000. It does not display the full year, but will sort files correctly. 2-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOS® DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date" upon entry of 2-digit date in this range. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. Product compliance issues:        MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. External commands with switches that use a date parameter require years beyond 2000 to be entered using all 4 digits. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.2 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.2 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Similarly, when MSBACKUP is backing up, restoring, or comparing files with dates greater than 1999 the file date is not displayed correctly. This is strictly a limitation of the MSBACKUP user interface and does not prevent MSBACKUP from properly backing up, restoring, or comparing files. Recommendations: There are no patches available at this time and no plans to develop any patches. The commands described above are infrequently used and easily worked around. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.2	Category:Compliant#
Language: Portuguese (Brazil)	OS: DOS	Release Date: 30 Sep 1993
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC Bios
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS is aware of dates beyond the year 2000. It does not display the full year, but will sort files correctly. 2-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOS® DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date" upon entry of 2-digit date in this range. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. Product compliance issues:        MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. External commands with switches that use a date parameter require years beyond 2000 to be entered using all 4 digits. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.2 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.2 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Similarly, when MSBACKUP is backing up, restoring, or comparing files with dates greater than 1999 the file date is not displayed correctly. This is strictly a limitation of the MSBACKUP user interface and does not prevent MSBACKUP from properly backing up, restoring, or comparing files. Recommendations: There are no patches available at this time and no plans to develop any patches. The commands described above are infrequently used and easily worked around. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.2	Category:Compliant#
Language: Spanish	OS: DOS	Release Date: 30 Sep 1993
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS is aware of dates beyond the year 2000. It does not display the full year, but will sort files correctly. 2-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOS® DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date" upon entry of 2-digit date in this range. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. Product compliance issues:        MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. External commands with switches that use a date parameter require years beyond 2000 to be entered using all 4 digits. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.2 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.2 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Similarly, when MSBACKUP is backing up, restoring, or comparing files with dates greater than 1999 the file date is not displayed correctly. This is strictly a limitation of the MSBACKUP user interface and does not prevent MSBACKUP from properly backing up, restoring, or comparing files. Recommendations: There are no patches available at this time and no plans to develop any patches. The commands described above are infrequently used and easily worked around. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.2	Category:Compliant#
Language: Swedish	OS: DOS	Release Date: 30 Sep 1993
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS is aware of dates beyond the year 2000. It does not display the full year, but will sort files correctly. 2-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOS® DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date" upon entry of 2-digit date in this range. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. Product compliance issues:        MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. External commands with switches that use a date parameter require years beyond 2000 to be entered using all 4 digits. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.2 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.2 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Similarly, when MSBACKUP is backing up, restoring, or comparing files with dates greater than 1999 the file date is not displayed correctly. This is strictly a limitation of the MSBACKUP user interface and does not prevent MSBACKUP from properly backing up, restoring, or comparing files. Recommendations: There are no patches available at this time and no plans to develop any patches. The commands described above are infrequently used and easily worked around. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.21	Category:Compliant#
Language: English	OS: DOS	Release Date: 10 Mar 1994
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	NONE
Product Dependencies:	NONE
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
How the product handles dates: MS-DOS is aware of dates beyond the year 2000. It does not display the full year, but does sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOS® DATE command does not correctly handle 2-digit dates from 00–79 and returns the error message "Invalid Date upon entry of 2-digit dates in this range.." Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. Product compliance issues:        MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. External commands with switches that use a date parameter require years beyond 2000 to be entered using all 4 digits. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.21 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the MS-DOS 6.21 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Similarly, when MSBACKUP is backing up, restoring, or comparing files with dates greater than 1999 the file date is not displayed correctly. This is strictly a limitation of the MSBACKUP user interface and does not prevent MSBACKUP from properly backing up, restoring, or comparing files. Recommendations: There are no patches available at this time and no plans to develop any patches. The commands that cause non-compliance are infrequently used and easily worked around. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.22	Category:Compliant#
Language: Arabic	OS: DOS	Release Date: 31 May 1994
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	none
Product Dependencies:	none
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS recognizes dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOSÒ DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date." External command with switches that use date parameter, require years 2000 and beyond to be entered using all for digits. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOSÒ DATE command is the only operating system command that accepts dates. See the note above for the 2-digit year logic. MS-DOSÒ file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOSÒ API the program must add 1980. Product compliance issues: MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.22 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.22 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Recommendations to meet compliance: There are no patches available at this time. The commands described above are infrequently used and easily worked around. This date issue does not constitute a significant threat to the stability and/or functionality of the product as a whole. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.22	Category:Compliant#
Language: Chinese - Simplified	OS: DOS	Release Date: 31 May 1994
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	none
Product Dependencies:	none
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS recognizes dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOSÒ DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date." External command with switches that use date parameter, require years 2000 and beyond to be entered using all for digits. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOSÒ DATE command is the only operating system command that accepts dates. See the note above for the 2-digit year logic. MS-DOSÒ file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOSÒ API the program must add 1980. Product compliance issues: MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.22 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.22 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Recommendations to meet compliance: There are no patches available at this time. The commands described above are infrequently used and easily worked around. This date issue does not constitute a significant threat to the stability and/or functionality of the product as a whole. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.22	Category:Compliant#
Language: Chinese - Traditional	OS: DOS	Release Date: 31 May 1994
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	none
Product Dependencies:	none
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS recognizes dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOSÒ DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date." External command with switches that use date parameter, require years 2000 and beyond to be entered using all for digits. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOSÒ DATE command is the only operating system command that accepts dates. See the note above for the 2-digit year logic. MS-DOSÒ file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOSÒ API the program must add 1980. Product compliance issues: MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.22 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.22 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Recommendations to meet compliance: There are no patches available at this time. The commands described above are infrequently used and easily worked around. This date issue does not constitute a significant threat to the stability and/or functionality of the product as a whole. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.22	Category:Compliant#
Language: Danish	OS: DOS	Release Date: 31 May 1994
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS recognizes dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOSÒ DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date." External command with switches that use date parameter, require years 2000 and beyond to be entered using all for digits. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOSÒ DATE command is the only operating system command that accepts dates. See the note above for the 2-digit year logic. MS-DOSÒ file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOSÒ API the program must add 1980. Product compliance issues: MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.22 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.22 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Recommendations to meet compliance: There are no patches available at this time. The commands described above are infrequently used and easily worked around. This date issue does not constitute a significant threat to the stability and/or functionality of the product as a whole. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.22	Category:Compliant#
Language: Dutch	OS: DOS	Release Date: 31 May 1994
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS recognizes dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOSÒ DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date." External command with switches that use date parameter, require years 2000 and beyond to be entered using all for digits. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOSÒ DATE command is the only operating system command that accepts dates. See the note above for the 2-digit year logic. MS-DOSÒ file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOSÒ API the program must add 1980. Product compliance issues: MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.22 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.22 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Recommendations to meet compliance: There are no patches available at this time. The commands described above are infrequently used and easily worked around. This date issue does not constitute a significant threat to the stability and/or functionality of the product as a whole. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.22	Category:Compliant#
Language: English	OS: DOS	Release Date: 31 May 1994
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	NONE
Product Dependencies:	NONE
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS recognizes dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOSÒ DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date." External command with switches that use date parameter, require years 2000 and beyond to be entered using all for digits. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOSÒ DATE command is the only operating system command that accepts dates. See the note above for the 2-digit year logic. MS-DOSÒ file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOSÒ API the program must add 1980. Product compliance issues: MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.22 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.22 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Recommendations to meet compliance: There are no patches available at this time. The commands described above are infrequently used and easily worked around. This date issue does not constitute a significant threat to the stability and/or functionality of the product as a whole. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.22	Category:Compliant#
Language: Finnish	OS: DOS	Release Date: 31 May 1994
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS recognizes dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOSÒ DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date." External command with switches that use date parameter, require years 2000 and beyond to be entered using all for digits. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOSÒ DATE command is the only operating system command that accepts dates. See the note above for the 2-digit year logic. MS-DOSÒ file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOSÒ API the program must add 1980. Product compliance issues: MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.22 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.22 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Recommendations to meet compliance: There are no patches available at this time. The commands described above are infrequently used and easily worked around. This date issue does not constitute a significant threat to the stability and/or functionality of the product as a whole. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.22	Category:Compliant#
Language: French	OS: DOS	Release Date: 31 May 1994
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS recognizes dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOSÒ DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date." External command with switches that use date parameter, require years 2000 and beyond to be entered using all for digits. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOSÒ DATE command is the only operating system command that accepts dates. See the note above for the 2-digit year logic. MS-DOSÒ file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOSÒ API the program must add 1980. Product compliance issues: MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.22 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.22 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Recommendations to meet compliance: There are no patches available at this time. The commands described above are infrequently used and easily worked around. This date issue does not constitute a significant threat to the stability and/or functionality of the product as a whole. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.22	Category:Compliant#
Language: German	OS: DOS	Release Date: N/A
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS recognizes dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOSÒ DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date." External command with switches that use date parameter, require years 2000 and beyond to be entered using all for digits. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOSÒ DATE command is the only operating system command that accepts dates. See the note above for the 2-digit year logic. MS-DOSÒ file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOSÒ API the program must add 1980. Product compliance issues: MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.22 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.22 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Recommendations to meet compliance: There are no patches available at this time. The commands described above are infrequently used and easily worked around. This date issue does not constitute a significant threat to the stability and/or functionality of the product as a whole. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.22	Category:Compliant#
Language: Hebrew	OS: DOS	Release Date: 31 May 1994
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	none
Product Dependencies:	none
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS recognizes dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOSÒ DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date." External command with switches that use date parameter, require years 2000 and beyond to be entered using all for digits. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOSÒ DATE command is the only operating system command that accepts dates. See the note above for the 2-digit year logic. MS-DOSÒ file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOSÒ API the program must add 1980. Product compliance issues: MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.22 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.22 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Recommendations to meet compliance: There are no patches available at this time. The commands described above are infrequently used and easily worked around. This date issue does not constitute a significant threat to the stability and/or functionality of the product as a whole. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.22	Category:Compliant#
Language: Italian	OS: DOS	Release Date: 31 May 1994
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS recognizes dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOSÒ DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date." External command with switches that use date parameter, require years 2000 and beyond to be entered using all for digits. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOSÒ DATE command is the only operating system command that accepts dates. See the note above for the 2-digit year logic. MS-DOSÒ file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOSÒ API the program must add 1980. Product compliance issues: MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.22 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.22 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Recommendations to meet compliance: There are no patches available at this time. The commands described above are infrequently used and easily worked around. This date issue does not constitute a significant threat to the stability and/or functionality of the product as a whole. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.22	Category:Compliant#
Language: Norwegian	OS: DOS	Release Date: 31 May 1994
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS recognizes dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOSÒ DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date." External command with switches that use date parameter, require years 2000 and beyond to be entered using all for digits. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOSÒ DATE command is the only operating system command that accepts dates. See the note above for the 2-digit year logic. MS-DOSÒ file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOSÒ API the program must add 1980. Product compliance issues: MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.22 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.22 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Recommendations to meet compliance: There are no patches available at this time. The commands described above are infrequently used and easily worked around. This date issue does not constitute a significant threat to the stability and/or functionality of the product as a whole. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.22	Category:Compliant#
Language: Portuguese	OS: DOS	Release Date: 31 May 1994
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS recognizes dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOSÒ DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date." External command with switches that use date parameter, require years 2000 and beyond to be entered using all for digits. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOSÒ DATE command is the only operating system command that accepts dates. See the note above for the 2-digit year logic. MS-DOSÒ file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOSÒ API the program must add 1980. Product compliance issues: MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.22 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.22 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Recommendations to meet compliance: There are no patches available at this time. The commands described above are infrequently used and easily worked around. This date issue does not constitute a significant threat to the stability and/or functionality of the product as a whole. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.22	Category:Compliant#
Language: Russian	OS: DOS	Release Date: 31 May 1994
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS recognizes dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOSÒ DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date." External command with switches that use date parameter, require years 2000 and beyond to be entered using all for digits. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOSÒ DATE command is the only operating system command that accepts dates. See the note above for the 2-digit year logic. MS-DOSÒ file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOSÒ API the program must add 1980. Product compliance issues: MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.22 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.22 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Recommendations to meet compliance: There are no patches available at this time. The commands described above are infrequently used and easily worked around. This date issue does not constitute a significant threat to the stability and/or functionality of the product as a whole. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.22	Category:Compliant#
Language: Spanish	OS: DOS	Release Date: 31 May 1994
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS recognizes dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOSÒ DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date." External command with switches that use date parameter, require years 2000 and beyond to be entered using all for digits. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOSÒ DATE command is the only operating system command that accepts dates. See the note above for the 2-digit year logic. MS-DOSÒ file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOSÒ API the program must add 1980. Product compliance issues: MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.22 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.22 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Recommendations to meet compliance: There are no patches available at this time. The commands described above are infrequently used and easily worked around. This date issue does not constitute a significant threat to the stability and/or functionality of the product as a whole. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.22	Category:Compliant#
Language: Swedish	OS: DOS	Release Date: 31 May 1994
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS recognizes dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOSÒ DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date." External command with switches that use date parameter, require years 2000 and beyond to be entered using all for digits. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOSÒ DATE command is the only operating system command that accepts dates. See the note above for the 2-digit year logic. MS-DOSÒ file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOSÒ API the program must add 1980. Product compliance issues: MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.22 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.22 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Recommendations to meet compliance: There are no patches available at this time. The commands described above are infrequently used and easily worked around. This date issue does not constitute a significant threat to the stability and/or functionality of the product as a whole. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-DOS	Version: 6.22	Category:Compliant#
Language: Thai	OS: DOS	Release Date: 31 May 1994
Operational Range:	04 Jan 1980 - 31 Dec 2035
Prerequisites:	none
Product Dependencies:	none
Clock Dependencies:	PC BIOS
Last Updated:	28 Oct 1999
Product Details
Description of how the product handles dates: MS-DOS recognizes dates beyond the year 2000. It does not display the full year, but will sort files correctly. Two-digit shortcut handling: If a 2-digit date is entered, the operating system will assume that the date entered is in the 20th century. The MS-DOSÒ DATE command does not correctly handle 2-digit dates from 00–79. This command returns the error message "Invalid Date." External command with switches that use date parameter, require years 2000 and beyond to be entered using all for digits. Dates entered using a 4-digit year are handled correctly (e.g. 01-01-2000). MS-DOSÒ DATE command is the only operating system command that accepts dates. See the note above for the 2-digit year logic. MS-DOSÒ file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOSÒ API the program must add 1980. Product compliance issues: MS-DOS cannot display a 4-digit date, using the DIR command (internal to COMMAND.COM). MS-DOS will not accept 2-digit date changes for the year 2000 and beyond. To enter the correct date, a 4-digit year must be entered to the DATE command (internal to COMMAND.COM). Failure to enter the correct 4-digit date will result in an "Invalid Date" error. MSBACKUP: Naming conventions do not recognize "tens" place. MSBACKUP from MS-DOS 6.22 creates a catalogue of the backups using a YMMDD format. When a backup is made with the same number in the "ones" place and a different number in the "tens" place (i.e., 1996 and 2006), MSBACKUP treats them as being made on the same date. They are numbered accordingly with a letter following the date to indicate that they are different. For example, the following series appeared on the DOS 6.22 system: CC60829A.FUL (No Description) was created on 8/29/1996 CC60829B.FUL (No Description) was created on 8/29/2006 CC60829B.FUL (No Description) was created on 8/29/1996 The actual date of the backup can be found by opening the .FUL file and scrolling to the next to the last line. There it is shown in the MM-DD-YY format. MSBACKUP does not recognize dates greater than 1999. MSBACKUP creates a date stamp on the backup files. When an attempt is made to create a backup over an existing backup, MSBACKUP displays a warning to prevent the user from destroying the file. The warning reads, for example, "You have inserted Backup diskette #2 from backup set CC60828B.FUL. This diskette was created using the DEFAULT setup on 8-28-96. Do you want to overwrite this diskette or retry using another diskette?" When the date the backup was made is greater than 1999, the date is improperly displayed; e.g., "This diskette was created using the DEFAULT setup on 8-29-CZ." For example: CC60829B.FUL = 8-29-CZ (system date = 8/29/2006) CC60828A.FUL = 8-28-CZ (system date = 8/28/2006) CC10829A.FUL = 8-29-AC (system date = 8/29/2001) Recommendations to meet compliance: There are no patches available at this time. The commands described above are infrequently used and easily worked around. This date issue does not constitute a significant threat to the stability and/or functionality of the product as a whole. Testing guidelines and recommendations: Some PCs do have a problem that resets the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If you are going to test for this error, Microsoft recommends that you execute the tests on a "test-bed" machine rather than a production machine. Please see the Windows Operating System Interactions with BIOS and Real Time Clock section in the Year 2000 white papers for further information.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-Oracle ODBC Driver	Version: 2.573	Category:Compliant*
Language: Chinese - Simplified	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	V2.573 driver requires Oracle v7.33 or greater, and corresponding SQL*Net libraries.
Product Dependencies:	Oracle Server, Oracle SQL*Net , ODBC Driver Manager, msvcrt.dll
Clock Dependencies:	None-aside from datetime data from Oracle servers.
Last Updated:	24 Aug 1999
Product Details
How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. The MS Oracle ODBC Driver adheres to the ODBC specifications. Testing of the driver has confirmed proper date handling characteristics. There are no known issues with the MS Oracle ODBC Driver and Oracle if date data is stored in a date column. Please refer to Oracle for any Year 2000 issues native to Oracle: http://www.oracle.com/ Two-digit shortcut handling: There is no 2-digit handling in the product. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Testing guidelines and recommendations: Users should be aware of any Year 2000 issues pertaining to the version of the Oracle server that they are working with.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-Oracle ODBC Driver	Version: 2.573	Category:Compliant*
Language: Chinese - Traditional	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	V2.573 driver requires Oracle v7.33 or greater, and corresponding SQL*Net libraries.
Product Dependencies:	Oracle Server, Oracle SQL*Net , ODBC Driver Manager, msvcrt.dll
Clock Dependencies:	None-aside from datetime data from Oracle servers.
Last Updated:	24 Aug 1999
Product Details
How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. The MS Oracle ODBC Driver adheres to the ODBC specifications. Testing of the driver has confirmed proper date handling characteristics. There are no known issues with the MS Oracle ODBC Driver and Oracle if date data is stored in a date column. Please refer to Oracle for any Year 2000 issues native to Oracle: http://www.oracle.com/ Two-digit shortcut handling: There is no 2-digit handling in the product. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Testing guidelines and recommendations: Users should be aware of any Year 2000 issues pertaining to the version of the Oracle server that they are working with.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-Oracle ODBC Driver	Version: 2.573	Category:Compliant*
Language: English	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	V2.573 driver requires Oracle v7.33 or greater, and corresponding SQL*Net libraries.
Product Dependencies:	Oracle Server, Oracle SQL*Net , ODBC Driver Manager, msvcrt.dll
Clock Dependencies:	None-aside from datetime data from Oracle servers.
Last Updated:	24 Aug 1999
Product Details
How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. The MS Oracle ODBC Driver adheres to the ODBC specifications. Testing of the driver has confirmed proper date handling characteristics. There are no known issues with the MS Oracle ODBC Driver and Oracle if date data is stored in a date column. Please refer to Oracle for any Year 2000 issues native to Oracle: http://www.oracle.com/ Two-digit shortcut handling: There is no 2-digit handling in the product. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Testing guidelines and recommendations: Users should be aware of any Year 2000 issues pertaining to the version of the Oracle server that they are working with.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: MS-Oracle ODBC Driver	Version: 2.573	Category:Compliant*
Language: French	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	V2.573 driver requires Oracle v7.33 or greater, and corresponding SQL*Net libraries.
Product Dependencies:	Oracle Server, Oracle SQL*Net , ODBC Driver Manager, msvcrt.dll
Clock Dependencies:	None-aside from datetime data from Oracle servers.
Last Updated:	24 Aug 1999
Product Details
How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. The MS Oracle ODBC Driver adheres to the ODBC specifications. Testing of the driver has confirmed proper date handling characteristics. There are no known issues with the MS Oracle ODBC Driver and Oracle if date data is stored in a date column. Please refer to Oracle for any Year 2000 issues native to Oracle: http://www.oracle.com/ Two-digit shortcut handling: There is no 2-digit handling in the product. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Testing guidelines and recommendations: Users should be aware of any Year 2000 issues pertaining to the version of the Oracle server that they are working with.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+	The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.