AutoInc. Magazine
   
Enter Our Photo Contest!
MAGAZINE
Home
Current Issue
Ad Index
AutoInc. Archive
How to Contribute
Reprint Permission
RSS
READER SERVICES
Subscription Info
Letters to the Editor
ANNUAL FEATURES
Top 10 Web Sites
Software Guide
NACE Online Daily News
How's Your Business?
ADVERTISING
Ad Opporunities
Media Planner
ABOUT AUTOINC.
AutoInc. Mission
Meet Our Staff
  Management Feature

The Y2K Problem

Posted 2/12/1999
By Terri Ruppert

Year 2000Imagine standing in line at the grocery store. It's Dec. 31, 1999, at 11:59 p.m. As the dawn of a new millennium breaks, so does just about everything else. The scanner refuses to read the bar code and the register beeps continually. It doesn't really matter, however, because in a moment, the lights flicker and go out. You try to leave, but the automatic doors refuse to open. Some one thinks to call for help, but the phone lines are dead _

This scenario may sound like the beginning of a horror movie, but it could be reality. All this chaos because of a two digit "glitch" in computer systems, commonly called the Y2K (Year 2000) bug. This error grew out of the efforts of early programmers to conserve precious computer memory. Dates could be recognized by a six digit number, mmddyy, instead of an eight digit number mmddyyyy. What these programmers didn't realize was that their code would be in use 30 years later.

The inability to recognize two digits doesn't sound disastrous, until you realize the implications.

Age is normally computed current year - birthday year = age (99 - 34 = 65). However, with the Y2K bug your age will now be calculated (00 - 34 = -34). To the computer, you're far too young to retire, much less collect social security.

Society today has been built around computers. We have become so dependent upon computers that we no longer recognize computer controlled activities. We take for granted the everyday things that are made possible by computers.

Let's take electricity for example. Whether it's hydroelectric, steam turbines, or generated by a nuclear power source, all of these methods depend upon computers to regulate their systems. Worst case scenarios will have entire cities shut down. People will lack even the most basic needs such as water (computer controlled purifying and distribution) and sewage processing (also computer controlled). Even the most basic emergency services could have a limited life span. While hospitals will be able to operate on generators for a limited time, the equipment in every department from admissions to ICU may have also succumbed to the Y2K bug.

On a less critical level, common, everyday conveniences could be disabled. Without electricity, artificial lights won't light, the coffee maker won't work, the electric hot water heater won't heat and the clothes dryer won't dry. The food in the refrigerator is in danger of spoiling, but without a gas stove, you won't be able to cook it. If you attempt to leave the house, most likely you will have to disable the garage door opener and open it manually. You may also have problems obtaining gasoline because most filling stations use electricity to activate the pumps. Even getting to the service station may be a problem because without electricity, traffic lights won't be operating and traffic will rapidly become gridlocked.

None of these possibilities are intended to frighten or alarm anyone. I simply wish to clarify the scope of the problem. Almost everything we use today, from ATMs to air traffic control, are dependent upon some type of computer, be it a chip that operates an automatic door at the supermarket to the supercomputer that controls our nuclear arsenal.

Since so many of the things mentioned above are out of your control, what can you do to ensure a smooth transition to the new millennium? Let's start in your office. If you use a computer, you need to make sure that the computer itself is year 2000 (Y2K) compliant. When you turn on a computer, it uses a basic input-output system (BIOS) to get such information as the date and time before loading the operating system. If the BIOS is not Y2K compliant, any date that is passed to the operating system or any application program will be incorrect. Since many application programs interface seamlessly with the operating system, this problem could be difficult to detect. Fortunately, there are many free programs available from the Internet that will test your computer's BIOS and let you know whether or not it is Y2K compliant. You can also contact the computer's manufacturer to see if the BIOS is compliant.

The next step is to determine if the operating system itself is Y2K compliant.

You may need to upgrade to a new operating system if the one you use is not compliant, or it may become more cost effective to upgrade to a completely new computer system. You may find it necessary to upgrade to the latest version of any application software, such as Quick Books or Peachtree Accounting Software, etc., to ensure compliance. Accounting software is heavily dependent upon dates to calculate delinquency, billing cycles, etc. Failure to ensure compliance could cause major headaches down the road. In fact, it's a good idea to check to see that any computer software you are using is Y2K compliant. A new law that was recently passed, the Year 2000 Information and Readiness Disclosure Act, contains fuzzy legal language that many believe relieves the software manufacturer of any responsibility for damage that may be a result of their software's non-compliance.

Other items and services that may fall prey to the Y2K bug are burglar and fire alarms, and credit card processing machines. Don't forget about banking services. We bank from home with online services, we use direct deposit for our payroll checks and imagine a world without the convenience of ATMs. However, these too may be vulnerable to the bug. The United States Treasury has authorized the printing of thousand dollar bills for the first time in decades in response to the public's growing concern about electronic monetary transactions and the Y2K bug.

The best advice for this year is the Boy Scout motto: "Be Prepared!" _ and a sense of humor never hurts.

Terri Ruppert is the manager of information systems and distribution for the Automotive Service Association.


Y2K Tips by Julie A. Finn

According to a study sponsored by Wells Fargo Bank, almost five million small businesses are at risk from the Y2K bug (The Year 2000 Computer Bug). Three-fourths of those businesses have not and do not plan to take action before 2000. Because of this, more than 700,000 small business will face problems in the new millennium that could force them to halt work. Following are several key steps shops can take to assess and begin to correct their Y2K vulnerability:

  1. Establish the importance and necessity of Y2K action by asking if an item or program needs to know the difference between 1999 and 2000. If the answer is no, Y2K action is most likely not necessary. However, if the answer is yes, action must be taken.
  2. Identify when each of your personal computers was manufactured. If the PC was manufactured before 1997, it will probably fail to properly calcu- late the millennium date. If the PC does this, the date can be manually set in the year 2000, and the PC will thereafter calculate the date correctly. Diagnostic programs are also available from computer stores to check a computer's compatibility, and soon the maker of Norton Utilities and Norton Antivirus will release Norton 2000, another diagnostic program. Apple computers have been Y2K compliant since they were first manu- factured in 1984.
  3. Check the compliance of all software. If the software program requires that a date be typed in, do you type in a four-digit year or a two-digit year? If you type in a two-digit year, the program is not compliant. Contact the software company to get a Y2K solution, but if the company cannot assure you that a solution will be available when you need it, you may need to look for another software program. Programs about which the makers have assured compliance include Windows 98, CCC's Pathways Digital Imaging and EZWorks, and ADP's products. Though Windows 95 and Windows 3.1 are not compliant, free patches to correct the problem can be downloaded from www.microsoft.com/y2k.
  4. If you have Internet access, visit Web sites that offer checklists or free testing utilities to check computer compliance. One site ( http://www.nstl.com/html/ymark_2000.html offers a testing utility that also checks for compliance to the leap year in 2000, while http://www.sba.gov/y2k offers a checklist, prepared by the Federal Reserve Board, designed specifically for small businesses.
  5. Ask about the compliance of companies with which you do business. General Motors has assured the compliance of all its vehicles and diagnostic tools, but how ready is your insurance company, your vendor or your bank? Reprinted with permission from the ASA Collision Repair Report


share your thoughts...

RATE THIS ARTICLE

What do you think of this article? Your input will help AutoInc. develop additional articles on this subject. Share your thoughts!

Your name

Your e-mail address

  

MOST ACCESSED ARTICLES

  • Fuel Injection Service, Not Just Cleaning
  • The Art of Extraction
  • EGR Systems: Operation and Diagnosis
  • Proactive Target Marketing:_Rethinking Your Business Strategy
  • Engine Performance: HO2S Diagnostics

    MOST E-MAILED ARTICLES

  • Developing Employee Potential
  • How Critical Thinking Can Help Your Business
  • How to Diagnose the Ford Glow Plug
  • What to Look for When Shopping for the Right Shop Management Software
  • Putting a Price Tag on Complaints
  • AutoInc. Web Site | ASA Web Site | OSHA's Next Step | Training and Continuing Education | Brighter Shades, Lower VOC Rating Color 1999 PAints | The Y2K Problem | Guest Editorial | Tech to Tech | Tech Tips | Shop Profile | Net Worth | Stat Corner | Chairman's Message

     
    Copyright (c) 1996-2009. Automotive Service Association®. All rights reserved.
    XML Add RSS headlines.