| Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| Y2K Readiness - Software
The software components of your PC environment include the operating systems, "shrink-wrapped" applications and "custom-built" applications. Each system offers unique challenges in assessing and remediating Y2K issues.
| Operating Systems |
 |
| Overview
Your operating system is the master control program that runs your computer. Operating systems are essential to all computer systems because they establish execution standards for every application program run on the system. DonÆt assume that because your hardware is Year 2000 compliant that your operating or network operating systems are also compliant. Each of these systems needs a thorough, individual assessment to determine if it is Year 2000 ready. Non-compliant operating systems may need to be fixed or replaced to ensure that they accurately reset their own date each time the system is restarted.
Tips
- Microsoft operating systems store and manipulate dates consistent with four-digit year formats, and their system clocks have been designed to recognize the Year 2000 as a leap year. Within the operating system, the file systems have been designed to handle dates beyond the Year 2000.
- The Windows NT Server 4.0 and some version of additional NT Server features have known Year 2000 issues. To make them Year 2000 compliant we suggest employing Windows NT4.0 Service Pack 4 (SP4) plus updates or Service Pack 5 (SP5) plus updates.
- In Windows 3.1 you cannot reset the DATE/TIME control panel applet to 02.29.2000 using a mouse. You must use the keyboard to set the date. For more information see this Product Guide page.
In addition to your computer operating system you may be using other system software, such as database management software, Internet services and system management utilities. All of these system software types interact with hardware and applications, so it is critical that they are Year 2000 compliant.
Some steps to consider:
- Determine the Year 2000 readiness of the version or releases of the installed system software.
- Determine migration alternatives for products that arenÆt Year 2000 readyùfix or replace.
- Secure and apply software corrections and replace those that need replacement with Year 2000 ready versions.
Additional Resources
For more information on the Year 2000 readiness of Microsoft operating systems, see the Product Guides.
To scan your system for the compliance of Microsoft products select the Microsoft Year 2000 Product Analyzer
For more information and download of an updated version of WINFILE.EXE for Windows 3.1, 3.11, see the Knowledge Base article.
Tools
Below is a list of Year 2000 remediation tools, with links to the companies that may be able to assist you in your Year 2000 remediation efforts. The tools listed on this site do not indicate an endorsement or recommendation on the part of Microsoft for the manufacturers, their products or the underlying technologies being used. You will need to do your own assessment to determine if the tools offered meet your needs. For information regarding these companies or their Year 2000 solutions, please contact the companies directly.
Operating Systems
Scan and analyze Microsoft and other vendorÆs operating systems.
| "Shrink-wrapped" Applications |
|
| Overview
The term "shrink-wrapped application" refers to any off-the-shelf, packaged software program designed to enable users to carry out a specific task or function. Word processors, spreadsheets, graphics programs and database managers are examples of applications.
The Year 2000 challenge may cause date problems and miscalculations to occur in your application software. Some applications have internal calendars that may miscalculate the leap year; others may force a two-digit date. Microsoft's compliant applications that store and manipulate dates do so consistent with four digits. In addition, these products do not use any special date codes and will automatically calculate the Year 2000 as a leap year.
You should verify with all vendors the readiness of the vendor provided application software you are currently using on your system. As we near the Year 2000, most are discovering additional tips and tricks to help their customers and will continue to update the information on their Web sites.
To determine whether your MS applications are Year 2000 ready, you can look them up in the Microsoft Product Guide. For other vendorsÆ products, you may want to visit their Web sites or contact the vendors directly. Both off the shelf or custom developed software applications should be assessed to determine whether they are compliant or need to be fixed or replaced.
Special Note on Runtime Libraries:
Runtime Libraries are files that provide functionality to applications. Users do not directly interact with runtime libraries; rather it is the user's actions with an application that utilize runtimes. By loading a Windows application you are using runtime libraries. By running an application such as Excel and then adding a third-party product you are introducing yet another runtime library to your system. If a runtime library mishandles the date, it doesn't matter if the application, operating system or BIOS are Year 2000 compliant--the environment is still not ready. If you use a non-Microsoft runtime library in conjunction with a Microsoft application it is possible the productÆs ability to handle dates properly will be affected.
Tips
Whether assessing Microsoft software or software from a different vendor, it is important to review the product-specific compliance statements of the vendors and their instructions for making the product Year 2000 compliant. Generally, vendors will offer the following guidance.
- Fix year 2000 problems by patches or service packs.
- Upgrade to new version of product.
- Migrate to another product.
Additional Resources
For more information on the Year 2000 readiness of Microsoft applications, see the Product Guide.
To scan your system for the compliance of Microsoft products select the Microsoft Year 2000 Product Analyzer
- An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please click here
- Download the Office 97 Year 2000 update.
Tools
Below is a list of Year 2000 remediation tools, with links to the companies that may be able to assist you in your Year 2000 remediation efforts. The tools listed on this site do not indicate an endorsement or recommendation on the part of Microsoft for the manufacturers, their products or the underlying technologies being used. You will need to do your own assessment to determine if the tools offered meet your needs. For information regarding these companies or their Year 2000 solutions, please contact the companies directly.
Applications
Scan and analyze Microsoft and other vendorÆs applications.
| Custom Applications |
|
| Overview
Custom applications are software programs that have been tailored to the specific needs of an individual or organization to help them better carry out a specific task or function.
The Year 2000 perhaps poses the greatest risk to organizations using custom developed software because there are no industry standards for customization. As a result, date handling may not be consistent. Organizations may want to consider implementing a review process to verify the ability of internally developed code to handle the Year 2000.
In reviewing your custom applications, it is important to triage these applications in terms of their importance to your organization. This will help you prioritize your efforts in assessing and remediating these applications. The following list is one way to categorize your applications:
- Human Life / Environment (e.g. elevators)
- Business Critical (e.g. AP/AR/GL)
- Business non-Critical (e.g. Enterprise Productivity)
- High-use Convenience (e.g. Personal Productivity)
- Low-use Convenience (e.g. Ad Hoc)
Challenges you may face in assessing your custom-developed software applications include:
- Custom application was developed with only a two-digit date field.
- No documentation exists for the application.
- No source code exists for the application.
- Application bypasses the BIOS or operating system and attempts to obtain date information directly from the hardware clock.
- Resources with experience in the application no longer exist, are unavailable or are prohibitively expensive.
Both off-the-shelf and custom developed software applications should be assessed to determine whether they are compliant or need to be fixed or replaced.
Special Note on Runtime Libraries:
Runtime Libraries are files that provide functionality to applications. Users do not directly interact with runtime libraries; rather it is the user's actions with an application that utilize runtimes. By loading a Windows application you are using runtime libraries. By running an application such as Excel and then adding a third-party product you are introducing yet another runtime library to your system. If a runtime library mishandles the date, it doesn't matter if the application, operating system or BIOS are Year 2000 compliant--the environment is still not ready. If you use a non-Microsoft runtime library in conjunction with a Microsoft application it is highly possible the Microsoft application will break.
Special Note on Data Interface
An end-to-end view of your organization and its computer systems is the best way to understand problems and risks related to data interfaces. Even if your PC platform is Year 2000 compliant, there may be an interface from that PC to a legacy system that is not working properly with dates. If this is the case, any information placed into the PC environment can cause problems. It is imperative that the interfaces between your PC and other platforms be understood, inventoried, analyzed, prioritized, fixed, and tested, just like any other portion of the Year 2000 project.
Tips
Custom-developed applications must be examined closely. Programs should be examined on a line-by-line basis to discover all uses of dates. Any code that bypasses the BIOS or operating system and attempts to obtain date information directly from the hardware clock, or utilizes two-digit fields, can cause problems.
Consider the following steps to help convert your self-developed software:
- Freeze source code, development environment and compilers.
- Analyze source code for non-year 2000 compliant statements and variable declaration.
- Edit Source Codeùin some cases the development environment or compilers may have to be migrated.
- Release new version of Source Code and put software under effective configuration management.
The real challenge is the configuration management of software developed by end users--self-developed software. An example of this might include Excel or Word Macros written by users who want to enlarge the functionality of standard software. Quality assurance and configuration management is missing in this type of customized code. Also, responsibility for future development and maintenance may not have been planned for and distribution is difficult to track.
Additional Resources
For a brief discussion of windowing techniques, please click here
Preparing Office Solutions for the Year 2000
This paper is designed to explain Year 2000 issues related to custom solutions built using Microsoft Office and Visual Basic for Applications. If you develop custom solutions using Microsoft Office, you should read this paper to assess any potential problems that might arise from operating those solutions past December 31, 1999. The material presented illustrates potential areas for concern and the steps required to address any issues.
How to Prepare Visual Basic Applications for the Year 2000
Ensure that your Visual Basic applications will behave properly with dates beyond 12/31/1999.
Visual C++ and the Year 2000
This whitepaper details information on Visual C++ and explores the technical issues involved with Visual C++ and date handling issues. Find out how to verify and fix date issues in a software system, suggested practices, and additional Y2K resources.
The Automation Libraries and the Year 2000
In an effort to improve code efficiency and lower the total cost of ownership for our products, Microsoft recommends that internal developers use a common Automation Library for handling dates. Over the years, the library has been updated to reflect changing customer needs and add additional functionality. This white paper will address your most frequently asked questions.
Building Year-2000 Compliant Applications with Visual Studio and Windows DNA
The Microsoft« Windows DNA architecture represents a comprehensive new framework for integrating client/server and internet software solutions on the Windows platform. Windows DNA is based on the premise of software component integration and interoperability. DNA combines "component based" software development with a "service based" operating system. However, integrated software components and modularity do not protect the developer from introducing Year 2000 compliance problems in their applications. Regardless of the tools used to develop software today, a clear Year 2000 philosophy is needed to avoid spending time reworking an application in future years. For more information see this white paper.
Tools
Below is a list of Year 2000 remediation tools, with links to the companies that may be able to assist you in your Year 2000 remediation efforts. For a tool to be listed on this site does not indicate an endorsement or recommendation on the part of Microsoft for either the manufacturer, its products or the underlying technologies being used. You will need to do your own assessment to determine if the tools offered meet your needs. For information regarding these companies or their Year 2000 solutions, please contact the companies directly.
Custom Applications
Scan and analyze custom applications created with Microsoft and other vendorÆs development tools.
If you are a Year 2000 Tool provider and would like to be listed in the Tools Guide, please email Y2Ktools@microsoft.com.
Please Note: We are no longer going to be accepting new entries into the tools guide after October 20, 1999.
ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFTÆS YEAR 2000 WEBSITE LOCATED AT http://www.microsoft.com/year2000/ (the "Y2K WEBSITE"). EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED PURSUANT TO THE TERMS HEREOF, THE TERMS OF THE Y2K WEBSITE, AND THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT FOR THE SOLE PURPOSE OF ASSISTING THE PLANNING FOR THE TRANSITION TO THE YEAR 2000. EACH MICROSOFT YEAR 2000 STATEMENT CONTAINS INFORMATION CURRENTLY AVAILABLE AND IS UPDATED REGULARLY AND SUBJECT TO CHANGE. MICROSOFT THEREFORE RECOMMENDS THAT YOU CHECK THE Y2K WEBSITE REGULARLY FOR ANY CHANGES TO ANY MICROSOFT YEAR 2000 STATEMENT. EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. CONSEQUENTLY, MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, MICROSOFT DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF ANY MICROSOFT YEAR 2000 STATEMENT IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY MICROSOFT OR ITS AUTHORIZED REPRESENTATIVES SHALL CREATE A WARRANTY OR IN ANY WAY DECREASE THE SCOPE OF THIS WARRANTY DISCLAIMER. IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER REGARDING ANY MICROSOFT YEAR 2000 STATEMENT INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, PUNITIVE OR SPECIAL DAMAGES, EVEN IF MICROSOFT OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE FOREGOING LIMITATION MAY NOT APPLY TO YOU. THE INFORMATION CONTAINED IN EACH MICROSOFT YEAR 2000 STATEMENT IS FOUND AT THE Y2K WEBSITE AND IS INTENDED TO BE READ IN CONJUNCTION WITH OTHER INFORMATION LOCATED AT THE Y2K WEBSITE, INCLUDING BUT NOT LIMITED TO MICROSOFTÆS YEAR 2000 COMPLIANCE STATEMENT, THE DESCRIPTION OF THE CATEGORIES OF COMPLIANCE INTO WHICH MICROSOFT HAS CLASSIFIED ITS PRODUCTS IN ITS YEAR 2000 PRODUCT GUIDE, AND THE MICROSOFT YEAR 2000 TEST CRITERIA.
ANY MICROSOFT YEAR 2000 STATEMENTS MADE TO YOU IN THE COURSE OF PROVIDING YEAR 2000 RELATED UPDATES, YEAR 2000 DIAGNOSTIC TOOLS, OR REMEDIATION SERVICES (IF ANY) ARE SUBJECT TO THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT (112 STAT. 2386). IN CASE OF A DISPUTE, THIS ACT MAY REDUCE YOUR LEGAL RIGHTS REGARDING THE USE OF ANY SUCH STATEMENTS, UNLESS OTHERWISE SPECIFIED BY YOUR CONTRACT OR TARIFF.
|
|
|
Operating Systems