RemoteAccess Lost Carrier Check
                          Version 1.0
              Another Quality Freeware from Martin Woods


    RALCC will read the enviroment variable 'RA' to find RA.LOG
    to find out who is Losing Carrier and send them a message informing
    them of the consequenses of this.

    RALCC is hard coded to send a LOCAL,PRIVATE  message in the message
    base of your choosing...

    The message is contained in RALCC.MSG (sample included) and is completely
    configurable with the exeption of the first line which *Must* have:

    %FSysops Name

    as the first line,this will be read in and show up in the "From"
    field in the message.

    The Subject line is hard coded as :
    "Carrier Lost on '+Date+' at '+Time+"

    Command Line Parameters:

            RALCC [MsgAreaId]');

            Squish MsgAreaId Example = SC:\Max\Msg\Muffin');
            Hudson MsgAreaId Example = H042C:\RA\MsgBase');
            *.Msg  MsgAreaId Example = FC:\Mail');
            Jam    MsgAreaId Example = JC:\Jam\General');

         IE: RALCC JC:\JAM\LOCAL   will post the message in your JAM
         base in C:\JAM\ and use the LOCAL area description

         Note: Hudson must have 3 digits ie: H012 for area 12

   You will see the above help screen when RALCC is run with no parameters
   or RALCC /?

   RALCC will create a 0 byte file called RALCC.DAT each time it is run
   and will read this file each time to get the date of the file so it
   doesn't keep posting messages over and over,so DON'T delete it.

   Have a look at your RA.LOG first,If you have a lot of "Lost Carrier"
   in there then each of those users will get a message the first time RALCC
   is run,if you don't want to send out a hundred messages,some referring
   to a "Lost Carrier" from 2 months ago you may want to run :

   RALCC as a LOCAL run first,you can do this by running in a temp dir
   such as c:\temp and creating a bunch of *.msg :

   RALCC FC:\TEMP

   This will read the RA.LOG and create the *.MSG's (fido style) in the Temp
   dir. and also create the RALCC.DAT,you may have to do this TWICE,the first
   run will create the DAT file with a file date of 1980 (first time)
   the second run will create a DAT file with the current date...

   Delete all the *.MSG's
   Then RALCC will start at the current date.

   When To RUN?

   Actually you could run it anytime,from the command line,or after each user
   logs off or as an event that runs once a day or week...

   Where to run it?
   Put it anywhere you like,just keep RALCC.EXE,RALCC.MSG together

   What about the other Nodes?

   Fire up RACONFIG and goto System -> Paths -> System Log
   if you have this set for RA.LOG then it will create a RA.LOG in *each*
   one of your node directorys ie: \RA\RA.LOG + \RA\NODE2\RA.LOG etc etc
   up to 250 log files...

   The alternative is set the logfile as an example:
   C:\RA\RA.LOG
   Then all activity will be written to just this *ONE* file
   and RALCC will read all node activity...


   btw this program is hardcoded to read RA.LOG if you have named this
   to something else then this program will not work for you.
   If this is a problem let me know and I can change the code to read
   "LogFileName" as it is entered in CONFIG.RA


                                             -Martin