My impressions on Microsoft's Y2K tools
I ran the Microsoft Y2K Product Analyzer on my PC. It created an HTML file with a list of the Microsoft Systems/Applications that it found on my system.
I have 5 applications that are “Compliant”. Three applications that are “Compliant (prerequisite required)”. Six applications that are “Compliance Unknown”. One application that is “Compliant with minor issues” and one that is “Compliant with minor issues (prerequisite required).
A Year 2000 Compliance Summary section is generated. This section contains a URL to Microsoft web site where you can get more information on the product. It also gives you a suggested action, although this action general simply says to “please refer to the product information found at the URL listed above”.
I went to the section for Word 97 SR-1 8.0 (English). This product had been listed as “Compliant (prerequisite required)”. They suggested “Office 97 SR-2 Patch” and gave the URL.
I went to their Web site and followed the instructions on their Web page. I had to downloaded and installed “Office 97 SR-1 Patch” first, which I did. I then returned to their Web site and ran the Office 97 version checker. This told me that I had to install Office 97 first. I'm running Office 8.0.3501 and there is no match for this product in their database.
So now I am back to the inventory stage. I am surprised to find that I am not running Office 97 SR-1. I am going to look closely at my Microsoft Y2K problems and make a decision as to whether I should reinstall Office 97 and apply the SR patches or just avoid the Y2K problem areas of Office.
Microsoft Year 2000 Resource CD
This CD is a mix bag of Y2K information and Microsoft marketing. The CD would have been more useful if it came out 1 or 2 years ago. There is some good information in this CD, but it looks more like a marketing tool.
Here are some of the topics that are discussed:
What are the main points of exposure for the PC?
Six layers: The PC has 6 main layers of exposure to Year 2000 problems:
1. Hardware
2. Operating System
3. Runtime Library
4. Applications
5. Custom Code
6. Data Interfaces
What are Microsoft's recommendations for working with the Year 2000 on a PC?
End-to-end examination of computing environment.
Use a test-bed.
Use a MS-DOS boot disk to check the BIOS and system clock.
Inspect custom code.
Use management tools where possible for inventory and distribution of fixes.
What are the driving business issues for Year 2000 decision-making?
Resources and time.
Supply chain.
Cost.
Contingency planning.
Digital Nervous System.
What steps should organizations take when dealing with the Year 2000 problem?
1. Inventory and Analysis:
2. Fix and/or replace:
3. Retirement:
What will the effects of a shortage of time and resources do to the decision-making process?
Triage becomes essential:
Systems that are mission-critical but carry risks different from traditional Information Technology. (Example: control systems for manufacturing equipment, embedded systems)
1. Systems that are mission critical. If these systems are lost, the company will cease to do business. (Example: core accounting systems or order entry systems)
2. Systems that, if lost, will cause significant pain and will disrupt major business processes. (Example: email systems, report writing systems or line-of-business applications)
3. Systems that, if lost, will only cause minor inconveniences. Work will continue with or without these facilitators. (Example: simple data manipulation tools, internal convenience tools)
4. Systems that are extraneous and should be retired. (Example: legacy applications that few individuals use)
The Microsoft White Pages Section covers the following topics:
Integrate the Enterprise
How To Prepare Visual Basic Applications for the Year 2000
Microsoft Access: How to Convert Between Julian Days and Dates
The Automation Libraries and the Year 2000
Year 2000 Test Considerations
Ctime And Its Relationship With The Year 2000 Issue
Building Year 2000-Compliant Applications with Visual Studio and Microsoft Windows DNA
I found the following information in the Automation Libraries section:
If you're running Windows 95 or Windows NT 3.51 or later, then you use the automation library.
Four files make up the automation library. These files are:
leaut32.dll
lepro32.dll
asycfilt.dll
stdole2.tlb
These files are installed either by the operating system or an application.
The automation library contains routines for interpreting two digit years and provides a convenient way for applications to create unambiguous (serial) dates. So, many of your applications probably use the automation libraries for date handling.
Over the years the automation libraries have been revised three times with regards to their date formatting behavior:
Library (OLEAUT32.DLL) Version Two Digit Year Cutoff
Before 2.20.00.4054 1999
Versions 2.20.00.4054 to 2.29.xx.xxxx inclusive 2029
Versions 2.30.00.xxxx and forward User determined
How do I know what version of the automation libraries my computer has?
Click the Start button, select the Find menu item, and click on "Files or Folders..." In the "Name & Location" tab, type (without quotes) "oleaut32.dll" in the field titled "Named." Select the drive in the "Look in" field that your operating system lives on (usually (C:) ). Click "Find Now." When the file shows up in the box below, right click on the file and select "Properties." Click the right hand tab that says "Version."
Name some applications that use automation libraries
Microsoft Office 95 and later
Microsoft Visual Studio (including Visual C++, Visual Basic, Visual Interdev and custom applications)
Microsoft Windows 95, Windows 98, Windows NT Workstation, Windows NT Server
Microsoft Internet Explorer
There are a few year 2000 issues that could result from different users having different versions of the automation libraries. These all involve the interpretation of years entered with only two digits. If your software applications and users enter four digit years, there are no problems. If your users or software are entering two digit years, then a scenario where different machines are entering years in different centuries is possible. For example, a data entry department could be running a custom application on both Windows NT 3.51 (without service packs) and on Windows NT 4.0 Workstation. If the users are entering dates like 1/1/10, the NT 3.51 machines could record the date as January 1, 1910 while the NT 4.0 machines may record January 1, 2010. By installing the latest service packs or newer applications (like Microsoft Office 97 or Internet Explorer 4.0), you can assure that your systems have more consistent date handling.
Overall, this has been a worthwhile exercise for me. Although I had to look past the Microsoft marketing, I did find some useful information on the CD and I am now more aware of Y2K problems with my Microsoft applications.
I wish I could inventory all of my application software this way. I have applied Y2K patches to most of my critical applications, but I keep wondering, “what have I missed?”
B.K.
|
