High Voltage Shareware

home *** CD-ROM | disk | FTP | other *** search

/ High Voltage Shareware / high1.zip / high1 / DIR24 / FLST120.ZIP / FASTLST.DOC < prev next >

Wrap

Text File | 1994-01-13 | 17KB | 602 lines

****************************************************************************** * * * * * ******* ** **** ****** **** **** ****** * * ** * **** ** ** * ** * ** ** ** * ** * * * ** * ** ** ** ** ** ** ** * * **** ** ** **** ** ** **** ** * * ** * ****** ** ** ** * ** ** * * ** ** ** ** ** ** ** ** ** ** ** * * **** ** ** **** **** ******* **** **** * * * * * * A Fast, Flexible and Powerful nodelist compiler * * * * * ****************************************************************************** * * * (C) Copyright 1992-1994 by Alberto Pasquale * * * * A L L R I G H T S R E S E R V E D * * * ****************************************************************************** * * * FastLst required many hours of work: if you like it and would like to * * support me in developing this and other similar products, please * * register. See REGISTER.DOC for more details. * * * ****************************************************************************** * * * How to contact the author: * * * * email: Alberto Pasquale of 2:332/504.1@fidonet.org * * When sending crash netmail, please call: * * 2:332/504@fidonet.org +39-59-450600 V32b * * 2:332/511@fidonet.org +39-59-450643 V32b * * 2:332/524@fidonet.org +39-59-581127 HST/V32 * * * * postal mail: Alberto Pasquale * * Viale Verdi 106 * * 41100 Modena * * Italy * * * ****************************************************************************** FastLst ver 1.20 User Manual DISCLAIMER FastLst is provided as is and comes with no warranty of any kind, either expressed or implied. In no event will the author be liable for any damages resulting from the direct or indirect use of this software. The user of this program bears all risk as to its quality and performance. LICENSE FastLst Copyright 1992-1994 by Alberto Pasquale, Modena, Italy All rights reserved. Commercial distribution and/or use prohibited without written permission of the author. You may copy and distribute verbatim copies of the original distribution archive of FastLst, providing you don't charge any fee exceeding your actual costs. You may enclose FastLst in CD-ROM collections of ShareWare and Public Domain programs or keep it in BBS download areas provided you do not charge any specific fee for the download. If you regularly use FastLst, you should REGISTER your copy (See Register.Doc). Files in the original archive: FastLst.Exe The executable program (OS/2 or Dos version) FastLst.Cfg The sample configuration file FastLst.Doc This documentation file Readme.1st Important notes Whatsnew.Txt Fixes and additions Register.Doc Info on Registration Register.Frm The Registration Form Register.Cum Special offer for cumulative registrations FlstWish.Txt I ask for your opinion Pag. 1 MAIN CHARACTERISTICS: - Compiles Version 7 format nodelists. - Support for old "Fidouser.Lst" sysop list - Multiple output nodelist compilation from one config file. - Decompression and compilation of new lists and diffs are automatically executed when necessary, with no need for clumsy batch files. - Very fast operation - Full 4D (point) support, both via the "Point,..." and "Boss,..." keywords. - Easy addition of nodes via the "Node,<address>,..." keyword in a private list. - In the case of SysOps of multiple nodes, keeps in the sysop lists (fidouser.lst and sysop.ndx) all the name/address entries. Allows to keep one address only for specified ones. - User Cost (Msg Fee) can be set different from Call Cost. Pag. 2 OVERALL OPERATION FastLst has been designed to be invoked regularly from one of your main batch files, after mail has been received or at pre-arranged times at your pleasure: if any new (compressed or not) nodelist/nodediff is detected, Fastlst processes them as required, otherwise it immediately exits with no further delay. If you want FastLst to compile all of your nodelists even if no new ones are present, you need to use the -f command line switch. For each "output block" in the config file: - New compressed lists or diffs are detected and unarchived. - New diffs are detected and applied: the resulting new nodelist is archived, if so requested in the config file. - New lists are detected and the pertinent output nodelists are rebuilt. If no new list is found for a specific "output block", that output nodelist is not compiled, unless the -f command line switch is specified. If you use the automatic Archive/Unarchive features of FastLst, you are supposed to always have in the pertinent directory an up-to-date copy of each nodelist (FastLst unarchives new lists/diffs only, it does not unarchive the lists that have already been unarchived in previous runs). ATTENTION: - Every time the config file is changed, FastLst rebuilds all the output nodelists, as if the -f command line switch was specified. - Every time a PasswordFile is changed, FastLst rebuild the nodelists that use it. Pag. 3 4D POINT SUPPORT: POINT and BOSS keywords The source nodelist and nodediff must be in standard "St. Louis" format, as described in FTS-0005. FastLst allows an extension to the input nodelist format in order to support true "4D" points. First method: Points are entered in the nodelist directly following their bossnode. Each one starts with the "Point,<point>" keyword. Example: ... ... ,504,Videl_3,Modena_I,Roberto_Zanasi,39-59-450600,9600,CM,XA,V32B,V42B Point,1,Pasquale,Modena_I,Alberto_Pasquale,-!Unpublished-,9600, Point,2,SysOp,Modena_I,Roberto_Zanasi,-!Unpublished-,2400, Point,3,Carta,Modena,Francesco_Carta,-!Unpublished-,2400, ... ... Second method: Points are entered in the nodelist after the "Boss,<address>" keyword. Example: ... ... Boss,2:332/504 ,1,Pasquale,Modena_I,Alberto_Pasquale,-!Unpublished-,9600, ,2,SysOp,Modena_I,Roberto_Zanasi,-!Unpublished-,2400, ,3,Carta,Modena,Francesco_Carta,-!Unpublished-,2400, ... ... Pag. 4 The NODE Keyword Another extension over FTS-0005 is provided to allow easy addition of nodes in small private lists. When you need to add a node to your nodelist to call it or to enforce a session password with it, you can use the "Node,<address>,..." keyword to avoid the necessity of adding its Zone and Host coordinators. You should specify a full 4D address (point optional). Any subsequent entry will take the current address as a starting point. E.g.: You want to add 9:8/7.3 With "Node,...": ... ... Node,9:8/7.3,Mickey,DisneyLand,Mickey_Mouse,1-800-111,9600,CM ... ... With "Boss,...": ... ... Boss,9:8/7 ,3,Mickey,DisneyLand,Mickey_Mouse,1-800-111,9600,CM ... ... With the traditional method: ... ... Zone,9,... Host,8,... ,7,... Point,3,Mickey,DisneyLand,Mickey_Mouse,1-800-111,9600,CM ... ... Now let's add 8:7/6 and 8:7/7: With "Node,...": ... ... Node,8:7/6,Mickey,DisneyLand,Mickey_Mouse,1-800-111,9600,CM ,7,Duck,DisneyLand,Donald_Duck,1-800-112,9600,CM ... ... Pag. 5 With the traditional method: ... ... Zone,8,... Host,7,... ,6,Mickey,DisneyLand,Mickey_Mouse,1-800-111,9600,CM ,7,Duck,DisneyLand,Donald_Duck,1-800-112,9600,CM ... ... Pag. 6 CONFIGURATION FILE FastLst requires a configuration file (defaults to FastLst.Cfg in the current directory). Before using FastLst you should edit the sample config file, following the comments in it. The keywords are not case sensitive. You should keep a copy of the original sample FastLst.Cfg, since it is extensively commented and it represents the real documentation of FastLst. Each line is parsed up to a 256 chars length, so don't go further (you can always split address lists into smaller ones). In the OS/2 version, any file specification can be a legal OS/2 name, between double quotes if necessary. Please be aware that the generation of text files (FidoTxt, FidoPrn, FidoUserLst verbs) and the use of many options and overrides can dramatically slow down the compilation process: use only the options/overrides that you really need if you mind compilation time. Pag. 7 COMMAND LINE PARAMETERS -c<config> Use <config> configuration file instead of FASTLST.CFG. -f Force compilation even if no new list/diff has been detected. -p Prepare: Unarc new lists and diffs, Apply diffs and Arc new nodelists, do not compile nodelists. -r When applying a diff, FastLst usually deletes the newly generated source nodelist file if a CRC error is detected. With this switch the new nodelist is _not_ deleted, so that it will be processed anyway. When compiling a list, FastLst usually aborts the compilation of the current output nodelist if a CRC error is detected. With this switch the current output nodelist will be entirely compiled anyway. -h or -? for help ERRORLEVELS 0 Normal termination 1 Help requested 2 File Open error 3 Can't find nodelist file 4 Disk Full 5 Can't find config file 6 Configuration error 7 Out of memory 8 Read error while applying diff 9 CRC error (applying diff) 10 CRC error (compiling list) 11 User Break 12 Cannot replace old output nodelist files with new ones Pag. 8 MISCELLANEOUS INFO MULTIPLE SYSOPS In the case of SysOps of more than one system, all the name/address couples are put in the SysOp Name Lists (Fidouser.lst and Sysop.ndx). If you want to keep one only name/address couple for some multiple SysOps, you can use the "SysDup <AddrLst>" option in the config file: the SysOps who have one of the listed addresses will be present in the SysOp lists with that entry only, even if they have other addresses. Example: Let's suppose that Robert Everywhere has 4 nodes: EveryWhere, Robert 1:456/987.0 EveryWhere, Robert 2:123/457.0 EveryWhere, Robert 2:123/457.8 EveryWhere, Robert 6:321/567.0 By default all the 4 addresses are available in the sysop lists (and some programs allow to choose among them, e.g. TimEd message editor by Gerard van Essen). If you prefer to keep one address only, you can specify the desired address in a SysDup line in the config file: e.g. "SysDup 2:123/457.8". REDIRECTED SYSTEMS Redirected systems (Unpublished phone number, on HOLD) are given the phone number, baud rate, modem type, cost and flags of the preceding coordinator, the Board name is prepended with '-R-'. If you have a session password with the system to be redirected or with the system it should be redirected to, no redirection is done in order to prevent password-mismatch errors in the case the Unpublished/Hold System calls you. These non-redirected systems take an EMPTY phone number string, so that your mailer does not send unwanted strings to your modem attempting to call these systems, should something appear in your outbound addressed to them. Pay attention: if you want to directly call these null_phone-systems or their coordinators, you have to give them a phone number using the "Phone <Addr> <NewNumber>" statement in the configuration file. <The End> Pag. 9