          *****************************************************************
          **********************   UPDATES TO Y2KWA   *********************
          *****************************************************************
          
               Since its first release on 17 May, 1999, Y2KWA has undergone 
          the following upgrades:
          
          Version 1.1, released 27 May, 1999:  
               When the user invoked the options menu during the count-down 
                 and  then  selected  the help display  the  program  would 
                 terminate.  Thus, if Y2KWA were run from the  AUTOEXEC.BAT 
                 file,  as is intended, the help display would  appear  but 
                 then the batch file would continue running.  Now, the help 
                 display appears and returns you to the options menu.
          
          Version 1.2,  released 11 June, 1999:  
               Now it is easier to exit the count-down.  Instead of  having 
                 to press [Ctrl]+[Break] just the [Esc] key is pressed.
          
               The alarm no longer sounds every time the count-down starts.  
                 I received a few complaints on this.  It still sounds  the 
                 alarm  when  a leap day has been trapped and  the  program 
                 pauses to alert the operator.  Also, when invalid  command 
                 line arguments have been used an alarm sounds so the  user 
                 can be alerted.
          
               When  the  user  chooses to re-enter the date,  there  is  a 
                 reminder to use a four-digit year.  Using a two-digit year 
                 will cause the system to default to the 19xx format.  This 
                 is because Y2KWA uses the system's DATE command to let the 
                 user set the date.
          
          Version 2.0, released July 1, 1999:
               When  user  is prompted to set the date,  rather  than  just 
                 going to DOS' DATE command, a more user friendly method is 
                 provided.
          
               Now,  Y2KWA  knows  the names of the  months.   Whenever  it 
                 displays  a  date, it uses the  format  DD-MonthName-YYYY. 
                 That way confusion between European style DD-MM-YY and  US 
                 style  MM-DD-YY is avoided. Is there an African, Asian  or 
                 Australian style?  Either way, the display Y2KWA uses  now 
                 should be clear as long as one knows enough English.
          
               Handling  of leap-day conflicts, the real big change.   When 
                 Y2KWA  halts in default mode over a conflict, it offers  a 
                 choice  of  likely dates to the user.  The user  can  also 
                 choose the Option menu at that time if for some reason the 
                 dates  offered are incorrect.  If the L switch is used  in 
                 the  command line Y2KWA will not halt but go  into  count-
                 down before setting the most likely date.  The most likely 
                 date is based upon the idea that a person would chose this 
                 switch  if he customarily booted his computer  every  day.  
                 Even  if he does so less frequently, I believe it will  be 
                 correct.   The only problem I can think of is that if  the 
                 computer  has  to boot more than once on  29  Feb.  (power 
                 failure, for example) it will then be set to 1 Mar. on the 
                 second time. I have not been able to figure a feasible way 
                 around that.
          

               Because  Y2KWA has experienced a fundamental change  in  the 
                 way it functions it has now jumped to version 2.0
          
          Version 2.1, released July 7, 1999:
               The "smarter" this program gets, the easier it is to miss  a 
                 small error in writing its code.  A few days after releas-
                 ing  version 2.0, I discovered that it was trapping  every 
                 transition from February to March on a non leap year  even 
                 when there was no conflict to trap.  I had made a  mistake 
                 in  writing a "switch" statement in the part that  handles 
                 conflicts.   Instead of breaking out of that part when  it 
                 calculated  there was no conflict, it went on  to  execute 
                 code  for the case where a conflict existed during a  leap 
                 year.   This mistake would case version 2.0 to favor  set-
                 ting  the  system to a wrong date on the  above  described 
                 cases.   Just one line of code that says "break;" was  all 
                 that  was  needed  to correct this and  move  the  current 
                 version of Y2KWA up just one notch. 



