Click above to get retro games delivered to your door ever month!

       PROTOCOLS  -  The   protocols   section   deals   with   the
       different  transfer  methods  used  by RemoteAccess  to send
       and receive files.  This section  also allows  you to define
       any new transfer protocols that you wish to add.

       The INTERNAL PROTOCOLS   submenu  allows  you  to   disable,
       enable, or  make available only  on an error-free  (ie. MNP)
       connect, any of the six internal protocols.    MNP (Microcom
       Networking Protocol),  also known  as ARQ (Automatic  Repeat
       Request),   is  a  method  by   which  modems   can   detect
       transmission errors  and  resend  the incorrect  data.  Only
       modems which both  have MNP  facilities can use this type of
       error correction.   Since, when using MNP,  error correction
       is carried out by the modem hardware,  the software does not
       need to watch the incoming  data for errors  or wait for the
       receiving modem to confirm that it has received all the data
       correctly.   Some protocols are  written especially  for MNP
       modems and  therefore get  very fast  throughput. If you use
       such a protocol  you should  set it for "error free" connect
       only.    An  example  of such  a  protocol  in  the internal
       protocol list is "Ymodem-G".

       When  using  an "error  free"  protocol,  RemoteAccess  will
       establish whether the user is using an MNP modem by  looking
       at  the  modem  connection string  to see if  it contains an
       errorfree response code. This code is definable in RACONFIG.
       {+} Available in the registered version only.


       The EXTERNAL PROTOCOLS submenu.   This option allows you  to
       interface  up  to  fifteen  external   protocols  for   your
       users to  use,  in addition   to the six that are  built-in.

       Name       : The  NAME  field  is  the  protocol name  as
                    it  will be  displayed to the user when they
                    download or  upload.   Note if  you  use the
                    textfile XFERPROT.A??  to override the  hard
                    coded protocol selection menu then this name
                    will not be displayed to the user.

       Key        : The KEY is the keypress that should activate
                    the  protocol.  Note  that  the  KEY must be
                    unique. In other words, since [Z]modem is an
                    internal  protocol,  you  can't  use [Z]  to
                    activate an external protocol.

       Ext ctl    : Before RemoteAccess  activates the  external
       file         protocol,  it   creates  a control file that
                    tells the protocol which  files to  send  or
                    receive.  This file consists of some general
                    information  and a  list of  files,  one per
                    line.  You  may  define  exactly  what  each
                    line  looks  like.  If  you  select  EXT CTL
                    FILE,  then   RemoteAccess  will  write  the
                    information   needed   by    Opus-compatible
                    external protocols at  the  beginning of the
                    file before  the file list.   Check the docs
                    for each protocol you  install to  determine
                    whether it is "Opus compatible".

       Batch      : If  the protocol has  the capability to send
                    or receive more than one file at a time, set
                    BATCH to "Yes".

       Status     : You may  temporarily  disable  the   current
                    protocol   by   setting   its   status    to
                    NOT-AVAILABLE,   re-enabling   it  later  by
                    setting it  to  ALWAYS  AVAILABLE.   If  you
                    wish to restrict  a protocol's  use to users
                    who have connected using an error correcting
                    modem then change the status to  ERROR FREE.
                    This option  is particularly  useful  if you
                    use protocols  such as "YModem-G" which  are
                    specifically designed  for error  correcting
                    modems.    (See  the  section  on   internal
                    protocols  for a full explanation  of "Error
                    Free" connections and MNP).

       Log file   : The LOG FILE is the  full path  and  name of
                    the log  file  that  the  external  protocol
                    writes. This file contains information about
                    what files were  actually sent  or received.
                    Without this information,  RemoteAccess will
                    not  be able  to  update the  user's record.
                    Most protocols  have the facility to  create
                    a log of the files  that were actually  sent
                    or  received;  if  the   protocol  you   are
                    installing doesn't, it  is  advisable not to
                    use it.

       Control    : The  CONTROL FILE is the full path and  name
       file         of   the  control  file  that   RemoteAccess
                    creates before activating the  protocol.  In
                    order to allow the use of as  many different
                    protocols as possible, you have full control
                    over the format of  this file.

       DL/UL      : DL/UL COMMAND LINE  tells RemoteAccess  what
       command      program  name  to   execute   in  order   to
       lines        activate   the   external  protocol.  It  is
                    possible  to   insert  variables   into  the
                    command   line    using    special   control
                    characters.  For example, the string:

                           PROTNAME.EXE Send *B

                    would be expanded to:

                           PROTNAME.EXE Send 2400

                    For  a  full  list of special control codes,
                    refer  to  the description  of a Type 7 menu
                    command in the  MENU  COMMANDS  section.  In
                    addition to these codes, the # symbol can be
                    used  if the  filename  to  send or  receive
                    needs to be specified on the command line.

       DL ctl     : The DL CTL  STRING  determines  the   format
       string       of  each file entry.  Inserting a "@" in the
                    string  substitutes that  position  with the
                    file name.  For  example, if you  wanted  to
                    download  the  file  C:\FILES\FUN\CASINO.ZIP
                    using an  Opus type  external  protocol, you
                    would set the control file string to:

                          Send @

                    When the control file is created, this would
                    be expanded to:

                          Send C:\FILES\IBM\FUN\CASINO.ZIP

                    If the user were to select a batch download,
                    say  RA*.ARJ, the  wildcard/pattern match is
                    expanded to a full list  of fully  qualified
                    path and file names.

       UL ctl     : The  UL CTL STRING works in exactly the same
       string       way as the DL CTL STRING, except  that   for
                    batch uploads,  instead of  specifying   the
                    full  file name,  it  substitutes  just  the
                    path   to  the  upload  directory,   as  the
                    filenames are not known prior to the upload.

       DL/UL      : When  the external protocol has finished and
       log          control  is  returned  to RemoteAccess,  the
       keyword      log file  that  was  created  is  scanned to
                    extract  information about  what  files were
                    sent or received.  RemoteAccess  scans   the
                    file for the  UP or DL LOG KEYWORD.  As soon
                    as it finds that word, it will scan  forward
                    x number of  words to  get the  name  of the
                    file  transferred   and  a  description,  if
                    available.  To  illustrate  how this  works,
                    look at this extract from a BiModem log:

                      = 10 Sep 14:10:10 BMOD DL-B \GRAPH\VGA.ZIP
                      = 10 Sep 14:12:22 BMOD DL-B \GRAPH\MAP.ZIP

                    The DL/UL LOG KEYWORD can be any word in the
                    log  file  that  indicates the transfer of a
                    single file.  The  keyword  in  the  example
                    above should be set to "DL-B".

       Log name   : This  option determines  how  many  words RA
       word 1       scans after it finds  the UL/DL LOG KEYWORD,
                    to find the file name that  was uploaded  or
                    downloaded.  In the previous example the LOG
                    NAME WORD 1 should be  set to "1", as RA has
                    to scan ahead 1 word  after  finding  "DL-B"
                    to obtain the downloaded file name.

       Log desc   : When a user uploads,  RA can  also  obtain a
       word 2       description   from  the  log  file   if  the
                    protocol used supports description  logging,
                    and write it directly to  the  FILES.BBS. To
                    achieve this you can set the LOG DESC WORD 2
                    to the number of words RA has to scan  after
                    it finds the  UL/DL  LOG  KEYWORD.  If   the
                    protocol doesn't support description logging
                    or RA cannot find a description, the user is
                    prompted for the description.

       Example : Installing Lynx as an external protocol
       -------------------------------------------------

       Select  an  empty  protocol slot,  and enter  the  following
       information:

        Name                  : Lynx
        Key                   : L
        Extended control file : No
        Batch available       : Yes
        Status                : Enabled
        Log file name         : C:\Ra\Dszlog.Txt
        Control file name     : C:\Ra\Lynx.Ctl
        Download command line : Lynx.Exe S /*P /*B /S /H @Lynx.Ctl
        Upload command line   : Lynx.Exe R /*P /*B /S /D /H #
        Download ctl string   : @
        Upload ctl string     :
        Download log keyword  : x
        Upload log keyword    : X
        Log : Name word #     : 10
        Log : Desc word #     : 0

       (Note  the  case  of  the upload and  download  log  keyword
        entries).

       The  above  example assumes that your  system  directory  is
       C:\RA.  To complete the installation, you'll need to set the
       DSZLOG environment variable to the full path and name of the
       log file that Lynx writes:

                   SET DSZLOG=C:\Ra\Dszlog.Txt