ftp.wwiv.com/ftp.wwiv.com.zip/ftp.wwiv.com/pub/BBS/SF32_1.ZIP/SF31_32.ZIP/SF31_32.DOC

Text File | 1992-03-20 | 12KB | 232 lines

                                 SF31_32
                               Version 1.0
                    Copyright (C) by Mike Woltz, 1992
                          Buffalo Creek Software
                               A Member Of
                 The Association Of Shareware Professionals



            SF31_32 is a SPITFIRE utility written to simplify the
       conversion process of upgrading from SPITFIRE v3.1 to SPITFIRE
       v3.2.

       Begin by placing SF31_32.COM in each SPITFIRE HOME directory
       per node and executing it.

       Messages will appear on the screen as it works to update
       system and work files to SPITFIRE v3.2 format.  SF31_32 will
       convert SFNODE.DAT, SFFAREA.DAT, SFMCONF.DAT, SFSYSTEM.DAT,
       and SFUSERS.DAT.

       Once this is completed, SF31_32 will display messages that
       inform you what additional steps YOU MUST TAKE to complete the
       conversion process.  Follow these steps closely!

       For your convenience, those steps are also listed here for reference.


       SPITFIRE version 3.2 uses a different format within DAILYLMT.DAT!
       The old format will not work!  You MUST alter your DAILYLMT.DAT file!
       Buffalo Creek Software has provided a utility (DAILYLMT.COM) for the
       purpose of creating and maintaining your DAILYLMT.DAT file.

       When files are uploaded using an external file transfer protocol,
       SPITFIRE version 3.2 moves uploaded file(s) to the appropriate File
       Area!  Therefore, you MUST alter all of your SFEXTUP<x>.BAT files so
       that they are NOT written to move the files out of your EXTERNAL
       directory to a File Area.  Such uploads will NOT work properly if
       you do not alter your batch files!

       SPITFIRE version 3.2 provides a new feature regarding downloads using
       an external file transfer protocol.  We strongly suggest that you study
       the SPITFIRE manual to learn about the use of "Usefile" in your
       SFEXTDN.BBS file!

       You must overwrite your current SPITFIRE.EXE and SPITFIRE.OVR files
       with the version 3.2 SPITFIRE.EXE and SPITFIRE.OVR files.  Further,
       you must place SFCALLOG.DAT (distributed with version 3.2) in your WORK
       directory!

         ENJOY!!!


      NEW FEATURES IN SPITFIRE 3.2
      ----------------------------

      File Tagging is supported by SPITFIRE v3.2.  When listing files
      each file is preceded by an alpha character with the exception of
      <S>, which is used to Stop the display.  Callers simply enter the
      alpha character preceding the file description.  After selecting
      the download option from the File Menu, SPITFIRE will automatically
      insert the name(s) of the file(s) tagged for downloading.

      Multi-line file descriptions are a new feature in SPITFIRE v3.2
      which the Sysop may optionally configure.  From the ALT+Z window, the
      Sysop sets whether the BBS will allow 1, 2, 3 or 4 line descriptions
      when files uploaded to the BBS.   It should be noted that if a file is
      uploaded for Sysop Only and the BBS is configured to use 2 or more line
      descriptions, the multi-line file description is written to HEYSYSOP.LOG.

      In addition, Sysops have the option, from the ALT+T window, of
      adding one line to the file description which credits the caller who
      uploaded the file.  An example of this would be: Uploaded by Mike Woltz.

      Multi-word text search is available from the Message and File Menus.
      A caller may enter up to six key words.  SPITFIRE uses these key words
      to locate the desired text in a message or file description.  If a
      key word is located in a message, SPITFIRE will display the subject
      of the message.

      SPITFIRE through the use of the companion utility, SFSENDIT, allows
      a special file to be downloaded by a specific caller or callers with a
      specific security level.  When the caller logs on to the BBS, he/she is
      notified that the file is awaiting them and given the option to download
      the file.  SFSENDIT is included with SPITFIRE v3.2.

      The DAILYLMT.DAT file format has been modified.  DAILYLMT.COM, also
      included in with SPITFIRE v3.2, is a menu-driven utility which easily
      allows the Sysop to create or modify their existing DAILYLMT.DAT file.
      New parameters in DAILYLMT.DAT, if appropriately defined, allow
      SPITFIRE to monitor and adjust a caller's security when a required
      upload/download file transfer ratio is violated.  Similarly, SPITFIRE
      will return the caller to their original security once the required
      upload/download ratio requirement has been satisfied.

      The format of SFDOOR.MNU has also changed, although SPITFIRE will
      recognize both the old and the new format.  An example of the new
      format might look like any of these:

      Guess A Number,SEC>=10
      Guess A Number,SEC=10
      Guess A Number,SEC<=10

      The line begins with the title of the door followed by the security
      parameter.  SEC>=10 would require a security greater than or equal to
      10, SEC=10 would require a security equal to 10 and SEC<=10 would
      require a security less than or equal to 10.  SFDOOR.COM is included
      in the SPITFIRE package.  It is an easy to use, menu-driven utility
      that allows the Sysop to create or modify their existing SFDOOR.MNU.

      SPITFIRE now provides a toggle (ALT+T window) which allows the
      Sysop to configure whether a caller is required to enter their password
      when returning from a door.

      A new work file, SFCALLOG.DAT is to be placed in the SPITFIRE work
      path.  SFCALLOG.DAT contains information which is used when writing to
      the caller's log.

      When external file transfer protocols are used, SPITFIRE automatically
      handles moving files to the appropriate directory.  This simplifies the
      batch files needed for external file transfers.  For instance, a sample
      ZModem batch file might look like this:

      BRK OFF
      ECHO OFF
      CD\SF\EXTERNAL
      DSZ.COM %2 rz
      CD\SF
      BRK ON

      SPITFIRE can also be configured to create a text file in your EXTERNAL
      directory which contains a list of the files to be downloaded, provided
      the external protocol is capable of reading the text file (for instance,
      DSZ.COM).  By using the file list, the path and name of each file is
      stored in the text file.  Using the text file allows up to 99 files to
      downloaded per batch.  When using the text file option, the file(s) are
      downloaded directly from the download file path.  This eliminates the
      risk of running out of disk space since the file(s) no long have to be
      copied to the EXTERNAL directory.  A ",USEFILE" should appear at the end
      of the protocol menu in SFEXTDN.BBS.  For example.

      <A> ZModem Batch,Batch,UseFile

      would take advantage of the text file download feature.  A sample batch
      file might look like this:

      BRK OFF
      CD\SF\EXTNOD1
      DSZ.COM %2 sz @C:\SF\EXTNOD1\SFEXTRAN.LST
      CD\SF
      BRK ON

      When exporting messages or capturing a chat, SPITFIRE gives the Sysop
      the option of sending the message or chat capture to a printer, provided
      a printer is attached and ready to go.

      SPITFIRE allows a file area to be configured as a "FREE" file area.
      When a file area is configured as a "FREE" file area, the caller's
      statistics are not updated when downloading files from this area.
      In addition, each file area contains a "Search File Area" field
      that is set to determine whether the file area will be included
      when searching for new files.  If toggled to Yes, the file area is
      searched and if toggled to No, the file area is skipped when listing
      new files.

      Some significant changes have been made in the Sysop Page feature.
      There are two more display files.  SFPGOFF.BBS/CLR will display to
      the caller if the Sysop has the Page feature turned off.  If the Sysop
      has the Page feature turned on but does not answer the page, then
      SFUNANS.BBS\CLR is displayed to the caller.  If a page goes unanswered
      and the caller continues to page the Sysop, SPITFIRE will not notify the
      Sysop of the additional pages, provided SPITFIRE finds SFPAGED.CLR/BBS
      in the display file path.  If the Sysop wishes to be paged multiple
      times, SFPAGED.BBS/CLR should not be used.  The length of time SPITFIRE
      sounds the page has been increased to 15 seconds.  If the page is not
      answered, [ CHAT REQUEST ] will blink in the caller information banner.

      The Sysop can now configure from the ALT+T window whether SPITFIRE
      will "Test Files Upon Boot".  This option is specifically included for
      BBS's that handle a large number of message conferences.  If this is
      toggled off, no tests are performed on the various message base files.
      It is highly recommended that this be toggled on, to ensure all the
      files are in working order.

      Another new toggle from the ALT+T window determines whether a caller
      who is being logged off due to password failure will be allowed to leave
      a comment to the Sysop, prior to SPITFIRE logging the caller off the BBS.

      When a caller changes to a new Message Conference, SPITFIRE will ask
      the caller if he/she would like to read messages in this conference.
      When a caller changes to a new File Area, SPITFIRE will ask the caller
      if he/she would like to list files in this area.

      The Sysop can now configure, per Message Conference, the maximum
      line length of messages saved in this conference.  Acceptable values
      range from 25 to 99 lines.

      A caller with Sysop security has the ability to copy a message from
      one conference to another.  This option also provides the flexibility
      of addressing the message copied to another caller.

      There are two new options in the <A>lter Conferences menu.  These
      include <I>...Include All Conferences and <R>...Remove All Conferences.

      When searching for a caller on the BBS, SPITFIRE will prompt for
      a full or partial name to be entered.  SPITFIRE will display any
      matches to a partial entry and prompt whether this is the caller
      from whom you are searching.  If N is entered, SPITFIRE will continue
      to search until a match is found or report that no satisfactory
      match could be found.

      A number of changes have been made in regard to CD-ROM file areas.
      SPITFIRE will skip over any file area marked as a CD-ROM file area,
      when listing for new files.  File statistics are not displayed
      after listing new files if a CD-ROM file area exists, since these
      file area(s) are skipped the file statistics would not be accurate.

      From the modem configuration window, the Sysop can configure a
      break length in the modem initialization string.  For each tilde (~)
      found in the string, SPITFIRE will pause according to the break length
      configured here.  1000 equals 1 second, 500 would be half a second,
      250 would be a quarter of a second, etc.

      The Drop To Dos password is no longer visible from the ALT+Z window.
      Only astericks display, providing tighter security for the BBS.  Should
      the Sysop forget the password, it will need to be reconfigured.

      This by no means, includes all the changes in SPITFIRE v3.2.  It is
      merely an attempt to highlight the most significant changes in this
      version.