
  KNOWN PROBLEMS

  The following is a brief list of known problems with Sir Gareth.  These
are all being addressed with urgency.

 Grail Crashing and/or Losing data

There have been NO instances of lost data or corrupt files found through
the use of Sir Gareth and its interaction with The Holy Grail in many
weeks of testing and development.  However, it should be considered
naive to run this program during evaluation without BACKING UP YOUR DATA
FILES!!!!

 Ampersands and Underlines in Screen Text:

The current method of data extraction does not take into account the use 
of the ampersand, (&), for denoting an underlined character.  We are 
writing a subroutine that will rectify this problem.

 Low Levels of BBS Activity in the Usage Chart
 
GRAIL does not by nature, take into account the use of PDQDOWN or other 
Terminal program downloader.  If you have a large number of callers using 
your DOS downloader, this will result in low charting results.  We are 
looking into ways of attaching the log files from various methods of 
Terminal downloading in order to correct this.  A previous problem, the
undocumented log instance of a new user logging on, has been dealt with,
and a remedy found.

 No EOF in Grail
 
GRAIL data files do not use a traditional End Of File condition to mark 
the last entry in a data file.  There are also 'holes' where data once 
existed but was removed.  To overcome this we loop to a predetermined 
number of blank requests before deciding that there is no more data to 
collect.  This method is inefficient and can be ineffective.  We are 
exploring methods of predetermining the 'holes' before data compilation.

 Command 'Lockouts'
 
Although there are a few commands that are seemingly 'locked out' from 
use, this is not a crippled shareware version.  The commands not in use 
were disabled in order to provide a reliable market product from which
we could discern the amount of interest in third party applications.
Maintenance releases will be shortly forthcoming with these commands
enabled, and other features added.
 
 Speed
 
Sir Gareth was written and compiled in a Windows Database language.  The 
reasoning behind this was very simple.  Although the program is 
comparitively slow, the database engine was included in the price of the
compiler.  If enough interest is shown by way of the registration of our
product, we plan to acquire a database engine compatible with our copy of
Borland's new C++ version 4.0 and rewrite Sir Gareth into that language
with many expanded features.

Registration information may be found on the accompanying text files 
REGIST.TXT and LICENCE.TXT.
