 |
This meant that when the year ticked over to 2000, computers and much software would have registered this as '00' and any date computations involving date ranges from the previous century would provide negative results causing many unforeseen problems. To compound this, the BIOS of many computers knew nothing of the year 2000, and when that time arrived, many reverted to 1980 or whatever year they were built. One of the computers in our office reverted to 1/1/1992 when we tested a rollover to the new century.
Most software and hardware vendors worked furiously and billions of dollars were spent around the world to correct the problems inherent in many systems regarding Y2K. Many consumers were forced to upgrade both their equipment and affected software.
RISC v3 (in 1998) was updated to ensure Y2K Compliance. This meant that the RISC application itself would work up to the year 2000 and beyond. Although RISC does only show two-digit years, the application prepends the appropriate two digits when performing any date calculations. But RISC will always get the current date from the workstation's BIOS (which may in turn get it from a server), so unless all components of your computer system are Y2K Compliant, it will mean that RISC or any other Y2K Compliant software package will have problems in operation.
Users of RISC v2.xx should upgrade to v6 (current release) to ensure Y2K compliance. Upgrade pricing is available on our Ordering RISC page. If you are unsure of which version of RISC you are currently licensed to use, check the RISC Userlist.
If you have any questions about the Y2K Bug, please do not hesitate to contact us via our Fax Support Line or call your local computer supplier or department technology section.
