Posted : 12/01/1999
Time Is Running Out A Y2K Checklist for the New Year
by Judie Gaillard
For the past few years, the world has been awaiting the arrival of the Year 2000 with heightened anticipation. However, after all the confetti settles and the champagne glasses are dry, people worldwide will be rushing to their computers to see if the predictions of the Millennium Bug were true.
The truth of the matter is that no one knows exactly what will happen at the stroke of midnight, Dec. 31, 1999. And with the New Year less than one month away, salon owners need to double and triple check that their systems will roll over without causing havoc with their businesses. Experts say we all will experience inconveniences from what is becoming widely recognized as the year 2000 problem (Y2K)--the question of how much inconvenience is unanswered.
Even if you have updated your system, I advise you to review it again. Experts predict everything from disrupted travel schedules to more serious problems such as large-scale power outages or even global recession.
These issues are a concern among users of computer-based equipment including salon management systems. Some of the consequences of equipment not properly representing the date simply are annoying; others could be very serious in their potential to cause financial harm to individuals and organizations. Recent news reports indicate that system failures have occurred during the testing process--from the banking industry to waste management, from school administration to home computers. Do you want to put your business in jeopardy?
Avoiding the Bug
As glitches go, the Y2K problem is simple enough. The "millennium bug" or year 2000 date rollover problem refers to the inability of some computers and computer-based systems to properly differentiate between the year representations of "00" as 1900 or 2000, and "99" as 1999 or 2099. Most systems use such two-digit year representations instead of the full four digits. Initially, this was done to save keyboard entry time and to conserve on expensive computer processing and storage resources. Although the processing and storage issues are no longer a big concern, the two-digit format remains easier to use from an operator standpoint and probably will remain in use despite the programming ambiguities.
Fixing the Y2K problem also is simple--in concept. Someone must examine every line of code in every computer, locate the instructions regarding dates, and rewrite them to accept 2000 as a year designation. But despite the rising din of warnings, surveys indicate that too few managers in business and government recognize how little time is left to complete the task.
Fears also seem to be subsiding among the U.S. population even as many say they will prepare for the worst. In a recent USA TODAY/National Science Foundation poll, 34 percent expect "major problems" in 2000, down from 48 percent in June 1998. According to one source, this is an alarming trend.
According to the June 8, 1998, issue of U.S. News and World Report, there are five major myths concerning the Y2K problem that need to be addressed. They include the belief that there is plenty of time to fix the problem, that someone will find a quick fix before all the problems occur, that enough money and manpower is being used to fix the problem, with so many new computers out there, surely they can't be vulnerable to a problem created 25 years ago and, finally, it won't affect me.
All five myths create their own problems; however, the last two seem to be the most unsettling when considering small business owners, including indoor tanning salon operators. For example, salon owners might feel that because the indoor tanning industry in relatively young, the Y2K problem will not affect industry computers. However, the notion that the Y2K problem applies only to old systems can give a false sense of security.
Ironically, one reason the Y2K bug has survived is the concept of "backward compatibility," which was introduced in the 1960s to bring order to computer development. IBM and other computer companies, realizing they couldn't expect clients to buy new software every year, made sure that each new model largely was compatible with earlier programs. However, that created an environment in which the old Y2K bugs have been able to worm their way--program by program--into the most modern equipment.
The second myth is that the Y2K bug will not affect me. Rather naive thinking even for the most novice of small business owners, many believe the problem has no impact on their lives. However, while most large businesses, banks and financial institutions have spent lavishly to prevent massive Y2K problems, smaller ones abound that have not. Already some debit machines at checkout counters have rejected credit cards with year 2000 expiration dates. So, even if your salon's computer and software equipment is Y2K compliant, what if the credit union you bank with or the distributor you purchase lotions from, is not?
There are a number of actions that can be taken to ensure Y2K compliance for your hardware and software. First, using Y2K problem detection tools for the PC, check all systems. Replace or upgrade equipment if the bug if found. In addition, contact manufacturers to get additional input; however, make sure to run your own tests.
And, just because your equipment is newer, don't under-estimate the Y2K bug. It is estimated that 47 percent of all 1997 PCs and as many as 79 percent of PCs built prior to 1997 will fail the 2000 compliance test. Most older generation mini and mainframe systems were designed with the space-saving two-digit date field and should be upgraded or replace.
Second, check all types of software. Check that all year date fields that perform calculations are formatted with four digits. In addition, if you are using "00" or "99" as dummy data to indicate dead or expired accounts, you need to convert those into another format.
Salon owners also will want to identify key business functions, processes and facilities that may be affected by the Y2K problem and replace affected items. Also, develop contingency plans to handle your business needs in case you experience Y2K problems with your computers, devices or building systems. Finally, make sure to identify and contact key providers of supplies and business services about their Y2K compliance plans.
The Year 2000 problem is easily checked and usually fixable. It is not recommended this check or fix be done from Windows. Use the checklist on page 52 to see if you can escape the bite of the Millennium Bug.
Checking your system with a boot disk:
- Insert a boot disk into your floppy drive then turn on the computer (see your operating system documentation on how to make a disk)
- Type DATE and change the date to 12-31-1999.
- Type TIME and change the time to 23:59.
- Turn the computer off. * Wait at least one minute.
- Restart the computer from the floppy drive and type date.
- If the year doesn't read 2000, there is a problem.
- Use DATE and TIME to reset the current date and time.
Checking your system using the BIOS setup
- Enter the computers BIOS setup at boot time (Check your computer's documentation).
- Change the date to 12-31-99.
- Change the time to 23:59.
- Turn the computer off.
- Wait at least one minute.
- Restart the computer and enter the BIOS setup.
- If the year doesn't read 2000, there is a problem.
- Use the BIOS setup to reset the current date and time.
If the year didn't read 2000, use the following steps to see if it can be fixed manually.
- Boot from a floppy disk or enter the BIOS setup.
- If the date reads 1900, change it to 2000.
- Restart the computer as in step 1, the year should read 2000.
If this doesn't fix the problem, you will have to upgrade the computer's BIOS or consider getting a new computer system. In addition, there also are several free and commercial utilities on the Internet to fix this problem. A good place to start is PC Magazine's Web site.
These tips are provided courtesy of FST Co., Inc.
|
|