Product Entry Guide Detail
------------------------
Microsoft Year 2000 Resource Center
Visual SourceSafe 4.0a (German)
| 01 Jan 1970 - 31 Dec 2027 | ||
| none | ||
| none | ||
| Operating System Clock | ||
| 05 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. How the product runtime handles dates: Visual SourceSafe 4.0a, has known issues with date handling for dates past 12/31/1999. These issues can be summarized as:
Visual SourceSafe 4.0a uses a 32-bit integer to store the number of seconds since 1/1/1970 for date handling. When these dates are displayed, the years since 1900 are stored in a signed char. This is a restrictive structure used by Visual SourceSafe 4.0a in handling date data and is the reason behind the display issues outlined below. Displaying year portion of dates Dates from 1/1/2000 to 12/31/2027 display a special character in place of the 10's digit of the year as follows (where X is any digit from 0-9): Dates like 200X, appear as 20:X Dates like 201X, appear as 20;X Dates like 202X, appear as 20<X For example the date 2003 is displayed as 20:3 and 2015 is displayed as 20;5. The issue described above is a cosmetic display issue and does not impact the storage of files or project data. This data is stored as documented in Books Online for VSS. Dates beyond 12/31/2027 are not legible and character mapping cannot be easily defined. Pulling file or project history by user specified dates This issue can be summarized by the following:
The issues described above are cosmetic display issues and do not impact the storage of files or project data. This data is stored as documented in Books Online for VSS. The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. Using –VD command line switch Visual SourceSafe commands using the -VD switch will execute on the latest version of the specified file when specifying a date past 12/31/1999. This issue impacts the following Visual SourceSafe 4.0a commands:
Depending on which command is used, this issue can cause data corruption and/or loss since the incorrect file may be used to perform the specified operation.
BIOS dependencies in Visual SourceSafe: Visual SourceSafe uses a "time stamp" to apply a date to files. This time stamp contains date information obtained from the user’s system clock. The time stamp is provided by the machine’s BIOS (Basic Input-Output System), and is not provided by Visual SourceSafe. If the machine uses a year 2000 non-compliant BIOS/RTC that fails to reset the system clock to January 1, 2000 (and if the operating system does not automatically correct the date) new files and new versions will be saved with incorrect time stamps. This could lead to versions of files not appearing in the history dialog. Users should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. Two-digit shortcut handling: The Visual SourceSafe 4.0a product handles 2-digit dates entered into the system as follows: Years 70 – 99 for dates 1/1/70 through 12/31/99 are converted to 1970 – 1999. Years 00 – 38 for dates 1/1/2000 through 1/18/2038 are not converted. Values 39 – 69 are undefined within the operational range and are not converted.
Recommendations to meet compliance: Upgrade to Visual Source Safe 5.0, apply the Visual Studio 97 Service Pack 3 and the Visual SourceSafe 5.0 Year 2000 Update. Please contact 1-888-MSFT-Y2K (or your local Microsoft Year 2000 Information line) and provide your Visual Source Safe 4.0 license number to request an upgrade. The Visual Studio 97 Service Pack 3 can be downloaded from http://msdn.microsoft.com/vstudio/sp/vs97/ and the Visual SourceSafe 5.0 Year 2000 Update can be downloaded from http://msdn.microsoft.com/ssafe/downloads/year2000.asp.
Recommended practices to develop year 2000 compliant applications: Both "displaying year portions of dates" and "pulling file or project history by user specified dates" issues do not impact the applications developers build using Visual SourceSafe as their source code control tool. The user can pull file or project history without specifying a date and will have history data before 1/1/2028 returned in the list. When viewing dates within Visual SourceSafe past the year 2000 rollover, you should be aware of the display problems with the year portion of the dates and map the appropriate 10’s digit with the character displayed as indicated in the issue description. When pulling file or project history do not specify a date so that the operation will return all versions of the file or project. When using the command line operations of Visual SourceSafe 4.0a, it is recommended that you do not use the –VD switch to operate on a specific version of a file after 12/31/1999. If possible, use the –V or –VL switch to specify the version or label of a specific version of the file or project you wish to operate on. If you are using the Visual SourceSafe 4.0a command line operations through batch files, we recommend that you remove all instances of the –VD switch from these batch files to ensure you do not corrupt your build, build process or Visual SourceSafe database. In the worst case, you can locate the specific version of a file using the Graphic User Interface (GUI) and searching the entire history through the show history command. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. This issue does not impact the ability of developers to build year 2000 compliant applications. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Visual SourceSafe 4.0a (German)
| 01 Jan 1970 - 31 Dec 2027 | ||
| none | ||
| none | ||
| Operating System Clock | ||
| 05 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. How the product runtime handles dates: Visual SourceSafe 4.0a, has known issues with date handling for dates past 12/31/1999. These issues can be summarized as:
Visual SourceSafe 4.0a uses a 32-bit integer to store the number of seconds since 1/1/1970 for date handling. When these dates are displayed, the years since 1900 are stored in a signed char. This is a restrictive structure used by Visual SourceSafe 4.0a in handling date data and is the reason behind the display issues outlined below. Displaying year portion of dates Dates from 1/1/2000 to 12/31/2027 display a special character in place of the 10's digit of the year as follows (where X is any digit from 0-9): Dates like 200X, appear as 20:X Dates like 201X, appear as 20;X Dates like 202X, appear as 20<X For example the date 2003 is displayed as 20:3 and 2015 is displayed as 20;5. The issue described above is a cosmetic display issue and does not impact the storage of files or project data. This data is stored as documented in Books Online for VSS. Dates beyond 12/31/2027 are not legible and character mapping cannot be easily defined. Pulling file or project history by user specified dates This issue can be summarized by the following:
The issues described above are cosmetic display issues and do not impact the storage of files or project data. This data is stored as documented in Books Online for VSS. The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. Using –VD command line switch Visual SourceSafe commands using the -VD switch will execute on the latest version of the specified file when specifying a date past 12/31/1999. This issue impacts the following Visual SourceSafe 4.0a commands:
Depending on which command is used, this issue can cause data corruption and/or loss since the incorrect file may be used to perform the specified operation.
BIOS dependencies in Visual SourceSafe: Visual SourceSafe uses a "time stamp" to apply a date to files. This time stamp contains date information obtained from the user’s system clock. The time stamp is provided by the machine’s BIOS (Basic Input-Output System), and is not provided by Visual SourceSafe. If the machine uses a year 2000 non-compliant BIOS/RTC that fails to reset the system clock to January 1, 2000 (and if the operating system does not automatically correct the date) new files and new versions will be saved with incorrect time stamps. This could lead to versions of files not appearing in the history dialog. Users should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. Two-digit shortcut handling: The Visual SourceSafe 4.0a product handles 2-digit dates entered into the system as follows: Years 70 – 99 for dates 1/1/70 through 12/31/99 are converted to 1970 – 1999. Years 00 – 38 for dates 1/1/2000 through 1/18/2038 are not converted. Values 39 – 69 are undefined within the operational range and are not converted.
Recommendations to meet compliance: Upgrade to Visual Source Safe 5.0, apply the Visual Studio 97 Service Pack 3 and the Visual SourceSafe 5.0 Year 2000 Update. Please contact 1-888-MSFT-Y2K (or your local Microsoft Year 2000 Information line) and provide your Visual Source Safe 4.0 license number to request an upgrade. The Visual Studio 97 Service Pack 3 can be downloaded from http://msdn.microsoft.com/vstudio/sp/vs97/ and the Visual SourceSafe 5.0 Year 2000 Update can be downloaded from http://msdn.microsoft.com/ssafe/downloads/year2000.asp.
Recommended practices to develop year 2000 compliant applications: Both "displaying year portions of dates" and "pulling file or project history by user specified dates" issues do not impact the applications developers build using Visual SourceSafe as their source code control tool. The user can pull file or project history without specifying a date and will have history data before 1/1/2028 returned in the list. When viewing dates within Visual SourceSafe past the year 2000 rollover, you should be aware of the display problems with the year portion of the dates and map the appropriate 10’s digit with the character displayed as indicated in the issue description. When pulling file or project history do not specify a date so that the operation will return all versions of the file or project. When using the command line operations of Visual SourceSafe 4.0a, it is recommended that you do not use the –VD switch to operate on a specific version of a file after 12/31/1999. If possible, use the –V or –VL switch to specify the version or label of a specific version of the file or project you wish to operate on. If you are using the Visual SourceSafe 4.0a command line operations through batch files, we recommend that you remove all instances of the –VD switch from these batch files to ensure you do not corrupt your build, build process or Visual SourceSafe database. In the worst case, you can locate the specific version of a file using the Graphic User Interface (GUI) and searching the entire history through the show history command. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. This issue does not impact the ability of developers to build year 2000 compliant applications. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Visual SourceSafe 4.0a (Italian)
| 01 Jan 1970 - 31 Dec 2027 | ||
| none | ||
| none | ||
| Operating System Clock | ||
| 05 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. How the product runtime handles dates: Visual SourceSafe 4.0a, has known issues with date handling for dates past 12/31/1999. These issues can be summarized as:
Visual SourceSafe 4.0a uses a 32-bit integer to store the number of seconds since 1/1/1970 for date handling. When these dates are displayed, the years since 1900 are stored in a signed char. This is a restrictive structure used by Visual SourceSafe 4.0a in handling date data and is the reason behind the display issues outlined below. Displaying year portion of dates Dates from 1/1/2000 to 12/31/2027 display a special character in place of the 10's digit of the year as follows (where X is any digit from 0-9): Dates like 200X, appear as 20:X Dates like 201X, appear as 20;X Dates like 202X, appear as 20<X For example the date 2003 is displayed as 20:3 and 2015 is displayed as 20;5. The issue described above is a cosmetic display issue and does not impact the storage of files or project data. This data is stored as documented in Books Online for VSS. Dates beyond 12/31/2027 are not legible and character mapping cannot be easily defined. Pulling file or project history by user specified dates This issue can be summarized by the following:
The issues described above are cosmetic display issues and do not impact the storage of files or project data. This data is stored as documented in Books Online for VSS. The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. Using –VD command line switch Visual SourceSafe commands using the -VD switch will execute on the latest version of the specified file when specifying a date past 12/31/1999. This issue impacts the following Visual SourceSafe 4.0a commands:
Depending on which command is used, this issue can cause data corruption and/or loss since the incorrect file may be used to perform the specified operation.
BIOS dependencies in Visual SourceSafe: Visual SourceSafe uses a "time stamp" to apply a date to files. This time stamp contains date information obtained from the user’s system clock. The time stamp is provided by the machine’s BIOS (Basic Input-Output System), and is not provided by Visual SourceSafe. If the machine uses a year 2000 non-compliant BIOS/RTC that fails to reset the system clock to January 1, 2000 (and if the operating system does not automatically correct the date) new files and new versions will be saved with incorrect time stamps. This could lead to versions of files not appearing in the history dialog. Users should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. Two-digit shortcut handling: The Visual SourceSafe 4.0a product handles 2-digit dates entered into the system as follows: Years 70 – 99 for dates 1/1/70 through 12/31/99 are converted to 1970 – 1999. Years 00 – 38 for dates 1/1/2000 through 1/18/2038 are not converted. Values 39 – 69 are undefined within the operational range and are not converted.
Recommendations to meet compliance: Upgrade to Visual Source Safe 5.0, apply the Visual Studio 97 Service Pack 3 and the Visual SourceSafe 5.0 Year 2000 Update. Please contact 1-888-MSFT-Y2K (or your local Microsoft Year 2000 Information line) and provide your Visual Source Safe 4.0 license number to request an upgrade. The Visual Studio 97 Service Pack 3 can be downloaded from http://msdn.microsoft.com/vstudio/sp/vs97/ and the Visual SourceSafe 5.0 Year 2000 Update can be downloaded from http://msdn.microsoft.com/ssafe/downloads/year2000.asp.
Recommended practices to develop year 2000 compliant applications: Both "displaying year portions of dates" and "pulling file or project history by user specified dates" issues do not impact the applications developers build using Visual SourceSafe as their source code control tool. The user can pull file or project history without specifying a date and will have history data before 1/1/2028 returned in the list. When viewing dates within Visual SourceSafe past the year 2000 rollover, you should be aware of the display problems with the year portion of the dates and map the appropriate 10’s digit with the character displayed as indicated in the issue description. When pulling file or project history do not specify a date so that the operation will return all versions of the file or project. When using the command line operations of Visual SourceSafe 4.0a, it is recommended that you do not use the –VD switch to operate on a specific version of a file after 12/31/1999. If possible, use the –V or –VL switch to specify the version or label of a specific version of the file or project you wish to operate on. If you are using the Visual SourceSafe 4.0a command line operations through batch files, we recommend that you remove all instances of the –VD switch from these batch files to ensure you do not corrupt your build, build process or Visual SourceSafe database. In the worst case, you can locate the specific version of a file using the Graphic User Interface (GUI) and searching the entire history through the show history command. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. This issue does not impact the ability of developers to build year 2000 compliant applications. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Visual SourceSafe 4.0a (Italian)
| 01 Jan 1970 - 31 Dec 2027 | ||
| none | ||
| none | ||
| Operating System Clock | ||
| 05 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. How the product runtime handles dates: Visual SourceSafe 4.0a, has known issues with date handling for dates past 12/31/1999. These issues can be summarized as:
Visual SourceSafe 4.0a uses a 32-bit integer to store the number of seconds since 1/1/1970 for date handling. When these dates are displayed, the years since 1900 are stored in a signed char. This is a restrictive structure used by Visual SourceSafe 4.0a in handling date data and is the reason behind the display issues outlined below. Displaying year portion of dates Dates from 1/1/2000 to 12/31/2027 display a special character in place of the 10's digit of the year as follows (where X is any digit from 0-9): Dates like 200X, appear as 20:X Dates like 201X, appear as 20;X Dates like 202X, appear as 20<X For example the date 2003 is displayed as 20:3 and 2015 is displayed as 20;5. The issue described above is a cosmetic display issue and does not impact the storage of files or project data. This data is stored as documented in Books Online for VSS. Dates beyond 12/31/2027 are not legible and character mapping cannot be easily defined. Pulling file or project history by user specified dates This issue can be summarized by the following:
The issues described above are cosmetic display issues and do not impact the storage of files or project data. This data is stored as documented in Books Online for VSS. The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. Using –VD command line switch Visual SourceSafe commands using the -VD switch will execute on the latest version of the specified file when specifying a date past 12/31/1999. This issue impacts the following Visual SourceSafe 4.0a commands:
Depending on which command is used, this issue can cause data corruption and/or loss since the incorrect file may be used to perform the specified operation.
BIOS dependencies in Visual SourceSafe: Visual SourceSafe uses a "time stamp" to apply a date to files. This time stamp contains date information obtained from the user’s system clock. The time stamp is provided by the machine’s BIOS (Basic Input-Output System), and is not provided by Visual SourceSafe. If the machine uses a year 2000 non-compliant BIOS/RTC that fails to reset the system clock to January 1, 2000 (and if the operating system does not automatically correct the date) new files and new versions will be saved with incorrect time stamps. This could lead to versions of files not appearing in the history dialog. Users should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. Two-digit shortcut handling: The Visual SourceSafe 4.0a product handles 2-digit dates entered into the system as follows: Years 70 – 99 for dates 1/1/70 through 12/31/99 are converted to 1970 – 1999. Years 00 – 38 for dates 1/1/2000 through 1/18/2038 are not converted. Values 39 – 69 are undefined within the operational range and are not converted.
Recommendations to meet compliance: Upgrade to Visual Source Safe 5.0, apply the Visual Studio 97 Service Pack 3 and the Visual SourceSafe 5.0 Year 2000 Update. Please contact 1-888-MSFT-Y2K (or your local Microsoft Year 2000 Information line) and provide your Visual Source Safe 4.0 license number to request an upgrade. The Visual Studio 97 Service Pack 3 can be downloaded from http://msdn.microsoft.com/vstudio/sp/vs97/ and the Visual SourceSafe 5.0 Year 2000 Update can be downloaded from http://msdn.microsoft.com/ssafe/downloads/year2000.asp.
Recommended practices to develop year 2000 compliant applications: Both "displaying year portions of dates" and "pulling file or project history by user specified dates" issues do not impact the applications developers build using Visual SourceSafe as their source code control tool. The user can pull file or project history without specifying a date and will have history data before 1/1/2028 returned in the list. When viewing dates within Visual SourceSafe past the year 2000 rollover, you should be aware of the display problems with the year portion of the dates and map the appropriate 10’s digit with the character displayed as indicated in the issue description. When pulling file or project history do not specify a date so that the operation will return all versions of the file or project. When using the command line operations of Visual SourceSafe 4.0a, it is recommended that you do not use the –VD switch to operate on a specific version of a file after 12/31/1999. If possible, use the –V or –VL switch to specify the version or label of a specific version of the file or project you wish to operate on. If you are using the Visual SourceSafe 4.0a command line operations through batch files, we recommend that you remove all instances of the –VD switch from these batch files to ensure you do not corrupt your build, build process or Visual SourceSafe database. In the worst case, you can locate the specific version of a file using the Graphic User Interface (GUI) and searching the entire history through the show history command. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. This issue does not impact the ability of developers to build year 2000 compliant applications. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Visual SourceSafe 4.0a (Japanese)
| 01 Jan 1970 - 31 Dec 2027 | ||
| none | ||
| none | ||
| Operating System Clock | ||
| 05 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. How the product runtime handles dates: Visual SourceSafe 4.0a, has known issues with date handling for dates past 12/31/1999. These issues can be summarized as:
Visual SourceSafe 4.0a uses a 32-bit integer to store the number of seconds since 1/1/1970 for date handling. When these dates are displayed, the years since 1900 are stored in a signed char. This is a restrictive structure used by Visual SourceSafe 4.0a in handling date data and is the reason behind the display issues outlined below. Displaying year portion of dates Dates from 1/1/2000 to 12/31/2027 display a special character in place of the 10's digit of the year as follows (where X is any digit from 0-9): Dates like 200X, appear as 20:X Dates like 201X, appear as 20;X Dates like 202X, appear as 20<X For example the date 2003 is displayed as 20:3 and 2015 is displayed as 20;5. The issue described above is a cosmetic display issue and does not impact the storage of files or project data. This data is stored as documented in Books Online for VSS. Dates beyond 12/31/2027 are not legible and character mapping cannot be easily defined. Pulling file or project history by user specified dates This issue can be summarized by the following:
The issues described above are cosmetic display issues and do not impact the storage of files or project data. This data is stored as documented in Books Online for VSS. The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. Using –VD command line switch Visual SourceSafe commands using the -VD switch will execute on the latest version of the specified file when specifying a date past 12/31/1999. This issue impacts the following Visual SourceSafe 4.0a commands:
Depending on which command is used, this issue can cause data corruption and/or loss since the incorrect file may be used to perform the specified operation.
BIOS dependencies in Visual SourceSafe: Visual SourceSafe uses a "time stamp" to apply a date to files. This time stamp contains date information obtained from the user’s system clock. The time stamp is provided by the machine’s BIOS (Basic Input-Output System), and is not provided by Visual SourceSafe. If the machine uses a year 2000 non-compliant BIOS/RTC that fails to reset the system clock to January 1, 2000 (and if the operating system does not automatically correct the date) new files and new versions will be saved with incorrect time stamps. This could lead to versions of files not appearing in the history dialog. Users should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. Two-digit shortcut handling: The Visual SourceSafe 4.0a product handles 2-digit dates entered into the system as follows: Years 70 – 99 for dates 1/1/70 through 12/31/99 are converted to 1970 – 1999. Years 00 – 38 for dates 1/1/2000 through 1/18/2038 are not converted. Values 39 – 69 are undefined within the operational range and are not converted.
Recommendations to meet compliance: Upgrade to Visual Source Safe 5.0, apply the Visual Studio 97 Service Pack 3 and the Visual SourceSafe 5.0 Year 2000 Update. Please contact 1-888-MSFT-Y2K (or your local Microsoft Year 2000 Information line) and provide your Visual Source Safe 4.0 license number to request an upgrade. The Visual Studio 97 Service Pack 3 can be downloaded from http://msdn.microsoft.com/vstudio/sp/vs97/ and the Visual SourceSafe 5.0 Year 2000 Update can be downloaded from http://msdn.microsoft.com/ssafe/downloads/year2000.asp.
Recommended practices to develop year 2000 compliant applications: Both "displaying year portions of dates" and "pulling file or project history by user specified dates" issues do not impact the applications developers build using Visual SourceSafe as their source code control tool. The user can pull file or project history without specifying a date and will have history data before 1/1/2028 returned in the list. When viewing dates within Visual SourceSafe past the year 2000 rollover, you should be aware of the display problems with the year portion of the dates and map the appropriate 10’s digit with the character displayed as indicated in the issue description. When pulling file or project history do not specify a date so that the operation will return all versions of the file or project. When using the command line operations of Visual SourceSafe 4.0a, it is recommended that you do not use the –VD switch to operate on a specific version of a file after 12/31/1999. If possible, use the –V or –VL switch to specify the version or label of a specific version of the file or project you wish to operate on. If you are using the Visual SourceSafe 4.0a command line operations through batch files, we recommend that you remove all instances of the –VD switch from these batch files to ensure you do not corrupt your build, build process or Visual SourceSafe database. In the worst case, you can locate the specific version of a file using the Graphic User Interface (GUI) and searching the entire history through the show history command. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. This issue does not impact the ability of developers to build year 2000 compliant applications. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Visual SourceSafe 4.0a (Japanese)
| 01 Jan 1970 - 31 Dec 2027 | ||
| none | ||
| none | ||
| Operating System Clock | ||
| 05 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. How the product runtime handles dates: Visual SourceSafe 4.0a, has known issues with date handling for dates past 12/31/1999. These issues can be summarized as:
Visual SourceSafe 4.0a uses a 32-bit integer to store the number of seconds since 1/1/1970 for date handling. When these dates are displayed, the years since 1900 are stored in a signed char. This is a restrictive structure used by Visual SourceSafe 4.0a in handling date data and is the reason behind the display issues outlined below. Displaying year portion of dates Dates from 1/1/2000 to 12/31/2027 display a special character in place of the 10's digit of the year as follows (where X is any digit from 0-9): Dates like 200X, appear as 20:X Dates like 201X, appear as 20;X Dates like 202X, appear as 20<X For example the date 2003 is displayed as 20:3 and 2015 is displayed as 20;5. The issue described above is a cosmetic display issue and does not impact the storage of files or project data. This data is stored as documented in Books Online for VSS. Dates beyond 12/31/2027 are not legible and character mapping cannot be easily defined. Pulling file or project history by user specified dates This issue can be summarized by the following:
The issues described above are cosmetic display issues and do not impact the storage of files or project data. This data is stored as documented in Books Online for VSS. The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. Using –VD command line switch Visual SourceSafe commands using the -VD switch will execute on the latest version of the specified file when specifying a date past 12/31/1999. This issue impacts the following Visual SourceSafe 4.0a commands:
Depending on which command is used, this issue can cause data corruption and/or loss since the incorrect file may be used to perform the specified operation.
BIOS dependencies in Visual SourceSafe: Visual SourceSafe uses a "time stamp" to apply a date to files. This time stamp contains date information obtained from the user’s system clock. The time stamp is provided by the machine’s BIOS (Basic Input-Output System), and is not provided by Visual SourceSafe. If the machine uses a year 2000 non-compliant BIOS/RTC that fails to reset the system clock to January 1, 2000 (and if the operating system does not automatically correct the date) new files and new versions will be saved with incorrect time stamps. This could lead to versions of files not appearing in the history dialog. Users should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. Two-digit shortcut handling: The Visual SourceSafe 4.0a product handles 2-digit dates entered into the system as follows: Years 70 – 99 for dates 1/1/70 through 12/31/99 are converted to 1970 – 1999. Years 00 – 38 for dates 1/1/2000 through 1/18/2038 are not converted. Values 39 – 69 are undefined within the operational range and are not converted.
Recommendations to meet compliance: Upgrade to Visual Source Safe 5.0, apply the Visual Studio 97 Service Pack 3 and the Visual SourceSafe 5.0 Year 2000 Update. Please contact 1-888-MSFT-Y2K (or your local Microsoft Year 2000 Information line) and provide your Visual Source Safe 4.0 license number to request an upgrade. The Visual Studio 97 Service Pack 3 can be downloaded from http://msdn.microsoft.com/vstudio/sp/vs97/ and the Visual SourceSafe 5.0 Year 2000 Update can be downloaded from http://msdn.microsoft.com/ssafe/downloads/year2000.asp.
Recommended practices to develop year 2000 compliant applications: Both "displaying year portions of dates" and "pulling file or project history by user specified dates" issues do not impact the applications developers build using Visual SourceSafe as their source code control tool. The user can pull file or project history without specifying a date and will have history data before 1/1/2028 returned in the list. When viewing dates within Visual SourceSafe past the year 2000 rollover, you should be aware of the display problems with the year portion of the dates and map the appropriate 10’s digit with the character displayed as indicated in the issue description. When pulling file or project history do not specify a date so that the operation will return all versions of the file or project. When using the command line operations of Visual SourceSafe 4.0a, it is recommended that you do not use the –VD switch to operate on a specific version of a file after 12/31/1999. If possible, use the –V or –VL switch to specify the version or label of a specific version of the file or project you wish to operate on. If you are using the Visual SourceSafe 4.0a command line operations through batch files, we recommend that you remove all instances of the –VD switch from these batch files to ensure you do not corrupt your build, build process or Visual SourceSafe database. In the worst case, you can locate the specific version of a file using the Graphic User Interface (GUI) and searching the entire history through the show history command. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. This issue does not impact the ability of developers to build year 2000 compliant applications. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Visual SourceSafe 4.0a (Spanish)
| 01 Jan 1970 - 31 Dec 2027 | ||
| none | ||
| none | ||
| Operating System Clock | ||
| 05 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. How the product runtime handles dates: Visual SourceSafe 4.0a, has known issues with date handling for dates past 12/31/1999. These issues can be summarized as:
Visual SourceSafe 4.0a uses a 32-bit integer to store the number of seconds since 1/1/1970 for date handling. When these dates are displayed, the years since 1900 are stored in a signed char. This is a restrictive structure used by Visual SourceSafe 4.0a in handling date data and is the reason behind the display issues outlined below. Displaying year portion of dates Dates from 1/1/2000 to 12/31/2027 display a special character in place of the 10's digit of the year as follows (where X is any digit from 0-9): Dates like 200X, appear as 20:X Dates like 201X, appear as 20;X Dates like 202X, appear as 20<X For example the date 2003 is displayed as 20:3 and 2015 is displayed as 20;5. The issue described above is a cosmetic display issue and does not impact the storage of files or project data. This data is stored as documented in Books Online for VSS. Dates beyond 12/31/2027 are not legible and character mapping cannot be easily defined. Pulling file or project history by user specified dates This issue can be summarized by the following:
The issues described above are cosmetic display issues and do not impact the storage of files or project data. This data is stored as documented in Books Online for VSS. The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. Using –VD command line switch Visual SourceSafe commands using the -VD switch will execute on the latest version of the specified file when specifying a date past 12/31/1999. This issue impacts the following Visual SourceSafe 4.0a commands:
Depending on which command is used, this issue can cause data corruption and/or loss since the incorrect file may be used to perform the specified operation.
BIOS dependencies in Visual SourceSafe: Visual SourceSafe uses a "time stamp" to apply a date to files. This time stamp contains date information obtained from the user’s system clock. The time stamp is provided by the machine’s BIOS (Basic Input-Output System), and is not provided by Visual SourceSafe. If the machine uses a year 2000 non-compliant BIOS/RTC that fails to reset the system clock to January 1, 2000 (and if the operating system does not automatically correct the date) new files and new versions will be saved with incorrect time stamps. This could lead to versions of files not appearing in the history dialog. Users should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. Two-digit shortcut handling: The Visual SourceSafe 4.0a product handles 2-digit dates entered into the system as follows: Years 70 – 99 for dates 1/1/70 through 12/31/99 are converted to 1970 – 1999. Years 00 – 38 for dates 1/1/2000 through 1/18/2038 are not converted. Values 39 – 69 are undefined within the operational range and are not converted.
Recommendations to meet compliance: Upgrade to Visual Source Safe 5.0, apply the Visual Studio 97 Service Pack 3 and the Visual SourceSafe 5.0 Year 2000 Update. Please contact 1-888-MSFT-Y2K (or your local Microsoft Year 2000 Information line) and provide your Visual Source Safe 4.0 license number to request an upgrade. The Visual Studio 97 Service Pack 3 can be downloaded from http://msdn.microsoft.com/vstudio/sp/vs97/ and the Visual SourceSafe 5.0 Year 2000 Update can be downloaded from http://msdn.microsoft.com/ssafe/downloads/year2000.asp.
Recommended practices to develop year 2000 compliant applications: Both "displaying year portions of dates" and "pulling file or project history by user specified dates" issues do not impact the applications developers build using Visual SourceSafe as their source code control tool. The user can pull file or project history without specifying a date and will have history data before 1/1/2028 returned in the list. When viewing dates within Visual SourceSafe past the year 2000 rollover, you should be aware of the display problems with the year portion of the dates and map the appropriate 10’s digit with the character displayed as indicated in the issue description. When pulling file or project history do not specify a date so that the operation will return all versions of the file or project. When using the command line operations of Visual SourceSafe 4.0a, it is recommended that you do not use the –VD switch to operate on a specific version of a file after 12/31/1999. If possible, use the –V or –VL switch to specify the version or label of a specific version of the file or project you wish to operate on. If you are using the Visual SourceSafe 4.0a command line operations through batch files, we recommend that you remove all instances of the –VD switch from these batch files to ensure you do not corrupt your build, build process or Visual SourceSafe database. In the worst case, you can locate the specific version of a file using the Graphic User Interface (GUI) and searching the entire history through the show history command. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. This issue does not impact the ability of developers to build year 2000 compliant applications. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Visual SourceSafe 4.0a (Spanish)
| 01 Jan 1970 - 31 Dec 2027 | ||
| none | ||
| none | ||
| Operating System Clock | ||
| 05 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. How the product runtime handles dates: Visual SourceSafe 4.0a, has known issues with date handling for dates past 12/31/1999. These issues can be summarized as:
Visual SourceSafe 4.0a uses a 32-bit integer to store the number of seconds since 1/1/1970 for date handling. When these dates are displayed, the years since 1900 are stored in a signed char. This is a restrictive structure used by Visual SourceSafe 4.0a in handling date data and is the reason behind the display issues outlined below. Displaying year portion of dates Dates from 1/1/2000 to 12/31/2027 display a special character in place of the 10's digit of the year as follows (where X is any digit from 0-9): Dates like 200X, appear as 20:X Dates like 201X, appear as 20;X Dates like 202X, appear as 20<X For example the date 2003 is displayed as 20:3 and 2015 is displayed as 20;5. The issue described above is a cosmetic display issue and does not impact the storage of files or project data. This data is stored as documented in Books Online for VSS. Dates beyond 12/31/2027 are not legible and character mapping cannot be easily defined. Pulling file or project history by user specified dates This issue can be summarized by the following:
The issues described above are cosmetic display issues and do not impact the storage of files or project data. This data is stored as documented in Books Online for VSS. The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. Using –VD command line switch Visual SourceSafe commands using the -VD switch will execute on the latest version of the specified file when specifying a date past 12/31/1999. This issue impacts the following Visual SourceSafe 4.0a commands:
Depending on which command is used, this issue can cause data corruption and/or loss since the incorrect file may be used to perform the specified operation.
BIOS dependencies in Visual SourceSafe: Visual SourceSafe uses a "time stamp" to apply a date to files. This time stamp contains date information obtained from the user’s system clock. The time stamp is provided by the machine’s BIOS (Basic Input-Output System), and is not provided by Visual SourceSafe. If the machine uses a year 2000 non-compliant BIOS/RTC that fails to reset the system clock to January 1, 2000 (and if the operating system does not automatically correct the date) new files and new versions will be saved with incorrect time stamps. This could lead to versions of files not appearing in the history dialog. Users should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. Two-digit shortcut handling: The Visual SourceSafe 4.0a product handles 2-digit dates entered into the system as follows: Years 70 – 99 for dates 1/1/70 through 12/31/99 are converted to 1970 – 1999. Years 00 – 38 for dates 1/1/2000 through 1/18/2038 are not converted. Values 39 – 69 are undefined within the operational range and are not converted.
Recommendations to meet compliance: Upgrade to Visual Source Safe 5.0, apply the Visual Studio 97 Service Pack 3 and the Visual SourceSafe 5.0 Year 2000 Update. Please contact 1-888-MSFT-Y2K (or your local Microsoft Year 2000 Information line) and provide your Visual Source Safe 4.0 license number to request an upgrade. The Visual Studio 97 Service Pack 3 can be downloaded from http://msdn.microsoft.com/vstudio/sp/vs97/ and the Visual SourceSafe 5.0 Year 2000 Update can be downloaded from http://msdn.microsoft.com/ssafe/downloads/year2000.asp.
Recommended practices to develop year 2000 compliant applications: Both "displaying year portions of dates" and "pulling file or project history by user specified dates" issues do not impact the applications developers build using Visual SourceSafe as their source code control tool. The user can pull file or project history without specifying a date and will have history data before 1/1/2028 returned in the list. When viewing dates within Visual SourceSafe past the year 2000 rollover, you should be aware of the display problems with the year portion of the dates and map the appropriate 10’s digit with the character displayed as indicated in the issue description. When pulling file or project history do not specify a date so that the operation will return all versions of the file or project. When using the command line operations of Visual SourceSafe 4.0a, it is recommended that you do not use the –VD switch to operate on a specific version of a file after 12/31/1999. If possible, use the –V or –VL switch to specify the version or label of a specific version of the file or project you wish to operate on. If you are using the Visual SourceSafe 4.0a command line operations through batch files, we recommend that you remove all instances of the –VD switch from these batch files to ensure you do not corrupt your build, build process or Visual SourceSafe database. In the worst case, you can locate the specific version of a file using the Graphic User Interface (GUI) and searching the entire history through the show history command. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. This issue does not impact the ability of developers to build year 2000 compliant applications. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Visual SourceSafe 5.0 (English)
| 01 Jan 1970 - 18 Jan 2038 | ||
| Visual SourceSafe 5.0 Year 2000 update (history issue) | ||
| None | ||
| Operating System Clock | ||
| 09 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. How the product runtime handles dates: Visual SourceSafe 5.0, as originally shipped, has a known issue when attempting to pull the history of a file or project filtered by user specified dates. This issue can be summarized as:
The issues described above are cosmetic display issues and do not impact the storage of files or project data. This data is stored correctly and clock rollover to the year 2000 will not cause data loss. The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. The most restrictive structure Visual SourceSafe uses for dates is a long integer containing the number of seconds since January 1, 1970.
BIOS dependencies in Visual SourceSafe: Visual SourceSafe uses a "time stamp" to data files. This time stamp contains date information obtained from the system clock. The time stamp is provided by the machine’s BIOS (Basic Input-Output System), and is not provided by Visual SourceSafe. If the machine uses a year 2000 non-compliant BIOS/RTC that fails to reset the system clock to January 1, 2000 (and if the operating system does not automatically correct the date) new files and new versions will be saved with incorrect time stamps. This could corrupt data in the history database. For example, if the version control system checks in a "new" file with an incorrect date (say, a year in the 1900s), the control system could overwrite the "new" version with an older version of the data file. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. Two-digit shortcut handling: Years 00 – 38 for dates 1/1/00 through 1/18/38 are converted to 2000 – 2038. Years 38 – 99 for dates 1/19/38 through 12/31/99 are converted to 1938 – 1999. Recommended practices to develop year 2000 compliant applications: The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. This issue does not impact the ability of developers to build year 2000 compliant applications. Common development errors dealing with year 2000 date issues: The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. Testing guidelines and recommendations: Customers should not need to change their behavior outside of the History pre-dialog that has the minor issues described above. An update for Visual SourceSafe version 5.0 to resolve the history report issue can be found at
| ||
| 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. | |
Microsoft Year 2000 Resource Center
Visual SourceSafe 5.0 (French)
| 01 Jan 1970 - 18 Jan 2038 | ||
| Visual SourceSafe 5.0 Year 2000 update (history issue) | ||
| None | ||
| Operating System Clock | ||
| 09 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. How the product runtime handles dates: Visual SourceSafe 5.0, as originally shipped, has a known issue when attempting to pull the history of a file or project filtered by user specified dates. This issue can be summarized as:
The issues described above are cosmetic display issues and do not impact the storage of files or project data. This data is stored correctly and clock rollover to the year 2000 will not cause data loss. The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. The most restrictive structure Visual SourceSafe uses for dates is a long integer containing the number of seconds since January 1, 1970.
BIOS dependencies in Visual SourceSafe: Visual SourceSafe uses a "time stamp" to data files. This time stamp contains date information obtained from the system clock. The time stamp is provided by the machine’s BIOS (Basic Input-Output System), and is not provided by Visual SourceSafe. If the machine uses a year 2000 non-compliant BIOS/RTC that fails to reset the system clock to January 1, 2000 (and if the operating system does not automatically correct the date) new files and new versions will be saved with incorrect time stamps. This could corrupt data in the history database. For example, if the version control system checks in a "new" file with an incorrect date (say, a year in the 1900s), the control system could overwrite the "new" version with an older version of the data file. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. Two-digit shortcut handling: Years 00 – 38 for dates 1/1/00 through 1/18/38 are converted to 2000 – 2038. Years 38 – 99 for dates 1/19/38 through 12/31/99 are converted to 1938 – 1999. Recommended practices to develop year 2000 compliant applications: The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. This issue does not impact the ability of developers to build year 2000 compliant applications. Common development errors dealing with year 2000 date issues: The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. Testing guidelines and recommendations: Customers should not need to change their behavior outside of the History pre-dialog that has the minor issues described above. An update for Visual SourceSafe version 5.0 to resolve the history report issue can be found at
| ||
| 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. | |
Microsoft Year 2000 Resource Center
Visual SourceSafe 5.0 (German)
| 01 Jan 1970 - 18 Jan 2038 | ||
| Visual SourceSafe 5.0 Year 2000 update (history issue) | ||
| None | ||
| Operating System Clock | ||
| 09 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. How the product runtime handles dates: Visual SourceSafe 5.0, as originally shipped, has a known issue when attempting to pull the history of a file or project filtered by user specified dates. This issue can be summarized as:
The issues described above are cosmetic display issues and do not impact the storage of files or project data. This data is stored correctly and clock rollover to the year 2000 will not cause data loss. The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. The most restrictive structure Visual SourceSafe uses for dates is a long integer containing the number of seconds since January 1, 1970.
BIOS dependencies in Visual SourceSafe: Visual SourceSafe uses a "time stamp" to data files. This time stamp contains date information obtained from the system clock. The time stamp is provided by the machine’s BIOS (Basic Input-Output System), and is not provided by Visual SourceSafe. If the machine uses a year 2000 non-compliant BIOS/RTC that fails to reset the system clock to January 1, 2000 (and if the operating system does not automatically correct the date) new files and new versions will be saved with incorrect time stamps. This could corrupt data in the history database. For example, if the version control system checks in a "new" file with an incorrect date (say, a year in the 1900s), the control system could overwrite the "new" version with an older version of the data file. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. Two-digit shortcut handling: Years 00 – 38 for dates 1/1/00 through 1/18/38 are converted to 2000 – 2038. Years 38 – 99 for dates 1/19/38 through 12/31/99 are converted to 1938 – 1999. Recommended practices to develop year 2000 compliant applications: The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. This issue does not impact the ability of developers to build year 2000 compliant applications. Common development errors dealing with year 2000 date issues: The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. Testing guidelines and recommendations: Customers should not need to change their behavior outside of the History pre-dialog that has the minor issues described above. An update for Visual SourceSafe version 5.0 to resolve the history report issue can be found at
| ||
| 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. | |
Microsoft Year 2000 Resource Center
Visual SourceSafe 5.0 (Italian)
| 01 Jan 1970 - 18 Jan 2038 | ||
| Visual SourceSafe 5.0 Year 2000 update (history issue) | ||
| None | ||
| Operating System Clock | ||
| 09 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. How the product runtime handles dates: Visual SourceSafe 5.0, as originally shipped, has a known issue when attempting to pull the history of a file or project filtered by user specified dates. This issue can be summarized as:
The issues described above are cosmetic display issues and do not impact the storage of files or project data. This data is stored correctly and clock rollover to the year 2000 will not cause data loss. The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. The most restrictive structure Visual SourceSafe uses for dates is a long integer containing the number of seconds since January 1, 1970.
BIOS dependencies in Visual SourceSafe: Visual SourceSafe uses a "time stamp" to data files. This time stamp contains date information obtained from the system clock. The time stamp is provided by the machine’s BIOS (Basic Input-Output System), and is not provided by Visual SourceSafe. If the machine uses a year 2000 non-compliant BIOS/RTC that fails to reset the system clock to January 1, 2000 (and if the operating system does not automatically correct the date) new files and new versions will be saved with incorrect time stamps. This could corrupt data in the history database. For example, if the version control system checks in a "new" file with an incorrect date (say, a year in the 1900s), the control system could overwrite the "new" version with an older version of the data file. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. Two-digit shortcut handling: Years 00 – 38 for dates 1/1/00 through 1/18/38 are converted to 2000 – 2038. Years 38 – 99 for dates 1/19/38 through 12/31/99 are converted to 1938 – 1999. Recommended practices to develop year 2000 compliant applications: The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. This issue does not impact the ability of developers to build year 2000 compliant applications. Common development errors dealing with year 2000 date issues: The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. Testing guidelines and recommendations: Customers should not need to change their behavior outside of the History pre-dialog that has the minor issues described above. An update for Visual SourceSafe version 5.0 to resolve the history report issue can be found at
| ||
| 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. | |
Microsoft Year 2000 Resource Center
Visual SourceSafe 5.0 (Japanese)
| 01 Jan 1970 - 18 Jan 2038 | ||
| Visual SourceSafe 5.0 Year 2000 update (history issue) | ||
| None | ||
| Operating System Clock | ||
| 09 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. How the product runtime handles dates: Visual SourceSafe 5.0, as originally shipped, has a known issue when attempting to pull the history of a file or project filtered by user specified dates. This issue can be summarized as:
The issues described above are cosmetic display issues and do not impact the storage of files or project data. This data is stored correctly and clock rollover to the year 2000 will not cause data loss. The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. The most restrictive structure Visual SourceSafe uses for dates is a long integer containing the number of seconds since January 1, 1970.
BIOS dependencies in Visual SourceSafe: Visual SourceSafe uses a "time stamp" to data files. This time stamp contains date information obtained from the system clock. The time stamp is provided by the machine’s BIOS (Basic Input-Output System), and is not provided by Visual SourceSafe. If the machine uses a year 2000 non-compliant BIOS/RTC that fails to reset the system clock to January 1, 2000 (and if the operating system does not automatically correct the date) new files and new versions will be saved with incorrect time stamps. This could corrupt data in the history database. For example, if the version control system checks in a "new" file with an incorrect date (say, a year in the 1900s), the control system could overwrite the "new" version with an older version of the data file. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. Two-digit shortcut handling: Years 00 – 38 for dates 1/1/00 through 1/18/38 are converted to 2000 – 2038. Years 38 – 99 for dates 1/19/38 through 12/31/99 are converted to 1938 – 1999. Recommended practices to develop year 2000 compliant applications: The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. This issue does not impact the ability of developers to build year 2000 compliant applications. Common development errors dealing with year 2000 date issues: The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. Testing guidelines and recommendations: Customers should not need to change their behavior outside of the History pre-dialog that has the minor issues described above. An update for Visual SourceSafe version 5.0 to resolve the history report issue can be found at
| ||
| 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. | |
Microsoft Year 2000 Resource Center
Visual SourceSafe 5.0 (Spanish)
| 01 Jan 1970 - 18 Jan 2038 | ||
| Visual SourceSafe 5.0 Year 2000 update (history issue) | ||
| None | ||
| Operating System Clock | ||
| 09 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. How the product runtime handles dates: Visual SourceSafe 5.0, as originally shipped, has a known issue when attempting to pull the history of a file or project filtered by user specified dates. This issue can be summarized as:
The issues described above are cosmetic display issues and do not impact the storage of files or project data. This data is stored correctly and clock rollover to the year 2000 will not cause data loss. The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. The most restrictive structure Visual SourceSafe uses for dates is a long integer containing the number of seconds since January 1, 1970.
BIOS dependencies in Visual SourceSafe: Visual SourceSafe uses a "time stamp" to data files. This time stamp contains date information obtained from the system clock. The time stamp is provided by the machine’s BIOS (Basic Input-Output System), and is not provided by Visual SourceSafe. If the machine uses a year 2000 non-compliant BIOS/RTC that fails to reset the system clock to January 1, 2000 (and if the operating system does not automatically correct the date) new files and new versions will be saved with incorrect time stamps. This could corrupt data in the history database. For example, if the version control system checks in a "new" file with an incorrect date (say, a year in the 1900s), the control system could overwrite the "new" version with an older version of the data file. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. Two-digit shortcut handling: Years 00 – 38 for dates 1/1/00 through 1/18/38 are converted to 2000 – 2038. Years 38 – 99 for dates 1/19/38 through 12/31/99 are converted to 1938 – 1999. Recommended practices to develop year 2000 compliant applications: The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. This issue does not impact the ability of developers to build year 2000 compliant applications. Common development errors dealing with year 2000 date issues: The history report issue does not have an impact on the applications that developers build using Visual SourceSafe as the source code control tool. Only the ability to view history where a date is specified is affected. Testing guidelines and recommendations: Customers should not need to change their behavior outside of the History pre-dialog that has the minor issues described above. An update for Visual SourceSafe version 5.0 to resolve the history report issue can be found at
| ||
| 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. | |
Microsoft Year 2000 Resource Center
Visual SourceSafe 6.0 (English)
| 01 Jan 1970 - 18 Jan 2038 | ||
| read BIOS dependencies in Visual SourceSafe | ||
| NONE | ||
| Operating System Clock | ||
| 09 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. How the product runtime handles dates: The most restrictive structure Visual SourceSafe uses for dates is a long integer containing the number of seconds since January 1, 1970.
BIOS dependencies in Visual SourceSafe: Visual SourceSafe uses a "time stamp" to data files. This time stamp contains date information obtained from the system clock. The time stamp is provided by the machine’s BIOS (Basic Input-Output System), and is not provided by Visual SourceSafe. If the machine uses a year 2000 non-compliant BIOS/RTC that fails to reset the system clock to January 1, 2000 (and if the operating system does not automatically correct the date) new files and new versions will be saved with incorrect time stamps. This could corrupt data in the history database. For example, if the version control system checks in a "new" file with an incorrect date (say, a year in the 1900s), the control system could overwrite the "new" version with an older version of the data file. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. Two-digit shortcut handling: Years 00 – 38 for dates 1/1/00 through 1/18/38 are converted to 2000 – 2038. Years 38 – 99 for dates 1/19/38 through 12/31/99 are converted to 1938 – 1999.
| ||
| 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. | |
Microsoft Year 2000 Resource Center
Visual SourceSafe 6.0 (French)
| 01 Jan 1970 - 18 Jan 2038 | ||
| read BIOS dependencies in Visual SourceSafe | ||
| NONE | ||
| Operating System Clock | ||
| 09 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. How the product runtime handles dates: The most restrictive structure Visual SourceSafe uses for dates is a long integer containing the number of seconds since January 1, 1970.
BIOS dependencies in Visual SourceSafe: Visual SourceSafe uses a "time stamp" to data files. This time stamp contains date information obtained from the system clock. The time stamp is provided by the machine’s BIOS (Basic Input-Output System), and is not provided by Visual SourceSafe. If the machine uses a year 2000 non-compliant BIOS/RTC that fails to reset the system clock to January 1, 2000 (and if the operating system does not automatically correct the date) new files and new versions will be saved with incorrect time stamps. This could corrupt data in the history database. For example, if the version control system checks in a "new" file with an incorrect date (say, a year in the 1900s), the control system could overwrite the "new" version with an older version of the data file. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. Two-digit shortcut handling: Years 00 – 38 for dates 1/1/00 through 1/18/38 are converted to 2000 – 2038. Years 38 – 99 for dates 1/19/38 through 12/31/99 are converted to 1938 – 1999.
| ||
| 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. | |
Microsoft Year 2000 Resource Center
Visual SourceSafe 6.0 (German)
| 01 Jan 1970 - 18 Jan 2038 | ||
| read BIOS dependencies in Visual SourceSafe | ||
| NONE | ||
| Operating System Clock | ||
| 09 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. How the product runtime handles dates: The most restrictive structure Visual SourceSafe uses for dates is a long integer containing the number of seconds since January 1, 1970.
BIOS dependencies in Visual SourceSafe: Visual SourceSafe uses a "time stamp" to data files. This time stamp contains date information obtained from the system clock. The time stamp is provided by the machine’s BIOS (Basic Input-Output System), and is not provided by Visual SourceSafe. If the machine uses a year 2000 non-compliant BIOS/RTC that fails to reset the system clock to January 1, 2000 (and if the operating system does not automatically correct the date) new files and new versions will be saved with incorrect time stamps. This could corrupt data in the history database. For example, if the version control system checks in a "new" file with an incorrect date (say, a year in the 1900s), the control system could overwrite the "new" version with an older version of the data file. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. Two-digit shortcut handling: Years 00 – 38 for dates 1/1/00 through 1/18/38 are converted to 2000 – 2038. Years 38 – 99 for dates 1/19/38 through 12/31/99 are converted to 1938 – 1999.
| ||
| 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. | |
Microsoft Year 2000 Resource Center
Visual SourceSafe 6.0 (Japanese)
| 01 Jan 1970 - 18 Jan 2038 | ||
| read BIOS dependencies in Visual SourceSafe | ||
| NONE | ||
| Operating System Clock | ||
| 09 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. How the product runtime handles dates: The most restrictive structure Visual SourceSafe uses for dates is a long integer containing the number of seconds since January 1, 1970.
BIOS dependencies in Visual SourceSafe: Visual SourceSafe uses a "time stamp" to data files. This time stamp contains date information obtained from the system clock. The time stamp is provided by the machine’s BIOS (Basic Input-Output System), and is not provided by Visual SourceSafe. If the machine uses a year 2000 non-compliant BIOS/RTC that fails to reset the system clock to January 1, 2000 (and if the operating system does not automatically correct the date) new files and new versions will be saved with incorrect time stamps. This could corrupt data in the history database. For example, if the version control system checks in a "new" file with an incorrect date (say, a year in the 1900s), the control system could overwrite the "new" version with an older version of the data file. Developers should contact their PC vendor to ensure that the computer's BIOS is year 2000 compliant. Two-digit shortcut handling: Years 00 – 38 for dates 1/1/00 through 1/18/38 are converted to 2000 – 2038. Years 38 – 99 for dates 1/19/38 through 12/31/99 are converted to 1938 – 1999.
| ||
| 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. | |
Microsoft Year 2000 Resource Center
Visual Studio 6.0 (Chinese - Simplified)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See Below | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, Windows 98, Windows NT 4.0 Service Pack 4 plus Year 2000 software updates, Internet Explorer 4.01 Service Pack 1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock, Operating System File Date API, OLEAUT32.DLL. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 13 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This report applies to: Enterprise and Professional editions. Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes NOTE: One or more of the bundled products or components in Visual Studio 6.0 has known issues. These products are listed below under section II of "Product Details." Please refer to this section for more information. Operational Range for Data: See individual product detail for products listed below. Outlook Express 4.01 date handling: If Outlook Express (OE) 4.01 (Service Pack 1 or Service Pack 2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than 99, OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as 97, then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year 99 is received and the current year is a multiple of 100 (e.g. 2000), than the year will be interpreted as the current year plus 98 (e.g. 2098). You can find more information about this fix in the Internet Explorer (32-bit) 4.0x Year 2000 disclosure document at http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430.Prerequisites: A prerequisite refers to what is needed for a given product to reach the compliance classification indicated. It could include a software update that is required or a specific version of a related Microsoft technology that the product needs.
Product Details There are three aspects of Year 2000 compliance for Visual Studio 6.0: compliance for the individual visual tools in the suite (such as Visual Basic and Visual C++), compliance of other Microsoft Products which ship as a part of Visual Studio (such as SQL Server Developer Edition), and compliance of the suite-specific features such as Visual Studio Analyzer, Installer tools, and Visual Component Manager.
The Year 2000 status of the Visual Studio 6.0 individual tools is described below. Please refer to the individual tools and their prerequisites in the Microsoft Year 2000 website for information on compliance status as well as specific information on date handling, recommended practices, usage errors, and testing guidelines:
Visual Studio Enterprise Edition also contains these additional Microsoft Products.
Visual Studio 6.0 Enterprise Edition also includes the following third party add on components which are not included in the above test results:
Visual Studio Enterprise Edition 6.0 also contains several suite specific features. Please refer to the below for specific information on date handling, recommended practices, and testing guidelines.
How the product runtime handles dates: The Visual Studio Analyzer tool and the Application Performance Explorer convert dates to a 4-digit format, sorts them, truncates them to 2 digits, and then displays the results. The Visual Component Manager tool passes the date inputs as a string type to the database (SQL or Access). Therefore, the Year 2000 status of the database being used needs to be determined. The Installer tools compare file timestamps by comparing the time_t data type. Dates for each of these Enterprise Edition Components are stored in a time_t data type format.
Two-digit shortcut handling: Visual Studio Analyzer: Two-digit shortcuts are supported where the date field equals the results field. Do not confuse the date field as the input field. Application Performance Explorer: Two-digit shortcuts are supported where the date field equals the results field. Do not confuse the date field as the input field. Visual Component Manager component: Two-digit shortcuts are supported, but the date field is passed to the database for query. Therefore, this tool’s ability to interpret dates in the correct century is affected by the database used. Two-digit dates in the Microsoft Application Performance Explorer 6.0, Microsoft Visual Studio Analyzer 6.0, and Microsoft Visual Component Manager 6.0 tools pass the string to the database for querying. Therefore, the tool’s ability to interpret dates correctly is affected by the database used.
Recommended practices to develop year 2000 compliant applications:
Visual Studio Database Tools: Oracle and Visual Studio Query Designer may interpret 2-digit year dates differently When using the Visual Studio 6.0 Query Designer against an Oracle database, it is highly recommended you set your regional settings to a 4-digit year setting such as MM/DD/YYYY to prevent incorrect or unexpected results from queries that could lead to data loss. When a date is entered into the Grid Pane of the Query Designer, it is formatted according to the regional settings. Then, this reformatted date is passed to Oracle, which interprets the date string according to the server’s configuration. If the year entered into the Grid Pane’s criteria cell is from 2000 through 2029 (the system default 2-digit year window for dates 2000 and later), the date will be converted by OLEAUT32 into a 2-digit value when parsed into the SQL Pane. Oracle will interpret this as a year from 1900 through 1929. For example: A user types the date "1/1/2001" into the Grid Pane’s criteria cell. With two digit years turned on, the date is reformatted to "1/1/01." When Oracle receives the string it interprets the date "1/1/01" to be "1/1/1901." If the date is being used in the criteria for an UPDATE or DELETE query, data loss may occur. This issue is addressed in the final release of Visual Studio 6.0 Service Pack 3. Testing guidelines and recommendations: Set the system clock on a non-production system to a time like 11:50 pm Dec 31, 1999 and let it automatically roll to the year 2000 and see if the application still works as expected.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | |
Microsoft Year 2000 Resource Center
Visual Studio 6.0 (Chinese - Traditional)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See Below | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, Windows 98, Windows NT 4.0 Service Pack 4 plus Year 2000 software updates, Internet Explorer 4.01 Service Pack 1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock, Operating System File Date API, OLEAUT32.DLL. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 13 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This report applies to: Enterprise and Professional editions. Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes NOTE: One or more of the bundled products or components in Visual Studio 6.0 has known issues. These products are listed below under section II of "Product Details." Please refer to this section for more information. Operational Range for Data: See individual product detail for products listed below. Outlook Express 4.01 date handling: If Outlook Express (OE) 4.01 (Service Pack 1 or Service Pack 2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than 99, OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as 97, then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year 99 is received and the current year is a multiple of 100 (e.g. 2000), than the year will be interpreted as the current year plus 98 (e.g. 2098). You can find more information about this fix in the Internet Explorer (32-bit) 4.0x Year 2000 disclosure document at http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430.Prerequisites: A prerequisite refers to what is needed for a given product to reach the compliance classification indicated. It could include a software update that is required or a specific version of a related Microsoft technology that the product needs.
Product Details There are three aspects of Year 2000 compliance for Visual Studio 6.0: compliance for the individual visual tools in the suite (such as Visual Basic and Visual C++), compliance of other Microsoft Products which ship as a part of Visual Studio (such as SQL Server Developer Edition), and compliance of the suite-specific features such as Visual Studio Analyzer, Installer tools, and Visual Component Manager.
The Year 2000 status of the Visual Studio 6.0 individual tools is described below. Please refer to the individual tools and their prerequisites in the Microsoft Year 2000 website for information on compliance status as well as specific information on date handling, recommended practices, usage errors, and testing guidelines:
Visual Studio Enterprise Edition also contains these additional Microsoft Products.
Visual Studio 6.0 Enterprise Edition also includes the following third party add on components which are not included in the above test results:
Visual Studio Enterprise Edition 6.0 also contains several suite specific features. Please refer to the below for specific information on date handling, recommended practices, and testing guidelines.
How the product runtime handles dates: The Visual Studio Analyzer tool and the Application Performance Explorer convert dates to a 4-digit format, sorts them, truncates them to 2 digits, and then displays the results. The Visual Component Manager tool passes the date inputs as a string type to the database (SQL or Access). Therefore, the Year 2000 status of the database being used needs to be determined. The Installer tools compare file timestamps by comparing the time_t data type. Dates for each of these Enterprise Edition Components are stored in a time_t data type format.
Two-digit shortcut handling: Visual Studio Analyzer: Two-digit shortcuts are supported where the date field equals the results field. Do not confuse the date field as the input field. Application Performance Explorer: Two-digit shortcuts are supported where the date field equals the results field. Do not confuse the date field as the input field. Visual Component Manager component: Two-digit shortcuts are supported, but the date field is passed to the database for query. Therefore, this tool’s ability to interpret dates in the correct century is affected by the database used. Two-digit dates in the Microsoft Application Performance Explorer 6.0, Microsoft Visual Studio Analyzer 6.0, and Microsoft Visual Component Manager 6.0 tools pass the string to the database for querying. Therefore, the tool’s ability to interpret dates correctly is affected by the database used.
Recommended practices to develop year 2000 compliant applications:
Visual Studio Database Tools: Oracle and Visual Studio Query Designer may interpret 2-digit year dates differently When using the Visual Studio 6.0 Query Designer against an Oracle database, it is highly recommended you set your regional settings to a 4-digit year setting such as MM/DD/YYYY to prevent incorrect or unexpected results from queries that could lead to data loss. When a date is entered into the Grid Pane of the Query Designer, it is formatted according to the regional settings. Then, this reformatted date is passed to Oracle, which interprets the date string according to the server’s configuration. If the year entered into the Grid Pane’s criteria cell is from 2000 through 2029 (the system default 2-digit year window for dates 2000 and later), the date will be converted by OLEAUT32 into a 2-digit value when parsed into the SQL Pane. Oracle will interpret this as a year from 1900 through 1929. For example: A user types the date "1/1/2001" into the Grid Pane’s criteria cell. With two digit years turned on, the date is reformatted to "1/1/01." When Oracle receives the string it interprets the date "1/1/01" to be "1/1/1901." If the date is being used in the criteria for an UPDATE or DELETE query, data loss may occur. This issue is addressed in the final release of Visual Studio 6.0 Service Pack 3. Testing guidelines and recommendations: Set the system clock on a non-production system to a time like 11:50 pm Dec 31, 1999 and let it automatically roll to the year 2000 and see if the application still works as expected.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | |
Microsoft Year 2000 Resource Center
Visual Studio 6.0 (English)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See Below | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, Windows 98, Windows NT 4.0 Service Pack 4 plus Year 2000 software updates, Internet Explorer 4.01 Service Pack 1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock, Operating System File Date API, OLEAUT32.DLL. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 13 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This report applies to: Enterprise and Professional editions. Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes NOTE: One or more of the bundled products or components in Visual Studio 6.0 has known issues. These products are listed below under section II of "Product Details." Please refer to this section for more information. Operational Range for Data: See individual product detail for products listed below. Outlook Express 4.01 date handling: If Outlook Express (OE) 4.01 (Service Pack 1 or Service Pack 2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than 99, OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as 97, then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year 99 is received and the current year is a multiple of 100 (e.g. 2000), than the year will be interpreted as the current year plus 98 (e.g. 2098). You can find more information about this fix in the Internet Explorer (32-bit) 4.0x Year 2000 disclosure document at http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430.Prerequisites: A prerequisite refers to what is needed for a given product to reach the compliance classification indicated. It could include a software update that is required or a specific version of a related Microsoft technology that the product needs.
Product Details There are three aspects of Year 2000 compliance for Visual Studio 6.0: compliance for the individual visual tools in the suite (such as Visual Basic and Visual C++), compliance of other Microsoft Products which ship as a part of Visual Studio (such as SQL Server Developer Edition), and compliance of the suite-specific features such as Visual Studio Analyzer, Installer tools, and Visual Component Manager.
The Year 2000 status of the Visual Studio 6.0 individual tools is described below. Please refer to the individual tools and their prerequisites in the Microsoft Year 2000 website for information on compliance status as well as specific information on date handling, recommended practices, usage errors, and testing guidelines:
Visual Studio Enterprise Edition also contains these additional Microsoft Products.
Visual Studio 6.0 Enterprise Edition also includes the following third party add on components which are not included in the above test results:
Visual Studio Enterprise Edition 6.0 also contains several suite specific features. Please refer to the below for specific information on date handling, recommended practices, and testing guidelines.
How the product runtime handles dates: The Visual Studio Analyzer tool and the Application Performance Explorer convert dates to a 4-digit format, sorts them, truncates them to 2 digits, and then displays the results. The Visual Component Manager tool passes the date inputs as a string type to the database (SQL or Access). Therefore, the Year 2000 status of the database being used needs to be determined. The Installer tools compare file timestamps by comparing the time_t data type. Dates for each of these Enterprise Edition Components are stored in a time_t data type format.
Two-digit shortcut handling: Visual Studio Analyzer: Two-digit shortcuts are supported where the date field equals the results field. Do not confuse the date field as the input field. Application Performance Explorer: Two-digit shortcuts are supported where the date field equals the results field. Do not confuse the date field as the input field. Visual Component Manager component: Two-digit shortcuts are supported, but the date field is passed to the database for query. Therefore, this tool’s ability to interpret dates in the correct century is affected by the database used. Two-digit dates in the Microsoft Application Performance Explorer 6.0, Microsoft Visual Studio Analyzer 6.0, and Microsoft Visual Component Manager 6.0 tools pass the string to the database for querying. Therefore, the tool’s ability to interpret dates correctly is affected by the database used.
Recommended practices to develop year 2000 compliant applications:
Visual Studio Database Tools: Oracle and Visual Studio Query Designer may interpret 2-digit year dates differently When using the Visual Studio 6.0 Query Designer against an Oracle database, it is highly recommended you set your regional settings to a 4-digit year setting such as MM/DD/YYYY to prevent incorrect or unexpected results from queries that could lead to data loss. When a date is entered into the Grid Pane of the Query Designer, it is formatted according to the regional settings. Then, this reformatted date is passed to Oracle, which interprets the date string according to the server’s configuration. If the year entered into the Grid Pane’s criteria cell is from 2000 through 2029 (the system default 2-digit year window for dates 2000 and later), the date will be converted by OLEAUT32 into a 2-digit value when parsed into the SQL Pane. Oracle will interpret this as a year from 1900 through 1929. For example: A user types the date "1/1/2001" into the Grid Pane’s criteria cell. With two digit years turned on, the date is reformatted to "1/1/01." When Oracle receives the string it interprets the date "1/1/01" to be "1/1/1901." If the date is being used in the criteria for an UPDATE or DELETE query, data loss may occur. This issue is addressed in the final release of Visual Studio 6.0 Service Pack 3. Testing guidelines and recommendations: Set the system clock on a non-production system to a time like 11:50 pm Dec 31, 1999 and let it automatically roll to the year 2000 and see if the application still works as expected.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | |
Microsoft Year 2000 Resource Center
Visual Studio 6.0 (French)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See Below | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, Windows 98, Windows NT 4.0 Service Pack 4 plus Year 2000 software updates, Internet Explorer 4.01 Service Pack 1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock, Operating System File Date API, OLEAUT32.DLL. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 13 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This report applies to: Enterprise and Professional editions. Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes NOTE: One or more of the bundled products or components in Visual Studio 6.0 has known issues. These products are listed below under section II of "Product Details." Please refer to this section for more information. Operational Range for Data: See individual product detail for products listed below. Outlook Express 4.01 date handling: If Outlook Express (OE) 4.01 (Service Pack 1 or Service Pack 2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than 99, OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as 97, then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year 99 is received and the current year is a multiple of 100 (e.g. 2000), than the year will be interpreted as the current year plus 98 (e.g. 2098). You can find more information about this fix in the Internet Explorer (32-bit) 4.0x Year 2000 disclosure document at http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430.Prerequisites: A prerequisite refers to what is needed for a given product to reach the compliance classification indicated. It could include a software update that is required or a specific version of a related Microsoft technology that the product needs.
Product Details There are three aspects of Year 2000 compliance for Visual Studio 6.0: compliance for the individual visual tools in the suite (such as Visual Basic and Visual C++), compliance of other Microsoft Products which ship as a part of Visual Studio (such as SQL Server Developer Edition), and compliance of the suite-specific features such as Visual Studio Analyzer, Installer tools, and Visual Component Manager.
The Year 2000 status of the Visual Studio 6.0 individual tools is described below. Please refer to the individual tools and their prerequisites in the Microsoft Year 2000 website for information on compliance status as well as specific information on date handling, recommended practices, usage errors, and testing guidelines:
Visual Studio Enterprise Edition also contains these additional Microsoft Products.
Visual Studio 6.0 Enterprise Edition also includes the following third party add on components which are not included in the above test results:
Visual Studio Enterprise Edition 6.0 also contains several suite specific features. Please refer to the below for specific information on date handling, recommended practices, and testing guidelines.
How the product runtime handles dates: The Visual Studio Analyzer tool and the Application Performance Explorer convert dates to a 4-digit format, sorts them, truncates them to 2 digits, and then displays the results. The Visual Component Manager tool passes the date inputs as a string type to the database (SQL or Access). Therefore, the Year 2000 status of the database being used needs to be determined. The Installer tools compare file timestamps by comparing the time_t data type. Dates for each of these Enterprise Edition Components are stored in a time_t data type format.
Two-digit shortcut handling: Visual Studio Analyzer: Two-digit shortcuts are supported where the date field equals the results field. Do not confuse the date field as the input field. Application Performance Explorer: Two-digit shortcuts are supported where the date field equals the results field. Do not confuse the date field as the input field. Visual Component Manager component: Two-digit shortcuts are supported, but the date field is passed to the database for query. Therefore, this tool’s ability to interpret dates in the correct century is affected by the database used. Two-digit dates in the Microsoft Application Performance Explorer 6.0, Microsoft Visual Studio Analyzer 6.0, and Microsoft Visual Component Manager 6.0 tools pass the string to the database for querying. Therefore, the tool’s ability to interpret dates correctly is affected by the database used.
Recommended practices to develop year 2000 compliant applications:
Visual Studio Database Tools: Oracle and Visual Studio Query Designer may interpret 2-digit year dates differently When using the Visual Studio 6.0 Query Designer against an Oracle database, it is highly recommended you set your regional settings to a 4-digit year setting such as MM/DD/YYYY to prevent incorrect or unexpected results from queries that could lead to data loss. When a date is entered into the Grid Pane of the Query Designer, it is formatted according to the regional settings. Then, this reformatted date is passed to Oracle, which interprets the date string according to the server’s configuration. If the year entered into the Grid Pane’s criteria cell is from 2000 through 2029 (the system default 2-digit year window for dates 2000 and later), the date will be converted by OLEAUT32 into a 2-digit value when parsed into the SQL Pane. Oracle will interpret this as a year from 1900 through 1929. For example: A user types the date "1/1/2001" into the Grid Pane’s criteria cell. With two digit years turned on, the date is reformatted to "1/1/01." When Oracle receives the string it interprets the date "1/1/01" to be "1/1/1901." If the date is being used in the criteria for an UPDATE or DELETE query, data loss may occur. This issue is addressed in the final release of Visual Studio 6.0 Service Pack 3. Testing guidelines and recommendations: Set the system clock on a non-production system to a time like 11:50 pm Dec 31, 1999 and let it automatically roll to the year 2000 and see if the application still works as expected.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | |
Microsoft Year 2000 Resource Center
Visual Studio 6.0 (German)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See Below | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, Windows 98, Windows NT 4.0 Service Pack 4 plus Year 2000 software updates, Internet Explorer 4.01 Service Pack 1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock, Operating System File Date API, OLEAUT32.DLL. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 13 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This report applies to: Enterprise and Professional editions. Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes NOTE: One or more of the bundled products or components in Visual Studio 6.0 has known issues. These products are listed below under section II of "Product Details." Please refer to this section for more information. Operational Range for Data: See individual product detail for products listed below. Outlook Express 4.01 date handling: If Outlook Express (OE) 4.01 (Service Pack 1 or Service Pack 2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than 99, OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as 97, then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year 99 is received and the current year is a multiple of 100 (e.g. 2000), than the year will be interpreted as the current year plus 98 (e.g. 2098). You can find more information about this fix in the Internet Explorer (32-bit) 4.0x Year 2000 disclosure document at http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430.Prerequisites: A prerequisite refers to what is needed for a given product to reach the compliance classification indicated. It could include a software update that is required or a specific version of a related Microsoft technology that the product needs.
Product Details There are three aspects of Year 2000 compliance for Visual Studio 6.0: compliance for the individual visual tools in the suite (such as Visual Basic and Visual C++), compliance of other Microsoft Products which ship as a part of Visual Studio (such as SQL Server Developer Edition), and compliance of the suite-specific features such as Visual Studio Analyzer, Installer tools, and Visual Component Manager.
The Year 2000 status of the Visual Studio 6.0 individual tools is described below. Please refer to the individual tools and their prerequisites in the Microsoft Year 2000 website for information on compliance status as well as specific information on date handling, recommended practices, usage errors, and testing guidelines:
Visual Studio Enterprise Edition also contains these additional Microsoft Products.
Visual Studio 6.0 Enterprise Edition also includes the following third party add on components which are not included in the above test results:
Visual Studio Enterprise Edition 6.0 also contains several suite specific features. Please refer to the below for specific information on date handling, recommended practices, and testing guidelines.
How the product runtime handles dates: The Visual Studio Analyzer tool and the Application Performance Explorer convert dates to a 4-digit format, sorts them, truncates them to 2 digits, and then displays the results. The Visual Component Manager tool passes the date inputs as a string type to the database (SQL or Access). Therefore, the Year 2000 status of the database being used needs to be determined. The Installer tools compare file timestamps by comparing the time_t data type. Dates for each of these Enterprise Edition Components are stored in a time_t data type format.
Two-digit shortcut handling: Visual Studio Analyzer: Two-digit shortcuts are supported where the date field equals the results field. Do not confuse the date field as the input field. Application Performance Explorer: Two-digit shortcuts are supported where the date field equals the results field. Do not confuse the date field as the input field. Visual Component Manager component: Two-digit shortcuts are supported, but the date field is passed to the database for query. Therefore, this tool’s ability to interpret dates in the correct century is affected by the database used. Two-digit dates in the Microsoft Application Performance Explorer 6.0, Microsoft Visual Studio Analyzer 6.0, and Microsoft Visual Component Manager 6.0 tools pass the string to the database for querying. Therefore, the tool’s ability to interpret dates correctly is affected by the database used.
Recommended practices to develop year 2000 compliant applications:
Visual Studio Database Tools: Oracle and Visual Studio Query Designer may interpret 2-digit year dates differently When using the Visual Studio 6.0 Query Designer against an Oracle database, it is highly recommended you set your regional settings to a 4-digit year setting such as MM/DD/YYYY to prevent incorrect or unexpected results from queries that could lead to data loss. When a date is entered into the Grid Pane of the Query Designer, it is formatted according to the regional settings. Then, this reformatted date is passed to Oracle, which interprets the date string according to the server’s configuration. If the year entered into the Grid Pane’s criteria cell is from 2000 through 2029 (the system default 2-digit year window for dates 2000 and later), the date will be converted by OLEAUT32 into a 2-digit value when parsed into the SQL Pane. Oracle will interpret this as a year from 1900 through 1929. For example: A user types the date "1/1/2001" into the Grid Pane’s criteria cell. With two digit years turned on, the date is reformatted to "1/1/01." When Oracle receives the string it interprets the date "1/1/01" to be "1/1/1901." If the date is being used in the criteria for an UPDATE or DELETE query, data loss may occur. This issue is addressed in the final release of Visual Studio 6.0 Service Pack 3. Testing guidelines and recommendations: Set the system clock on a non-production system to a time like 11:50 pm Dec 31, 1999 and let it automatically roll to the year 2000 and see if the application still works as expected.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | |
Microsoft Year 2000 Resource Center
Visual Studio 6.0 (Italian)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See Below | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, Windows 98, Windows NT 4.0 Service Pack 4 plus Year 2000 software updates, Internet Explorer 4.01 Service Pack 1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock, Operating System File Date API, OLEAUT32.DLL. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 13 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This report applies to: Enterprise and Professional editions. Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes NOTE: One or more of the bundled products or components in Visual Studio 6.0 has known issues. These products are listed below under section II of "Product Details." Please refer to this section for more information. Operational Range for Data: See individual product detail for products listed below. Outlook Express 4.01 date handling: If Outlook Express (OE) 4.01 (Service Pack 1 or Service Pack 2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than 99, OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as 97, then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year 99 is received and the current year is a multiple of 100 (e.g. 2000), than the year will be interpreted as the current year plus 98 (e.g. 2098). You can find more information about this fix in the Internet Explorer (32-bit) 4.0x Year 2000 disclosure document at http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430.Prerequisites: A prerequisite refers to what is needed for a given product to reach the compliance classification indicated. It could include a software update that is required or a specific version of a related Microsoft technology that the product needs.
Product Details There are three aspects of Year 2000 compliance for Visual Studio 6.0: compliance for the individual visual tools in the suite (such as Visual Basic and Visual C++), compliance of other Microsoft Products which ship as a part of Visual Studio (such as SQL Server Developer Edition), and compliance of the suite-specific features such as Visual Studio Analyzer, Installer tools, and Visual Component Manager.
The Year 2000 status of the Visual Studio 6.0 individual tools is described below. Please refer to the individual tools and their prerequisites in the Microsoft Year 2000 website for information on compliance status as well as specific information on date handling, recommended practices, usage errors, and testing guidelines:
Visual Studio Enterprise Edition also contains these additional Microsoft Products.
Visual Studio 6.0 Enterprise Edition also includes the following third party add on components which are not included in the above test results:
Visual Studio Enterprise Edition 6.0 also contains several suite specific features. Please refer to the below for specific information on date handling, recommended practices, and testing guidelines.
How the product runtime handles dates: The Visual Studio Analyzer tool and the Application Performance Explorer convert dates to a 4-digit format, sorts them, truncates them to 2 digits, and then displays the results. The Visual Component Manager tool passes the date inputs as a string type to the database (SQL or Access). Therefore, the Year 2000 status of the database being used needs to be determined. The Installer tools compare file timestamps by comparing the time_t data type. Dates for each of these Enterprise Edition Components are stored in a time_t data type format.
Two-digit shortcut handling: Visual Studio Analyzer: Two-digit shortcuts are supported where the date field equals the results field. Do not confuse the date field as the input field. Application Performance Explorer: Two-digit shortcuts are supported where the date field equals the results field. Do not confuse the date field as the input field. Visual Component Manager component: Two-digit shortcuts are supported, but the date field is passed to the database for query. Therefore, this tool’s ability to interpret dates in the correct century is affected by the database used. Two-digit dates in the Microsoft Application Performance Explorer 6.0, Microsoft Visual Studio Analyzer 6.0, and Microsoft Visual Component Manager 6.0 tools pass the string to the database for querying. Therefore, the tool’s ability to interpret dates correctly is affected by the database used.
Recommended practices to develop year 2000 compliant applications:
Visual Studio Database Tools: Oracle and Visual Studio Query Designer may interpret 2-digit year dates differently When using the Visual Studio 6.0 Query Designer against an Oracle database, it is highly recommended you set your regional settings to a 4-digit year setting such as MM/DD/YYYY to prevent incorrect or unexpected results from queries that could lead to data loss. When a date is entered into the Grid Pane of the Query Designer, it is formatted according to the regional settings. Then, this reformatted date is passed to Oracle, which interprets the date string according to the server’s configuration. If the year entered into the Grid Pane’s criteria cell is from 2000 through 2029 (the system default 2-digit year window for dates 2000 and later), the date will be converted by OLEAUT32 into a 2-digit value when parsed into the SQL Pane. Oracle will interpret this as a year from 1900 through 1929. For example: A user types the date "1/1/2001" into the Grid Pane’s criteria cell. With two digit years turned on, the date is reformatted to "1/1/01." When Oracle receives the string it interprets the date "1/1/01" to be "1/1/1901." If the date is being used in the criteria for an UPDATE or DELETE query, data loss may occur. This issue is addressed in the final release of Visual Studio 6.0 Service Pack 3. Testing guidelines and recommendations: Set the system clock on a non-production system to a time like 11:50 pm Dec 31, 1999 and let it automatically roll to the year 2000 and see if the application still works as expected.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | |
Microsoft Year 2000 Resource Center
Visual Studio 6.0 (Japanese)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See Below | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, Windows 98, Windows NT 4.0 Service Pack 4 plus Year 2000 software updates, Internet Explorer 4.01 Service Pack 1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock, Operating System File Date API, OLEAUT32.DLL. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 13 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This report applies to: Enterprise and Professional editions. Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes NOTE: One or more of the bundled products or components in Visual Studio 6.0 has known issues. These products are listed below under section II of "Product Details." Please refer to this section for more information. Operational Range for Data: See individual product detail for products listed below. Outlook Express 4.01 date handling: If Outlook Express (OE) 4.01 (Service Pack 1 or Service Pack 2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than 99, OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as 97, then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year 99 is received and the current year is a multiple of 100 (e.g. 2000), than the year will be interpreted as the current year plus 98 (e.g. 2098). You can find more information about this fix in the Internet Explorer (32-bit) 4.0x Year 2000 disclosure document at http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430.Prerequisites: A prerequisite refers to what is needed for a given product to reach the compliance classification indicated. It could include a software update that is required or a specific version of a related Microsoft technology that the product needs.
Product Details There are three aspects of Year 2000 compliance for Visual Studio 6.0: compliance for the individual visual tools in the suite (such as Visual Basic and Visual C++), compliance of other Microsoft Products which ship as a part of Visual Studio (such as SQL Server Developer Edition), and compliance of the suite-specific features such as Visual Studio Analyzer, Installer tools, and Visual Component Manager.
The Year 2000 status of the Visual Studio 6.0 individual tools is described below. Please refer to the individual tools and their prerequisites in the Microsoft Year 2000 website for information on compliance status as well as specific information on date handling, recommended practices, usage errors, and testing guidelines:
Visual Studio Enterprise Edition also contains these additional Microsoft Products.
Visual Studio 6.0 Enterprise Edition also includes the following third party add on components which are not included in the above test results:
Visual Studio Enterprise Edition 6.0 also contains several suite specific features. Please refer to the below for specific information on date handling, recommended practices, and testing guidelines.
How the product runtime handles dates: The Visual Studio Analyzer tool and the Application Performance Explorer convert dates to a 4-digit format, sorts them, truncates them to 2 digits, and then displays the results. The Visual Component Manager tool passes the date inputs as a string type to the database (SQL or Access). Therefore, the Year 2000 status of the database being used needs to be determined. The Installer tools compare file timestamps by comparing the time_t data type. Dates for each of these Enterprise Edition Components are stored in a time_t data type format.
Two-digit shortcut handling: Visual Studio Analyzer: Two-digit shortcuts are supported where the date field equals the results field. Do not confuse the date field as the input field. Application Performance Explorer: Two-digit shortcuts are supported where the date field equals the results field. Do not confuse the date field as the input field. Visual Component Manager component: Two-digit shortcuts are supported, but the date field is passed to the database for query. Therefore, this tool’s ability to interpret dates in the correct century is affected by the database used. Two-digit dates in the Microsoft Application Performance Explorer 6.0, Microsoft Visual Studio Analyzer 6.0, and Microsoft Visual Component Manager 6.0 tools pass the string to the database for querying. Therefore, the tool’s ability to interpret dates correctly is affected by the database used.
Recommended practices to develop year 2000 compliant applications:
Visual Studio Database Tools: Oracle and Visual Studio Query Designer may interpret 2-digit year dates differently When using the Visual Studio 6.0 Query Designer against an Oracle database, it is highly recommended you set your regional settings to a 4-digit year setting such as MM/DD/YYYY to prevent incorrect or unexpected results from queries that could lead to data loss. When a date is entered into the Grid Pane of the Query Designer, it is formatted according to the regional settings. Then, this reformatted date is passed to Oracle, which interprets the date string according to the server’s configuration. If the year entered into the Grid Pane’s criteria cell is from 2000 through 2029 (the system default 2-digit year window for dates 2000 and later), the date will be converted by OLEAUT32 into a 2-digit value when parsed into the SQL Pane. Oracle will interpret this as a year from 1900 through 1929. For example: A user types the date "1/1/2001" into the Grid Pane’s criteria cell. With two digit years turned on, the date is reformatted to "1/1/01." When Oracle receives the string it interprets the date "1/1/01" to be "1/1/1901." If the date is being used in the criteria for an UPDATE or DELETE query, data loss may occur. This issue is addressed in the final release of Visual Studio 6.0 Service Pack 3. Testing guidelines and recommendations: Set the system clock on a non-production system to a time like 11:50 pm Dec 31, 1999 and let it automatically roll to the year 2000 and see if the application still works as expected.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | |
Microsoft Year 2000 Resource Center
Visual Studio 6.0 (Korean)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See Below | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, Windows 98, Windows NT 4.0 Service Pack 4 plus Year 2000 software updates, Internet Explorer 4.01 Service Pack 1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock, Operating System File Date API, OLEAUT32.DLL. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 13 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This report applies to: Enterprise and Professional editions. Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes NOTE: One or more of the bundled products or components in Visual Studio 6.0 has known issues. These products are listed below under section II of "Product Details." Please refer to this section for more information. Operational Range for Data: See individual product detail for products listed below. Outlook Express 4.01 date handling: If Outlook Express (OE) 4.01 (Service Pack 1 or Service Pack 2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than 99, OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as 97, then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year 99 is received and the current year is a multiple of 100 (e.g. 2000), than the year will be interpreted as the current year plus 98 (e.g. 2098). You can find more information about this fix in the Internet Explorer (32-bit) 4.0x Year 2000 disclosure document at http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430.Prerequisites: A prerequisite refers to what is needed for a given product to reach the compliance classification indicated. It could include a software update that is required or a specific version of a related Microsoft technology that the product needs.
Product Details There are three aspects of Year 2000 compliance for Visual Studio 6.0: compliance for the individual visual tools in the suite (such as Visual Basic and Visual C++), compliance of other Microsoft Products which ship as a part of Visual Studio (such as SQL Server Developer Edition), and compliance of the suite-specific features such as Visual Studio Analyzer, Installer tools, and Visual Component Manager.
The Year 2000 status of the Visual Studio 6.0 individual tools is described below. Please refer to the individual tools and their prerequisites in the Microsoft Year 2000 website for information on compliance status as well as specific information on date handling, recommended practices, usage errors, and testing guidelines:
Visual Studio Enterprise Edition also contains these additional Microsoft Products.
Visual Studio 6.0 Enterprise Edition also includes the following third party add on components which are not included in the above test results:
Visual Studio Enterprise Edition 6.0 also contains several suite specific features. Please refer to the below for specific information on date handling, recommended practices, and testing guidelines.
How the product runtime handles dates: The Visual Studio Analyzer tool and the Application Performance Explorer convert dates to a 4-digit format, sorts them, truncates them to 2 digits, and then displays the results. The Visual Component Manager tool passes the date inputs as a string type to the database (SQL or Access). Therefore, the Year 2000 status of the database being used needs to be determined. The Installer tools compare file timestamps by comparing the time_t data type. Dates for each of these Enterprise Edition Components are stored in a time_t data type format.
Two-digit shortcut handling: Visual Studio Analyzer: Two-digit shortcuts are supported where the date field equals the results field. Do not confuse the date field as the input field. Application Performance Explorer: Two-digit shortcuts are supported where the date field equals the results field. Do not confuse the date field as the input field. Visual Component Manager component: Two-digit shortcuts are supported, but the date field is passed to the database for query. Therefore, this tool’s ability to interpret dates in the correct century is affected by the database used. Two-digit dates in the Microsoft Application Performance Explorer 6.0, Microsoft Visual Studio Analyzer 6.0, and Microsoft Visual Component Manager 6.0 tools pass the string to the database for querying. Therefore, the tool’s ability to interpret dates correctly is affected by the database used.
Recommended practices to develop year 2000 compliant applications:
Visual Studio Database Tools: Oracle and Visual Studio Query Designer may interpret 2-digit year dates differently When using the Visual Studio 6.0 Query Designer against an Oracle database, it is highly recommended you set your regional settings to a 4-digit year setting such as MM/DD/YYYY to prevent incorrect or unexpected results from queries that could lead to data loss. When a date is entered into the Grid Pane of the Query Designer, it is formatted according to the regional settings. Then, this reformatted date is passed to Oracle, which interprets the date string according to the server’s configuration. If the year entered into the Grid Pane’s criteria cell is from 2000 through 2029 (the system default 2-digit year window for dates 2000 and later), the date will be converted by OLEAUT32 into a 2-digit value when parsed into the SQL Pane. Oracle will interpret this as a year from 1900 through 1929. For example: A user types the date "1/1/2001" into the Grid Pane’s criteria cell. With two digit years turned on, the date is reformatted to "1/1/01." When Oracle receives the string it interprets the date "1/1/01" to be "1/1/1901." If the date is being used in the criteria for an UPDATE or DELETE query, data loss may occur. This issue is addressed in the final release of Visual Studio 6.0 Service Pack 3. Testing guidelines and recommendations: Set the system clock on a non-production system to a time like 11:50 pm Dec 31, 1999 and let it automatically roll to the year 2000 and see if the application still works as expected.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | |
Microsoft Year 2000 Resource Center
Visual Studio 6.0 (Spanish)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See Below | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, Windows 98, Windows NT 4.0 Service Pack 4 plus Year 2000 software updates, Internet Explorer 4.01 Service Pack 1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock, Operating System File Date API, OLEAUT32.DLL. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 13 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This report applies to: Enterprise and Professional editions. Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes NOTE: One or more of the bundled products or components in Visual Studio 6.0 has known issues. These products are listed below under section II of "Product Details." Please refer to this section for more information. Operational Range for Data: See individual product detail for products listed below. Outlook Express 4.01 date handling: If Outlook Express (OE) 4.01 (Service Pack 1 or Service Pack 2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than 99, OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as 97, then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year 99 is received and the current year is a multiple of 100 (e.g. 2000), than the year will be interpreted as the current year plus 98 (e.g. 2098). You can find more information about this fix in the Internet Explorer (32-bit) 4.0x Year 2000 disclosure document at http://www.microsoft.com/technet/year2k/product/user_list.asp?prod=1430.Prerequisites: A prerequisite refers to what is needed for a given product to reach the compliance classification indicated. It could include a software update that is required or a specific version of a related Microsoft technology that the product needs.
Product Details There are three aspects of Year 2000 compliance for Visual Studio 6.0: compliance for the individual visual tools in the suite (such as Visual Basic and Visual C++), compliance of other Microsoft Products which ship as a part of Visual Studio (such as SQL Server Developer Edition), and compliance of the suite-specific features such as Visual Studio Analyzer, Installer tools, and Visual Component Manager.
The Year 2000 status of the Visual Studio 6.0 individual tools is described below. Please refer to the individual tools and their prerequisites in the Microsoft Year 2000 website for information on compliance status as well as specific information on date handling, recommended practices, usage errors, and testing guidelines:
Visual Studio Enterprise Edition also contains these additional Microsoft Products.
Visual Studio 6.0 Enterprise Edition also includes the following third party add on components which are not included in the above test results:
Visual Studio Enterprise Edition 6.0 also contains several suite specific features. Please refer to the below for specific information on date handling, recommended practices, and testing guidelines.
How the product runtime handles dates: The Visual Studio Analyzer tool and the Application Performance Explorer convert dates to a 4-digit format, sorts them, truncates them to 2 digits, and then displays the results. The Visual Component Manager tool passes the date inputs as a string type to the database (SQL or Access). Therefore, the Year 2000 status of the database being used needs to be determined. The Installer tools compare file timestamps by comparing the time_t data type. Dates for each of these Enterprise Edition Components are stored in a time_t data type format.
Two-digit shortcut handling: Visual Studio Analyzer: Two-digit shortcuts are supported where the date field equals the results field. Do not confuse the date field as the input field. Application Performance Explorer: Two-digit shortcuts are supported where the date field equals the results field. Do not confuse the date field as the input field. Visual Component Manager component: Two-digit shortcuts are supported, but the date field is passed to the database for query. Therefore, this tool’s ability to interpret dates in the correct century is affected by the database used. Two-digit dates in the Microsoft Application Performance Explorer 6.0, Microsoft Visual Studio Analyzer 6.0, and Microsoft Visual Component Manager 6.0 tools pass the string to the database for querying. Therefore, the tool’s ability to interpret dates correctly is affected by the database used.
Recommended practices to develop year 2000 compliant applications:
Visual Studio Database Tools: Oracle and Visual Studio Query Designer may interpret 2-digit year dates differently When using the Visual Studio 6.0 Query Designer against an Oracle database, it is highly recommended you set your regional settings to a 4-digit year setting such as MM/DD/YYYY to prevent incorrect or unexpected results from queries that could lead to data loss. When a date is entered into the Grid Pane of the Query Designer, it is formatted according to the regional settings. Then, this reformatted date is passed to Oracle, which interprets the date string according to the server’s configuration. If the year entered into the Grid Pane’s criteria cell is from 2000 through 2029 (the system default 2-digit year window for dates 2000 and later), the date will be converted by OLEAUT32 into a 2-digit value when parsed into the SQL Pane. Oracle will interpret this as a year from 1900 through 1929. For example: A user types the date "1/1/2001" into the Grid Pane’s criteria cell. With two digit years turned on, the date is reformatted to "1/1/01." When Oracle receives the string it interprets the date "1/1/01" to be "1/1/1901." If the date is being used in the criteria for an UPDATE or DELETE query, data loss may occur. This issue is addressed in the final release of Visual Studio 6.0 Service Pack 3. Testing guidelines and recommendations: Set the system clock on a non-production system to a time like 11:50 pm Dec 31, 1999 and let it automatically roll to the year 2000 and see if the application still works as expected.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | |
Microsoft Year 2000 Resource Center
Visual Studio 97 (English)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4 SP4 - plus Year 2000 software updates, Windows NT 3.51 SP 5, Windows 95 OSR2, Windows 98 – plus Year 2000 software updates, Internet Explorer 3.02, SQL Server 6.5 SP55, MDAC 2.0 SP1, Scripting 1.2, FrontPage 97, Visual Studio 97 SP3 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock, Visual Basic runtime, (OLE) Automation Libraries | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 13 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This report applies to: Enterprise and Professional editions. Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes NOTE: One or more of the bundled products or components in Visual Studio 97 has known issues. Please refer to the "Products Details" section below for more information. Prerequisites: A prerequisite refers to what is needed for a given product to reach the compliance classification indicated. It could include a software update that is required or a specific version of a related Microsoft technology that the product needs.
Product Details There are two aspects of Year 2000 compliance for Visual Studio 97: compliance for the individual visual tools in the suite (such as Visual Basic 5.0 and Visual C++5.0) and, compliance of other Microsoft Products which ship as a part of Visual Studio, such as SQL Server 6.5 Developer Edition.
The Year 2000 status of the Visual Studio 6.0 individual tools is described below. Please refer to the individual tools Microsoft Year 2000 website for definitive information on compliance status as well as specific information on date handling, recommended practices, usage errors, and testing guidelines:
Visual Studio 97 Enterprise Edition also contains these additional Microsoft Products.
Please refer to Product Guides for each product for further details on:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | |
Microsoft Year 2000 Resource Center
Visual Studio 97 (French)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4 SP4 - plus Year 2000 software updates, Windows NT 3.51 SP 5, Windows 95 OSR2, Windows 98 – plus Year 2000 software updates, Internet Explorer 3.02, SQL Server 6.5 SP55, MDAC 2.0 SP1, Scripting 1.2, FrontPage 97, Visual Studio 97 SP3 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock, Visual Basic runtime, (OLE) Automation Libraries | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 13 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This report applies to: Enterprise and Professional editions. Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes NOTE: One or more of the bundled products or components in Visual Studio 97 has known issues. Please refer to the "Products Details" section below for more information. Prerequisites: A prerequisite refers to what is needed for a given product to reach the compliance classification indicated. It could include a software update that is required or a specific version of a related Microsoft technology that the product needs.
Product Details There are two aspects of Year 2000 compliance for Visual Studio 97: compliance for the individual visual tools in the suite (such as Visual Basic 5.0 and Visual C++5.0) and, compliance of other Microsoft Products which ship as a part of Visual Studio, such as SQL Server 6.5 Developer Edition.
The Year 2000 status of the Visual Studio 6.0 individual tools is described below. Please refer to the individual tools Microsoft Year 2000 website for definitive information on compliance status as well as specific information on date handling, recommended practices, usage errors, and testing guidelines:
Visual Studio 97 Enterprise Edition also contains these additional Microsoft Products.
Please refer to Product Guides for each product for further details on:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | |
Microsoft Year 2000 Resource Center
Visual Studio 97 (German)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4 SP4 - plus Year 2000 software updates, Windows NT 3.51 SP 5, Windows 95 OSR2, Windows 98 – plus Year 2000 software updates, Internet Explorer 3.02, SQL Server 6.5 SP55, MDAC 2.0 SP1, Scripting 1.2, FrontPage 97, Visual Studio 97 SP3 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock, Visual Basic runtime, (OLE) Automation Libraries | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 13 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This report applies to: Enterprise and Professional editions. Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes NOTE: One or more of the bundled products or components in Visual Studio 97 has known issues. Please refer to the "Products Details" section below for more information. Prerequisites: A prerequisite refers to what is needed for a given product to reach the compliance classification indicated. It could include a software update that is required or a specific version of a related Microsoft technology that the product needs.
Product Details There are two aspects of Year 2000 compliance for Visual Studio 97: compliance for the individual visual tools in the suite (such as Visual Basic 5.0 and Visual C++5.0) and, compliance of other Microsoft Products which ship as a part of Visual Studio, such as SQL Server 6.5 Developer Edition.
The Year 2000 status of the Visual Studio 6.0 individual tools is described below. Please refer to the individual tools Microsoft Year 2000 website for definitive information on compliance status as well as specific information on date handling, recommended practices, usage errors, and testing guidelines:
Visual Studio 97 Enterprise Edition also contains these additional Microsoft Products.
Please refer to Product Guides for each product for further details on:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | |
Microsoft Year 2000 Resource Center
Visual Studio 97 (Japanese)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4 SP4 - plus Year 2000 software updates, Windows NT 3.51 SP 5, Windows 95 OSR2, Windows 98 – plus Year 2000 software updates, Internet Explorer 3.02, SQL Server 6.5 SP55, MDAC 2.0 SP1, Scripting 1.2, FrontPage 97, Visual Studio 97 SP3 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock, Visual Basic runtime, (OLE) Automation Libraries | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 13 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This report applies to: Enterprise and Professional editions. Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes NOTE: One or more of the bundled products or components in Visual Studio 97 has known issues. Please refer to the "Products Details" section below for more information. Prerequisites: A prerequisite refers to what is needed for a given product to reach the compliance classification indicated. It could include a software update that is required or a specific version of a related Microsoft technology that the product needs.
Product Details There are two aspects of Year 2000 compliance for Visual Studio 97: compliance for the individual visual tools in the suite (such as Visual Basic 5.0 and Visual C++5.0) and, compliance of other Microsoft Products which ship as a part of Visual Studio, such as SQL Server 6.5 Developer Edition.
The Year 2000 status of the Visual Studio 6.0 individual tools is described below. Please refer to the individual tools Microsoft Year 2000 website for definitive information on compliance status as well as specific information on date handling, recommended practices, usage errors, and testing guidelines:
Visual Studio 97 Enterprise Edition also contains these additional Microsoft Products.
Please refer to Product Guides for each product for further details on:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | |
Microsoft Year 2000 Resource Center
Vizact 2000 1.0 (English)
| - | ||
| None | ||
| None | ||
| System clock for timing animations and other visual behaviors are not date dependent | ||
| 04 Nov 1999 | ||
|
How the product handles dates: Vizact does not have date dependencies, nor does it handle dates. Testing guidelines and recommendations: Primary testing consists of running timed behaviors before, during and after all | ||
| 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. | |
Microsoft Year 2000 Resource Center
Web TV Networks RTW 07/30/1999 (English)
| 01 Jan 1980 - 31 Dec 2035 | ||
| NONE | ||
| Requires a WebTV based set top box | ||
| The only clock dependency is for WebTV Network time only | ||
| 05 Oct 1999 | ||
|
How the product handles dates: The WebTV Network client displays dates in the following areas:
Dates are displayed in US English format with 4-digit years. Users do not input dates. Dates are generated by the WebTV Networks service or are embedded in WebSite pages Two-digit shortcut handling: WebTV clients do not use 2-digit year dates Validation guidelines and recommendations: Procedure: Set your system clock to any time and date that it accepts. From the client send mail or post to a news group. Download TV listings. Note that the times in mail or messages and the listings time and date are set based on the client offset from Greenwich Mean Time and the Service offset from GMT, which is based on Pacific Standard Time.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
WinCE ETK for VC++ 5.0 EP 2.0 (English)
| - | ||||||||
| None | ||||||||
| None | ||||||||
| Operating System clock and OLEAUT32 | ||||||||
| 10 May 1999 | ||||||||
|
Windows CE Embedded Toolkit for Visual C++ 5.0 EP 2.0 Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. Operational Range for Data: Original Equipment Manufacturer Dependent. How the product runtime handles dates: Windows CE stores a compressed year in the OAL (HAL) layer which is controlled by the Original Equipment Manufacturer (OEM). It is up to the OEM to store this data. Most specify a 100-year range (i.e. 1950 – 2049). Windows CE takes and returns a 4-digit year except in the OAL layer that talks directly to the hardware. External interfaces for Windows CE are 4-digit years. Common date usage errors: The OEM develops the real-time clock unless it is provided on the CPU. The OEM also implements real-time clock functions. Windows CE is dependent upon the OEM and their implementation of the OEM real-time clock APIs. The OEM is to provide the correct information in their OAL/hardware to maintain proper date handling. The documentation and sample files provided to OEMs show the OEM how to provide proper date handling. Two-digit shortcut handling: Windows CE does not have two-digit conversion logic but OLE does. OLE converts a 2-digit date to a 4-digit date using the following rules:
OLE programmatically uses 4-Digit dates. The place that this conversion is used is when an application is supplied a 2-digit string representing a year and OLE is required to interpret/convert it. The operating system itself does not rely of this conversion.
Testing guidelines and recommendations: Microsoft recommends that OEMs call GetSystemTime and SetSystemTime to ensure the system clock is correct. These APIs in turn call the OEM real-time clock functions that need to be tested for their date-handling characteristics. The testing would consist of trying to set various dates and then checking the result of these attempts. Locale Date formats for SSHORTDATE The Locale tables that ship with Windows CE 2.01 do not contain 4-digit date formats for all locales. To supplement the date formats for a locale, an OEM can supply a date format to the GetDateFormat() API or use a format specified by SLONGDATE. An OEM is not encouraged to change the locale data files but instead add a system applet to enable date format overrides. Locales not supporting 4-digit SSHORTDATE as of posting Catalan - Spain German - Switzerland German - Liechtenstein English - United Kingdom English - Australia English - Canada English - New Zealand English - Ireland English - South Africa English - Caribbean Spanish - Spain (Traditional Sort) Spanish - Mexico Spanish - Spain (Modern Sort) French - Belgium French - Canada French - Switzerland Hebrew - Israel Italian - Switzerland Dutch - Netherlands Dutch - Belgium Polish - Poland Russian - Russia Serbian - Serbia (Latin) Serbian - Serbia (Cyrillic) Albanian - Albania Indonesian - Indonesia Ukrainian - Ukraine Belarussian - Belarus Estonian - Estonia Latvian - Latvia Vietnamese - Viet Nam Basque - Spain Macedonian - Republic of Macedonia Afrikaans - South Africa Faeroese - Faeroe Islands Malay - Malaysia Malay - Brunei Darussalam
| ||||||||
| 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. | |
Microsoft Year 2000 Resource Center
WinCE ETK for VC++ 5.0 EP 2.1 (English)
| - | ||||||||
| None | ||||||||
| None | ||||||||
| Operating System clock and OLEAUT32 | ||||||||
| 10 May 1999 | ||||||||
|
Windows CE Embedded Toolkit for Visual C++ 5.0 EP 2.1 Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. Operational Range for Data: Original Equipment Manufacturer Dependent How the product runtime handles dates: Windows CE stores a compressed year in the OAL (HAL) layer which is controlled by the Original Equipment Manufacturer (OEM). It is up to the OEM to store this data. Most specify a 100-year range (i.e. 1950 – 2050). Windows CE takes and returns a 4-digit year except in the OAL layer that talks directly to the hardware. External interfaces for Windows CE are 4-digit years.
Two-digit shortcut handling: Windows CE does not have two-digit conversion logic but OLE does. OLE converts a 2-digit date to a 4-digit date using the following rules:
OLE programmatically uses 4-Digit dates. The place that this conversion is used is when an application is supplied a 2-digit string representing a year and OLE is required to interpret/convert it. The operating system itself does not rely of this conversion.
Common development errors dealing with year 2000 date issues: The OEM develops the real-time clock unless it is provided on the CPU. The OEM also implements real-time clock functions. Windows CE is dependent upon the OEM and their implementation of the OEM real-time clock APIs. The OEM is to provide the correct information in their OAL/hardware to maintain proper date handling. The documentation and sample files provided to OEMs show (the OEM) how to provide proper date handling. Testing guidelines and recommendations: Microsoft recommends that OEMs call GetSystemTime and SetSystemTime to ensure the system clock is correct. These APIs in turn call the OEM real-time clock functions that need to be tested for their date-handling characteristics. The testing would consist of trying to set various dates and then checking the result of these attempts. Locale Date formats for SSHORTDATE The Locale tables that ship with Windows CE 2.01 do not contain 4-digit date formats for all locales. To supplement the date formats for a locale, an OEM can supply a date format to the GetDateFormat() API or use a format specified by SLONGDATE. An OEM is not encouraged to change the locale data files but instead add a system applet to enable date format overrides. Locales not supporting 4-digit SSHORTDATE as of posting Catalan - Spain German - Switzerland German - Liechtenstein English - United Kingdom English - Australia English - Canada English - New Zealand English - Ireland English - South Africa English - Caribbean Spanish - Spain (Traditional Sort) Spanish - Mexico Spanish - Spain (Modern Sort) French - Belgium French - Canada French - Switzerland Hebrew - Israel Italian - Switzerland Dutch - Netherlands Dutch - Belgium Polish - Poland Russian - Russia Serbian - Serbia (Latin) Serbian - Serbia (Cyrillic) Albanian - Albania Indonesian - Indonesia Ukrainian - Ukraine Belarussian - Belarus Estonian - Estonia Latvian - Latvia Vietnamese - Viet Nam Basque - Spain Macedonian - Republic of Macedonia Afrikaans - South Africa Faeroese - Faeroe Islands Malay - Malaysia Malay - Brunei Darussalam
| ||||||||
| 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. | |
Microsoft Year 2000 Resource Center
WinCE Platform Builder 2.11 (English)
| - | ||||||||
| None | ||||||||
| OLE | ||||||||
| Operating system clock and OLEAUT32 | ||||||||
| 10 May 1999 | ||||||||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. Operational Range for Data: Original Equipment Manufacturer dependent.How the product runtime handles dates: Windows CE stores a compressed year in the OAL (HAL [Hardware Abstraction Layer]) layer that is controlled by an original equipment manufacturer (OEM). It is up to the OEM to store this data with most specifying a 100-year range (i.e. 1950 – 2049). Windows CE takes and returns a 4-digit year except in the OAL layer that talks directly to the hardware. External interfaces for Windows CE are 4-digit years. Two-digit shortcut handling: Windows CE does not have 2- to 4- digit conversion logic but OLE does. OLE converts a 2-digit date to a 4-digit date using the following rules:
OLE programmatically uses 4-digit dates. The place that this conversion is used is when an application is supplied a 2-digit string representing a year and OLE is required to convert it. The operating system itself does not rely on this conversion. Common development errors dealing with year 2000 date issues: The OEM is required to develop the real-time clock unless it is provided on the CPU. The OEM must also implement real-time clock functions. Windows CE is dependent upon the OEM and their implementation of the OEM real-time clock APIs. The OEM must provide the correct information in their OAL/hardware to maintain proper date handling. The documentation and sample files illustrate how the OEM maintains compliance. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Microsoft recommends OEMs call GetSystemTime and SetSystemTime to ensure the system clock is correct. These APIs will in turn call the OEM real-time clock functions that need to be tested for compliance. The testing would consist of trying to set various dates and then checking the result of these attempts. Locale Date formats for SSHORTDATE The Locale tables that ship with Windows CE 2.11 contain at least one 4-digit SSHORTDATE format for every locale. An OEM who chooses to add a locale should consider including at least one 4-digit SSHORTDATE format for their custom locale.
| ||||||||
| 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. | |
Microsoft Year 2000 Resource Center
WinCE Platform Builder 2.12 (English)
| 01 Jan 1970 - 31 Dec 2035 | ||||||||
| NONE | ||||||||
| Windows NT 4 Service Pack 5, Windows 2000, Windows CE 2.12 (ships in Platform Builder 2.12), Internet Explorer 4.01 Service Pack 1 | ||||||||
| system clock | ||||||||
| 29 Sep 1999 | ||||||||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes How the product runtime handles dates: Platform Builder only uses dates (other than file timestamps) in the CEC (CE component) files and catalog to indicate when the component was created. These dates are not used for calculations. File timestamps are used by the build engine to determine when components should be built. Two-digit shortcut handling: Platform Builder relies on OLE to convert 2 digit dates provided in CEC (CE component) files to 4-digit dates. OLE converts a 2-digit date to a 4-digit date using the following rules:
OLE programmatically uses 4-Digit dates. Recommendations: Microsoft recommends Platform Builder users use 4-digit dates when writing CEC fields to add components to Platform Builder’s catalog. Microsoft also recommends that developers make sure the custom OAL they implement when building a platform is Year 2000 compliant. Platform Builder 2.12 contains Windows CE OS 2.12 components. Platform Builder uses the Windows CE OS 2.12 build tools and build scripts to build images containing these components. For more details on this issue see the Windows CE OS 2.12 Year 2000 compliance statement. | ||||||||
| 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. | |
Microsoft Year 2000 Resource Center
WinCE Platform Builder 2.12 (Japanese)
| 01 Jan 1970 - 31 Dec 2035 | ||||||||
| NONE | ||||||||
| Windows NT 4 Service Pack 5, Windows 2000, Windows CE 2.12 (ships in Platform Builder 2.12), Internet Explorer 4.01 Service Pack 1 | ||||||||
| system clock | ||||||||
| 29 Sep 1999 | ||||||||
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes How the product runtime handles dates: Platform Builder only uses dates (other than file timestamps) in the CEC (CE component) files and catalog to indicate when the component was created. These dates are not used for calculations. File timestamps are used by the build engine to determine when components should be built. Two-digit shortcut handling: Platform Builder relies on OLE to convert 2 digit dates provided in CEC (CE component) files to 4-digit dates. OLE converts a 2-digit date to a 4-digit date using the following rules:
OLE programmatically uses 4-Digit dates. Recommendations: Microsoft recommends Platform Builder users use 4-digit dates when writing CEC fields to add components to Platform Builder’s catalog. Microsoft also recommends that developers make sure the custom OAL they implement when building a platform is Year 2000 compliant. Platform Builder 2.12 contains Windows CE OS 2.12 components. Platform Builder uses the Windows CE OS 2.12 build tools and build scripts to build images containing these components. For more details on this issue see the Windows CE OS 2.12 Year 2000 compliance statement. | ||||||||
| 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. | |
Microsoft Year 2000 Resource Center
WinCE Tool Kit for VJ++ 1.1 (English)
| 01 Jan 1900 - 31 Dec 2037 | ||
| NONE | ||
| Visual Studio 5.0 with Visual J++ 1.1 or Visual J++ 1.1 stand alone, Windows CE 2.0 | ||
| NONE | ||
| 10 May 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes How the product runtime handles dates: Java handles dates through several classes that are part of the standard Java class libraries. Classes include java.util.Date, java.util.Calendar, java.util.GregorianCalendar, java.util.TimeZone, and java.text.SimpleDateFormat. These classes allow for the conversion of date strings to or from fields of a record, for the formatting of strings in different locales, for date/time arithmetic, and for handling time zones throughout the world. Two-digit shortcut handling: Two-digit shortcuts are not available without explicit programmer truncation of fields or strings. For example, years are handled within the java.util.Date class as the number of years since 1900, so the year 2000 is specified as 100. Two-digit shortcuts would have to be synthesized by explicit programmer action along the lines of truncating a 4-digit string representation of a year down to 2 digits. Recommended practices to develop year 2000 compliant applications: The standard Java classes have taken year 2000 issues into consideration. Straightforward usage of java.util.Date and the other classes mentioned above will enable year 2000 compliance. Common development errors dealing with year 2000 date issues: Know and understand how java.util.Date.parse() parses strings. Some of its rules may catch the unsuspecting programmer, as numbers greater than 70 are regarded as a year number, but if it is greater than 1900, 1900 is subtracted from it. See The Java Language Specification by James Gosling, Bill Joy, and Guy Steele, Addison-Wesley, Reading: MA, 1996, pages 622 and following for more details about this primary date class and its functionality, or see your online Java references. Testing guidelines and recommendations: Inspect calls to the java.util.Date() constructor, checking its first argument which will either be the year as an integer, or a string which gets parsed by java.util.Date.parse(). In either case make sure that the above conventions are consistently adhered to.
| ||
| 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. | |
Microsoft Year 2000 Resource Center
WinCE Tool Kit for VJ++ 1.1 (Japanese)
| 01 Jan 1900 - 31 Dec 2037 | ||
| NONE | ||
| Visual Studio 5.0 with Visual J++ 1.1 or Visual J++ 1.1 stand alone, Windows CE 2.0 | ||
| NONE | ||
| 10 May 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes How the product runtime handles dates: Java handles dates through several classes that are part of the standard Java class libraries. Classes include java.util.Date, java.util.Calendar, java.util.GregorianCalendar, java.util.TimeZone, and java.text.SimpleDateFormat. These classes allow for the conversion of date strings to or from fields of a record, for the formatting of strings in different locales, for date/time arithmetic, and for handling time zones throughout the world. Two-digit shortcut handling: Two-digit shortcuts are not available without explicit programmer truncation of fields or strings. For example, years are handled within the java.util.Date class as the number of years since 1900, so the year 2000 is specified as 100. Two-digit shortcuts would have to be synthesized by explicit programmer action along the lines of truncating a 4-digit string representation of a year down to 2 digits. Recommended practices to develop year 2000 compliant applications: The standard Java classes have taken year 2000 issues into consideration. Straightforward usage of java.util.Date and the other classes mentioned above will enable year 2000 compliance. Common development errors dealing with year 2000 date issues: Know and understand how java.util.Date.parse() parses strings. Some of its rules may catch the unsuspecting programmer, as numbers greater than 70 are regarded as a year number, but if it is greater than 1900, 1900 is subtracted from it. See The Java Language Specification by James Gosling, Bill Joy, and Guy Steele, Addison-Wesley, Reading: MA, 1996, pages 622 and following for more details about this primary date class and its functionality, or see your online Java references. Testing guidelines and recommendations: Inspect calls to the java.util.Date() constructor, checking its first argument which will either be the year as an integer, or a string which gets parsed by java.util.Date.parse(). In either case make sure that the above conventions are consistently adhered to.
| ||
| 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. | |
Microsoft Year 2000 Resource Center
WinCE Toolkit for VB 5.0 1.0 (English)
| - | ||
| Visual Basic 5.0 | ||
| Windows CE operating system 2.0 or later, OLEAUT32.DLL | ||
| System Clock determines default 2-digit year interpretation rules | ||
| 10 May 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. How the product runtime handles dates: The Toolkit utilizes OLEAut32 for date handling and follows the same rules as OLEaut32. Microsoft established the default in the OLE Automation (now simply Automation) libraries as of version 2.20.4049 of OleAut32.dll. Now, a 2-digit year between 00 and 29 is interpreted as 20xx (2000 –2029) while a 2-digit year between 30 and 99 is interpreted as 19xx (1930 – 1999). The new Automation libraries provide the functionality that the Toolkit requires for date functions. Sample Code The following code displays years from 00 to 99 and displays them in a multiline text box when you click cmdConvertDate.. The code then displays the initial date entered, the full year as converted by the defaults native to the Toolkit. Option Explicit Private Sub cmdConvertDate_Click() Dim inyear Dim iyear Dim txtdate Dim vbcrlf Dim a vbcrlf = Chr(13) & Chr(10) For inyear = 0 To 99 If inyear <= 9 Then iyear = "0" + CStr(inyear) Else iyear = CStr(inyear) End If txtdate = "01/01/" + iyear If IsDate(txtdate) Then a = Year(txtdate) Text1.Text = Text1.Text & "Date Entered: " & txtdate & _ " Year (VB Default): " & a & vbcrlf End If Next End Sub | ||
| 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. | |
Microsoft Year 2000 Resource Center
WinCE Toolkit for VB 5.0 1.0 (Japanese)
| - | ||
| Visual Basic 5.0 | ||
| Windows CE operating system 2.0 or later, OLEAUT32.DLL | ||
| System Clock determines default 2-digit year interpretation rules | ||
| 13 Sep 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. How the product runtime handles dates: The Toolkit utilizes OLEAut32 for date handling and follows the same rules as OLEaut32. Microsoft established the default in the OLE Automation (now simply Automation) libraries as of version 2.20.4049 of OleAut32.dll. Now, a 2-digit year between 00 and 29 is interpreted as 20xx (2000 –2029) while a 2-digit year between 30 and 99 is interpreted as 19xx (1930 – 1999). The new Automation libraries provide the functionality that the Toolkit requires for date functions. Sample Code The following code displays years from 00 to 99 and displays them in a multiline text box when you click cmdConvertDate.. The code then displays the initial date entered, the full year as converted by the defaults native to the Toolkit. Option Explicit Private Sub cmdConvertDate_Click() Dim inyear Dim iyear Dim txtdate Dim vbcrlf Dim a vbcrlf = Chr(13) & Chr(10) For inyear = 0 To 99 If inyear <= 9 Then iyear = "0" + CStr(inyear) Else iyear = CStr(inyear) End If txtdate = "01/01/" + iyear If IsDate(txtdate) Then a = Year(txtdate) Text1.Text = Text1.Text & "Date Entered: " & txtdate & _ " Year (VB Default): " & a & vbcrlf End If Next End Sub | ||
| 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. | |
Microsoft Year 2000 Resource Center
WinCE Toolkit for VB 6.0 1.0 (English)
| - | ||
| None | ||
| Microsoft Internet Explorer 4.01 Service Pack 1 | ||
| Operating System Clock and Oleaut32.dll | ||
| 08 Jul 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. Operational Range for Data: As per Oleaut32How the product runtime handles dates: The Toolkit utilizes OLEAut32 for date handling and follows the same rules as OLEaut32. Microsoft established the default in the OLE Automation (now simply Automation) libraries as of version 2.20.4049 of OleAut32.dll. Now, a 2-digit year between 00 and 29 is interpreted as 20xx (2000-2029) while a 2-digit year between 30 and 99 is interpreted as 19xx (1930-1999). The new Automation libraries provide the functionality that the Toolkit requires for date functions. Note on Internet Explorer 4.01 Service Pack 1: If Outlook Express (OE) 4.01 (Service Pack 1 or Service Pack 2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than 99, OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as 97, then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year 99 is received and the current year is a multiple of 100 (e.g. 2000), then the year will be interpreted as the current year plus 98 (e.g. 2098). You can find more information about this software update in the Internet Explorer (32-bit) 4.0x Year 2000 disclosure document.
Sample Code The following code displays years from 00 to 99 and displays them in a multiline text box when you click cmdConvertDate. The code then displays the initial date entered, the full year as converted by the defaults native to the Toolkit. Option Explicit Private Sub cmdConvertDate_Click() Dim inyear Dim iyear Dim txtdate Dim vbcrlf Dim a vbcrlf = Chr(13) & Chr(10) For inyear = 0 To 99 If inyear <= 9 Then iyear = "0" + CStr(inyear) Else iyear = CStr(inyear) End If txtdate = "01/01/" + iyear If IsDate(txtdate) Then a = Year(txtdate) Text1.Text = Text1.Text & "Date Entered: " & txtdate & _ " Year (VB Default): " & a & vbcrlf End If Next End Sub
| ||
| 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. | |
Microsoft Year 2000 Resource Center
WinCE Toolkit for VB 6.0 1.0 (Japanese)
| - | ||
| None | ||
| Microsoft Internet Explorer 4.01 Service Pack 1 | ||
| Operating System Clock and Oleaut32.dll | ||
| 13 Sep 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. Operational Range for Data: As per Oleaut32How the product runtime handles dates: The Toolkit utilizes OLEAut32 for date handling and follows the same rules as OLEaut32. Microsoft established the default in the OLE Automation (now simply Automation) libraries as of version 2.20.4049 of OleAut32.dll. Now, a 2-digit year between 00 and 29 is interpreted as 20xx (2000-2029) while a 2-digit year between 30 and 99 is interpreted as 19xx (1930-1999). The new Automation libraries provide the functionality that the Toolkit requires for date functions. Note on Internet Explorer 4.01 Service Pack 1: If Outlook Express (OE) 4.01 (Service Pack 1 or Service Pack 2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than 99, OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as 97, then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year 99 is received and the current year is a multiple of 100 (e.g. 2000), then the year will be interpreted as the current year plus 98 (e.g. 2098). You can find more information about this software update in the Internet Explorer (32-bit) 4.0x Year 2000 disclosure document.
Sample Code The following code displays years from 00 to 99 and displays them in a multiline text box when you click cmdConvertDate. The code then displays the initial date entered, the full year as converted by the defaults native to the Toolkit. Option Explicit Private Sub cmdConvertDate_Click() Dim inyear Dim iyear Dim txtdate Dim vbcrlf Dim a vbcrlf = Chr(13) & Chr(10) For inyear = 0 To 99 If inyear <= 9 Then iyear = "0" + CStr(inyear) Else iyear = CStr(inyear) End If txtdate = "01/01/" + iyear If IsDate(txtdate) Then a = Year(txtdate) Text1.Text = Text1.Text & "Date Entered: " & txtdate & _ " Year (VB Default): " & a & vbcrlf End If Next End Sub
| ||
| 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. | |
Microsoft Year 2000 Resource Center
WinCE Toolkit for VC++ 5.0 5.0 (English)
| - | ||
| None | ||
| Windows CE operating system 2.0 | ||
| System Clock | ||
| 10 May 1999 | ||
|
Windows CE Toolkit for Visual C++ 5.0 Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: Depends on Windows CE Operating System. How the product runtime handles dates: This development tool can create applications that call the Windows CE Operating System date application programming interfaces (APIs). Visual C++ 5.0 for Windows CE handles dates as expected through a range of clock dates between 1970 and 2037. Leap years are handled properly, and function is provided to 2037 without issue. Two-digit shortcut handling: Two-digit shortcuts, if desired, must be implemented by the programmer using this development tool. Recommended practices to develop year 2000 compliant applications: The only known Year 2000 issue is that the standard C library time.h is not supported in this release. These time APIs are planned to be supported in a future release; in the meantime the programmer should use the standard Windows CE APIs for handling dates. These APIs and their year 2000 compliance are documented separately for each Windows CE Operating System release. Common development errors dealing with year 2000 date issues: A programmer may create date fields using this product and may be assuming 2-digit year fields to be 19XX. Programmers are advised to review such code. | ||
| 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. | |
Microsoft Year 2000 Resource Center
WinCE Toolkit for VC++ 5.0 5.0 (Japanese)
| - | ||
| None | ||
| Windows CE operating system 2.0 | ||
| System Clock | ||
| 13 Sep 1999 | ||
|
Windows CE Toolkit for Visual C++ 5.0 Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: Depends on Windows CE Operating System. How the product runtime handles dates: This development tool can create applications that call the Windows CE Operating System date application programming interfaces (APIs). Visual C++ 5.0 for Windows CE handles dates as expected through a range of clock dates between 1970 and 2037. Leap years are handled properly, and function is provided to 2037 without issue. Two-digit shortcut handling: Two-digit shortcuts, if desired, must be implemented by the programmer using this development tool. Recommended practices to develop year 2000 compliant applications: The only known Year 2000 issue is that the standard C library time.h is not supported in this release. These time APIs are planned to be supported in a future release; in the meantime the programmer should use the standard Windows CE APIs for handling dates. These APIs and their year 2000 compliance are documented separately for each Windows CE Operating System release. Common development errors dealing with year 2000 date issues: A programmer may create date fields using this product and may be assuming 2-digit year fields to be 19XX. Programmers are advised to review such code. | ||
| 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. | |
Microsoft Year 2000 Resource Center
WinCE Toolkit for VC++ 6.0 (English)
| - | ||
| None | ||
| Windows CE operating system 2.11, Microsoft Internet Explorer 4.01 Service Pack 1 | ||
| System Clock | ||
| 14 Sep 1999 | ||
|
Windows CE Toolkit for Visual C++ 6.0 Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: Depends upon Windows CE Operating System How the product runtime handles dates: This development tool can create applications that call the Windows CE Operating System date application programming interfaces (APIs). Visual C++ 6.0 for Windows CE handles dates through the range of clock dates between 1970 and 2037. Leap years are handled properly, and the product functions with dates to 2037 without issue. Two-digit shortcut handling: Two-digit shortcuts, if desired, must be totally implemented by the programmer using this development tool. Note on Internet Explorer 4.01 Service Pack 1: If Outlook Express (OE) 4.01 (Service Pack 1 or Service Pack 2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than 99, OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as 97, then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year 99 is received and the current year is a multiple of 100 (e.g. 2000), then the year will be interpreted as the current year plus 98 (e.g. 2098). You can find more information about this software update in the Internet Explorer (32-bit) 4.0x Year 2000 disclosure document.Recommended practices to develop year 2000 compliant applications: The only known Year 2000 issue is that the standard C library time.h is not supported in this release. These time APIs are planned to be supported in a future release; in the meantime the programmer should use the standard Windows CE APIs for handling dates. These APIs and their year 2000 compliance are documented separately for each Windows CE Operating System release. Common development errors dealing with year 2000 date issues: A programmer may create date fields using this product and may be assuming 2-digit year fields to be 19XX. Programmers are advised to review such code. | ||
| 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. | |
Microsoft Year 2000 Resource Center
WinCE Toolkit for VC++ 6.0 (Japanese)
| - | ||
| None | ||
| Windows CE operating system 2.11, Microsoft Internet Explorer 4.01 Service Pack 1 | ||
| System Clock | ||
| 13 Sep 1999 | ||
|
Windows CE Toolkit for Visual C++ 6.0 Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: Depends upon Windows CE Operating System How the product runtime handles dates: This development tool can create applications that call the Windows CE Operating System date application programming interfaces (APIs). Visual C++ 6.0 for Windows CE handles dates through the range of clock dates between 1970 and 2037. Leap years are handled properly, and the product functions with dates to 2037 without issue. Two-digit shortcut handling: Two-digit shortcuts, if desired, must be totally implemented by the programmer using this development tool. Note on Internet Explorer 4.01 Service Pack 1: If Outlook Express (OE) 4.01 (Service Pack 1 or Service Pack 2) receives an IMAP mail message or a News message with a 2-digit year as the sent date, the date can be misinterpreted under certain conditions. If the 2-digit year is anything other than 99, OE will assume the century value is the same as the current century. If the current year is 2000, and a 2-digit date is received as 97, then the year will be interpreted as 2097. However, there is one special case when different logic is applied. If the 2-digit year 99 is received and the current year is a multiple of 100 (e.g. 2000), then the year will be interpreted as the current year plus 98 (e.g. 2098). You can find more information about this software update in the Internet Explorer (32-bit) 4.0x Year 2000 disclosure document.Recommended practices to develop year 2000 compliant applications: The only known Year 2000 issue is that the standard C library time.h is not supported in this release. These time APIs are planned to be supported in a future release; in the meantime the programmer should use the standard Windows CE APIs for handling dates. These APIs and their year 2000 compliance are documented separately for each Windows CE Operating System release. Common development errors dealing with year 2000 date issues: A programmer may create date fields using this product and may be assuming 2-digit year fields to be 19XX. Programmers are advised to review such code. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (Arabic)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 18 May 1999 | ||
|
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980.2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (Chinese - Traditional)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (Czech)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (Danish)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (Dutch)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (English)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 21 Jun 1999 | ||
|
Updates- There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (Finnish)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (French)
| 01 Jan 1980 - 31 Dec 2035 | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (German)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MSDOS 6.22 | ||
| System Clock | ||
| 21 Jun 1999 | ||
|
Updates- There is an updated version of WINFILE.EXE. For more information see Knowledge Base article at http://www.microsoft.com/intlkb/germany/support/kb/d34/d34669.htm.This update does not address all of the issues listed in the Product Deviations section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (Greek)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 18 May 1999 | ||
|
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980.2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (Hebrew)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 18 May 1999 | ||
|
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980.2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (Hungarian)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (Italian)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (Japanese)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 21 Jun 1999 | ||
|
Prerequisites: Updated version of WINFILE.EXE. For more information see below link.DOS/V user Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOSÒ file system API’s are an exception. MS-DOSÒ file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOSÒ API the program must add 1980.2-digit shortcut handling: This is a function of the underlying MS-DOS Ò operating system.More information on MS-DOS Ò Ò issues:
The MS-DOS Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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 white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm for further information.Testing guidelines and recommendations: Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (Korean)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (Norwegian)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (Pan-European)
| 04 Jan 1980 - 31 Dec 2035 | ||
| None | ||
| MSDOS 6.22 | ||
| System Clock | ||
| 18 May 1999 | ||
|
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980.2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (Polish)
| 04 Jan 1980 - 31 Dec 2035 | ||
| none | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (Portuguese (Brazil))
| 04 Jan 1980 - 31 Dec 2035 | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (Portuguese)
| 04 Jan 1980 - 31 Dec 2035 | ||
| none | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 18 May 1999 | ||
|
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980.2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (Russian)
| 04 Jan 1980 - 31 Dec 2035 | ||
| none | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (Spanish)
| 04 Jan 1980 - 31 Dec 2035 | ||
| none | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (Swedish)
| 04 Jan 1980 - 31 Dec 2035 | ||
| none | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.1 (Thai)
| 04 Jan 1980 - 31 Dec 2035 | ||
| none | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 18 May 1999 | ||
|
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980.2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.11 (Canadian French)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MS DOS 6.22 | ||
| System clock | ||
| 18 Jun 1999 | ||
|
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980.2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.11 (Chinese - Traditional)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MS DOS 6.22 | ||
| System clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.11 (Czech)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MS DOS 6.22 | ||
| System clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.11 (Danish)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MS DOS 6.22 | ||
| System clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.11 (Dutch)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MS DOS 6.22 | ||
| System clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.11 (English)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MS DOS 6.22 | ||
| System clock | ||
| 21 Jun 1999 | ||
|
Updates- There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557This update does not address all of the issues listed in the Product Issues section below. Windows 3.11 remains Compliant# with or without this update. Description of how the product handles dates: Storage: All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.11 (Finnish)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MS DOS 6.22 | ||
| System clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.11 (French)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MS DOS 6.22 | ||
| System clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.11 (German)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MSDOS 6.22 | ||
| System Clock | ||
| 21 Jun 1999 | ||
|
Updates- There is an updated version of WINFILE.EXE. For more information see Knowledge Base article at http://www.microsoft.com/intlkb/germany/support/kb/d34/d34669.htm.This update does not address all of the issues listed in the Product Deviations section below. Windows 3.11 remains Compliant# with or without this update. Description of how the product handles dates: Storage: All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.11 (Greek)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MS DOS 6.22 | ||
| System clock | ||
| 18 Jun 1999 | ||
|
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980.2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.11 (Hungarian)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MS DOS 6.22 | ||
| System clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.11 (Italian)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MS DOS 6.22 | ||
| System clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.11 (Norwegian)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MS DOS 6.22 | ||
| System clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.11 (Polish)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MS DOS 6.22 | ||
| System clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.11 (Portuguese)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MS DOS 6.22 | ||
| System clock | ||
| 18 Jun 1999 | ||
|
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980.2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.11 (Russian)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MS DOS 6.22 | ||
| System clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.11 (Spanish)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MS DOS 6.22 | ||
| System clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.11 (Swedish)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MS DOS 6.22 | ||
| System clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.11 (Thai)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MS DOS 6.22 | ||
| System clock | ||
| 18 Jun 1999 | ||
|
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980.2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.11 (Turkish)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MS DOS 6.22 | ||
| System clock | ||
| 16 Nov 1999 | ||
|
Updates: There is an updated version of WINFILE.EXE. For more information see Knowledge Base article Q85557.This update does not address all of the issues listed in the Product Issues section below. Windows 3.1 remains Compliant# with or without this update. Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980. 2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance acceptable deviations: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 3.2 (Chinese - Simplified)
| 04 Jan 1980 - 31 Dec 2035 | ||
| MSDOS 5.0 or later | ||
| System Clock | ||
| 12 Mar 1999 | ||
|
Description of how the product handles dates: Storage. All dates are stored internally as 4-digit dates. MS-DOS® file system API’s are an exception. MS-DOS® file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS® API the program must add 1980.2-digit shortcut handling: This is a function of the underlying MS-DOS® operating system. More information on MS-DOS® issues:
The MS-DOS® DATE command is the only OS command that accepts dates––the Date/Time property within Windows uses a graphical interface. See the note above for the 2-digit logic. Also, since the MS-DOS® file system API’s return a year offset from 1980, the programmer has to add 1980 to the date value returned to get the correct date. Product compliance minor issues: The date cannot be set to 02-29-2000 in the DATE/TIME control panel applet using the mouse. To work around this issue, use the keyboard to set the date on 02-29 of the year 2000. Note that the system does roll over to February 29 correctly. If the user does not touch the date/time control panel applet on the February 29, 2000, the machine will have the correct time and date. Recommendations: Microsoft is investigating the Date/Time control panel issue. No fix is available at this time. Common date usage errors: Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If 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. Testing guidelines and recommendations: Please see the white paper on Windows Operating System Interactions with BIOS and Real Time Clock at http://www.microsoft.com/technet/year2k/white/rtbios/rtbios1.htm.Contact the vendors of all applications designed to run on Windows 3.1 to obtain information concerning the Year 2000 compliance status of the applications when run on Windows 3.1. | ||
| 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. | |
Microsoft Year 2000 Resource Center
Windows 95 4.00.950 (Basque)
| 01 Jan 1980 - 31 Dec 2035 | |||
| Windows 95 year 2000 Software Update | |||
| PC BIOS | |||
| 12 Nov 1999 | |||
|
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.To learn how to check your version of Windows 95, see our Knowledge Base article from our Microsoft Support site - Q158238.Microsoft has released a software update for Windows 95 that addresses the known issues described below. To download, please click Windows 95 year 2000 software update.To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International.Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here.How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command 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" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings in the Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to use 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows:
COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. The fix moves the 2-digit year cutoff from 1999 to 2029.XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing 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 article in the white paper section of this product guide for further information. | |||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows 95 4.00.950 (Canadian French)
| 01 Jan 1980 - 31 Dec 2035 | |||
| Windows 95 Year 2000 Software Update | |||
| None | |||
| PC BIOS | |||
| 12 Nov 1999 | |||
|
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.To learn how to check your version of Windows 95, see our Knowledge Base article from our Microsoft Support site - Q158238.Microsoft has released a software update for Windows 95 that addresses the known issues described below. To download, please click Windows 95 year 2000 software update.To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International.Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here.How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command 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" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings in the Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to use 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows:
COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. The fix moves the 2-digit year cutoff from 1999 to 2029.XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing 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 article in the white paper section of this product guide for further information. | |||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows 95 4.00.950 (Catalan)
| 01 Jan 1980 - 31 Dec 2035 | |||
| Windows 95 year 2000 Software Update | |||
| PC Bios | |||
| 12 Nov 1999 | |||
|
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.To learn how to check your version of Windows 95, see our Knowledge Base article from our Microsoft Support site - Q158238.Microsoft has released a software update for Windows 95 that addresses the known issues described below. To download, please click Windows 95 year 2000 software update.To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International.Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here.How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command 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" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings in the Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to use 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows:
COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. The fix moves the 2-digit year cutoff from 1999 to 2029.XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing 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 article in the white paper section of this product guide for further information. | |||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows 95 4.00.950 (Chinese - Simplified)
| 01 Jan 1980 - 31 Dec 2035 | ||
| Windows 95 Year 2000 Software Update | ||
| None | ||
| PC BIOS | ||
| 12 Nov 1999 | ||
|
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.To learn how to check your version of Windows 95, see Knowledge Base article from Microsoft's Support site - Q158238.Product Details: Microsoft has released a software update for Windows 95 that addresses the issues described below. To download the Windows 95 year 2000 Software Update, please click here.To receive the Year 2000 Resource Center CD from Microsoft that will include this update, please click here, or in the US call 1-888-MSFT Y2k.Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for information on the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here.Additional Information Windows 95 Year 2000 Update may not update VDHCP.386. If the Dial Up Networking 1.3 or the Winsock2 Updates for Windows 95 have been installed on the Windows 95 machine prior to installing Windows 95 year 2000 Software Update, the Windows 95 year 2000 Software Update will not update VDHCP.386. For more information, please see the Knowledge Base Article To determine if you have either Dial Up Networking or Winsock installed, check Control Panel/ Add/Remove Programs. If either update has been installed, it will be on the list of installed products. The year 2000 software update for Dial Up Networking 1.3 and Winsock 2 is available at Dial Up Networking 1.3 and Winsock 2 Year 2000 Update.
Corporate Customers A Windows 95 Corporate Year 2000 Companion is available for corporations to address Year 2000 Update deployment issues and to ease administration. This Corporate Year 2000 Companion is recommended for corporate customers after they have installed the Windows 95 year 2000 update released in April 1999. The Corporate Year 2000 Companion incorporates: 1) deployment and maintenance features requested by corporate customers, and 2) the Dial Up Networking 1.3 and Winsock 2 year 2000 software update. An English version is available at Windows 95 Corporate Year 2000 Companion.To determine which Year 2000 updates have been applied to your Windows 95 system, install the Windows 95 Corporate Companion available from the Windows 95 download site or Windows Update. Run the Update Information Tool (QFECHECK.EXE) that is installed with the Corporate Companion to view which Y2K updates are deployed on the system. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command 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" message. This issue is fixed (see below) by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings from Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows:
COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. This fix moves the 2-digit year cutoff from 1999 to 2029.XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Software Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing 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 article in the white paper section of this product guide for further information.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows 95 4.00.950 (Chinese - Traditional)
| 01 Jan 1980 - 31 Dec 2035 | ||
| Windows 95 Year 2000 Software Update | ||
| None | ||
| PC BIOS | ||
| 12 Nov 1999 | ||
|
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.To learn how to check your version of Windows 95, see Knowledge Base article from Microsoft's Support site - Q158238.Product Details: Microsoft has released a software update for Windows 95 that addresses the issues described below. To download the Windows 95 year 2000 Software Update, please click here.To receive the Year 2000 Resource Center CD from Microsoft that will include this update, please click here, or in the US call 1-888-MSFT Y2k.Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for information on the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here.Additional Information Windows 95 Year 2000 Update may not update VDHCP.386. If the Dial Up Networking 1.3 or the Winsock2 Updates for Windows 95 have been installed on the Windows 95 machine prior to installing Windows 95 year 2000 Software Update, the Windows 95 year 2000 Software Update will not update VDHCP.386. For more information, please see the Knowledge Base Article To determine if you have either Dial Up Networking or Winsock installed, check Control Panel/ Add/Remove Programs. If either update has been installed, it will be on the list of installed products. The year 2000 software update for Dial Up Networking 1.3 and Winsock 2 is available at Dial Up Networking 1.3 and Winsock 2 Year 2000 Update.
Corporate Customers A Windows 95 Corporate Year 2000 Companion is available for corporations to address Year 2000 Update deployment issues and to ease administration. This Corporate Year 2000 Companion is recommended for corporate customers after they have installed the Windows 95 year 2000 update released in April 1999. The Corporate Year 2000 Companion incorporates: 1) deployment and maintenance features requested by corporate customers, and 2) the Dial Up Networking 1.3 and Winsock 2 year 2000 software update. An English version is available at Windows 95 Corporate Year 2000 Companion.To determine which Year 2000 updates have been applied to your Windows 95 system, install the Windows 95 Corporate Companion available from the Windows 95 download site or Windows Update. Run the Update Information Tool (QFECHECK.EXE) that is installed with the Corporate Companion to view which Y2K updates are deployed on the system. How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command 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" message. This issue is fixed (see below) by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings from Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows:
COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. This fix moves the 2-digit year cutoff from 1999 to 2029.XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Software Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing 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 article in the white paper section of this product guide for further information.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows 95 4.00.950 (Czech)
| 01 Jan 1980 - 31 Dec 2035 | |||
| Windows 95 year 2000 software update | |||
| None | |||
| PC BIOS | |||
| 12 Nov 1999 | |||
|
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.To learn how to check your version of Windows 95, see our Knowledge Base article from our Microsoft Support site - Q158238.Microsoft has released a software update for Windows 95 that addresses the known issues described below. To download, please click Windows 95 year 2000 software update.To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International.Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here.How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command 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" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings in the Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to use 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows:
COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. The fix moves the 2-digit year cutoff from 1999 to 2029.XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing 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 article in the white paper section of this product guide for further information. | |||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Windows 95 4.00.950 (Danish)
| 01 Jan 1980 - 31 Dec 2035 | |||
| Windows 95 Year 2000 Update | |||
| None | |||
| PC BIOS | |||
| 12 Nov 1999 | |||
|
Product Details Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Windows 95 version 4.00.950 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.To learn how to check your version of Windows 95, see our Knowledge Base article from our Microsoft Support site - Q158238.Microsoft has released a software update for Windows 95 that addresses the known issues described below. To download, please click Windows 95 year 2000 software update.To receive the Year 2000 Resource Center CD from Microsoft, please contact your local subsidiary. For local contact information please check Microsoft International.Windows 95 shipped with various versions of Internet Explorer. Microsoft recommends using Internet Explorer 4.01 Service Pack 2 or greater, including any software updates which are applicable. Please check the Year 2000 Product Guide for the version of Internet Explorer you have. If you are unsure which version of Internet Explorer you are using click here.How the product handles dates: Storage. Dates are stored internally as 4-digit dates. MS-DOS file system APIs are an exception. MS-DOS file system APIs use a year offset from 1980 to store dates. When a program gets a date from an MS-DOS API the program must add 1980. Two-digit shortcut handling: MS-DOS DATE command 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" message. This issue is fixed by the updated version of COMMAND.COM. Also, the MS-DOS file system APIs return a year offset from 1980. The programmer has to add 1980 to the date value returned to get the appropriate date. Win32 APIs are not affected by this. Product Issues resolved in the Windows 95 year 2000 Software Update: SHELL32.DLL - The "Find Files or Folders" Dialog Date tab displays the year in YY format. This format results in non-numeric displays for years greater than 2000. For example, entering 03/20/2003 will display as 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. COMCTL32.DLL – When Regional Settings in the Control Panel is set to use two digits for years, the Date/Time Picker function may not display the proper date. To ensure proper display of dates: set Regional Settings to use 4-digit date display. WINFILE.EXE - Windows File Manager does not display or sort dates beyond the year 2000 appropriately. When using Windows File Manager to view the contents of folders, and users have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows:
COMMAND.COM - The DATE command (internal to COMMAND.COM) does not appropriately handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the message "Invalid Date". VDHCP.386 – Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as having been obtained the previous day. The system date is displayed correctly but the DHCP client reports an incorrect date. TIMEDATE.CPL –Time and Date control applet - When the date is set to February 29 the applet will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back. DIALER.EXE - Phone Dialer applet - The Show Call log option doesn’t display the date correctly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the log date will display as 100, 101, 102, etc. MFC40.DLL and MFC40U.DLL: Programs using one of these DLLs to represent dates may interpret a year 2000 or later dates incorrectly. For example, 02/05/2000 may get represented as 02/05/100. Microsoft has updated these DLL's to prevent this from happening. Software Developers using MFC can get more information from the MFC40.DLL compliance document. Microsoft Visual C++ Runtime library files Applications that utilize these runtime libraries may behave as if current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem would reoccur any year the first of April fell on a Sunday. For more information on this issue, please see OLE Automation - The Microsoft Automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current 2-digit year cutoff is 1999. This means that 2-digit years beginning with 00 will be interpreted as being in the 1900s, i.e. 1/1/00 is converted to 1/1/1900, irrespective of the user’s century window settings in Control Panel\Regional Settings\Date tab. The fix moves the 2-digit year cutoff from 1999 to 2029.XCOPY.EXE – When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as 2 digits except for the years 80 - 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) 2-digit dates are accepted but are recognized as being within the 1900s (02/05/01 is seen as 02/05/1901). Testing guidelines and recommendations: Microsoft Jet Database Engine 3.0 and Microsoft Office 95 When you try to synchronize two members of a replica set that was created before the year 2000, and the current date on your computer is after the year 2000, a synchronization message might appear. This is because of how the expression service mishandles date entries in the MSysExchangeLog table in replicas. When a replica set created before the year 2000 is compacted after the year 2000, exchange information relating to synchronizations after the year 2000 is deleted from the MSysExchangeLog table. After this information is deleted, the generation information in the MSysExchangeLog table and the MSysGenHistory table does not match, and the replicas cannot be synchronized. To resolve this issue, download the latest Microsoft Office 95 Year 2000 Update from the Microsoft Web site at http://www.officeupdate.microsoft.com/ Some PCs reset the system date to 1980 or other invalid dates when the computer reaches the year 2000. This problem is created by flaws in the computer hardware and in low-level BIOS software provided by other vendors. If users are going to test for this error, Microsoft recommends executing 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 article in the white paper section of this product guide for further information. | |||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Itemized List of products in each Volume
|
ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFT'S YEAR 2000 WEBSITE LOCATED AT http://microsoft.com/year2000/ (the "Y2K WEBSITE"). EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED PURSUANT TO THE TERMS HEREOF, THE TERMS OF THE Y2K WEBSITE, AND THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT FOR THE SOLE PURPOSE OF ASSISTING THE PLANNING FOR THE TRANSITION TO THE YEAR 2000. EACH MICROSOFT YEAR 2000 STATEMENT CONTAINS INFORMATION CURRENTLY AVAILABLE AND IS UPDATED REGULARLY AND SUBJECT TO CHANGE. MICROSOFT THEREFORE RECOMMENDS THAT YOU CHECK THE Y2K WEBSITE REGULARLY FOR ANY CHANGES TO ANY MICROSOFT YEAR 2000 STATEMENT. EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. CONSEQUENTLY, MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, MICROSOFT DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF ANY MICROSOFT YEAR 2000 STATEMENT IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY MICROSOFT OR ITS AUTHORIZED REPRESENTATIVES SHALL CREATE A WARRANTY OR IN ANY WAY DECREASE THE SCOPE OF THIS WARRANTY DISCLAIMER. IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER REGARDING ANY MICROSOFT YEAR 2000 STATEMENT INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, PUNITIVE OR SPECIAL DAMAGES, EVEN IF MICROSOFT OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE FOREGOING LIMITATION MAY NOT APPLY TO YOU. THE INFORMATION CONTAINED IN EACH MICROSOFT YEAR 2000 STATEMENT IS FOUND AT THE Y2K WEBSITE AND IS INTENDED TO BE READ IN CONJUNCTION WITH OTHER INFORMATION LOCATED AT THE Y2K WEBSITE, INCLUDING BUT NOT LIMITED TO MICROSOFT'S YEAR 2000 COMPLIANCE STATEMENT, THE DESCRIPTION OF THE CATEGORIES OF COMPLIANCE INTO WHICH MICROSOFT HAS CLASSIFIED ITS PRODUCTS IN ITS YEAR 2000 PRODUCT GUIDE, AND THE MICROSOFT YEAR 2000 TEST CRITERIA. ANY MICROSOFT YEAR 2000 STATEMENTS MADE TO YOU IN THE COURSE OF PROVIDING YEAR 2000 RELATED UPDATES, YEAR 2000 DIAGNOSTIC TOOLS, OR REMEDIATION SERVICES (IF ANY) ARE SUBJECT TO THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT (112 STAT. 2386). IN CASE OF A DISPUTE, THIS ACT MAY REDUCE YOUR LEGAL RIGHTS REGARDING THE USE OF ANY SUCH STATEMENTS, UNLESS OTHERWISE SPECIFIED BY YOUR CONTRACT OR TARIFF.
|
||
|
Wednesday, November 17, 1999 © 1999 Microsoft Corporation. All rights reserved. Terms of use. This site is being designated as a Year 2000 Readiness Disclosure and the information contained herein is provided pursuant to the terms hereof and the Year 2000 Information and Readiness Disclosure Act.  | ||