Three things are necessary and sufficient to have a y2k problem.
A two character year field is not of itself a bad thing unless accompanied by both progamming errors and a harmful context. Even the programming errors are only of cosmetic importance without the context.
Computers not attached to the network are not addressed, nor are mac, sun, sgi, etc.
Lab equipment, lab data gathering computers, and gathered data are the responsibility of the faculty PI. I have made all known y2k web links available on the COP website. I wrote two letters to faculty encouruaging them to contact their vendors.
COP1, COP3, COP4, COP6 are Netware 3.12 patched to current level. Novell website says version 3.12 is y2k-ok with updates. Have personally set server clock to 12-31-99 and let it roll over to make sure servers will not crash overnight, correctly display 2000 and have a Feb 29.
COP2 is Netware 3.11. Novell website said it was not tested. Had expected this server to be taken out of service before 1-1-2000 but am no longer sure of that. Did same operation as for 3.12 servers and found it was ok. There may be some cosmetic issues. If that should become a problem, I could upgrade or abandon COP2, migrating its users to COP1. COP2 runs on a Dell p90, which was tested with test2000 (see PC section below) and found it is y2k-ok.
COP5 is Netware 4.11. Novell website says it is y2k-ok.
Windows NT 4 servers are patched to sp3. Microsoft website says Windows NT 4 server is y2k-ok with minor issues.
All PCs are p166 or better. The vast majority are Dell Dimension or Optiplex. Tested a p166 with test2000.exe from www.year2000.com and found it to be y2k-ok. Assume newer Dell computers are also y2k-ok.
All PCs run WIN95. Tested it by setting the clock ahead. Microsoft website says WIN95 is y2k-ok with minor issues.
All PCs use Office 97. Microsoft website says Office 97 is y2k-ok with minor issues. Tested Schedule+ by setting recurring appointment across 1999-2000 boundary. Tested applications written in Access 97.
Current versions of Pegasus mail client and the Mercury mail server are certified y2k-ok by the author.
In 3Q99 the college bought 120 Dell Optiplex Pentium iii's. They run win98 with y2k patches applied by Dell. Personally ran test2000.exe on one and it passed.
Along with the new computers we upgraded to the latest version of the Netware client, Netscape, Host Explorer, and Pegasus Mail. These programs are all certified y2k-ok by the manufacturers.
Healthnet plans to replace all hubs before 1-1-2000.
Upgraded to Arcserve 6.1 which is certified y2k-ok by Cheyenne. Tested it by doing a backup with the server clock set ahead, and by doing a post-y2k restore of an old backup.
All my programs are written in one of the following:
FoxPro/DOS 2.0 and 2.5 (32-bit)
MS Access 97
Visual Basic 5
The Microsoft website declares Office 97 and Visual Basic 5 as y2k-ok. All my programs are y2k-ok to since they count the number of seconds past some origination point to represent date/time values. If this count is held in a 32-bit integer, there will be a y2k-like crisis in 136 years.
Some of my early database programs had 2-digit year fields on input and display screens. I went through every FoxPro application of mine in 1996 and made corrections as appropriate to each situation. This is all documented in my journals. All my production programs are now y2k-ok.
The HP website says all jetdirect hardware and firmware is y2k-ok. Upgraded to latest version of JetAdmin management software. Could use that to upgrade firmware if necessary later.
Tested the K2 computers with test2000 and found them to be y2k-ok.
The Asthma Lab was contacted by their vendor. My staff tested their lab software and determined it was not y2k compliant. The vendor did not have an upgrade available. The delivery date had been pushed back several times. This matter remains unresolved as of 8-1-99.
© 1999 University of Florida