              ____  _  KiwiSoft Virus                 
             / ___|| | __ _ _   _  ___ _ __   ___ ___   ___  
             \___ \| |/ _` | | | |/ _ \ '__| | __/ _ \ / _ \
              ___) | | (_| | |_| |  __/ |    | _|  _  | (_) |
             |____/|_|\__,_|\__, |\___|_|    |_||_| |_|\__\_\
                            |___/  v0.63 RELEASE      
_____________________________________________________________________________

                         Revision 6 - 16 Jan 2000

      This document is best viewed with 77 columns (ie Zap's default)

** Questions answered in this file

   Q1: Why should I use Slayer over other similar products?
   Q2: Why doesn't Slayer claim to detect as many viruses as other
       similar products?
   Q3: What happens if I find a bug, somthing I don't like, or have a
       suggestion about Slayer?
   Q4: What should I do if I find a virus on my computer?
   Q5: What sort of hardware do I require to run Slayer?
   Q6: How secure is Slayer in a school environment?
   Q7: What filing systems has Slayer been tested with?
   Q8: What viruses families can Slayer detect and remove?
   Q9: Can I use Slayer's features in my own software?
  Q10: Who was involved in the Slayer project?
  Q11: How can I contact Kiwi Software?
  Q12: What is planned for future releases of Slayer?
  Q13: Why doesn't Slayer expire?
  
If you have a question that is not answered here, please refere to Q11 on
how to contact us.
_____________________________________________________________________________
       
** Q1: Why should I use Slayer over other similar products?

   A1: We like to think that Slayer is faster, more flexible and
       easier to use than other anti-virus tool available for
       RISC OS.  It also boasts a far more comprehensive feature
       list than any other available virus killer for RISC OS, and
       even surpasses many available on the PC.
       
** Q2: Why doesn't Slayer claim to detect as many viruses as other
       similar products?
       
   A2: We decided at the very start of the development of Slayer, that
       we wanted it to be as speedy as possible.  One of the ways we
       achive this is by not scanning for viruses that are no longer in
       the wild, or are extinct.  We also do not add support for viruses
       that we our selves have not 'seen', as there is a danger of many
       false alarms.  We believe we have collected a large percentage,
       if not all RISC OS viruses in the past 4 years.
       
** Q3: What happens if I find a bug, somthing I don't like, or have a
       suggestion about Slayer?
       
   A3: Don't whinge to your friends, whinge at us.  We feel that we have
       implemented every feature that we deem useful, and have done so
       properly and efficently.  If you think differently, please contact
       us.
       
** Q4: What should I do if I find a virus on my computer?

   A4: First of all, scan your computer for viruses with Slayer if you
       havn't already.  If Slayer fails to detect the virus, send us a
       sample of it, either via snail or electronic mail.  We are normally
       able to return an updated version of Slayer's virus detection engine
       the next day that can detect and remove the virus safely.
       
** Q5: What sort of hardware do I require to run Slayer?

   A5: Slayer will run on any RISC OS 3 desktop computer.  It works on a
       1MB machine with no problems.
       
** Q6: How secure is Slayer in a school environment?

   A6: Hopefully, very secure.  You can password protect the 'big' iconbar
       menu, and it implements disc authorisation, so only authorised
       floppy discs can be used.  Slayer's 'Chaperon' technology prevents
       many viruses and even users from being able to detect or remove it
       from memory.  It can even help to stop it's deletion from the drive
       it is running on.  It is not however, secure before it fully starts,
       as this is not really possible in the case of RISC OS.
       
** Q7: What filing systems has Slayer been tested with?
   
   A7: Slayer should work with any FileCore or Image filing systems.  The
       following list shows the systems that we /know/ work;
       
       Alsystems ZIPFS 1.48 		  RISC OS 3.6, 3.7, 3.8
       ATAFS 1.94			  RISC OS 3.6
       Argo IZipFS 1.00a		  RISC OS 3.5, 3.6, 3.7, 3.8, 4.02
       ADFS				  RISC OS 3.0, 3.1, 3.5, 3.6, 3.7,
                                                  3.8, 4.02
       RAMFS				  RISC OS 3.0, 3.1, 3.5, 3.6, 3.7,
                                                  3.8, 4.02
       SCSIFS (SoftSCSI CD-ROM)	          RISC OS 3.5, 3.6
       IDEFS 3.20			  RISC OS 3.6
       IDEFS 3.23			  RISC OS 3.6, 3.8
       IDEFS 3.24			  RISC OS 3.7, 3.8
       Resources			  RISC OS 3.0, 3.1, 3.5, 3.6, 3.7,
                                                  3.8, 4.02
       MemFS 2.11			  RISC OS 3.0, 3.1, 3.6, 3.7, 4.02
       MemFS 1.08			  RISC OS 3.1
       ArcFS 0.73a ro	    		  RISC OS 3.6, 3.7, 3.8, 4.02
       raFS 1.10 to 1.15                  RISC OS 3.6, 3.7, 3.8, 4.02
       DoomFS 1.04, 1.09		  RISC OS 3.6, 3.7, 3.8, 4.02
       StrongHelp 2.60			  RISC OS 3.6, 3.7, 3.8, 4.02
       X-Files 0.58			  RISC OS 3.6, 3.7, 3.8, 4.02
       SparkFS 1.32                       RISC OS 3.6, 3.7, 3.8, 4.02
       CFS 1.10                           RISC OS 3.6, 3.7, 3.8
       CacheFS 0.21                       RISC OS 3.6, 3.7, 3.8, 4.02
       MacFS 1.07                         RISC OS 3.6, 3.7, 4.02
       PocketFS2                          RISC OS 3.6, 3.7, 4.02
       PsiFS 1.00                         RISC OS 3.6, 3.7, 4.02
       
** Q8: What viruses families can Slayer detect and remove?

       Slayer detects what be believe to be the majority, if not all
       viruses that are in the wild today.  Look in the !Viruses file
       for a list of known viruses, and the ones that Slayer can detect.

** Q9: Can I use Slayer's features in my own software?

   A9: Slayer provides SWI and Wimp Message chunks, and the format for
       the various plug-ins allow you to add virus protection to your
       own software.  For more details, and information about obtaining
       a licence, please contact us.
       
**Q10: Who was involved in the Slayer project? 

  A10: Many people have contributed to the Slayer project over the past
       three years.
       
       Luke Graham & Rob Kendrick of Kiwi Software (UK)
        The main brains behind Slayer.  You can blaim most things on this
        pair, including DeHackEd...
        
       Graham Allen of The Page Designer
        Did most of the ground work for Slayer's networking.  This has since
        been taken over by Rob, due to Graham working himself to death. 
        
       Paul Vigay of Digital Phenomena
        Lots of virus samples
	       
       Richard Murray
        Virus samples
        
       Pineapple Software
        Virus samples, and a reason. :-)
       
       Marc Warne of Alpha Programming
        Virus samples
 
       Jonathan Brandy
        Virus samples
 
       Alisdair McDiarmid of Illusion Software
        For putting up with Rob's constant banter, and a couple of bug
        reports.
       
       Justin Fletcher of Prolific Software Products :-)
        For the wonderful HeapLib and DispLib - two key libraries in Slayer.
        Also, for supplying an excellent method of stress relief.
 
       Thomas Olsson
        For the loverly SlotMachine memory manager, that eventually replaced
        Justin's HeapLib, and for LIRC.	
 
       Theo Markettos
        Various suggestions
        
       Cam Gregory aka Fonz
        The winner of 'the most annoying beta tester' award.  He kept
        reporting bugs.  Loads of them.  We've shut him up now though. :)
        
**Q11: How can I contact Kiwi Software?
       
  A11: You can email us at;
        slayer@page-designer.co.uk
        
       You can visit our website at;
        http://www.kiwisoft.co.uk/
       
       You can visit Slayer's website at;
        http://www.kiwisoft.co.uk/software/slayer/
        
       You can fax us at;
        +44 (023) 80846431
        
       You can post gifts such as money and food to;
        Kiwi Software (UK)
        12 The Quantocks
        Dibden Purlieu
        Southampton
        Hampshire
        SO45 5QU
        ENGLAND.
        
       If you wish to contact one of the authors directly; here are some
       email addresses you should use (in order of preference)
       
       Rob Kendrick (Scanning engine, SlayerScript, most of the poncy bits)
        rob@kiwisoft.co.uk
        unciscy@eh.org
        
       Luke Graham (Virus removal, finger printing, most of the WIMP code)
        luke@kiwisoft.co.uk
        quango@eh.org
        
       Graham Allen (Networking)
        graham@kiwisoft.co.uk
        xyra@eh.org
        
**Q12: What is planned for future releases of Slayer?
       
  A12: We are intend to add the following features to Slayer in future
       releases.  If you have any other suggestions, please refere to Q11
       on how to contact us.
       
       * Expand on Disc Authorisation
       * Better and more specific virus load line checking
       * Zap/StrongED mode for SlayerScript
       * Make finger print aquisition more flexible
       * CLI version (suitable for pre-desk) 
       * Different user levels from beginner to expert.
       * Better intergration with the Filer
       * Multiple scans
       * Universal plug-in format
       * Bypass FSLock for removal of viruses
       * Make Heuristic scanning a plugin, and return 'worry' levels
       * Make SlayerScript more flexible, and byte-compiled.

**Q13: Why doesn't Slayer expire?

  A13: Because you paid good money for it.  Would you expect a word processor
       or drawing application to stop working every couple of months, and
       you have to buy it again?
       
       Slayer will say that it is getting rarther old, but it won't stop you
       from running it.  You should note, however, that even though virus
       updates are available for download by anybody, new updates will not
       always work with old Slayers.
       
       