Y2k Issue on PC LAN

ncline.gif (410 bytes)jun99.gif (1083 bytes)

Manfred Chan

y2k.gif (2818 bytes)Y2k is a very hot topic in recent months. Although the y2k problem poses a serious threat, yet with proper planning, it is not the end of the world. In order to assess the y2k problem on LAN, we have to investigate all LAN components such as: networking devices, servers, and software being installed on this hardware.

The Computing Services Centre (CSC) will ensure the y2k compliance of all networking devices and servers managed by the CSC and the software provided centrally. On the other hand, user departments have the responsibility to ensure the y2k compliance of their student LAN machines and software as well as the departmental-specific PC software being used by their staff.

In fact, the CSC had started to study the y2k impact on our PC LAN in 1998. Since then, y2k compliance has always been listed as part of the tender specifications for all new purchases of both hardware and software.

The CSC tackles the solution of y2k compliance in four phases. They are summarised as follows:

1)   Identifying the potential y2k problems

Basically the main y2k problem for PC hardware lies in the BIOS component. In order to collect statistics of how many PC BIOS must be upgraded, we put command scripts on all Win95 and Pathworks V5.1 clients. The scripts were mainly used for collecting hardware information such as the PC BIOS version and BIOS type. We then worked out the BIOS upgrade plan based on the hardware information.

We also needed to identify the importance of the software currently deployed for every department. Questionnaires were used to help determining the software that are mission critical for the departments. Software classified as critical had been checked for y2k compliance by the user department. In order to assist user departments in finding out the y2k compliance of some common software, the CSC has maintained a y2k compliant list for quick reference. For details, please visit http://www.cityu.edu.hk/csc/y2k/stafflan/y2k_cityusw.html.

2)   Checking the y2k compliance of each component

After identifying the different components, it was time for us to start the y2k scanning. The BIOS tester program, TransCentury Office, was adopted to check for y2k compliance of the PC BIOS. To ease the operation, all clients should be running on Windows 95.

In addition, we also used the TransCentury Office to scan data files created by software like MS Access, Paradox and Excel. This program can help identify the y2k problem of some common databases as well as Excel worksheets.

3)   Applying the y2k patches or upgrading the y2k non-compliant components

As the majority of our users have either the T2P4 or the TP4N ASUS motherboards, we therefore decided to upgrade the BIOS for these two motherboards only. For other types of motherboards, we have to deal with them separately in different ways. The BIOS upgrade was completed by 31 May 1999.

Up until now, we have fixed all the departmental NT servers by applying the y2k fix on the Microsoft Windows NT version 4.0 with service patch 3. We shall upgrade the NT to service patch 5 once the patch is stable enough (patch 4 is unstable either). All other y2k non-compliant NT servers are replaced with Pentium 166 with BIOS upgraded.

The TransCentury Office also provides a user-friendly interface to novice users for fixing the y2k problem of their databases and spreadsheet files. The software helps to identify the problematic y2k items such as the 2 digits in the year field and provides an easy-to-use menu for rectifying the data fields in the worksheet or database.

Besides, we are trying our best to keep the central software y2k compliant by obtaining y2k certificates from vendors or collecting information from the related authorised Web sites. Y2k non-compliant software may be upgraded to the y2k compliant version if possible.

The following table shows the y2k compliance of the centrally supported software:
Software Y2k Compliant? Implication
Acrobat Reader 3.0 Yes  
Borland C++ No Upgrade to V5.02
Clipart Library Yes  
Eudora Pro. V3.x Yes  
FreeZip Yes  
KEATerm V4.23 No Upgrade to KEA! 4.20
Lotus 123 Rel. 9 Yes  
McAfee Antivirus Yes  
MS Access Jet DataBase No Upgrade to V3.0
MS Chinese MS Office 97 Pro. Yes  
MS Chinese Windows 95 Yes, with minor issues No fix from Microsoft
MS FrontPage 98 Yes  
MS Office 97 Pro. Yes  
MS Visual Basic No Upgrade to > 4.0 (32 bit)
MS Visual C++ V5.0 Yes  
MS Visual Foxpro No Upgrade to > 5.0
MS Windows 95 Yes, with minor issues Applying the fix before 30 Jun 1999
Netscape V4.5 & plugins Yes  
Pathworks mail No To be obsolete
PC-240 No To be obsolete
SimpTerm Yes  
WordPerfect V8.0 Yes  
WS-FTP Pro V6.01 (32 bit ) Yes  

4)   Actual or simulated y2k testing on each component

Although we have checked and applied the y2k patches to most LAN components, yet there are still risks. Actual or simulated testing should be done to check the y2k compliance. Furthermore, the CSC is doing risk analyses on all critical services and preparing contingency plans just in case the y2k problem really occurs.

issue20.gif (1037 bytes)

[u logo]
Computing Services Centre
City University of Hong Kong
ccnetcom@cityu.edu.hk

[Home Page][CSC Home][NetComp Home][Content Home][Previous Page][Next Page]