Beijing Paradise BBS Backup/PARADISE.ISO/software/BBSDOORW/RAMAN210.ARJ/WHATSNEW.210

Text File | 1993-04-22 | 8.9 KB | 190 lines

                RemoteAccess Manager 2.10 - April 22, 1993
                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

                        Changes from 2.10/GAMMA
                        ~~~~~~~~~~~~~~~~~~~~~~~
 * Fixed bug where it would not increment the number of posts in the MSGACT
   option.

 * Fixed bug where MSGACT would return a runtime error if you had an old
   RAMAN.MSG file laying around.

 * Fixed bug which caused the DAILY, WEEKLY, MONTHLY maintenance to not
   execute automatically unless you had a certain combination of options
   turned on.

 * The options to create Top/Low user bulletins and Top/Low files bulletins
   now use a memory based sort rather than a disk-based sort.  This will
   eliminate the need for workfiles which were filling up hard drives with
   great regularity, and also increases the speed several thousand percent.
   (quite literally)  The one drawback is that, for now, you may only have
   a maximum of 100 users/files listed, if that is considered a drawback
   at all since most use this as a top 10 or top 15 listing anyway..

 * If RAMAN finds a virus, it will now post a message to the Sysop
   informing him/her about this.  The message is posted in the area you have
   defined in RAMANCFG as the 'Post area'.

 * If a virus is found in a file, RAMAN will exit with errorlevel 1.  This
   makes RAMAN's SCANB option ideal for running as the virus scanner via
   RA 2.0's new option to scan uploads for viruses, especially since it will
   not flake out and return non-zero errorlevels on GIF's and uncompressed
   files.

 * Added an IMPORTALL parameter. (only available as a command line parameter)
   This switch will attempt to locate a FILE_ID.DIZ or DESC.SDI file for each
   file in your file database.  If one is found, the description will be
   replaced with it.  If not, the original description will be retained.  It
   is recommended that this only be used once as it will take a considerable
   amount of time to run obviously.

 * Added a KILLHEAD parameter. (only available as a command line parameter)
   This switch will remove any and all headers from your file database.  You
   can use this if you decide you really didn't want headers in your listings
   after all, etc.

 * Added a RESTORE parameter. (only available as a command line parameter)
   If you are using RAMAN's option to make a backup of the file database, this
   option will restore the database from those backups.  Use this if the
   database becomes corrupted for whatever reason.

 * Added a %COST macro for the ADDHEAD option.  If the default cost for the
   current file area is greater than 0, this macro will be replaced by that
   value.  If the file area is marked as free, this macro will be replaced by
   the word 'FREE'. (no quotes, of course)

 * Added a %MEDIA macro for the ADDHEAD option.  If the area is on CD-ROM,
   this will be replaced by 'CD-ROM'.  If it is on the hard drive, it will be
   replaced by 'HARD DISK'.


                           Bugs fixed from 2.01
                           ~~~~~~~~~~~~~~~~~~~~
 * Updated RAMAN to work with RA 2.0/GAMMA.  This version will not work
   with any version of RA previous to 2.00/GAMMA-1.

 * Fixed problem with RAMAN not padding a '0' on single digit dates/times.

 * Fixed problem with -REARC reporting that it could not remove a work
   directory.  In many cases, this was a false report.  In the few
   legitimate cases, this should be fixed, especially when running over
   a network.

 * Fixed bug in the COMMENT option where it would report incorrect file
   names when adding comments to ZIP files.  The comments would be added to
   the right file, but it would be logged incorrectly.  This was limited to
   ZIP files, ARJ worked fine.

 * Fixed bug where RAMAN would write incorrect information to your daily
   upload/download bulletins if you use a Type 15 exit.


                          New options from 2.01
                          ~~~~~~~~~~~~~~~~~~~~~
 * ADDCOUNT has been removed, it's simply obsolete with the new RA.

 * RAMAN now uses a user-configurable file header.  The header to be added
   to the top of your file listings is contained in RAMAN.HDR which must be
   located in your RAMAN system directory.  A sample is provided in this
   archive.  The following macros are currently supported:

   %SYSOP     - Sysop name or "Unregistered" if applicable
   %BBS       - Name of your BBS
   %FILES     - Number of files in this file area
   %BYTES     - Number of bytes in this file area
   %AREA      - Name of this file area
   %AREA#     - Number of this file area
   %LDATE     - Date in a long format, i.e. January 01, 1993
   %SDATE     - Date in a short format, i.e. 01-01-93
   %12TIME    - Time in 12 hour format
   %24TIME    - Time in 24 hour format
   %DLS       - Number of files downloaded from this area

   These commands are not case sensitive.  When replacing the macros with
   the actual information, RAMAN will center each line and resize each line
   to prevent over-runs.


 * Added a switch to supplement the ARCLOG option.  With this switch enabled,
   after archiving your logfile, RAMAN will add the archive to another archive
   whose filename is the month/year.  For example, RA011793.ARJ would be added
   to an archive named RA0193.ARJ.  This allows you to keep your logfiles
   bundled according to month.  A supplementary switch allows the first
   archive to be deleted after being added.  This is in RAMANCFG under
   Options.Other_Options.  The same thing can be done with the user file
   backups as well.

 * RAMANCFG now has a slot to specify a 'Work Directory'.  This is the
   directory where RAMAN will create most of it's temporary work files in
   options such as the top/low files and top/low users bulletins.  It is
   possible to significantly increase the speed of such options by
   specifying the work directory on a RAM drive as these options, in
   particular, rely on a disk-based sorting algorithm.  If you do decide
   to use a RAM drive, be sure it is large enough to accomodate the work
   files.  The larger your system, the larger the files.  This is found
   under Paths.System_Paths.

 * After reading the configuration file, RAMAN checks each path against
   reality.  If the RAMAN System path is invalid, RAMAN will halt.  If any
   of the other paths are invalid or any bulletin path/names are invalid,
   RAMAN will substitute valid names and make a note about it in the logfile.

 * If there are certain files you do NOT want rearchived under any
   circumstances (RA_111.ARJ for example, since Andrew asked that it not be
   rearced), you can list these files in a file called NOREARC.CTL which is
   located in the RAMAN system directory.  You need only put the filename,
   not a full path+filename and it is not case sensitive.  Wildcards are
   currently not allowed.  A sample file would be:

    RA_111.ARJ
    GE_100.ZIP
    FD202.ARJ
    RA_200G1.ARJ

 * If there are certain files you do NOT want in archives, you can list
   these files in a file called TRASH.CTL.  When RAMAN rearchives files, any
   file in the archive which is found in TRASH.CTL will be deleted prior to
   re-archiving the file.  Wildcards are not allowed.  A sample file would be:

    AD.ANS
    CALLNOW.TXT

 * The ADDMSNG option can now, rather than use the missing description string
   defined in RAMANCFG, import a FILE_ID.DIZ or DESC.SDI description file.  If
   you have this option turned ON, it will do the following:
     1) Attempt to extract FILE_ID.DIZ and DESC.SDI from the archive
     2) If one of these files is found, it will import it as the description
     3) If neither file was extracted, it defaults and uses the string defined
        in RAMANCFG.

 * New option in RAMANCFG to use handles instead of real names in the
   top/low user bulletins.

 * New option to create a bulletin of the top and least X downloaded files on
   your BBS.

 * New option to create bulletins of users with the least number of calls,
   posts, uploads, and downloads.

 * Added a PACK option (parameter is PACK, also available in RAMANCFG).  This
   option will have RAMAN physically remove entries with the DELETED bit set
   in the file database.  This is equivalent to RAMSG's Pack option, but this
   applies to the FDB instead.

 * Changed the ORPDESC keyword to KILLORP.

 * Reworked the ABC option.  ABC is now much smarter than it was
   in previous versions of RAMAN.  Instead of tearing comments from the
   file listings, ABC now recognizes comments.

 * RAMAN will recognize descriptions which are up to 16384 characters long.
   The exception is that the Allfiles/Newfiles option will only recognize
   up to 255 characters for this release.

 * FREQCOUNT will only consider an entry a File Request if the FREQ keyword
   is in a line preceding a Sent: line.  This is applicable to FrontDoor
   only as far as I can tell.


EOF (WHATSNEW.210)