home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
High Voltage Shareware
/
high1.zip
/
high1
/
DIR24
/
FLST120.ZIP
/
FASTLST.CFG
next >
Wrap
Text File
|
1994-01-15
|
24KB
|
611 lines
;*****************************************************************************
;* *
;* (C) Copyright 1992-1994 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.FRM for more details. *
;* *
;*****************************************************************************
;* *
;* How to contact the author: Alberto Pasquale of 2:332/504.1@fidonet.org *
;* Viale Verdi 106 *
;* 41100 Modena *
;* Italy *
;* *
;*****************************************************************************
; Sample FastLst 1.20 config file
; G L O B A L I N F O
; RegKey <RegistrationKey> ; If you are a registered user, put your
; registration key here (not case sensitive)
StatusLog c:\max\bt.log ; Binkley style log file
InputPath h:\NodeList\ ; Specifies the default path for input files.
; You can override it by using a full pathname
; in input-file specifications.
; Created if not existing.
ArcPath c:\file\Lists\ ; Specifies the default path for Archived
; nodelist files.
; You can override it by using a full pathname
; in Archived-file specifications.
; TmpPath d:\tmp\ ; DOS only, not used in the OS/2 version.
; Path for temporary files: please be sure there is
; enough space for the nodelist size you usually
; compile. You can use a Ram Disk to speed-up the
; Merge-Sort process, provided you have an
; adequately sized one.
KillAfter ; Old V7 files are killed after the new ones have been
; successfully written.
; Thus you will always have a valid nodelist, even in the case
; of a compilation error. On the other hand you could need some
; more spare disk space to hold the old and new files during
; compilation.
; Dash2Comma ; Change dashes to commas in the phone number
; NoDash ; Remove dashes from the phone number
; NoReport ; Do not output nodelist statistics
V7BugFix ; Circumvents a bug with V7 nodelist in Binkley 2.50
; (and perhaps in many other programs whose V7
; search function was inspired by Binkley's sources)
; that can sometimes hide segments of V7 nodelist.
; If you are unsure, keep this keyword active.
; Cost table:
;
; Each entry in the cost table has the following format:
; <PartPhone> <Cost> [<UCost> [<StripFlags>]]
;
; <PartPhone> is a partial phone number, as in the nodelist entries.
; <Cost> is the cost field of the compiled nodelist (0->65535).
; It represents the "Call Cost" for any node whose phone number begins
; with <PartPhone> in the source nodelist (before dialing translations).
; <UCost> is an optional "User Cost" (fee for a netmail message on BBS).
; If it is not used, it's taken equal to <Cost>.
; If you would like your users to be able to send netmail messages
; from the BBS with no need for "credits", you should set UCost to 0.
; <StripFlags> is an optional list of nodelist flags (not case sensitive)
; to be stripped from entries of nodes whose phone number begins with
; <PartPhone>.
; Thus you can strip some modem-type flags (V32, HST, ZYX, ...)
; when calling into critical areas.
; This parameter can only be used after <UCost>.
;
; When searching for "PartPhone", the first matching entry is applied:
; in the case of entries with an initial part in common, you have to
; specify them in sequence from the longest to the shortest.
;
; If no match is possible, the last line specifies the international
; <Cost> and optional <UCost> and <StripFlags>.
;
; An example follows:
cost
; 1-703-5555 100 0 HST,H14,H16 ; strip HST from modem flags
; 45-123-456 100 0 V32,V32b ; strip V32 and/or V32b
39-59 0 0 ; for local calls
39- 60 0 ; for domestic long distance calls
- 300 0 ; for international calls
end
; Dial table:
;
; Each entry in the dial table has the following format:
; <PartPhone> [<Prefix>][/<Suffix>]
;
; <PartPhone> is a partial phone number, as in the nodelist entries.
; <Prefix> and <Suffix> define a dial translation.
; <PartPhone> will be stripped from numbers beginning with it, while
; <Prefix> and <Suffix> will be prepended/appended to the remainder.
; No spaces are allowed between prefix, suffix and the
; separating slash. Examples:
;
; A prefix alone is specified as-is in the second argument:
; "39- 0" strips "39-" and adds "0" at the beginning of the number.
;
; A suffix alone must be preceded by a slash:
; "39-59- /!" strips "39-59-" and adds "!" at the end of the number.
;
; A prefix/suffix couple is separated by a slash:
; "39- 0/!" strips "39-", adds "0" at the head and "!" at the end.
;
; The first matching entry is applied: in the case of entries with
; an initial part in common, you have to specify them in sequence
; from the longest to the shortest.
;
; If no match is possible, the last line specifies the international
; prefix/suffix.
Dial
39-59- ; Remove the country and area codes for local calls
39- 0 ; Remove the country code and add the domestic prefix
- 00 ; Add the prefix for international calls
End
; TypeDef table:
;
; If you have a modem that does not need different dial strings
; for different protocol connections, you can skip this section.
; For Example a Zyxel modem usually needs one only dial string
; for every type of connection (unless you do not use "Multi-Auto"
; mode).
; Instead, if you need different dial strings, you can use the
; Modem_Type field in conjunction with some front-end feature
; that allows to specify different dial strings for different
; modem types ("ModemTrans" in Binkley).
;
; Each entry in the TypeDef table has the following format:
; <Flag> <Value>
;
; <Flag> is a Nodelist flag, <Value> is a number 0->255.
; The nodelist flags of each node are searched for <Flag>.
; The <Flag> must match completely a nodelist flag: if <Flag> is V32
; and the nodelist flag is V32B, it's not a match.
; The search is not case sensitive.
; If <Flag> is found, the corresponding ModemType field is set to <Value>,
; otherwise the <Flag> in the next "TypeDef" is searched for.
; The ModemType field of the compiled nodelist will be determined by the
; first match only: If you define HST before V32, a node with both V32 and
; HST will have a HST modem type.
;
; An Example follows for a USR HST/V32B modem:
;
; TypeDef
; H16 1 ; first choice: if available it's the fastest way.
; ZYX 2 ; ZYX implies V32B, so they have the same priority
; V32B 2 ; for a USR Dual Standard modem.
; H14 3
; V32 4
; HST 5
; End
; BitType
;
; If you need old-style bit-oriented modem type, you must enable this
; verb. In this case the "TypeDef" works differently:
; <Value> should be a power of 2 (1, 2, 4, 8, 16, 32, 64, 128)
; The ModemType will be determined by ORing all the <Value>s corresponding
; to <Flag>s that found a match in the nodelist flags.
; The dial string used by your front-end will be determined by the order
; of their specifications (the order of "ModemTrans" in Binkley).
;
; An Example follows for a USR HST/V32B modem:
;
; TypeDef
; H16 1
; ZYX 2
; V32B 2
; H14 4
; V32 8
; HST 16
; End
; O U T P U T N O D E L I S T
; Version7 <Path> <Nodex> [<SysopNdx>]
;
; Start of a block of config verbs defining the generation of a Version 7
; nodelist. You can generate one or more Version 7 nodelists with
; different names and path for the output files.
; Each "Version7" statement marks the beginning of a new output-nodelist
; definition.
;
; <Path> is the path where the output .DAT and .NDX files are placed.
; <Nodex> is the file name for the .DAT and address-index .NDX files.
; <SysopNdx> is the file name for the sysop-index .NDX file.
; If you omit <SysopNdx>, no V7 SysOp-index will be generated.
; Unless you use different output nodelists for different domains,
; you should usually adopt <Nodex>="NODEX" and <SysopNdx>="SYSOP".
;
; All the following verbs, up to the next "Version7" (if any), are
; related to the preceding "Version7" output files.
Version7 e:\V7\ NODEX SYSOP
; FidoUserLst [<FidoUserLst>]
;
; Generate "fidouser.lst style" text SysOp list.
; <FidoUserLst> optionally specifies an output file name, which defaults
; to "FidoUser.Lst". Different output blocks require different names.
; FidoUserLst
; SysOpLst
;
; Output SysOp data from all the input nodelists to the previously
; specified list/index.
; If commented out, local "SysOpLst" options can be specified in
; selected input "NodeList" blocks.
SysOpLst
; SysDup <AddrLst>
;
; When a SysOp name is present in various nodes, all the name/address
; couples are kept in the SysOp lists (fidouser.lst/sysop.ndx).
; If you want to keep only one address you can use one or more SysDup
; lines: the SysOps who have the addresses listed in <AddrLst> will be
; present in the output sysop lists with the specified address only.
; You can use abbreviated addresses, if you like, provided that the
; first address of every "SysDup" is complete (FastLst cannot make
; any assumption for the first item in a list).
; SysDup 2:332/504 505 336/980 3:25/28.27
; I N P U T N O D E L I S T
; NodeList <NodeList> [<PartAddr>]
;
; Start of a block of config verbs defining the processing of the
; specified <NodeList> file.
; You can use many "NodeList" statements to compile several different
; nodelist segments into the same output files specified by the preceding
; "Version7" statement.
; Each "NodeList" verb marks the beginning of a new input-nodelist
; processing-info block.
;
; When an address is present in more than one <NodeList> (e.g. you
; compile both the full nodelist and the faster updated local region
; or zone segment) only the entry found in the last compiled <NodeList>
; is put in the indexes. To have the most up-to-date entries in your
; V7 indexes, please include local segments after the larger list.
;
; <NodeList> is the name of the input nodelist: if a terminal ".???"
; is specified, all the files with 3 digits at the place of '???' are
; examined and that with the latest 3 digit day of the year is
; choosen for compilation.
;
; The optional <PartAddr> is a partial address that must be specified for
; nodelist segments that do not have full address info.
; For example, a REGION segment usually starts with the "Region," keyword
; and does not contain any Zone info: its up to you to tell FastLst which
; zone we are talking about. Analogously you should provide zone and net
; info when compiling a Hub segment.
; The region is assumed equal to the net number of the partial address,
; the hub equal to the node number.
;
; E.g.: "NodeList nodelist.???" Nodelist with zone info
; "NodeList region33.??? 2" Region nodelist, in zone 2
; "NodeList net.332 2:33" Net nodelist, in zone 2, region 33.
; "NodeList hub.500 2:332" Hub nodelist, in zone 2, net 332
; "NodeList locnode.500 2:332/500" Some nodes in zone 2,
; net 332, hub 500
; "NodeList points.504 2:332/504" Points of 2:332/504 in
; "Point," format.
; "NodeList morenode.lst" Some nodes in the "Node," format.
; No <PartAddr> required since the
; "Node," line gives full info.
; "NodeList points33.lst" Point List of region 33, in the "Boss,"
; format. No <PartAddr> required since
; the "Boss," line gives full info.
NodeList nodelist.???
; NodeDiff <NodeDiff>
;
; If the above <NodeList> needs to be updated via the NodeDiff method,
; specify the <NodeDiff> name, that must terminate with ".???".
; FastLst will search for a suitable <NodeDiff>, considering the
; files that have a 3 digit day of the year in the place of the
; trailing '???'.
NodeDiff NODEDIFF.???
; ArcList <ArcList> [<Keep#>]
;
; You can specify the name of the archive containing <NodeList>.
; It is necessary if you use automatic extraction/rearchiving, but
; it can even be used only to delete old files.
;
; If "NodeDiff" is specified, <ArcList> is used to ReArc the resulting
; <NodeList> after the application of <NodeDiff>.
; The old <NodeList> must be already present in uncompressed form.
; If "NodeDiff" is not used, <NodeList> is extracted from <ArcList>.
;
; If <ArcList> has a terminating ".<a>??" (where <a> is a character
; depending on the archive type), all the files that have 2 digits
; in the place of '??', are considered, taking the digits as the
; last 2 digits of the day of the year.
;
; <Keep#> optionally specifies the number of archives to be kept,
; basing on the day of the year (max 10).
ArcList nodelist.z?? 1
; ArcDiff <ArcDiff> [<Keep#>]
;
; You can specify the name of the archive containing <NodeDiff>.
; It is necessary if you use automatic extraction, but it can
; even be used only to delete old files.
;
; <ArcDiff> must terminate with ".<a>??", where <a> is a character
; depending on the archive type.
; All the files that have 2 digits in the place of '??' are examined,
; taking the digits as the last 2 digits of the day of the year.
;
; <Keep#> optionally specifies the number of archives to be kept,
; basing on th day of the year (max 10).
ArcDiff nodediff.z?? 5
; UnArc <UnArcCmd>
;
; If no "NodeDiff" verb is used, this is the command to extract <NodeList>
; from <ArcList>; otherwise it is the command to extract <NodeDiff>
; from <ArcDiff>.
;
; The two parameters %a and %f can be used in the place of the archive
; file name (including path) and the file name (no path) to be extracted.
; This command will be executed from the dir where the file to be
; extracted resides.
;
; In the case you are using a case-sensitive de/compression program, make
; sure to use the correct switches in <UnArcCmd> and/or the correct
; case (Lower/Upper) in <NodeList> and <NodeDiff> specifications.
;
; If you need to use a batch (*.BAT for Dos or *.CMD for OS/2) or a Dos
; program under OS/2, you must invoke the command processor (usually cmd
; for OS/2, command for Dos) as in the following example:
; UnArc cmd /c pkunzip -o %a %f (OS/2)
; UnArc command /c myunarc %a %f (Dos)
UnArc unzip -oj %a %f
; Arc <ArcCmd>
;
; Applicable only when "NodeDiff" is used.
; <ArcCmd> is the command to archive the new <NodeList> to <ArcList>
; after applying <NodeDiff>. If <ArcList> has a terminating ".<a>??",
; the 2 digits of the day of the year are put in the place of '??'.
;
; The two parameters %a and %f can be used in the place of <ArcList>
; (including path) and <NodeList> (no path).
; This command will be executed from the dir where <Nodelist> resides.
;
; If you need to use a batch (*.BAT for Dos or *.CMD for OS/2) or a Dos
; program under OS/2, you must invoke the command processor (see
; description of "UnArc").
Arc zip -k %a %f
; SysOpLst
;
; if not already used in the "OUTPUT NODELIST" section, can be used to
; enable output to the SysOp list/index for the current <NodeList>.
; SysOpLst
; FidoTxt [<FidoTxt>]
;
; Generate an 80 Column Text List of nodes.
; <FidoTxt> optionally specifies an output file name, which defaults to
; "NodeList.Txt". If the same file name has already been used for other
; nodelists, the output is appended.
; FidoTxt
; FidoPrn [<FidoPrn>]
;
; Generate a 132 Column Text List of nodes.
; <FidoPrn> optionally specifies an output file name, which defaults to
; "NodeList.Prn". If the same file name has already been used for other
; nodelists, the output is appended.
; FidoPrn
; S E G M E N T S E L E C T I O N S
; The following verbs allow to include or exclude selected <NodeList>
; segments. If you do not use them, the full <NodeList> is compiled.
; Be aware that the process of checking each address against the list
; of segments to be included or excluded could slow down the
; compilation, even if some gain could come from the exclusion of
; large segments.
; IncAddr <PartAddrLst>
;
; If you want to selectively include nodelist segments, you can use this
; option: only zones/regions/nets/hubs/nodes/points that are listed in
; <PartAddrLst> will be present in the output files.
; You can specify zone, region/net, hub/node and point numbers.
; The following example compiles: zone 1, region 33 of zone 2,
; hub 100 of net 200 of zone 2, net 632 of zone 3, node 4:801/17
; IncAddr 1 2:33 2:200/100 3:632 4:801/17
; ExcAddr <PartAddrLst>
;
; If you want to exclude some segments from the compilation, you can
; list them in <PartAddrLst>, in the same way as for "IncAddr".
; You can use either "IncAddr" or "ExcAddr" or both of them to
; Include only selected segments and exclude sub-segments.
; The example excludes Hub 500 of net 332 of zone 2.
; ExcAddr 2:332/500
; IncCoord <CoordLev>
;
; The coordinators of the specified and upper levels will be
; always included, even if excluded by "IncAddr"/"ExcAddr".
; <CoordLev> can be ZC, RC, NC, HC.
; IncCoord NC
; IncSysOp <PartAddrLst>
;
; If not used, all the SysOp entries of the compiled segments
; will be in the output SysOp list/index (if SysOpLst is active).
; If you want to limit the SysOp entries to selected segments,
; you can use this verb, listing partial addresses in <PartAddrLst>.
; SysOps from segments excluded from compilation via "IncAddr"/"ExcAddr"
; will obviously never be present in the SysOp list/index anyway.
; The following example includes only SysOps from zone 2.
;
; IncSysOp 2
; A D D R E S S S P E C I F I C S T U F F
;
; Often you will compile segments of a previously compiled nodelist.
; For example you could have a "NodeList nodelist.???" block for the
; interzonal nodelist and then a "NodeList region.033" block for
; your region's nodelist segment.
; The majority of entries in the latter will be duplicates of entries
; already found in the former.
; However, in the case of duplicates, only the entries found in the last
; involved "NodeList" block will go to the indexes and be active.
; This way you can compile the full interzonal nodelist while keeping
; your segment up-to-date with local segments that get updated faster
; than the full nodelist.
;
; When you have to specify "Address Specific Stuff" for nodes that are
; present in more than one "NodeList", you can do that in the last
; involved "NodeList" block only, avoiding unnecessary specifications in
; the previous involved "NodeList" blocks.
;
; WARNING: make sure all addresses have full info (incl. zone).
; Password <Addr> <Password>
;
; Allows to specify <Password> one <Addr> at a time.
; V7 has no limit on password length, however the programs that use
; it are usually limited to 8 chars. Some (rare) programs have problems
; with 8 chars and need a maximum of 7 or 6 chars.
; Password 2:332/504.4 Password
; PasswordFile <PasswordFile>
;
; Allows to include a password file that contains many address/password
; couples, one per line.
; In this file you can omit the "Password" keyword.
; It is recommended that you use a different file for each "NodeList"
; block, so that the processing of a "NodeList" involves only the relevant
; address/password couples.
; However, should you share a file between two or more "NodeList",
; the only side-effect would be a performance decrease.
; If you like, you can use some "Password" keywords together with one
; "PasswordFile", however you cannot use more than one "PasswordFile"
; per "NodeList".
; PasswordFile nodelist.pwd
; Phone <Addr> <NewNumber>
;
; Allows to override a nodelist phone number.
; <NewNumber> must be in the form used in the nodelist.
; Phone 2:332/501.0 39-59-399999
; NodeFlags <Addr> <NewNodeFlags>
;
; Allows to substitute the flags listed in the nodelist entry of
; <Addr>. If you want to change the CM flag or modem type flags
; (HST, V32b, ZYX) etc, you can use this verb.
; NodeFlags 2:332/501.0 CM,H16,V32b
; Flags <Addr> <Flags>
;
; The Flags statement allows to set the "user defined" bits in the Flags
; word of the compiled nodelist entry.
; These bits are named 5,6,7,8,9,A,B,D,E,F where bit 5 is the 6th bit and
; F is the 16th bit of the word.
; Flags 2:332/501.0 AB5 ; Set bits 5,A & B.
; Cost <Addr> <NewCost> [<NewUCost>]
;
; <NewCost> and <NewUCost> are in the range 0->65535.
; Overrides the Cost and User_Cost fields of <Addr> in the compiled nodelist.
; If no <NewUCost> is given, it's taken equal to <NewCost>.
; Cost 2:332/501.0 150
; E N D O F F I R S T I N P U T N O D E L I S T B L O C K
; The config file continues with subsequent input-nodelist blocks pertaining
; to the current output-nodelist block.
NodeList REGION.033 2 ; Region 33 in zone 2
ArcList region33.zip
UnArc unzip -oj %a %f
PasswordFile region33.pwd
NodeList region24.??? 2 ; Region 24 in zone 2
ArcList origr24.l?? 1 ; Keep 1 origr24.l??
UnArc lh x /o %a %f
NodeList ptlist.??? ; PointList in "Boss," format
ArcList ptlist.l?? 1 ; Keep 1 ptlist.l??
UnArc lh x /o %a %f
NodeList Points.Lst 2:332/504 ; Points of 2:332/504 in "Point," format:
; the starting address is required !
; E N D O F O U T P U T N O D E L I S T B L O C K
; The config file could continue with subsequent output nodelist blocks
; defining the compilation of other output binary files (e.g. for other
; domains).
Version7 e:\V7\ NODER33 SYSOPR33
SysOpLst
NodeList REGION.033 2 ; Region 33 in zone 2
PasswordFile region33.pwd