===========================================================================
== Appendix A - Finding Perl
===========================================================================

Before any Perl script can work, you need to tell the script where the
Perl interpreter is held on your system (this step may not be necessary
on all systems - RISC OS users can just set the file type of scripts
to 'Perl (102)').

If you don't know where the Perl interpreter is held on your webserver,
then you could ask your servers administrator or try and find it out
for yourself.

To do this, use a telnet program to connect to your webserver and logon
as prompted. Once you are at a 'command line', enter the following text:
 which perl
The server should return something like:
 /usr/bin/perl
This is the path to your Perl interpreter. If you can't find Perl and
don't think it is installed, then ask your server administrator to
install Perl for you. On *no account* install Perl yourself in either
your cgi-bin or in the same directory as your html files - this creates
an extremely large security risk and is not recommended. Also, the
Perl files tend to be quite large so you'll also be consuming your
valuable disk space.

===========================================================================
== Appendix B - Setting file permissions
===========================================================================

Either use your FTP program to do this or a telnet session. Go into
the directory containing the script and you need to make sure visitors
can run the script. How to do this various from setup to setup, but
here is a rough guide:

- Posix compatible systems (UNIX, Linux, BSD etc)
  You need to make the script 'group and world readable and
  executable'. You can do this via the 'chmod' command.

  The english version of the command is:
   chmod gw+rx pod.cgi
  Where it will add 'r'ead and e'x'ecutable rights to the 'g'roup and
  'w'orld for pod.cgi. If this command doesn't work, you may have to
  use the less understandable octal version, thusly:
   chmod 0755 pod.cgi
  which does the same thing.

  Do not set the script to group or world writable - as this will
  give visitors the ability to overwrite your script.
  
- Windows systems
  On Windows servers you may also need to associate .cgi extensions with
  the Perl interpreter.
  - WebSite
    Place your scripts in the cgi-shl directory

- RISC OS systems
  You need to ensure that the file access parameters are set to:
   Locked      NO
   Owner read  YES   Owner write  YES
   Public read YES   Public write NO
  And that the filetype is set to &102 (Perl).
  - Netplex
    If you are running NetPlex you need to ensure that it is set to
    use 'UNIX-style cgi variables'. NetPlex needs scripts to reside
    in a directory called cgi-bin
  - WebJames
    The cgi-bin directory needs to have the attributes 'is-cgi'
    and 'cgi-api=redirect' set.