ATTENTION  *********************************************  ATTENTION

                         B U G S    L I S T

8/13/88 - KI6LO
ADDRESSING NON-EXSISTENT DRIVES - V4.1, V4.2
STILL OPEN 8/16/88
---------------------------------------------
   Due to the fact DOS reports logical drives in the way I ask it how
 many drives, the program allways thinks there are 5 drives attached
 to the system, A thru E. While most systems have a minimum of one (1)
 floppy drive (A:) and perhaps one (1) hard drive (usually C:), this can
 present a problem. If you select drive B: and there isn't one, the program
 gets lost and gets a headache. The best way to alleviate this for now is
 to DOUBLE-CHECK your drive input statements when entering data from kybd.
 The program limits the highest drive to E in default request but you can
 enter any drive letter, so for now, just be careful. Really it's not as
 serious as it seems. All the data is protected by the way the program
 handles it.

8/13/1988 - KI6LO
DXCC CALCULATIONS ERROR - V4.1
FIXED IN V4.2
----------------------------------
    When entering the LATITUDE and LONGITUDE during the opening
  LOGBOOK initialization, DO NOT enter LONGITUDE as a even number.
  This means do not enter 37.00 or -23.00 or 54.00 or -123.00 .... etc.
  I know there are individuals who know their LAT and LONG down to
  5 decimal places and want to be exact, but if you enter a LONGITUDE
  ending with '.00', the program will most likely bomb during DXCC
  initialization. Start with LONGITUDE equal to ###.01

    If you run into this bug, the program says 'ILLEGAL ARCS IN ARGUMENT'
  and then dies. Restart LOGBOOK and select the LOGBOOK MAINTENANCE option
  on the MAIN MENU. Then select the UPDATE USER PARAMETERS option. Increase
  the LONGITUDE by another hundreths or so. What this does is to skew the
  calculation just enough to allow the checks to pass in the algorithm. I
  do not know why, but with LAT and LONG both ending in '.00', invarible
  sometime during the loop of 450+ calculations an ARCSIN will come up greater
  than one (>1). This causes the program to crash. By adjusting (fudge-factor)
  the value of the LONGITUDE, the results are moved to within limits. The
  results are close enough for our purposes of beam pointing since most beams
  have a beamwidth of 15 degrees or more, being off by a degree or two isn't
  going to drop the signal any. If all else fails, set both LAT and LONG to
  non-zero decimal values and retry.

    If you setup the LAT and LONG and initialize the DXCC database, then ADD
  to it or EDIT any position data of the entries, the error may appear again.
  You will have to reset the USER's data and reinit the entire DXCC or the new
  entries/data will be wrong. I dont think this will happen to often. I will
  try to fix the problem in the next revision.

8/16/88  KI6LO
INABILITY TO ADDRESS DIFFERENT PATHS ON HD's - V4.1
FIXED IN V4.2
----------------------------------------------------
    A slight oversight in my part would not allow the 4.1 program to
  access a different harddisk drive/path for backups,restores and creates
  of the LOGBOOK databases files. I have fixed this and tested it on
  a dual-harddisk system and mixed harddisk/floppy systems. It seems to work
  as advertised now. If any more problems with this, drop me a line.

8/16/88 KI6LO
LONGPATH BEARING CALCULATION ERROR - V4.1
FIXED IN V4.2
------------------------------------------------------
    Another of MURPHY's parctical jokes. If you are running v4.1, you will
  notice that the longpath bearing is NOT allways 180 degress opposite of
  GREAT CIRCLE bearing, as it should be. An older version of this section of
  code was linked in by mistake. It will work ok now. Also resets GC bearing at
  360 degrees back to 0 degress since they are the same and most compasses
  use 0 instead of 360.

