Welcome to AC Online Campus Direct FIT FAQ's
 

Home

FAQ's

Contact Us

Seminars

Distance Learning

Apple

Dept. Contacts

        
 
 

Academic Computing Y2k Compliance FAQ v. 0.1a
November 1, 1999 Click here for current report
This is a preliminary "rough" draft of the Academic Computing Y2k Compliance FAQ. This FAQ will undergo several revisions in the coming months to report our progress.

What is the Y2k (Year 2000) problem?

"The problem is that when computers were introduced to the worlds of government, banking, and big business, memory space was at a premium, so much so that every bit and byte was counted and programs were designed to use as little memory as possible. One way of shaving off a few figures here and there was to record the year by its last two digits, so '1998' is shortened to '98'. Which works just fine, until midnight on December 31st 1999 when that counter clicks over from 99, to 00. Without the first two digits of the year, the computer cannot know that it is the year 2000, and must effectively work on the presumption that it is 1900, all over again. Of course the programmers who created this system could foresee this would cause a problem, but as well as a degree of short-termism there was a widespread disbelief that anyone would be using the same computers and programs nearly thirty years later. They were wrong, and the result is that our computers, those symbols of progress and forward thinking, will doggedly refuse to leave the last century."

- Excerpted from the BBC Education: Millennium Bug Information

More info can be found at:

Y2000 FAQ's , FAQ's on the year 2000 and Yahoo's Year 2000 links


How will this affect Academic Computing?
While we do not expect to be building bunkers or storing canned goods we are taking Y2k seriously from a Hardware, Operating System and Application standpoint. With a little luck January 1, 2000 will come and go unnoticed.

What will we be doing over the next few months?
  • Simulate Jan 1, 2000 by moving the date ahead on every computer/Server type we have.
  • Run diagnostic Y2k software
    • Real time clocks
    • BIOS
    • System clocks
    • Date rollover
    • Leap year
    • Vender specific tests
  • Check all software venders websites for their Y2K compliance statements.
  • Install service packs and patches to software with known issues.
  • Alerting departments if particular Academic Computing software is problematic.
  • Our Current progress report is here