;
; ChuggaList  Configuration file
;
; This should be your "main" Fido address. Do you need this? Not really, you
; will only need it if you're including files without "Zone,x" headers, e.g.
; the helplist: and if you use Xtralist for these, it won't be necessary.
;
Address    2:250/219.0
;
; This is your system's baudrate. If a nodelist baudrate is higher than this
; then it is set to this: so for a 2400 system, even 9600 systems will appear
; to be 2400, but 1200 systems will appear to be 1200.
;
Baud       9600
;
; These options declare "main" nodelists, i.e. distributed nodelists with
; FTS-0005 "diff" files. The parameters are a directory to find the nodelist
; files in, a "list root" and a "diff root". These "roots" have a three
; digit "day of year" number appended afterwards to produce the names of the
; lists and diffs. If the "list root" is "NList_" then the lists will be
; called "NList_001", "NList_129" etc.
;
NodeSource <Binkley$Dir>.Nodelist.Fido NList_ NDiff_
;
; These are "extra" nodelists: NOT POINTLISTS!! They may be for OtherNet(tm)
; networks that do not distribute diff files. The first parameter is the
; filename of the extra list. The second, optional, parameter is a zone
; number: this is rarely needed. It is for if the list does not include
; "Zone,x" at the beginning and you don't want it going in your zone.
;
;Xtralist <ChuggaList$Dir>.219Fake
;
; This is just the directory where you want the output files placed.
;
Nodelist <Binkley$Dir>.NodeList.Fido
;
; These are POINT lists. You give the address of the boss and the filename
; of the pointlist. The pointlist is almost FTS-0005.. just that they should
; ALL have "Point," as an identifier. If a point goes down, don't mark it as
; "Down," COMMENT IT OUT! ... Or else the point number will be interpreted
; as a node number, and all points following as points off a down, maybe
; non-existent node.. and you will (probably) get confused!
;
;Pointlist 2:250/219 25219Pts
;
; Substitutions are simply the type: one of "Password", "Phone" or "CM"; the
; address and the data to substitute (not for CM), e.g.:
;
;Phone      2:252/500 012345
;
; Notice that all occurences of the same node should be included, in this
; case 2:250/208 and 2:9225/65 are the same, and the password MUST be given
; for both: because the caller doesn't say who s/he think s/he is calling..
;
; Output nodelist formats are just given as single keywords: the presence of
; a keyword (uncommented) causes the generation of that nodelist. If no
; format is specified for generation (or if no nodelist files could be
; opened for any specified format) the nodelist(s) will not be parsed.
;
; This keyword generates a QuickBBS nodelist, with filenames "QNL_IDXbbs"
; and "QNL_DATbbs".
;
QuickBBS
;
; This keyword generates an ArchyList nodelist, with filenames "NodesIndex"
; and "NodesData". By adding "Xtras" as a parameter, a "NodesXtra" file may
; be generated.
;
;ArchyList Xtras
;
; This keyword will generate an OPUS version 7 nodelist, when I obtain the
; specifications for it. Why? Well, if you use PC-Binkley, for example, then
; ChuggaList under RISC-OS will probably be faster than XlaxNode under the
; PC Emulator.
;
;OpusV7 - Not implemented yet
;
; This keyword will do dial translations. Not needed if you use BinkleyTerm,
; but useful if you don't.
;
; The %%'s are for Binkley's BlindDial feature.
;
Dial 44-705-
Dial 44- %%0
Dial ALL %%010-
;
;SystemTree
;SysopTree
Password 2:250/219.0 Password_goes_here