ftp.wwiv.com/ftp.wwiv.com.zip/ftp.wwiv.com/pub/MISC/TGFAQ_A2.ZIP/ALLTGFAQ.ZIP/ALLTGFAQ.DOC

Text File | 1997-05-03 | 43KB | 699 lines

                    ░▒▓█ Allfix Setup for Telegard FAQ █▓▒░

  *  FAQ Overview

      This document details how to setup Allfix software so it works with
  Telegard.  The primary scope of this document is to help assist on the
  basic setup and processing of allfix.  This document will not go into
  detail on many features of allfix that is left up for the reader to
  investigate by reading allfix.doc or using the online help.

  *  Why use Allfix?
      Have you ever been on a bbs and come across a echo that has alot of
  weird looking echomail like the following:

 --------------------------------------------------------------------------
 Today, Monday 21-04-97, XYZ BBS received the following files.

 Area : DFN_RPG         Comment : DFN: Role Playing Games
 -----------------------------------------------------------------------
 AB2V102A.ZIP   447,360    >>---> ARROWBRIDGE II <---<<
                        Arrowbridge II - The Guardians  of
                        Darkness, is a D&D style door.  It
                        has active combat routines, built-
                        in com routines up to 115,000bps &
                        supports multinode systems.
                        ...........and more file description....
 -----------------------------------------------------------------------------
 447,360     bytes in 1   file(s)

 Total of 447,360 in 1 file(s)

 File requests are welcome 23 hrs per day, not during Zone Mail Hour

 FREQ FILES for an allfiles listing from this system.
 Files are held in Holding directories for a few days then moved.

 Thanks, The Sysop (Using ALLFIX v4.33 build 6, "Simply the Best")

 ... Information deteriorates upward through bureaucracies.
 ---
   * Origin: Some BBS

 ---------------------------------------------------------------------
      Have you ever been on a bbs that gets a ton of files but the sysop
 or users aren't in the 'uploaded by ..' field?  But some weird name like
 the above Echo Tag DFN_RPG is?  Well then that bbs is likely connected
 to what is called the Filebone.  The filebone is just a term for a network
 system that spreads or hatches files out to various bbses from one source.
 It is similar to the Fidonet Backbone but instead of echomail its files.
 IF you want to join such a FileBone or just one file echo that someone
 you know has then Allfix is the best choice.  Why use allfix?  Well
 there are other programs out there like TICK or such but allfix is in my
 opinion the best overall and most user friendly.  It completely automates
 the process for you.  It will receive files from your uplink (where you get
 the files from) to your system then upload directly to your bbs so users
 can download them immediately.  This FAQ will show you how to setup
 Allfix to work with Telegard and process such file activities as auto
 uploading of new files to the bbs and file annoucements.  Advanced topics
 like FileFind and such are beyond the scope of this document.  The new
 (recent not really new) feature of the built in Request Processor is another
 feature not covered here at this time.

  *  Needed Materials:
     This document assumes you are using the following:
     o Telegard v3.02 (Dos version is assumed)
     o Gecho Tosser program using JAM bases for Telegard.
     o Frontdoor Front end mailer
     o Allfix v4.41 - Filename Afix_441.zip

     I am currently using 4.33 for Allfix at this time with Telegard v3.02
 (multi-line setup).  I'm using Dos 6.22, so any OS/2 questions for Allfix
 are beyond the scope of this document but should be the same thing overall.
 I'm using Desqview for my multi-tasker.  I have yet to upgrade my allfix
 to v4.41 but it is the same overall.  This document does not guarrentee
 a complete setup with your system.  I only do this FAQ to outline the
 setup of Telegard that *I* have for my system as an outline to follow
 for your system.  If any doubts backup your files.  I am setting up this
 new v4.41 version on a test copy of Telegard that I run on another computer
 so that I can follow the steps myself on setup to ensure it is proper (since
 I've not setup Allfix on my bbs in a few years ago).  If you are using
 Squish or some other tosser then I'm sorry.  This document is using info
 for and about the above data.

  * Allfix Setup
    You will see commands given in this manner like Asetup -> System Data.
  That means within the Asetup program (asetup.exe) you go to the System
  Data Option.  There are advanced topics I will touch on like if you wish
  to be a hub.  But for this document it won't be covered as extensive as
  the basic setup for Telegard.  I will only 'touch' on it so more advanced
  users can get an outline of an example setup.  For starting users only
  wishing to setup allfix for getting files then you can ignore those
  options.  Those items for advanced users will have ** near them.
    First a minor note of terminology.  Throughout the doc you will see the
  term Tick file or *.tic file.  Back when file distribution was just a
  baby the program called TICK was it.  Basically a TICK file is a file
  of parameter info that allfix reads and helps it process it.  Take a look
  at one or two when you get them.  It won't hurt you.  But basically it
  tells allfix what file is being processed, what echo it belongs to,
  any description and many other technical info.
    For any shown directories or files mentioned it is assumed you will
  make those directories or files.

    1) Step One - Basic Setup:
       If you haven't yet download and obtain the allfix archive.  I suggest
  you then unzip it into its own directory like c:\allfix.  Its a good thing
  to add this directory to your Path statement in Autoexec.bat.  Note: If you
  have limited environment space and a long path statement use something
  shorter that you will know.  For example use c:\all instead if it helps
  in every little bit of optimization.  Once you have unzipped the archive
  you will need to read the Readme.1st file inside.  Without doing so your
  lost.  Since there is a critical part in there (a password for the archive
  unzipping) in the file.
    2) Step Two - Get to know the files (optional)
       Yes, we could just jump right in and get to work but I suggest that
  you spend some time looking over the programs and files.  Skim the
  documentation.  This is a benefit in the long run since there will be
  sections of the setup program refered here and it will help you in the
  long run with pre-knowledge of those areas or key terms.
    3) Step Three - Basic Setup
       At this point you should start a basic setup of the program.  I would
  review the allfix.doc file to see what is needed on the basic setup.  The
  basic setup program is asetup.exe.  The first time you enter it will
  make you the setup config file for it.  At this point your ready to
  configure Allfix to your liking.  At this point I assume you have
  configured some basic stuff already but if you haven't that's fine.
  I only have this setup for more advanced people who like to jump ahead.
    4) Step Four - Setup
       At this point all the work is in Asetup.exe
       1.  System Data -> Address Maintenence -> Network Addresses
           If you are reading this echo (TG_SUP on Fidonet) I assume you
  probably are in fidonet.  I would enter as the Main address your fidonet
  number.  Then if you are in any other networks you should give each aka
  slot the other addresses.  For example, for myself I enter Main->1:112/91
  Aka 1-> 33:409/1 (AdventureNet), etc.  Without this info allfix doesn't
  know how to process anything.
       2.  System Data -> Address Maintenance -> Site Information
           Allfix is the basic user interface as that of Gecho and Frontdoor.
  If you are used to those products this program should be a breeze.  You
  will notice this group of items needs to be filled out.  The bbs name
  and other info should be given.  This is just like Gecho and Frontdoor's
  Site Information areas.  This is info used in file annoucements or
  templates (advanced topic).
       3.  System Data -> Address Maintenance -> Aka Matching
           This can be skipped as its not required for Telegard setup.  But
  This is a feature you can read up on and return to at a later time.
       4.  System Data -> Address Maintenance -> Domain Names **
           Same as 3 above.
       5.  System Data -> Address Maintenance -> Uplink Manager **
           This is used if you are a major file hub and YOU have an uplink
  that you send requests for new file areas or such from YOUR downlinks.
  This FAQ assumes that you are on the bottom level (a common node who
  is only getting files) and not a hub.  Therefore treat as 3 above.
       6.  System Data -> Pathnames (part 1)
           The program has got to know where things are so this is where
  we supply it the info it needs to work.  Again, its very similar to that
  of Gecho and Frontdoor.
           -> Msg Base - Skip at this time - not needed for Telegard
           -> Netmail - Important since it has to know where your netmail
  file attach messages are and such.  If your using the default Frontdoor
  settings then this would be c:\fd\netmail\.
           -> Netmail out - this is usually the same as Netmail.
           -> Inbound - This is vital because it tells where incoming
  files and *.tic files are located so allfix can process them.  In this
  example setup we'll use c:\newfiles\.  You should use the same inbound
  directory that gecho and frontdoor points to.  For example c:\newfiles\.
           -> Secure Inbound ** - usually the same as inbound unless you are
  needing extra security precautions (advanced not covered here).
           -> Outbound, Pkt In and Pkt Out not needed here - skip.
           -> Tic path ** - this is where outgoing *.tic files are placed.
  But this is if you want to be a Hub and have downlinks get files.
  But for this document you can skip it.  For myself I use c:\all\tick\.
           -> Queue path ** - This is where pass through files are stored
  until they are sent to downlinks.  For this document skip it.  For myself
  (and for those who might want to start as a hub) I use c:\all\queue\.
       7.  System Data -> Pathnames (part 2)
           -> List path ** - this is for CD-roms.  Since I do not have
  such here online I suggest skipping it.
           -> Rcvd Path - If a file is bad (lights went out during a
  transfer in FD and didn't complete coming across) or it is a orphan (ie
  doesn't have a *.tic file with it) then allfix can move it to a directory
  for later viewing or checking.  I suggest you have 2 holding directories
  for this particular function.  I use c:\all\tick\hold\ for any such files
  and it will move them here.  Of course its a good idea to check this
  directory to make sure things aren't cluttered if you use this method.
           -> Bad tics - This is the second directory I suggest.  But this
  and the previous one are not required.  They only help you out in allfix
  organization.  I use c:\all\tick\bad\ myself.  This directory will hold
  any bad ticks.  Well for example if a file and a *.tic file comes in
  that you do not have IN allfix then allfix can't do much but move it
  here.  So then at a later time when you do add that file echo to allfix
  you can reprocess allfix using a parameter (run allfix by itself to
  see the possible parameters) to re-process those files.  In the echomail
  area this would be like a bad_msgs area for Frontdoor or gecho.
           -> Dupe path - optional item but I leave mine blank so it
  will move duplicate files (say you are connected to two filebone nets
  and get the same file twice) to the Bad Tics holding directory.
           -> Auto add ** - advanced feature.  Suffice it to say you should
  read up on this it could be useful (G).  There is a program by the current
  filename called AAdd120b.zip which supports Telegard and will do nifty
  features like adding auto-added areas to allfix and TG.  Something to let
  you do some research on (G).  Homework and a quiz will be given later.
           -> Tag path ** - skip unless you want to be a file hub.
           -> Tmp Path - I have c:\all\temp\ for mine.  This is an area
  in which allfix can covert files say from zip to arj.  While I do not
  handle that via allfix some might.  However, it is also used as a temp
  directory for processing files for incoming and outgoing as well.
           -> Template - This is where your files that are contained in
  template.zip are located.  The suggested I belive is c:\allfix\template
  but myself I place them in the main allfix directory (c:\all\).  Templates
  are just a way to give flavor and spice to file reports and annoucements.
           -> Billing and Old Bills ** - Skip for this document not needed.
       8.  System Data -> FileNames
           -> Alias ** - This is a file like c:\fd\files.lst which contain
  a list of files that people can file request (FREQ) from your system.
  For this document you can skip it.
           -> Logfile - This is any record of allfix activity.  You should
  place it and name it as you see fit (for example c:\fd\allfix.log).
           -> Mgr Log ** - if your to be a hob this is any activity that
  is caused by running the areamanger like Allfix Mgr command.
           -> Echotoss - If you are using a file annoucement area that will
  go out through a local net or whatever this is useful.  It should point
  your echomail.jam file.  For example, c:\tg\echomail.jam.  However, if
  you are not using that particular feature of Telegard skip it.  This
  basically will add the new message (file annoucement post) to this file
  so when Gecho runs next it will send it out.
           -> Unwanted and Wanted ** - These files are for registered setups
  of allix.  It is an advanced feature so you can skip it.
           -> Semaphore - This is the semaphore file to affect if outgoing
  mail is created (ie file annoucements).  This is optional and may be
  skipped if you wish.  I use c:\fd\fdrescan.now for my setup.
       9.  System Data -> Origin Lines **
           If you are to setup a file annoucement system for your bbs or
  network then this should be given info.  IT is basically info to add
  to the origin line of the mail.  It can be skipped as its advanced.
      10.  System Data -> External Programs **
           The default setup here should be kept and not modified.  Simply,
  this area is used to add archiver or converter programs.  You will notice
  Scan is one item.  It is a registered feature of allfix where you can let
  Allfix Virus scan the files before uploading them to the bbs.
      11.  System Data -> External Programs -> Options
           -> Swapping method : Depending on your setup you should give it
  the best method of swapping out.  For example if you use XMS more you
  ought to give XMS priority over EMS.
           -> Redirect output - I personally have this set at Yes while
  the default is No.  Use the online help to see what it does.  Experiemnt
  to fit what you like best.  But it has no bearing overall to the setup.
           -> Virus Errorlevel, files to scan, EAC ** - The rest of the
  options here can be ignored for this setup as they are advanced.
      12.  System Data -> Global Options
           -> Log Style - You should tell it what format you wish to use.
           -> Mailer Mode - Give it the mailer you are using.
           -> Date Format - optional, experiment.
           -> Msg Compability - Fido is usually used here.
           -> Local requests ** - Advanced - can skip.
           -> Replace Extension ** - Advanced - can skip.
           -> Other options of this area - You can ignore or experiment
  they are not crucial to the TG setup.  But are added spice to help you.
      12.  System Data -> Miscellaneous
           -> Log Options - You should go in here and set what you feel
  is useful to log.  The more info the bigger the log file.  It is useful
  to have it all on for debugging the initial setup.
           -> Areamgr options ** - If you are to be a hub this will be
  the heart of your operation.  You should read about it for more details.
           -> Edit Days, Months - No need to go here default is fine.
           -> Exclude files ** - Advanced.  But Basically the jist of
  this option is say you wanted not to show that XXX*.gif is uploaded here
  you can do that for file annoucements.  Ignore for basic setup.
           -> Asetup colors - Obviously this is so you can have a better
  interface of colors.  Its not required to enter but if you wish different
  colors then by all means play with them.

                Now the easy part is over.  Now we tackle the hard part.

      13.  [Main Menu] FileFind System **
           This is an advanced section and will not be covered by the scope
  of this document.  I would suggest reading on it if interested.

                At this point I'm going to skip around the main menu.

      14.  [Main Menu] Utilities **
           IF you wish to edit the sample templates (used in file reports)
  you can do that here.  This section also allows you to export or import
  data to let others see what your setup is for debugging.

      15.  [Main Menu] Node Manager
           Since I'm assuimg you wish to get files from a uplink then you
  will need to enter here next.  This area will contain master info on
  your uplinks (or downlinks if your a hub).  I'm going to give you an
  example of my file hub.  I get files from 1:112/101 (for Fidonet Filebone
  related files).  Enter the node manager and lets insert your file uplink.
  It is assumed you at this point KNOW your hub.  If you do not then find
  one since you can't get files from thin air (G).
           -> System - This is the network address of your uplink (or if
  you are to be a hub downlink).  For me its 1:112/101.
           -> Sysop - the name of the sysop.  Its more a info to you and
  for information on allfix request reports.
           -> Route Via - Rarely used so you can skip it.
           -> Holding directory ** - Advanced but a nifty feature (G).
           -> Authorized groups - This is like Gecho. It tells what group
  (see later on group manager) the node can have access to.  For this
  case lets say Group 1 is Fidonet.  It is not defined at this point so
  we can come back to it but REMEBER to come back.
           -> Fileecho and areamgr passwords - are for security and you
  can read on which pw protects what feature of allfix if you want them.
           -> Use Aka - Keep the default here "Setup/aka matching" this
  seems to work best for this field.  It basically allows allfix to figure
  out which network the node belongs to (in this case uses setup info).
           -> File Attach status and Other mail status - If your to be
  just a node getting files then you can keep this at default.  However,
  if you are to be a hub and send files out you might which to assign
  CRASH or HOLD or other status bits to the mail.  In other words for a hub
  this allows you to CRASH (send files out asap) or hold (so they are picked
  up by a system calling in or for Long distance boards).
           -> Tic File Mode ** - The default is fine but if you wish to
  have an advanced setup (for hubs mainly) read up on this option.
           -> Packing mode ** - This is the same as Tic File Mode.
           -> Compression Type - Zip is default.  This tells allfix which
  compression type the files coming in for THIS node are.  So it can then
  test, scan, convert or whatever other process it might need easilly.
           -> Advanced Options ** - These options can be skipped and
  are mainly used for HUBS not nodes just getting files.
           -> Cost sharing options ** - For hubs who which to have bills
  and a Cost recovery program (CRP) system setup for files.  You can skip.

        At this point you should have your uplink in allfix or should.

      16.  [Main Menu] Request Processor **
           This feature is for those who wish to have a built in FREQ (file
  request) processor for their bbses instead of say Frontdoor's built in
  ability.  Please note this is in 4.41 if using an earlier allfix you may
  not see this and other features listed in the FAQ.

      17.  [Main Menu] Allfiles lists **
           This is the same as 16 and is an advanced feature so you can
  skip #16 and #17 for this basic setup.

        At this point you have most of the setup complete however we now
  need to get to the hard part of the setup and heart of the operation.

    4) Step Four - Fcomp
       We must tell Allfix at this point what file bases you currently have
  online on your bbs.  This is so when we get to the next step and we know
  where files should go we can tell allfix the right data.  Whenever you
  create new file bases you should run Fcomp.exe.  It comes with the
  allfix and fully supports Telegard v3.02+.  To run it yuo type
  Fcomp 19 (Data directory) - Where 19 tells it for telegard and the
  Data directory is where your fareas.dat is located like c:\tg\data\.
  This information is also used in later steps as well as the next one.

    5) Step Five - File Echos
       File Echos are just like Message echos but instead of echomail they
  use files for the medium of exchange.
       1.  [Main Menu] File echo system
           We now need to enter this series of menu items from the main
  menu to start adding file echos to your setup.  A File echo is just like
  a message echomail area but instead of messages its files that are used.
           -> File Echo manager - We'll cover this in a minute.
           -> Hatch Manager & Magic FileNames ** - Are advanced options and
  are made for hubs mainly or file requesting.  Study them if interested.
           -> Group manager -This is the editor that allows you to add
  groups to allfix.  Just like Gecho's group manager a group allows you
  to categorize sections.  For example if you are getting files from fidonet
  filebone then create a group for each fileecho group.  When you join a
  file distribution network you will get a list of file echos like
  filebone.na for fidonet.  You will notice there are groups (in most
  organized networks at least) like AD is a group for Author direct files
  which might have a handful of file echos in it.  Another group is TG_SUP
  which has only one file echo TG_SUP for this fine bbs software! This allows
  you to do things at a faster pace and organize things.  It allows you to
  make changes faster without worrying about conflicts.  Let's assume for
  this FAQ you are in Fidonet and getting files from the Filebone:

  Let's jump in and create a group while I explain the Group Manager itself.

       2.  [File Echo System Menu] Group Manager
              -> Group - This is the slot that is used for group defaults.
  It ranges from 0-255.  Lets say we use slot 1 for Fidonet.
              -> Name: This is the name of the File Echo group.  For example
  TG_SUP or DDSDOORS or PDN.  Good way to use is to list the name with
  the group tag and a short description like PDN: Programmer's Distribution
  Network.  Here is a HINT to help things out.  If you have the filebone.na
  or a similar formated file from a file hub you can import your areas from
  that file INTO allfix.  This will save you time and speed things up.
  You should edit out any file groups or file echos you do not like from
  the file and then using the Asetup -> Utilities -> Import Data you can
  import using the Filebone.na feature!  Let's use TG_SUP for our example
  Group name.
              -> Mask ** - This field is basically an advanced feature that
  is used with auto-adding of file echos.  For example say a group tends
  to have all its file echos with WIN_* well you can give it that very
  mask and when a new file echo say Win_New is added it will add it using
  this group's pre-set info.  For now however, we'll leave it blank.
              -> Unique, Add BBS and BBS Mask ** - Are advanced features
  used in conjuction with auto-added areas.  You should skip it.

              The bottom of the manager says for defaults of auto-added
  areas.  While this is true we should use this area as well since any echo
  you add manually to allfix will use the defaults for THAT group slot you
  pick.  This will help in saving time for alot of the information.

              -> File Echo Description - Actually it should say Group
  description.  Here you might say "AD: Author Direct files -" and leave
  the rest blank.  This is so you could add in a specific echo description
  after the dash.  For example "- Windows software".  The "AD:.." part
  is a good technique to show which group it belongs to for viewing ease.
              -> Dest - This tells (the group default - for more specific
  areas for EACH file echo you can specify that in the file echo manager)
  where to have allfix place the files after processing them from your
  inbound area (c:\newfiles in my example above).  Allfix will create the
  directory if it doesn't exist.
              -> Use FDB - If you do not see this you have not used the
  Fcomp utility as directed, please redo step four.  Assuming you have
  and allfix knows what directories TG is using for files then we can
  figure out this item.  To be honest I'm using 4.33 and this toggle is
  not there.  But if you select yes allfix will update TG data files and
  show the file has been uploaded.  So I would toggle this yes.
              -> Use FDBS - This will either update (when a file comes in)
  files.bbs with the new files or not.  If you have programs using this
  file then you might want it yes otherwise no real need for it.
              -> Keep # - This is just a feature used if you wish to delete
  files that are overlly abundent in quantity.  But leaving it at default
  should be sufficient with any setup unless you are hurt for space.
              -> Template - If you select this item and you see no files
  listed you should unzip template.zip where you told allfix to look for
  them.  This allows you to assign (if you want) a file for netmails or
  bbs file annoucement echos.  Typically reports is the template most use
  for file annoucement echos and such.  This is a moderately advanced
  feature and only mess with it if you wish to do such activities.
              -> Banner - This is a report or just a simple banner (see
  banner.apl for example) that can be added to archives coming into your
  bbs (like a bbs ad or a 'this file is virus scanned' message).  But
  it is a registered only feature.
              -> Use Aka - This tells allfix which network address to
  use (ie which network basically) this group is used for.
              -> LongDesc - If you see files that come in with short
  descriptions when you know they have longer ones this might be the cause.
  You can toggle what you want to be shown in the data base (TG/allfix).
  I find that the toggle 'File_id.diz/Ldesc' works the best since the FULL
  file_id.diz is uploaded into TG for you.
              -> Cost ** - Skip unless you want to charge downlinks.
              -> Max Days - This is the max days to keep a file in this
  group.  I find the default 0 (unlimited) to be the best solution.
              -> Max Size and Max Files - Is just like max days but tells
  if the size or # of files should be limited.  Again 0 works the best here.
              -> Systems -This field allows you to edit system connections.
  If you have an uplink or a downlink here is where you add them (or if they
  use allfix requests its done automatically).
              -> Advanced Options [Menu]
                 -> Convert - If you wish to have files converted to a
  preferred format say *.Rar here is how.
                 -> Convert all, inc ** - Advanced conversion features.
                 -> Pass through - This is for systems who allow people to
  get files (downlinks) from them but they themselves do not carry that file
  echo online so it passes through their system only.  This is the toggle.
                 -> Allow replace - If you wish to have files replaced like
  when new fidonet.na files come out then this feature allows it.
                 -> Announce ** - If you are using file reports then this
  is how you can include areas in those reports by this toggle.
                 -> Add File_id.diz (!!!) - This is a super feature.  If
  the archive does not have one it will add one based on the *.tic file that
  it comes in with (assuming that tic file has a basic description).
                 -> Virus scan - Reg only feature.  You can scan files
  that come in and then do various actions with them.
                 -> Check dupes - If you have duplicate files this will
  either tell allfix to act on those or not.
                 -> Visible, Tiny SB, no touch ** - Advanced hub features.
                 -> Security - Just a toggle that will verify things in
  *.tic files are correct for this group.
                 -> Send original ** - Advanced hub feature - skip.
                 -> Add pic specs - If you have gifs and wish to add the
  resolution and such info to the TG descriptions this will do so!
                 -> Update magic ** - Magic aliases are used in the file
  request abilities and should be read up on if you want such features.
                 -> Touch AV - If you wish Allfix to affect (ie add a
  file to it or whatnot) AV files (those with security envelopes).

       3.  [File Echo System Menu] File Echo Manager -> Options
           Let's cover the options menu for the file echos first before
  we add any file echos.  These options cover all the file echos and
  are vital for some operations.
           -> Keep original file date - This toggle is for those who might
  wish to make 'old' files 'new' ones (G).  Say a 1984 file coming in
  with this toggled yes will add the CURRENT date (ie 1997) to it.
           -> Download counters - Another way of cheating.  Say you want
  a echo to seem active in downloads.  This allows you to add a download
  counter say 12 for EVERY file echo file that comes in.  This could be
  dangerous so use it wisely.  Default is perfect as well.
           -> Update descript.ion - If using 4dos you should use this
  item otherwise for non-4dos systems default is fine.
           -> Max # of systems ** - Advanced hub feature - skip.
           -> Inv. ?lo files - I have no idea on this feature sorry.
           -> Dupe checking - This toggle allows you to tell allfix by
  which method you wish to have allfix check for duplicates.
           -> Min HD space to import - For those limited with space allows
  you to set a limit for allifix on imports.
           -> Max tic file archive size - Rarely is *.tic files over a few
  kilobytes but in case they are you can limit it.
           -> max files to pack ** - Advanced tic packing feature - skip.
           -> Sort file echo - Allows sorting by groups or not.
           -> Tic archive specs ** - Advacned tic operations - skip.
           -> Longdesc character - The default works most of the time but
  if for some reason your long descriptions aren't importing it could be
  the character that starts the description is different.
           -> Longdesc width - Say you wish only a 10 character wide file
  description for each file.  This is how!
           -> Spaces to indent - Default works the best.
           -> Filter Ansi, Longdesc - if your descriptions are showing up
  oddly you might toggle these yes.  Otherwise the default works best.
           -> one line longdesc - If you wish only one line file descriptions
  this it your toggle!
           -> max length of longdesc - Same as width but allows you to limit
  the number of lines shown for that file.
           -> Add tag - This is a nice feature as well.  If you wish to
  show the users that a file came from TG_sup you could toggle it to
  Uploader and it will add the tag to that file.
           -> Filter String - Say you wish to omit profanity or such words
  from descriptions this allows it.

       4.  [File Echo System Menu] File Echo Manager
           The first time you enter the file echo manager to add or change
  file echos it will ask for which group the file echo is to belong to.
  This is why we covered groups first.  For our example lets use the
  group we just setup.  This is the true heart of the program.  Alot of
  the items below are the same for the Group manager but are for that
  individual file echo and not for a group.

           -> Tag - This is your file echo tag.  For example say you are
  in the Group TG_SUP that group has the echo TG_SUP (yes same tag) for
  Telegard related support from fidonet.  This is where it goes.
           -> Description - The new echo is using the group description
  so you could edit it (unless you imported file echos from the Import Data
  section of Utilities) to your liking.  If imported its already here.
           -> Dest - The directory for this file echo to place files in.
  This is just like the group manager and uses its default.  However, if
  you wish to make it even more specfic say c:\dls\tg for the group you
  could have c:\doors\tg\scripts for just scripts.  However, seeing as
  TG_SUP only has one echo this example is of no use but there are plenty
  of groups that do have specific setups like that.
           -> Use FDB, Use FDBS - Same as group manager info above.
           -> Group - Tells which group this file echo belongs to.  If
  you do not wish to use the one selected then you can change it.
           -> Keep #, Template, Banner, Advanced options, Use Aka,
  LongDesc, Cost, Max Days, Max Size, Max Files and Systems are all
  identical information as above for group manager but are for the specific
  file echo shown.  This allows you to customize each file echo if you
  wish to diverge from the group defaults.  Say for example you could use
  a different template and keep this file echo limits on max size if you
  wish to do so.  The group defaults would be given here but these sections
  are here for you to make your personal choices on setup.

    6) Step Six - Are we done yet?!
       Well yes.  At this point you should know so much about allfix to
  teach a class in it.  At least I hope so.  There is online help for
  each item by pressing F1 at any time in the program.  So while my
  descriptions got intense the docs might just show more details that I have
  or less details.  In the conclusion of this FAQ we have some last few
  sections to help those who wish more advanced setups and lastly some
  hints and batch file material of the more important areas as a general
  outline for you to follow.  If at this point you are ready to go then you
  do not need to read on.  However, there might be things more for you to
  learn that will give that extra edge of working with allfix.  I will only
  touch on certain things here and will rely on the reader to investigate
  the documentation for further details.

       1) File Annoucements
          As shown at the top of this FAQ I showed what a typical file
  annoucement is.  It is a message posted just like a regular echomail
  message posted say in TG_SUP (Telegard support for fidonet).  Instead
  of a person doing it Allfix posts it to the bbs it is serving on.  IF
  you wish to have such on your board say for a local fidonet echomail
  base that has such reports here is the section how.  You will have to
  go through the above information and find the various areas I mentioned
  that a particular option was for file annoucements and then invoke those
  options.  Then we shall go to the main menu section of "New File Reports"
  and "BBS new file dirs".  They are used in conjuction with each other
  to process new files.  It is required that you have already used Fcomp
  as outlined above to use these features.
          [Main Menu] -> BBS new File dirs - When you add a new entry.
            -> File area - When you select this field it will give you a
  list of directories you currently have online in Telegard (via the Fcomp
  utility).  I would for sake of example since most people have one general
  upload directory you select that directory.  IF you do not have such then
  select a directory files are placed or held or uploaded to.  For me I use
  the Upload file directory for myself.
            -> Desc - This is just a short description of that file area
  if you wish to supply one for allfix (for easy reading).
            -> Group - Since we've created one already in our examples above
  lets select that one.  This just attaches this feature to a particular
  group for different reports if you wish.
                Now that we've done that and assigned at least one new file
  directory we can continue.  What we have done is whenever a new file is
  uploaded to your bbs by a user and you run allfix File it will scan the
  upload directory and if a new file is present make a report.  This report
  could be in a local directory or a echomail base for everyone to view.

          [Main Menu] -> New File Reports
            -> Groups - This field determines which group the file report
  should be associated with.  Why have this?  Well say you have customized
  an adult file report, via the template editor, with sensitive info like
  freq info that general users shouldn't see.  You could have say just the
  adult groups have THAT report and the others use a standard report.  Then
  the adult report could be shown only in the adult file annoucement echo
  while the other is shown to everyone.  That is only one example of the
  features of allfix.
            -> Msg area - Since this report is going to be posted on your
  bbs or a network you need to supply it what message area.  Selecting this
  field will allow you to select the various formats.  But for myself, I
  use JAM and give it a name like c:\tg\msgs\fileinf where all local file
  annoucements go to.  It seems squish is not supported.
            -> Use Aka - This tells which origin address to add to the
  origin line of the report (ie which network it belongs to if any).
            -> Origin ** - If you wish to give customized origin lines
  here is how to do it.  These will be at the bottom of the file report.
            -> Template - The standard file annoucement pre-made template
  is REPORTS so I would use that unless you make one of your own.
            -> From - Allows you to tell who "posted" the report.  Take for
  example "BBS X File Reporter".
            -> To - This is to who it is posted to.  Take for example you
  could say "Everyone on BBS X" or "Everyone in Net 112".
            -> Subject - Just like from and to, but is the subject line.
  You could do for example "New Files arrived on BBS X".
            -> Inactive ** - Just use the default no for now.
            -> Systems - This tells allfix which nodes (bbses) are connected
  to receive the file reports (if given through a network).

        Now you should be able to generate a file report at this point.

       2) Utility programs
          There are a group of associated programs with allfix that help
  the user in various tasks.
          Fixutil.exe - This is a allfix maintenance utility that allows
  you to do various things like make master file lists and such.
  For example fixutil describe allows you to import data from filebone.na.
          Hatch.exe - allows you to hatch a file on the fly.  This is
  for downlinks mainly but if you wish to hatch a file out to friends
  who are connected this is how.

       3) Batch files and Miscellaneous
          One minor last thing that is vital to the allfix operation - the
  batch file to run it!  You should study the commands of allfix for further
  customization if you wish by simply running allfix by typing "allfix" in
  the directory it is in.  I would suggest placing allfix in your PATH
  statement for easier processing as well.  Since most people will have
  their files come WITH attached *.tic files then you can simple do the
  following batch file segment:

          In the section at the top that runs before FD returns back after
  say processing events include -

          If exist c:\inbound\*.tic       Goto Allfix

          Notes: Inbound is the directory where incoming files are stored
  which was discussed back earlier in the FAQ.  Goto could be replaced with
  a CALL if you wish to run a batch file like allf.bat which I do.  This
  allows you to customize the batch file at will easier.

          Once the batch file detects tick files it will go to that section
  and run the next few lines.

          cd c:\allfix (or the directory where allfix is located)
          Allifix F S A

          Complicated huh?  Read what each parameter does to see if you need
  it.  For example if your not doing file annoucements A (annouce) is not
  needed for this line.

          At this point you should be a fairly good person with allfix.
  I know this FAQ was extremely long and I'm sorry, I tend to be over
  technical so I don't have to repeat things later on (G).

  **************************************************************************

  ■ Contact Information
    Fringe BBS - EWOG II [phone]
    Networks : Fidonet 1:112/91, AdventureNet 33:409/1, GamesNet 100:6607/1,
               MirageNet 90:803/11 and a few others (G)
    Echomail: TG_Sup fidonet echo frequent reader/poster
    Internet: [e-mail] (BBS email gateway)

  ----------------------= End of Allfix FAQ =------------------------------