Y2K

1. Your computer hardware
   
   Computer hardware is limited in what it can do, hold, store or process by the BIOS, a chip with ROM code in it that gives the computer the basic knowledge about itself. It is a form of psuedo-intelligence. The BIOS determines (among many other things) how many bytes of information can be stored in the date information, within the data the computer hardware uses to know about itself. Most hardware manufactured prior to mid 1997 allowed only enough date information hardware storage for a month of 0-11 (January through December), for a day of 0-30 (actually 1-31), and a year consisting of only two digits (the last two digits) of the four digit year. There were various schemes that BIOS manufacturers used to compile the characters to form a month, day, year format but they all did more or less the same thing. They ASSUMED the first two digits of the year were 19. Some did limited calculations to determine the schedule for leap years. Some just assigned several years as leap years knowing that the computer would have a very limited lifespan. The ugly problem arises as the year 2000 comes around and the computer only sees the last two digits, 00, and by way of the limited intelligence it has been given, assumes that the 00 is 1900, in the same manner it did for 19+97, 19+98, 19+99, 19+00, instead of 2000. Some even see it as 1980, the beginning year for the IBM PC's first ROM. The problem will not shut down your computer or keep it from working, as many Y2K doomsdayers have leds users to believe; it will only have the wrong HARDWARE date for use of the operating system. The real time clock, the hardware that keeps the actual time (hours, minutes and seconds) is NOT affected. You can test your own computer by just setting the date to January 1, 00 to see what it will do. There are also several software packages that will look at your system and determine if it is Y2K compliant. (See the Y2K compliant information.) Just because it is or is not, does not mean you don't have problems or do have problems concerning the turn of the century.
   
   
2. Your computer software
   
   All software bears a common name but wears several different uniforms of heirarchy in the computer. The BIOS ROM that is described in the hardware section is actually software instructions for the computer, loaded into the chip. It is the lowest (in terms of structure) level of software. The operating system (OS) that allows you as a user to communicate with the hardware and (hopefully) accomplish something useful with the computer is the next lowest level of software, often termed the base or foundation. In common terms, the operating system talks to the hardware for you. It also provides the "hooks" for allowing other things to join your system, such as a network, the internet, and other real world architecture. (For simplicity, I'll leave it at that since that is part 4 of the Y2K problem.) The user interface, the third level of software (technically part of the OS) that is currently in most PC operating systems such as MAC and WINDOWSXX, is the next and most visible of the levels. A graphical user interface (GUI), is what you see of the operating system; in current operating systems it would be called the desktop. In DOS it is the C:> prompt. Simplisticly, the interface talks to the OS and the OS talks to the hardware. The highest level is the application level; this is what we use to perform daily tasks. The application talks to the interface while the interface talks to the OS and the OS talks to the hardware. (Got that yet?) Also in simple terms, this level is the program that you use to do your work, such as word processing, spreadsheets, accounting and so on. Although there are exceptions, most application programs maintain separate storage and processing information concerning dates and time. Most applications do NOT utilize real time date functions that are dependant on the hardware. Some can be real time but are not totally dependant on that information. Most programmers that write applications have conformed over the years to the same format as the hardware data mapping as a matter of consistancy. There are arguments both for and against that decision. The non-conformists, a term that has often described me, seem to have come out on top on this battle. They have written day, date and time independant applications based on the Julian calendar. That method of date determination, assigns a number to each day, with day number 1 being the beginning of calculated time, AD. Date dependant functions such as accruals and interest calculations merely count the number of days between the beginning and ending assigned dates. They did NOT assume that we were only working in the twentieth century. As a rule of thumb, most of these applications are Y2K compliant since they offer the opportunity for the user to input the date for foundational processing, rather than ONLY taking it from the hardware.
   
   Most of these application programs only accumulate and process data that has been gathered and qualified by themselves. The less dependant they are on other programs, and the less dependance other programs have on them is in direct correlation as to how easy they are to fix, if they need to be fixed. The lower the level of software, the more difficult the job of fixing a problem. Since at all software levels, other software depends on what information it is given from the software levels lower than it is. This dependance procedure is a two edged sword that cuts work in some cases, but can cause a great wound as in the Y2K problem based on the age old data processing theory, garbage in, garbage out.
   
   
3. Your embedded devices
   
   Embeded devices are ROM like chips or processors that more or less perform like the ROMs in computers. They give and maintain guidelines and rules for devices they are contained within such as calculators, microwave ovens, conventional appliances, radios, TVs, automobiles, boats, cars, airplanes and the like. Some had limitations; others planned ahead. Some have information that does not care about the year. Some of these have compliance statements from the manufacturers; others do not. Most will continue to function, though they may not be compliant technically. The actual effect can only be determined by actual and physical testing instad of a theoretical guess.
   
   
4. Outside suppliers that effect you
   
   Often, as is the case with some software to other software, there is a dependance factor that you may or may not have control over. Some things that effect your life you can change, others you cannot. While you use power, water, phones and other services, you generally cannot control the actual delivery of those services other than getting them or not. The getting is a decision to use them and then paying for the service. If the power company is effected by the Y2K problem and can't deliver power to you on January 1, 2000, none of your planning or lack of it is going to matter. You may still decide to use power and are willing to pay for it but can't get it anyway. Without going into great detail, there are obvious other similar situations.
   
   It is our opinion that due diligence can and should be done by all individuals and businesses. As of this writing, most banks, finacial institutions, brokerage houses, insurance companies and service organizations have declared compliance or intention to comply (as in the case of the government). We do not feel that MOST individuals will be affected at all. There will be some irritations and some inconveniences caused by non-compliant devices. However, we do not feel that the world will end, life as we know it will stop, or even major slowdowns will happen. Life will go on and though some manual corrections will probably have to occur in various situations, January 2, 2000 will come.
   
   Our biggest concern is that the groups painting a doomsday attitude advocate making a run on banks and finacial institutions. Not only do we feel that is not needed, we feel that it will cause many problems to the financial networks of the world if that advice is followed. The world's financial networks depend on a constantly replensihing supply of cash in to supply the needs for cash to others. If cash is removed from circulation, the wheels of a well oiled financial conveyor belt will grind to a halt. If you want to do that sort of thing as insurance to yourself, do it gradually over the next twelve months. Keep most of it in circulation by buying supplies that will keep (non-perishables) as emergency rations, such as canned goods, bottled water and the like. If you are in flood or earthquake areas, that sort of emergency ration is good to have on hand anyway. When it comes around to January 1, 2000, and everything is still going more or less as it should, and all daily life is occurring reasonably well, at least the financial network of the world will NOT come to a halt because of well meaning but insecure humans, if you follow that advice. After all, what would cash do for you anyway if the buying, selling and money flow functions grind to a halt?