home *** CD-ROM | disk | FTP | other *** search
Text File | 1991-10-17 | 156.9 KB | 5,216 lines |
-
-
-
-
-
-
-
- X_List Version 2.14
- ===================
-
-
- An eXtended AVAIL file generator
-
- For Opus v1.03 and Opus v1.1x compatible BBS systems.
-
- For Maximus CBCS 1.02 compatible BBS systems.
-
- For QuickBBS 2.64 compatible BBS systems.
-
- For RemoteAccess 1.00 compatible BBS systems.
-
- For SuperBBS 1.10 compatible BBS systems.
-
- Limited support for Opus 1.7x compatible BBS systems.
-
-
-
- X_List was Original written by Kristian Ottosen, 2:231/34.13
-
- X_List Versions above 2.05 updated by Per Holm, 2:230/22
-
- X_List documentation original by Stig Jacobsen, 2:231/16
-
- X_List documentation Modified by Per Holm, 2:230/22
- with help from George Cordner, 2:25/200,
- And Louise Thomasen, 2:231/34.22
- X_List documentation Proof-read by Dan Schmidt, 2:230/143
-
- Adjust program by Stig Jacobsen, The Ideal Copy, 2:231/16
- Adjust versions above 2.11 updated by Per Holm, 2:230/22
-
- MakeXDir & X_VanVab programs by Per Holm, Asgaard BBS, 2:230/22
- Based on Original programs by Kristian Ottosen, 2:231/34.13
-
-
- Comments & suggestions: to
- --------------------------
- Per Holm
- Asgaard BBS
- FidoNet: 2:230/22
- EggNet: 97:9451/4
- 24 hour crashmail accepted at:
- ++45-86-119043
-
- or
-
- Internet: fysiph@aau.dk
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- CONTENTS
-
-
- LICENSE . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
-
- INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . 10
-
- REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . 12
-
- RUNNING X_LIST . . . . . . . . . . . . . . . . . . . . . . . 13
-
- COMMANDLINE SWITCHES . . . . . . . . . . . . . . . . . . . . 13
-
- CONTROLFILE - INFO . . . . . . . . . . . . . . . . . . . . . 14
-
- CONTROLFILE - GENERAL . . . . . . . . . . . . . . . . . . . . 15
- License . . . . . . . . . . . . . . . . . . . . . . . . 15
- PrmFile . . . . . . . . . . . . . . . . . . . . . . . . 15
- SysOp . . . . . . . . . . . . . . . . . . . . . . . . . 15
- SystemPath . . . . . . . . . . . . . . . . . . . . . . . 15
- AreaFile . . . . . . . . . . . . . . . . . . . . . . . . 16
- XListData . . . . . . . . . . . . . . . . . . . . . . . 16
- XLogFile . . . . . . . . . . . . . . . . . . . . . . . . 16
- LogLevel . . . . . . . . . . . . . . . . . . . . . . . . 17
- FileMode . . . . . . . . . . . . . . . . . . . . . . . . 18
- BBS . . . . . . . . . . . . . . . . . . . . . . . . . . 18
- Mailer . . . . . . . . . . . . . . . . . . . . . . . . . 19
- BoardName . . . . . . . . . . . . . . . . . . . . . . . 19
- Address . . . . . . . . . . . . . . . . . . . . . . . . 20
- Drives . . . . . . . . . . . . . . . . . . . . . . . . . 20
- MaxDrive . . . . . . . . . . . . . . . . . . . . . . . . 20
- Debug . . . . . . . . . . . . . . . . . . . . . . . . . 20
- Hindustan . . . . . . . . . . . . . . . . . . . . . . . 21
-
- CONTROLFILE - PUBLIC LIST . . . . . . . . . . . . . . . . . . 22
- OutFile . . . . . . . . . . . . . . . . . . . . . . . . 22
- NewsList . . . . . . . . . . . . . . . . . . . . . . . . 22
- CommaFile . . . . . . . . . . . . . . . . . . . . . . . 22
- CommaFormat . . . . . . . . . . . . . . . . . . . . . . 23
- Index . . . . . . . . . . . . . . . . . . . . . . . . . 23
- MaxFiles . . . . . . . . . . . . . . . . . . . . . . . . 23
- Header . . . . . . . . . . . . . . . . . . . . . . . . . 24
- Footer . . . . . . . . . . . . . . . . . . . . . . . . . 24
- Level . . . . . . . . . . . . . . . . . . . . . . . . . 24
- Skip <nn> . . . . . . . . . . . . . . . . . . . . . . . 25
- Skip Barricaded . . . . . . . . . . . . . . . . . . . . 25
- Skip Text . . . . . . . . . . . . . . . . . . . . . . . 25
- Skip Missing . . . . . . . . . . . . . . . . . . . . . . 25
- Show . . . . . . . . . . . . . . . . . . . . . . . . . . 25
- First . . . . . . . . . . . . . . . . . . . . . . . . . 26
-
- X_LIST 2.14 - PAGE 2
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- Last . . . . . . . . . . . . . . . . . . . . . . . . . . 26
- MaxAreas . . . . . . . . . . . . . . . . . . . . . . . . 26
- MarkLast . . . . . . . . . . . . . . . . . . . . . . . . 26
- EuroDate . . . . . . . . . . . . . . . . . . . . . . . . 26
- Lan-Ud . . . . . . . . . . . . . . . . . . . . . . . . . 26
- Lan-Fa . . . . . . . . . . . . . . . . . . . . . . . . . 27
- Lan-Fr . . . . . . . . . . . . . . . . . . . . . . . . . 27
- Lan-Fp . . . . . . . . . . . . . . . . . . . . . . . . . 27
- Lan-Mi . . . . . . . . . . . . . . . . . . . . . . . . . 27
- Lan-Fl . . . . . . . . . . . . . . . . . . . . . . . . . 27
- Lan-NF . . . . . . . . . . . . . . . . . . . . . . . . . 27
-
- CONTROLFILE - AREA MAINTENANCE . . . . . . . . . . . . . . . 28
- Rewrite . . . . . . . . . . . . . . . . . . . . . . . . 28
- Adopt . . . . . . . . . . . . . . . . . . . . . . . . . 28
- ReFlow . . . . . . . . . . . . . . . . . . . . . . . . . 29
- RemMiss . . . . . . . . . . . . . . . . . . . . . . . . 29
- Crap . . . . . . . . . . . . . . . . . . . . . . . . . . 29
- Secure . . . . . . . . . . . . . . . . . . . . . . . . . 29
- ZapZero . . . . . . . . . . . . . . . . . . . . . . . . 30
- DupeReport . . . . . . . . . . . . . . . . . . . . . . . 30
- OrphanReport . . . . . . . . . . . . . . . . . . . . . . 30
- KeepLatest . . . . . . . . . . . . . . . . . . . . . . . 31
- Touch . . . . . . . . . . . . . . . . . . . . . . . . . 31
- AdoptComment . . . . . . . . . . . . . . . . . . . . . . 31
- Convert . . . . . . . . . . . . . . . . . . . . . . . . 31
-
- CONTROLFILE - OKFILE GENERATION . . . . . . . . . . . . . . . 32
- OkFile . . . . . . . . . . . . . . . . . . . . . . . . . 32
- OkHeader . . . . . . . . . . . . . . . . . . . . . . . . 32
- Password All . . . . . . . . . . . . . . . . . . . . . . 32
- Password nn . . . . . . . . . . . . . . . . . . . . . . 32
- Magic . . . . . . . . . . . . . . . . . . . . . . . . . 33
-
- CONTROLFILE - LOGFILE ANALYSIS . . . . . . . . . . . . . . . 34
- LogFile . . . . . . . . . . . . . . . . . . . . . . . . 34
- Upload . . . . . . . . . . . . . . . . . . . . . . . . . 34
- Download . . . . . . . . . . . . . . . . . . . . . . . . 34
- DailyReport . . . . . . . . . . . . . . . . . . . . . . 35
- SessionReport . . . . . . . . . . . . . . . . . . . . . 35
- CoSysOp . . . . . . . . . . . . . . . . . . . . . . . . 36
- Include . . . . . . . . . . . . . . . . . . . . . . . . 36
- UserAdjust . . . . . . . . . . . . . . . . . . . . . . . 37
- FreeFile . . . . . . . . . . . . . . . . . . . . . . . . 37
- QNewAll . . . . . . . . . . . . . . . . . . . . . . . . 37
-
- CONTROLFILE - MATRIX/MESSAGES/FILE-FORWARD . . . . . . . . . 38
- MsgArea . . . . . . . . . . . . . . . . . . . . . . . . 38
- MsgDrArea . . . . . . . . . . . . . . . . . . . . . . . 38
- MsgFrom . . . . . . . . . . . . . . . . . . . . . . . . 38
-
- X_LIST 2.14 - PAGE 3
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- MsgSize . . . . . . . . . . . . . . . . . . . . . . . . 39
- InBound . . . . . . . . . . . . . . . . . . . . . . . . 39
- RSPFiles . . . . . . . . . . . . . . . . . . . . . . . . 39
- WelcomeMsg . . . . . . . . . . . . . . . . . . . . . . . 39
- ThanxMsg . . . . . . . . . . . . . . . . . . . . . . . . 40
- DupeMsg . . . . . . . . . . . . . . . . . . . . . . . . 41
- ExeMsg . . . . . . . . . . . . . . . . . . . . . . . . . 42
- ExtMsg . . . . . . . . . . . . . . . . . . . . . . . . . 42
- Lan-Ul . . . . . . . . . . . . . . . . . . . . . . . . . 43
- Lan-Wt . . . . . . . . . . . . . . . . . . . . . . . . . 43
- Lan-We . . . . . . . . . . . . . . . . . . . . . . . . . 43
- Lan-Dr . . . . . . . . . . . . . . . . . . . . . . . . . 43
- Lan-Yg . . . . . . . . . . . . . . . . . . . . . . . . . 43
- Lan-Th . . . . . . . . . . . . . . . . . . . . . . . . . 43
- Lan-Pa . . . . . . . . . . . . . . . . . . . . . . . . . 43
- KillReceived . . . . . . . . . . . . . . . . . . . . . . 43
- MatrixPath . . . . . . . . . . . . . . . . . . . . . . . 44
- ForceIntl . . . . . . . . . . . . . . . . . . . . . . . 44
- Outbound . . . . . . . . . . . . . . . . . . . . . . . . 44
- HouseClean . . . . . . . . . . . . . . . . . . . . . . . 44
- Zones . . . . . . . . . . . . . . . . . . . . . . . . . 45
- Forward . . . . . . . . . . . . . . . . . . . . . . . . 45
- ForwardMsg . . . . . . . . . . . . . . . . . . . . . . . 46
- LotechMailer . . . . . . . . . . . . . . . . . . . . . . 46
- Name . . . . . . . . . . . . . . . . . . . . . . . . . . 47
- Move . . . . . . . . . . . . . . . . . . . . . . . . . . 48
- Tick . . . . . . . . . . . . . . . . . . . . . . . . . . 48
- ForwardReport . . . . . . . . . . . . . . . . . . . . . 48
-
- NEW MESSAGE TEXTFILE FORMAT . . . . . . . . . . . . . . . . . 50
-
- WELCOME, THANX, DUPE & EXE-MSG FILE OLD FORMAT . . . . . . . 52
-
- FORWARD MESSAGE FILE OLD FORMAT . . . . . . . . . . . . . . . 53
-
- OPUS LANGUAGE SUPPORT . . . . . . . . . . . . . . . . . . . . 54
-
- PWD SECURITY FILE FOR FILE-FORWARD & DISTRIBUTION . . . . . . 55
-
- TIC SECURITY FILE FOR FILE-ROUTING . . . . . . . . . . . . . 58
-
- FILE DISTRIBUTION CONTROL FILE (XL_TICK.CTL) . . . . . . . . 59
- Area . . . . . . . . . . . . . . . . . . . . . . . . . . 59
- Local . . . . . . . . . . . . . . . . . . . . . . . . . 59
- Local CRC . . . . . . . . . . . . . . . . . . . . . . . 59
- Local Restrict . . . . . . . . . . . . . . . . . . . . . 59
- Local News . . . . . . . . . . . . . . . . . . . . . . . 60
- Local To . . . . . . . . . . . . . . . . . . . . . . . . 60
- Local Subject . . . . . . . . . . . . . . . . . . . . . 60
- Local Prolog . . . . . . . . . . . . . . . . . . . . . . 60
-
- X_LIST 2.14 - PAGE 4
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- Local Epilog . . . . . . . . . . . . . . . . . . . . . . 60
- Local Format . . . . . . . . . . . . . . . . . . . . . . 60
- Hold . . . . . . . . . . . . . . . . . . . . . . . . . . 61
- News . . . . . . . . . . . . . . . . . . . . . . . . . . 61
- Subject . . . . . . . . . . . . . . . . . . . . . . . . 62
- Prolog . . . . . . . . . . . . . . . . . . . . . . . . . 62
- Epilog . . . . . . . . . . . . . . . . . . . . . . . . . 62
- Format . . . . . . . . . . . . . . . . . . . . . . . . . 63
- CRC . . . . . . . . . . . . . . . . . . . . . . . . . . 63
-
- HATCHING FILES . . . . . . . . . . . . . . . . . . . . . . . 65
-
- RESTRICTED DISTRIBUTION FILES . . . . . . . . . . . . . . . . 66
-
- INCLUDED X_LIST UTILITIES . . . . . . . . . . . . . . . . . . 68
- MAKEXDIR . . . . . . . . . . . . . . . . . . . . . . . . 68
- X_VANVAB . . . . . . . . . . . . . . . . . . . . . . . . 69
- ADJUST . . . . . . . . . . . . . . . . . . . . . . . . . 69
-
- OTHER X_LIST UTILITIES . . . . . . . . . . . . . . . . . . . 70
- X_NEW . . . . . . . . . . . . . . . . . . . . . . . . . 70
- OPINTTOP . . . . . . . . . . . . . . . . . . . . . . . . 70
-
- HISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
-
- NEW IDEAS FOR FEATURES THAT MIGHT SHOW UP LATER . . . . . . . 77
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 5
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
-
- Extremely legal stuff:
- ----------------------
-
- Copyright (C) 1988-1991 DUGFRISK UNLIMITED, All rights reserved.
- Copyright (C) 1989-1991 BIFROST UNLIMITED, All rights reserved.
-
- No part of this manual may be reproduced, transmitted,
- transcribed, stored in a retrieval system, or translated into any
- language (natural or computer), in any form or by any means,
- except as described in the following license without the prior
- written permission of Bifrost UNLIMITED.
-
- You are granted a limited license to use the software described
- in this manual. The software may be used or copied only in
- accordance with the terms of that license, which is described on
- the beginning of the next page.
-
-
- THIS SOFTWARE IS NOT FOR SALE
- -----------------------------
-
- X_LIST V2.14 is subject to the following license terms and
- conditions.
-
- SINGLE COPY SOFTWARE LICENSE
- DUGFRISK & BIFROST UNLIMITED
- ----------------------------
-
- 1.0 X_LIST V2.14 is copyrighted material. You may use it on a
- trial basis provided you do not violate the copyright and if
- you follow these simple rules. Use of X_LIST V2.14 on a
- regular basis requires purchase as described later.
-
- 1.1 You may not make any changes or modifications to X_LIST
- V2.14, and you may not de-compile, disassemble, or otherwise
- reverse-engineer it. You may not rent or lease it to others.
-
- 1.2 You may make copies of X_LIST V2.14 only under the terms of
- the following section entitled "Limited License to Copy and
- use".
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 6
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- 2.0 LIMITED WARRANTY. DUGFRISK & BIFROST does not warrant that
- the functions contained in the software will meet your
- requirements or that the operation of the software will be
- uninterrupted or error free. The warranty does not cover any
- media or documentation which has been subjected to damage or
- abuse by you. The software warranty does not cover any copy
- of the software which has been altered or changed in any way
- by you or others. DUGFRISK & BIFROST are not responsible for
- problems caused by changes in the operating characteristics
- of the computer hardware or operating system which are made
- after the delivery of the software.
-
- 2.1 DUGFRISK & BIFROST SHALL NOT IN ANY WAY BE LIABLE FOR
- SPECIAL, INCIDENTAL, CONSEQUENTIAL, INDIRECT OR OTHER
- SIMILAR DAMAGES ARISING FROM ANY BREACH OF THESE WARRANTIES
- EVEN IF DUGFRISK OR BIFROST OR ITS AGENT HAS BEEN ADVISED OF
- THE POSSIBILITY OF SUCH DAMAGES.
-
- 2.2 The warranties set forth above are in lieu of all other
- express and implied warranties, whether oral, written, or
- implied, and the remedies set forth above are your sole and
- exclusive remedies.
-
- 3.0 INTEGRATION. This License constitutes the entire agreement
- and understanding between the parties and supersedes any
- prior agreement or understanding whether oral or written,
- relating to the subject of this License. This Agreement may
- only be modified by a written agreement signed by BIFROST.
-
- 4.0 If you have a strong feeling, that you have been reading all
- this crap before, it beats me.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 7
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- LIMITED LICENSE TO COPY AND USE
- -------------------------------
-
- You are granted a limited license to copy and distribute X_LIST
- Version 2.14 under the following conditions:
-
- - X_LIST V2.14 must be copied in its unmodified form,
- complete with the following files:
- READ.ME : Release information.
- X_LIST.DOC : This documentation.
- X_LIST.EXE : Executable file.
- MAKEXDIR.DOC : Doc's for MakeXDir...
- MAKEXDIR.EXE : Utility program.
- X_VANVAB.EXE : Add Avatar color to the listings.
- ADJUST.DOC : Documentation for above.
- ADJUST.COM : Up-/Down-load adjuster.
- XL_ADVAN.CTL : Advanced controlfile.
- XL_SIMPL.CTL : Simple Opus controlfile.
- XL_OPUS.CTL : Opus sample controlfile.
- XL_MAX.CTL : Maximus sample controlfile.
- XL_QUICK.CTL : Simple QuickBBS controlfile.
- XL_QBBS.CTL : QuickBBS sample control file.
- XL_RA.CTL : RemoteAccess sample ctrl. file.
- INBOUND.CTL : Another sample control file.
- FILEROUT.CTL : Sample Forward control file.
- XL_TICK.CTL : Sample Tick Process file.
- BADEXT.TXT : Ext message example.
- FWDMSG.TXT : Forward message example.
- DUPEMSG.TXT : Dupe message example.
- NOARCMSG.TXT : Please Arc message example.
- THANXMSG.TXT : Thank you message example.
- THNX_MSG.TXT : Another Thanx message example.
- WELCOME.TXT : Example of welcome message.
-
- - You may change the archive format to any archive type,
- as long as none of the files in the archive have been
- changed and the name are XLIST214.xxx.
-
- - All the files in the archive must be distributed
- together.
-
- - No fee, charge or other compensation may be accepted or
- requested by anyone without the express written
- permission from DUGFRISK or BIFROST unlimited. This
- includes disk vendors.
-
- - X_LIST V2.14 may not be distributed in conjunction
- with any other product or service without a specific
- license from DUGFRISK UNLIMITED or BIFROST UNLIMITED.
-
-
- X_LIST 2.14 - PAGE 8
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- ************************************************************
-
- - In order to use X_LIST V2.14 on a regular basis, you
- must at least send a postcard to the following address:
-
- DUGFRISK UNLIMITED
- Kristian Ottosen
- Mejlgade 69, 4.tv
- DK-8000 Aarhus C.
- DENMARK
-
- All we ask is to be able to show your postcard to our
- grandchildren and say "Look at this one Williamina -
- here's another nice postcard from a guy at Papua New
- Guinea".
- ************************************************************
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 9
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- INTRODUCTION
-
- X_List v1.00 was only meant to be a fast file listing generator
- and making it available for downloading on your Opus 1.03 system.
- However with version 2.xx, some unique and superior features were
- added... Have a look!!..
-
- o Generation of a public list. All files available for user
- download or file-requesting. There are various options
- available to give you a large amount of control over what is
- being included in this file.
-
- o Output file in a Commafile format for further processing by
- your DataBase program, now using a user defined format.
-
- o Various FILES.BBS maintenance functions, such as stripping
- ^Z's, removing 'missing' files, auto-adopting orphan files
- etc.
-
- o Generation of OKFILE.LST in either OPUS or FrontDoor format
- (used by Opus/Binkley or Frontdoor for approving file-
- requests).
-
- o Sending thank-you messages to uploaders and nasty notes if a
- duplicate file is uploaded, or an uploaded file isn't
- arc'ed. It will also adjust the users upload, if an unwanted
- (dupe or not arc'ed) file is uploaded.
-
- o Sending welcome-on-this-system-hope-you-like-it messages to
- new users.
-
- o Generating a daily report about the use of your system as a
- message to the SysOp.
-
- o Ability to move files from one directory to another.
-
- o Ability to act as a file-robot, i.e. it can automatically
- attach new/changed files for pickup by another system.
-
- o Various security options to be used with the file-robot and
- move-file options.
-
- o Ability to process files in a TICK compatible File
- Distribution Network, and announce files arrived, into an
- public echo-mail area.
-
- o Ability to mail a daily report to the sysop of file
- processed by the file-robot and file-distribution-robot.
-
-
-
- X_LIST 2.14 - PAGE 10
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- o Free-files is a special term. It's simply files that do not
- count in your users download. X_List/Adjust will subtract
- the size of the free-files downloaded from a user record..
-
- o Deletion of old versions of a file.
-
- o Multi Zone and Point support.
-
- o Supports several BBS systems: OPUS v.1.0x, OPUS 1.1x,
- Maximus 1.02, QuickBBS v.2.64, RemoteAccess v1.0x,
- SuperBBS v1.1x.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 11
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- REQUIREMENTS
-
- To run X_List you need:
-
- An IBM-PC or compatible.
- About 200 kb of available memory - More won't hurt.
- ANSI.SYS installed in your CONFIG.SYS.
- An Opus v1.03 compatible file-system, message-system and
- logfile, an Opus 1.1x compatible file-system, a Maximus 1.02
- compatible file-system, a RemoteAccess 1.00 file-system, a
- SuperBBS 1.10 file-system (using QuickBBS Compatible Log and
- Files.BBS's), or a QuickBBS v2.64 file system using
- utilities for importing messages to QuickBBS message system.
-
- NOTE: Using Opus 1.7x, You need to convert the FILESBBS.DAT
- file into single FILES.BBS (compatible with OPUS 1.1x)
- before running X_List, X_List are curently not able to
- handle the FILESBBS.DAT database..
-
- X_list has been tested on a variety of systems, it will also work
- with compatible mailers like BinkleyTerm v2.00 and later
- versions, and FrontDoor v1.99.
-
- X_List v.2.xx was originally written in Turbo Pascal v4.0, later
- ported to Turbo Pascal 5.0 and 5.5.
-
- X_List.Doc was created using Word Perfect v.4.2, later updated
- using Word Perfect v.5.0.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 12
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- RUNNING X_LIST
-
- Not much to be said about this. You will probably want to run it
- on a daily basis, perhaps every time you do your daily
- maintenance.
-
- X_List always needs a controlfile, because it uses this to figure
- out what to do.
-
- If you run X_List like: "X_LIST" <Enter>, it will only use the
- default controlfile name of X_LIST.CTL.
-
- If you want to use another controlfile, you can give it like:
- "X_LIST MYCTL". You need not to give an extension to the
- filename; X_List assumes the extension .CTL if none is given.
-
- Several control-files are supplied with X_List itself. A simple
- one for just making a list of available files, an all-singing
- all-dancing version, that shows all the abilities of X_List, and
- some other strange setups.
-
- COMMANDLINE SWITCHES
-
- The command line of X_List has the following format:
-
- X_LIST [<ControlFile>] [<Switch> [<Switch> ..]]
-
- <ControlFile> : An X_list control file, if no control file is
- specified, X_List will default to use a file
- named 'X_LIST.CTL' in the current directory.
-
- <Switch> : One or more of the following switches:
-
- /H<File> : Hatch a file for File Distribution for more
- information see page 65.
- /A<Area> : Area where a file should be hatched.
- /R<flags> : Special Restriction flags for Hatched files.
- /T<Tick> : Use another TICK control file (see also page 48
- and page 55 for additional information).
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 13
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- CONTROLFILE - INFO
-
- All paths must be terminated with a back-slash, like: C:\OPUS\
-
- '%' is the comment-character. When this character is encountered
- in the controlfile, the rest of the line is skipped.
-
- There is one statement per line. Most statements only makes sense
- if they're listed once in the controlfile.
-
- Unless otherwise stated, all statements are entirely optional.
- If a statement is not given, it is assumed to be turned off.
-
- If a statement is given twice, the last statement will be active,
- this goes for the PrmFile too. An exception from this is the
- statements like Forward, Crap, Name etc. which will be stacked.
-
- All statements are case-insensitive. Some of the parameters may
- be case sensitive.
-
- You can use standard Dos device-names anywhere. If you want to
- let the dupe-report go directly to your printer, your could
- specify "DupeReport LPT1" or something of that nature.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 14
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- CONTROLFILE - GENERAL
-
- These are some common things that is needed for overall operation
- of X_List.
-
- License: The license number was introduced in ver. 2.03 and
- gave those who registered some extra options, this
- facility was skipped in ver. 2.04, but the control
- statement has been kept for downward
- compatibility.
-
- "Licence <LicenceNumber>"
-
-
- PrmFile: Name of the OPUS v1.03 or OPUS 1.1x parameter file
- which contains useful information like BoardName,
- LogFile, MatrixPath, SysOp (name of the SysOp),
- Zone, Net, Node, Address, InBound, OutBound and
- SystemPath. When using this option you may omit
- these statements in the X_list controlfile.
- X_List will automatically detect if it is a 1.03
- or a 1.1x .PRM file, and change the BBS flag.
-
- "PrmFile C:\Opus\BBS.Prm"
-
-
- SysOp: The name of the SysOp, if not specified, the name
- in the PrmFile will be used, if no PrmFile is
- selected, the default name will be SysOp.
-
- "SysOp Per Holm"
-
-
- SystemPath: This statement is used to tell X_LIST where the
- system information files are to be located.
- The System files are:
-
- Opus 1.03 -> SYSTEM??.BBS
- Opus 1.1x -> SYSTEM##.DAT
- Opus 1.7x -> SYSFILE.DAT & SYSMSG.DAT
- Max 1.02 -> FILES.DAT (changeable)
- RA -> FILES.RA (changeable)
- QuickBBS -> (none use 'AreaFile' instead)
-
- "SystemPath C:\Opus\"
-
- When using Maximus and RemoteAccess you may add a
- filename after the path to change the default name
- of the system files..
-
-
- X_LIST 2.14 - PAGE 15
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- "SystemPath C:\Max\FILES.DAT"
- AreaFile: QuickBBS area description file. The file should
- tell where to find the file areas on a QuickBBS
- system, and point to the QuickBBS file area file.
- When used the System??.BBS/System??.DAT or the
- FILES.RA files will not be used, unless you use
- the MsgArea <areanumber> option. The QuickBBS
- areas will be numbered staring with area 1 for the
- first line, 2 for the second etc.....
-
- "AreaFile C:\QBBS\FLSEARCH.TXT"
-
-
- XListData: This creates a small file which is used for
- storing such things as when X_List was last run
- etc,etc.,. Normally you have no need to mess with
- this file, but you can delete it to force X_List
- to scan your logfile from the beginning if needed.
- Please note, that if the file is missing, the
- built-in mailrobot (if enabled) will not attempt
- to send any files. This file also defaults to
- NUL:. If not given, the logfile will be scanned
- from the start each time, and you will be unable
- to use the MailRobot (below).
-
- "XListData C:\X_List\X_List.Dat"
-
- XLogFile: When running X_List early in the morning (when
- even SysOp's feel tired) it is nice to have a log
- of what really happened. Use this statement to get
- an OPUS compatible logfile..
-
- "XLogFile C:\X_List\X_List.Log"
-
- ** WARNING: do not use a logfile already used by 'LogFile' **
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 16
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- LogLevel: Use this to get a more or less informative log,
- use a value between 0 and 6. "LogLevel 6"
- 0 : No log info.
- 1 : '!'
- 2 : '!','*'
- 3 : '!','*','+'
- 4 : '!','*','+',':'
- 5 : '!','*','+',':','#'
- 6 : '!','*','+',':','#',' '
-
- "LogLevel 5"
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 17
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- FileMode: This control statement are made for use with some
- LAN's and Multi-task programs. The basic idea is
- to change the method a file are opened, by default
- Turbo Pascal opens all files in Read/Write mode
- (FileMode 2), this does cause some LAN and Multi-
- task programs to proces a read error if to tasks
- or workstations wishes to access the same file...
- The statement need a value for the FileMode to be
- used, please refer to you LAN manual for mode
- information.
-
- "FileMode 2 % R/W mode"
- "FileMode 0 % R/O mode"
-
-
- BBS: This control statement is used to tell X_List
- which BBS type it must support. The default BBS
- type is 'OPUS' v 1.03. The BBS type will be
- updated by the PrmFile command, to the correct
- OPUS version, if you want to change this place one
- of these commands after the PrmFile command:
-
- "BBS OPUS % Opus ver 1.03"
- "BBS O % Opus ver 1.03"
- "BBS OPUS1.10 % Opus ver 1.1x"
- "BBS 1 % Opus ver 1.1x"
- "BBS 7 % Opus ver 1.7x"
- "BBS Maximus % Max version 1.02"
- "BBS M % Max version 1.02"
- "BBS QuickBBS % QuickBBS mode"
- "BBS Q % QuickBBS mode"
- "BBS RemoteAccess % RemoteAccess"
- "BBS R % RemoteAccess"
- "BBS SuperBBS % SuperBBS"
- "BBS S % SuperBBS"
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 18
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- Mailer: Lately I discovered that FrontDoor does not use
- the same OkFile format as OPUS and Binkley, this
- statement may be used to generate a frontdoor
- compatible okfile, with time the statement will
- get a more general meaning. the default is "OPUS":
-
- "Mailer OPUS % Opus ver 1.03"
- "Mailer O % Opus ver 1.03"
- "Mailer OPUS1.10 % Opus ver 1.1x"
- "Mailer 1 % Opus ver 1.1x"
- "Mailer RemoteAccess % RemoteAccess"
- "Mailer R % RemoteAccess"
- "Mailer Binkley % Binkley Term"
- "Mailer B % Binkley Term"
- "Mailer FrontDoor % FrontDoor"
- "Mailer F % FrontDoor"
-
-
- BoardName: Use this keyword to state the name of your system.
- All characters including % (comment) are allowed
- after the BoardName control statement.
-
- "BoardName Asgaard BBS."
-
- *** WARNING: No Comment on Boardname Statement ***
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 19
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- Address: X_List need to know your system address, this
- statement may be used to tell X_List your Full
- address.
-
- "Address 2:230/22"
-
- or
-
- "Address 2:230/22.3"
-
- You may now specify Aka addresses, these are used
- when forwarding files or messages to other Zones
- that you are a member of:
-
- "Address 2:230/22 % FidoNet"
- "Address 27:1345/100 % SigNet"
- "Address 97:9451/4 % EggNet"
-
- You may have between none and ten Aka addresses
- (this is the same as 11 Address statements).
-
- A special feature with the address statement is
- point Zero, the addresses 2:230/22 and 2:230/22.0
- will internally be treated as he same address,
- except in messages, where they will be written as
- entered in the Address lines.. This feature may be
- used for cosmetic reasons.
-
-
- Drives: A list of drives to check for free space.
-
- "Drives CDEFIJ"
-
- Default is drives CDEFGHIJ. Last drive is Z
- This command should be used instead of the
- MaxDrive statement.
-
-
- MaxDrive: The maximum number of drives to check for free
- diskspace, "MaxDrive 3" will check drive C,
-
- "MaxDrive 4" will check drive C and D.
- "MaxDrive 0" will not check any drives.
-
- This Control statement has been kept for downward
- compatibility with older versions of X_List. The
- statement may be removed in future versions.
-
-
- Debug: Enable the internal debugger, just in case.
-
- X_LIST 2.14 - PAGE 20
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
-
-
- Hindustan: Proper generation of messages cannot be expected
- if this is set to a wrong value. Please refer to
- the sample controlfiles for explanation of usage.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 21
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- CONTROLFILE - PUBLIC LIST
-
- The public list is the file that shows all files available for
- download on your system. These statements need not be used, but
- you can gain a better control over the program if you do.
-
- OutFile: X_List needs to know where to put the resulting
- public list (list of all files on the board), and
- what to name it.
-
- "C:\FILE\1\ASG_LIST.TXT"
-
- The outputfile defaults to NUL: - I.e. no
- outputfile at all.
- You may use the X_VANVAB program to add some
- avatar or ANSI colors to this file, depending on
- the BBS system you are using.
-
-
- NewsList: X_List may make a separate list containing only
- the latest files arrived at your BBS.
-
- "NewsList F:\MISC\ASG_NEWS.TXT"
-
- You may use the X_VANVAB program to add some
- avatar colors to this file, if you run an OPUS
- system..
-
-
- CommaFile: As well as the above file, you may want another
- file for further processing by other programs.
- This states the name of an outputfile in DBase III
- (or Basic) format. eg. a raw file without
- comments, with each field separated by a comma
- (,). The record-layout for this file can be found
- in the resulting commafile file.
-
- "CommaFile C:\DB\CommaLst.TXT"
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 22
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- CommaFormat: If you don't like the default commafile format,
- you may define your own format of the CommaFile
- The following words may be used:
-
- %file : Name of the file.
- %size : The size of the file.
- %area : Area number of the file.
- %comment : Insert file comment in DBASE
- file. *** VERY SLOW ***
- %year : The year part of the file date.
- %month : The month part of the file date.
- %day : The day part of the file date.
- %hour : Hour part of the file time.
- %min : minute part of the file time.
- %sec : Sec. part of the file time.
- %zone : Your zone number.
- %net : Net number.
- %node : Node number.
- %point : Point number.
- %address : The full Zone:Net/Node.Point
- address.
-
- "CommaFormat '%file','%area','%size'"
-
-
- Index: Future utilities from Dugfrisk unlimited and
- Bifrost unlimited may require an X_list generated
- Master-index file. This is made by specifying the
- path to this file and the day of the week when it
- should be written.
- 0=Sunday..6=Saturday and 7=All.
- The file will be named XXXXYYYY.IDX where XXXX and
- YYYY are net and node number as 4 HEX digits.
-
- "Index 5 C:\OPUS\DANELIB\"
-
- Will write an index every friday!!
- The format of this file will be described later in
- this document.
-
-
- MaxFiles: How many files do you expect to have on your
- system at any time? Should be stated. It is set to
- a default value of 1500 files. It is also used for
- allocating memory for sorts etc. The maximum limit
- is 10.000 files.
-
- "MaxFiles 1500"
-
-
-
- X_LIST 2.14 - PAGE 23
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- Header: If you want a header at the start of the public
- list, you can give a path to a file here. It could
- be the LOGO.BBS file. For instance:
- C:\OPUS\MISC\LOGO.BBS. Then LOGO.BBS would be the
- first thing the user will see, when viewing your
- total filelist. Useful for communicating with the
- typical download freak. At least you should write
- the name of your board here, since X_List defaults
- to not putting any header in the list at all. You
- may use wildcards in this statement, this will
- give you a random header file (will choose one of
- Max 10)..
-
- "Header C:\Opus\Misc\Logo?.BBS"
- "Header C:\Opus\Misc\Logo.BBS"
-
-
- Footer: You may also insert a text file in the end of the
- Public list using the Footer statement.
-
- "Footer C:\Opus\Misc\Logo?.BBS"
- "Footer C:\Opus\Misc\Logo.BBS"
-
- Level: Only areas that allows users with this level or
- below, should be written in the public list.
- Usually you will not want files intended for
- SysOp's only to be included in a public file, so
- you could use: "Level Priv" to include all areas
- with access for privileged or below users. The
- default is to use a level of normal. Levels known
- by the program is: 'Twit', 'Disgrace', 'Limited',
- 'Normal', 'Worthy', 'Privil', 'Favored', 'Extra',
- 'Clerk', 'AsstSysop' and 'SysOp'.
- QuickBBS and RemoteAccess users may use a value in
- the range 0 - 65535 for user levels. (the usable
- levels are described in the QuickBBS and
- RemoteAccess manuals). Eg. "Level 32000"
-
- "Level Extra"
- "Level 32000"
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 24
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- Skip <nn>: This tells X_List to skip a particular area,
- regardless of what level it has. Used for
- overriding the "Level" keyword above.
-
- "Skip 23"
-
- This option should now work within QuickBBS mode,
- the areas from the FLSearch file will be numbered
- from Area one and follow the linienumbers in the
- file..
-
- Skip Barricaded: Use this option to tell that you don't want to
- include barricaded areas in the listing,
- regardless to what level they require.
-
- ** OPUS/MAX/RA ONLY **
-
-
- Skip Text: Strip all text-only lines from the FILES.BBS
- files. eg. produce a public list with a file
- listed on every single line. The Skip Text
- statement may be reversed for a single area using
- 'Show <area> Text'.
-
-
- Skip Missing: When generating the Public list you may decide
- that all those missing files should not be in the
- list. This option will leave them out of the
- Public List. This statement may be reversed for a
- single area using 'Show <area> Missing'.
-
-
- Show: The exact opposite of "Skip". It will include an
- area in the public list regardless of level.
-
- "Show 23"
-
- You may also reverse the 'Skip Test' and 'Skip
- Missing' statements for a one or more areas by
- using one or more lines like the following:
-
- "Show 23 Missing"
- "Show 24 Missing"
- "Show 23 Text"
-
- This option should work within QuickBBS mode, the
- areas from the FLSearch file will be numbered from
- Area one and follow the linienumbers in the file..
-
-
-
- X_LIST 2.14 - PAGE 25
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- First: Well, Kristian has put all his file-areas in the
- range 50-99, that is because he doesn't want
- X_List wasting precious time wading through areas
- 1-49. This statement tells what SYSTEMnn.BBS/.DAT
- file, Area.Dat or FILES.RA entry to use.
- ** Not available for QuickBBS **
-
- "First 1"
-
-
- Last: Tells which is the last SYSTEMnn.BBS file or last
- area record to be looked into.
- ** Not available for QuickBBS **
-
- "Last 99"
-
- MaxAreas: When using Maximus, it is possible to have the
- file areas described by character like AA BZ etc.
- Since X_List is limited to 255 areas described by
- numbers 1 to 255, we have to translate the Maximus
- areas above 99 to something X_List will be able to
- handle... The MaxAreas statement will start
- numbering the special areas beginning with area
- number 100... X_List will accept one or more
- MaxAreas control lines.. In commands like Skip,
- Adopt and other commands using an area number, you
- have to use the number of the Maximus areas,
- instead of the characters.
-
- "MaxAreas AA AB AC BA B1"
- "MaxAreas ZA ZB ZC"
-
- MarkLast: X_list defaults to mark last months file with a
- '*' in the Opus way.
- You may change the number of days using MarkLast.
-
- "MarkLast 30"
-
- EuroDate: Use European date form ('DD/MM-YY') in the Public
- filelists.
-
-
- Lan-Ud: Update info in the Public List.
-
- "Lan-UD Updated by % X_LIST V2.14"
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 26
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- Lan-Fa: The area information in each area header in the
- public list.
-
- "Lan-FA File Area # % File area # (header)"
-
-
- Lan-Fr: This line will be inserted just below the area
- header if the files are available for filerequest.
-
- "Lan-FR (Matrix filerequest possible)"
-
-
- Lan-Fp: If the area is password protected this message
- will be inserted under the Area header.
-
- "Lan-FP (You need a password to f.req here)"
-
-
- Lan-Mi: If a file is not available this message will be
- inserted instead of the file date.
-
- "Lan-MI Disappeared % Missing files"
-
-
- Lan-Fl: And this in the and of the Public list.
-
- "Lan-FL titles listed % Total no of files"
-
-
- Lan-NF: If you wish to change the comment in top of the
- NewsList file, you need to use this statement.
-
- "Lan-NF New files: %1 day period %2 - %3"
-
- The following Meta strings may be used:
-
- %1 : Number of days to be included, the value
- is entered using the MarkLast statement.
-
- %2 : First date of the period.
-
- %3 : The current date...
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 27
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- CONTROLFILE - AREA MAINTENANCE
-
- X_List runs through every FILES.BBS file on your system, so why
- not do some housekeeping while we're at it?
-
- Rewrite: You may have noticed that programs such as Fido-
- Fam insists on putting a Ctrl-Z at the end of
- every modified FILES.BBS. Whenever a file gets
- added to this FILES.BBS by Opus, (beyond the Ctrl-
- Z) your users won't see it, because Opus stops
- reading it when it encounters the Ctrl-Z.
- This cures the problem by writing a new FILES.BBS
- without ^Z's while reading the old one. Note that
- all lines after a ^Z is lost. This is a temporary
- limitation and will be resolved in a future
- release.
-
- "Rewrite % Rewrite all areas"
-
- You may also choose to do a rewrite in a few
- areas, or disable it for some..
-
- "Rewrite 2 % Rewrite in area 2"
- "Rewrite 4 - % Skip rewrite of area 4"
-
-
- Adopt: X_List may find some orphan files in your
- fileareas. With this statement you can get it to
- add these parent-less files to the FILES.BBS, thus
- making them available for download by your users.
- It may have undesirable results, though...
- Of course it will not insert files that should not
- be available for downloading. This is: FILES.BBS,
- FILES.BAK, DIR.BBS, DIR.BAK and X_LIST.DIR.
-
- "Adopt % Adopt all areas"
-
- You may also choose to do an adopt files in a few
- areas, or disable it for some..
-
- "Adopt 2 % Adopt in area 2"
- "Adopt 4 - % Skip adopt in area 4"
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 28
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- ReFlow: X_LIST will tidy your FILES.BBS in different ways
- by splitting descriptions too long to be displayed
- by Opus<Tm> into separate lines with spaces
- inserted to get the indent right
-
- "ReFlow % Reflow all areas"
-
- You may also choose to do a rewrite in a few
- areas, or disable it for some..
-
- "Reflow 2 % Reflow in area 2"
- "Reflow 4 - % Skip reflow of area 4"
-
-
- RemMiss: If you want to add style to your FILES.BBS's you
- can use this option to remove any lines in them
- that states a file is missing. Use however with
- care, as your descriptions of any missing files
- will be gone!
-
- "RemMiss % Remove missing files from all areas"
-
- You may also choose to do a rewrite in a few
- areas, or disable it for some..
-
- "RemMiss 2 % Remove Miss. files in area 2"
- "RemMiss 4 - % Keep Missing files in area 4"
-
-
- Crap: This option informs X_List that you don't want to
- keep the listed file. If it sees it while wading
- through the areas, it will be erased. This is
- useful for scratching things such as DIR.BAK,
- FILES.BAK, ZAXXON.ARC (non-PD) etc. If you want to
- zap more than one file, you can give this
- statement several times. The filename given should
- not include a path.
-
- "Crap Dir.Bak"
- "Crap Masturba.Arc"
- "Crap *.GIF"
-
- **** Warning: Watch out for Wildcards ****
-
-
- Secure: When running through the Areas X_List will make a
- directory Files.Gbs to ensure that no one just
- uploads a Files.GBS..
- ** Used to fix an OPUS 1.03 and 1.1x bug **
-
-
- X_LIST 2.14 - PAGE 29
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- ZapZero: While speeding through the areas , X_List may
- delete empty files from the directories
- (unsuccessful uploads etc.).
-
-
- DupeReport: On a large system, there will typically be above
- 1000 files available for download. This makes it
- fairly hard to ensure that no duplicate files are
- to be found around in the areas. With this option
- you can specify a filename which will end up being
- a nice report of duplicate files for the SysOp
- enabling you to cut down the use of your precious
- diskspace. A file is called a DUPE, if there is
- another file with the same name (the extension may
- be different), and the smallest file is less than
- 20% smaller than the bigger one. This is not the
- most safe criteria, but will work most of the
- time. Here is an example where X_list will say
- that two files are dupes but they are NOT:
- OPINT102.ZIP 57014 bytes.
- OPINT102.5IP 57461 bytes.
- This dupe criteria has been changed to be like
- this staring with version 2.10, because of all the
- new packing methods that has entered the scene
- these days.
- DupeReport [/M] [/C] [/D] [<DupeFile>]
- /M : Send report as Msg to SysOp.
- /C : Mail report to CoSysOps.
- /D : Delete file after sending.
-
- "DupeReport /M /C /D C:\Tmp\Dupes.$$$"
-
-
- OrphanReport: If used, this will create a file to be used for
- writing a report of orphan files on your system.
- Useful if you want to check out floating files
- before making them available for download.
-
- OrphanReport [/M] [/C] [/D] [<OrphanFile>]
- /M : Send report as Msg to SysOp.
- /C : Mail report to CoSysOps.
- /D : Delete file after sending.
-
- "OrphanReport /M /C /D C:\Tmp\Orphan.$$$"
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 30
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- KeepLatest: Say you want to delete old copies of the nodelist
- updates - and only keep the latest four:
-
- "KeepLatest 4 C:\FILE\NODELIST\NODEDIFF.A*"
-
- X_LIST will then look at all the matching files
- and delete these files except those 4 with the
- latest dates.
- This option should be used with great care, a
- typing error might cause you to loose some
- important files...
-
-
- Touch: Touch is simply the good old thing ,it stamps
- current date and time on existing files. This
- version doesn't use wildcard like '*' or '?'.
- Usage:
-
- "Touch E:\OPUSFILE\INFO\ASG_LIST.ARC"
-
- ** WARNING: NEVER TOUCH THE FILES X_LIST IS WORKING ON **
-
-
- AdoptComment: When adopting new files your X_LIST might add a
- comment, this can be done like this:
-
- "AdoptComment (description missing)"
-
-
- Convert: And you may replace special characters in the
- public list and FILES.BBS.
- The below translations are useful in Denmark:
- Convert { æ % Ascii 145 "ae"
- Convert | ¢ % Ascii 155 "oe"
- Convert } å % Ascii 134 "aa"
- Convert [ Æ % Ascii 146 "AE"
- Convert \ ¥ % Ascii 157 "OE"
- Convert ] Ã… % Ascii 143 "AA"
- Convert ^F å
- Convert ^Q æ
- Convert ^[ ¢
- Note that some Download Counters use one or more
- of the above characters, and this option may cause
- the Download counter to get confused by changing
- these characters..
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 31
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- CONTROLFILE - OKFILE GENERATION
-
- If you want to, X_List can create an OkFile for you too. An
- OkFile is the file that Opus,Binkley and FrontDoor uses for
- approving file-requests. X_List will include each area that is in
- the public list in the OkFile too. It will look something like
- the following for an OPUS/Binkley OKFILE: "D:\FILES\OPUSUTIL\*.*"
- Each line matches one of the File areas.
-
- OkFile: This names the resulting list of approved files
- for file request. Depending on the mailer used,
- this file will be in either Opus/Binkley or
- FrontDoor format...
-
- "Okfile C:\NET\OKFILE.LST"
-
-
- OkHeader: You may have some files or directories in your
- OKFILE.LST that are not in any of your
- SYSTEMnn.BBS/SYSTEMnn.DAT/AREA.DAT/FLSEARCH.CTL
- files. This may include your netfilearea, your
- upload area or the like. This statement names a
- file which is written to the OkFile before all of
- the regular areas. This file must have the same
- structure as the OKFILE itself. Check you mailer
- documentation for more information.
-
- "OkHead C:\Ctl\OkHead.TXT"
-
-
- Password All: When generating an Opus/Binkley compatible OKFILE
- you may add a password to all file areas. Note,
- that in the password the case IS significant!
-
- "Password All SECRETS"
-
- ** Not available for The FrontDoor Mailer **
-
-
- Password nn: When generating an Opus/Binkley compatible OKFILE,
- you may add/remove/change the password for a
- single area.
-
- "Password 55" Remove password
- "Password 56 SECRET" Add/Change password
-
- ** Not available for The FrontDoor Mailer **
-
-
-
-
- X_LIST 2.14 - PAGE 32
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- Magic: Use this option to make some often updated files
- available using a magic filename. To be used like
- this.
-
- "Magic Nodelist C:\File\NetInfo\Nodelist.A*"
- "Magic Nodediff C:\File\NetInfo\NodeDIFF.A*"
- "Magic Fnews C:\File\NetInfo\Fnews???.Arc"
- "Magic Secret C:\Pvt\Secret*.* Password"
-
- ** Note Passwords does not work along with **
- ** the FrontDoor Mailer. **
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 33
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- CONTROLFILE - LOGFILE ANALYSIS
-
- If you want it, X_List will send various messages to your users,
- depending on what they have uploaded to your board. It can also
- send welcome messages to new users.
- It looks in the Opus/Maximus/QuickBBS/RA logfile for the required
- information, and all logging levels ought to work.
- There are sample messages supplied in the distribution arcfile.
-
- Note the X_List Opus 1.10 log analysis will only work if the
- SysOp language are English...
-
- Note, that with R.A. 1.10, You must not have changed the naming
- of the Months, if You are using different *.RAL files, to provide
- different languages. If You have changed the months in a RAL file
- then X_List processing of the logging in that month, won't work,
- as R.A. 1.10 uses the current users language in the logging. This
- has been reported to the Author, and hopefully he will hardcode
- the names of the month in to the program, at least for logging
- purpose.
-
- LogFile: This is the log file we want to analyze. The file
- must be like an OPUS log file or a QuickBBS log
- file. RemoteAccess must use a QuickBBS compatible
- log file. You may add up to 10 LogFile statements.
-
- "LogFile C:\Opus\Opus.Log"
- "LogFile C:\Max\Max.Log"
-
-
- Upload: When analyzing an OPUS/Binkley compatible log
- there might be some external programs adding some
- other upload descriptions instead of 'UL-' like
- the OPUS, Binkley uses 'Received-'.
-
- "Upload +Received- % Use Binkley Uploads."
- "Upload =RECV % Use BIOPUS entrys too"
-
- Note the first character which is the log level
- indicator (eg. '=').
-
-
- Download: And for the Download we have excactly the same
- facility:
-
- "Download +Sent- % Use Binkley Downloads"
- "Download =SEND % And BIOPUS"
-
-
-
-
- X_LIST 2.14 - PAGE 34
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- DailyReport: If you want it, we can send you a message every
- day about the usage of your system since X_List
- last was run. It will be sent as a private message
- to 'MsgFrom' (above) and end up in area 'MsgArea'
- (above).
- 'DailyReport [/M] [/C] [/D] [<ReportFile>]'
- /M : Mail the report.
- /C : Send copy to CoSysOps.
- /D : Delete after sending.
-
- "DailyReport % Send report to all"
- "DailyReport /M /C D:\Reports\Daily.Rep"
-
-
- SessionReport: When processing mail, it is nice to check if all
- mailsessions during the last period was running as
- they should... This statement will enable some
- nice report features..
-
- SessionReport [<Flags>] [<Sessionfile>]
-
- <Flags> : [/M] [/C] [/D] [/A] [/I] [/O]
-
- /M : Mail the Report.
- /C : Copy for CoSysOps....
- /D : Delete file after mailing.
- /F : Full Report. (Default)
- /I : Report incoming sessions only.
- (other system dialing)
- /O : Report outgoing sessions only.
- (this system dialing)
- /U : Report BBS connections.
- /A : Append to existing File.
-
- If no SessionFile is specified, the SessionReport
- will be placed in the DailyReport....
-
- "SessionReport"
-
- "SessionReport /M /D /O D:\Tmp\Session.$$$"
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 35
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- CoSysOp: You may wish to send a copy of the daily report to
- your CO-SysOp Mrs Ackermann.
-
- "CoSysOp Mrs. Ackermann"
-
- And to the other one who is a point somewhere.
-
- "CoSysOp 2:230/22.3 Cr. Ackermann"
-
- To use this option you need the Matrix path set to
- the NetMail directory or the AREA: tag set, this
- is described later in this document.
-
- CoSysOp [<Flags>] [<Node>] <Name>
-
- <Flags> : Report Types for this CoSysOp
- (Default are All report Types)
- /R : Send Daily Report
- /S : Send Session Report
- /D : Send Dupe Report
- /O : Send Orphan Report
- /F : Send Forward Report.
- /1 : Send Reports of type 1
- /2 : Send Reports of type 2
- /3 : Send Reports of type 3
- For usage of /1, /2 and /3 See pp 49
-
- <Node> : Nodenumber of the CoSysOp (Optional)
-
- <Name> : Name of the CoSysOp
-
-
- Include: Normally X_List checks the public list to see if
- an uploaded file is a dupe. However, if your
- upload area is not included in the public list,
- you can use this statement to inform the program
- where to find newly uploaded files.
- give a path, and a wildcard specification -
- Exactly as with the Dos DIR command.
-
- "Include C:\Uploads\*.*"
- "Include C:\Inbound\*.*"
- "Include C:\Gif\*.Gif"
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 36
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- FreeFiles are files for downloading that won't have any influence
- on your users download-amount. Often, you don't want files such
- as the Opus end-users manual to count in the upload:download
- ratio.
- X_List can create a file, that states what adjustments should be
- should be made to the User file. This file is also used for
- subtracting uploaded dupefiles from the users upload amount.
- Due to the proposed changes to the structure of the USER file,
- the actual adjustment will be made by an external program
- 'ADJUST' - It should be included in the X_List archive.
-
- UserAdjust: Gives path and filename to the user adjustment
- controlfile. The format of this file is described
- in the ADJUST.DOC file.
-
-
- FreeFile: States a file that is 'free' to download. The size
- of this file will be put in the controlfile above
- used by the adjuster-program. This statement can
- be given as many times as needed.
-
-
- QNewAll: When running in QuickBBS mode, you have two
- methods for checking for new users, either you
- have to be sure if the user is registered, or you
- may write welcome messages to users who are not
- yet in the UserFile.
-
- "QNewAll % Write to all possible new users"
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 37
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- CONTROLFILE - MATRIX/MESSAGES/FILE-FORWARD
-
- MsgArea: This should be the number, path or area name of
- the message area, that all X_List messages are put
- in. Currently, all messages sent will be made
- private, regardless of what attribute the
- corresponding area have set. The messages
- generated will be the .MSG file format used by
- OPUS 1.03. Here are some examples:
-
- "MsgArea 1 % Use Opus Area one for messages"
- "MsgArea c:\Msg\Local\ % or the Path"
-
- When using a QuickBBS or RemoteAccess system you
- place the messages into a QBBS/RA compatible
- message database.
-
- "MsgArea c:Ra\Msgs\ 1 % Add to area 1"
-
- You may also chose to generate .PKT files to be
- placed in the inbound area for tossing to the
- correct area. Here is how to handle this:
-
- "MsgArea AREA:LOCAL % Or Echo Mailname .PKT"
- "MsgArea AREA: % This is for the Matrix Area"
-
-
- *** Note that if you are using the AREA: options
- you must set the 'InBound' Directory, and 'AREA'
- must be in uppercase.
-
-
- MsgDrArea: If you want your Daily report in another area than
- MsgArea you may use this statement, the usage is
- the same as for the MsgArea statement.
-
- "MsgDrArea AREA:SYSOP" or "MsgDrArea 1"
-
-
- MsgFrom: This should be the SysOp's name and is used for in
- the "From:" field of every generated message. If
- this control statement is not specified the name
- of the Sysop statement will be used. The default
- SysOp name is "SysOp".
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 38
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- MsgSize: X_List will by default not allow the size of the
- messages it write to be more than 6-7 kb... If You
- wish to change this default, just specify the size
- using this control statement (min 2 kb, max 32 kb)
-
- MsgSize 8192 % Cut messages at k kb"
- MsgSize 8 % Cut messages at 8-9 Kb"
-
-
- InBound: When running a BBS which do not use the Opus .MSG
- format you may use the 'AREA:' option to send the
- messages. This control statement must be used to
- tell X_List where to place the .PKT files.
-
- "InBound C:\Traffic\In"
-
- RSPFiles: When requesting files on a Binkley system, you may
- get a response file, X_LIST is able to move these
- .RSP files into a matrix message (to use this
- statement both the MatrixPath and the Inbound path
- must be specified).
-
- "RSPFiles"
-
-
- The below textfiles are pure ASCII and can be created with any
- ASCII editor, such as EDLIN <sigh>.
-
- WelcomeMsg: X_List can make a nice welcome-message. for your
- new users. When scanning the logfile X_List will
- check if a user is online for the first time, and
- if this is the case the user will get a welcome
- message, when using this statement..
- If you use wildcards in the filename, X_List will
- pick one of those files for this session.
-
- "WelcomeMsg C:\Opus\X_List\Welcome.Txt"
- "WelcomeMsg C:\Opus\X_List\Welcome?.Txt"
-
- If you use OPUS 1.1x, you may wish to use the
- language support, for more details see the section
- OPUS LANGUAGE SUPPORT on page 50.
-
- "WelcomeMsg C:\Opus\X_List\Welcome?.#xt"
-
- The format of the WelcomeMsg file will be
- discussed below.
-
-
-
-
- X_LIST 2.14 - PAGE 39
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- ThanxMsg: Name of the file(s) that will be sent as a message
- to all uploaders (except files not arc'ed,
- duplicate files and special Extensions - see
- below).
- If you use wildcards in the filename, X_List will
- pick one of those files for this session.
-
- "ThanxMsg C:\Opus\X_List\ThanxMsg.Txt"
- "ThanxMsg C:\Opus\X_List\Thanx*.Txt"
-
- If you use OPUS 1.1x, you may wish to use the
- language support, for more details see the section
- OPUS LANGUAGE SUPPORT on page 50.
-
- "ThanxMsg C:\Opus\X_List\Thanx*.#xt"
-
- The format of the ThanxMsg file will be discussed
- below.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 40
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- DupeMsg: Sometimes users upload files that already exists
- on the system. This statement can be used for
- sending a nasty note, telling them to use L)ocate
- before uploading any more files. The full filename
- is compared, however there is some special things
- taken into account:
- A file will be considered a DUPE if there is
- another file with the same name (the extension may
- be different), and the smallest file is less than
- 20% smaller than the largest one. This is not the
- most safe criteria, but will work most of the
- time. Here is an example where X_list will say
- that two files are dupes but they are NOT:
- OPINT102.ZIP 57014 bytes.
- OPINT102.5IP 57461 bytes.
- If you use wildcards in the filename, X_List will
- pick one of those files for this session.
-
- "DupeMsg C:\Opus\X_List\DupeMsg.Txt"
- "DupeMsg C:\Opus\X_List\DupeMsg.Tx?"
-
- If you use OPUS 1.1x, you may wish to use the
- language support, for more details see the section
- OPUS LANGUAGE SUPPORT on page 50.
-
- "DupeMsg C:\Opus\X_List\DupeMsg?.#xt"
-
- The format of the DupeMsg file will be discussed
- below.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 41
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- ExeMsg: You may want to teach your users that only arc'ed
- files are welcome on your system. This textfile
- will end up as a msg. to all uploaders who have
- sent a file with .EXE, .COM, TXT or .DOC
- extension. Unfortunately it is no longer possible
- to check for selfextracting archive programs any
- more. The reason for this is that there are just
- to many different archive systems.
- If you use wildcards in the filename, X_List will
- pick one of those files for this session.
-
- "ExeMsg C:\Opus\X_List\ExeMsg.Txt"
- "ExeMsg C:\Opus\X_List\ExeMsg.Tx?"
-
- If you use OPUS 1.1x, you may wish to use the
- language support, for more details see the section
- OPUS LANGUAGE SUPPORT on page 50.
-
- "ExeMsg C:\Opus\X_List\ExeMsg?.#xt"
-
- The format of the ExeMsg file will be discussed
- below.
-
-
- ExtMsg: If you have some special extension you like or
- dislike you may write a special message to those
- uploading such files.
- If you use wildcards in the filename, X_List will
- pick one of those files for the current session.
-
- "ExtMsg MAC C:\Opus\X_List\MacMsg.Txt"
- "ExtMsg GIF C:\Opus\X_List\GifMsg.Tx?"
-
- If you use OPUS 1.1x, you may wish to use the
- language support, for more details see the section
- OPUS LANGUAGE SUPPORT on page 50.
-
- "ExeMsg MAC C:\Opus\X_List\MacMsg.#xt"
-
- The format of the ExtMsg File will be discussed
- below.
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 42
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- Lan-Ul: If someone uploads a dupe he will get a message
- with a subject like this:
-
- "To send ABC.AR1 is a waste of time"
-
- The first part of the text is selected like this:
-
- "Lan-UL To send % Dupes part I"
-
-
- Lan-Wt: And here is the second part:
-
- "Lan-WT is a waste of time % Dupes part II"
-
-
- Lan-We: Subject line for the welcome message to the new
- users.
-
- "Lan-WE Welcome to Asgaard BBS!! % Welcome User"
-
-
- Lan-Dr: Subject line for the daily report from X_List.
-
- "Lan-DR Your daily report % Daily Report."
-
-
- Lan-Yg: Subject line for the Forward messages.
-
- "Lan-YG You got yourself a % Forward Message"
-
-
- Lan-Th: Subject for the thanx for the upload message.
-
- "Lan-TH Thanks for sending % ThankYou message"
-
-
- Lan-Pa: Subject for the message sent when the user did not
- ARC the uploaded files.
-
- "Lan-PA Try Arc'ing % Exe/Com uploads"
-
-
- KillReceived: X_LIST may delete it's own messages when received.
- This does not include messages written by X_LIST
- versions below Ver 2.04.
-
- When using messages to be sent as NetMail, these statements are
- needed to generate a proper origin line, and addresses. If your
- messages are local-only, then you can leave the below commented
- out - Then only a tear line will be put in the message.
-
- X_LIST 2.14 - PAGE 43
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
-
- MatrixPath: The path to your Matrix message area.
- This is used with the Forward command if you send
- a forward message, or if your Co-SysOp has his own
- nodenumber (Either as a point or a board).
-
- "MatrixPath 90 % Use message area 90"
- "MatrixPath c:\Msg\Local\ % Path to .MSG dir."
- "MatrixPath AREA:LOCAL % Echo Mailname for .PKT"
- "MatrixPath AREA: % This is for the Matrix Area"
- "MatrixPath C:\RaMsgs\ 90 % RA/QBBS msg base"
-
- *** Note that if you are using the AREA: options
- you must set the 'InBound' Directory, and 'AREA'
- must be in uppercase.
-
-
- ForceIntl: When writing messages for other Zones, X_List will
- insert a ^aINTL with some additional information.
- If you are a member of more than one Zone
- (normally different networks), you may force
- X_List to insert the ^aINTL information in all
- NetMail messages
-
- "ForceINTL % always Insert INTL information"
-
-
- X_List also have a built-in MailRobot! (Another program to
- scratch!). It is fairly simple, and works this way: Each file
- listed will have its modification time compared with the time
- X_List was last run - Any new (or changed) files that have
- entered the system since last run, will be file-attached by
- appending (or creating) a .HLO file in your outbound area for
- each subscribing system. X_List wants to know:
-
- Outbound: This is the path to your holding (outbound) area.
-
-
- HouseClean: Clean out in the outbound area, delete bad dialup
- files (*.$*) and any sent .PWD files.
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 44
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- Zones: When using Binkley v2.40 as mailer, you have the
- opportunity to use multi zone support, using extra
- directories like this (in zone two):
-
- C:\OutBound\ < Standard Zone two
- C:\OutBound.001\ < Zone one.
- C:\OutBound.FFF\ < Zone 4095
-
- If not used you must use the Zone Gate to send
- messages/Forward files..
-
-
- Forward: The name of the file(s) to file-attach for other
- systems. Usage like:
-
- Forward <file> <Dest>[,<Dest>[..]]
-
- <Dest> : [<Flag>]<Addr>[!<Pwd>>]
- <Flag> : C = Crash, D = Direct, N=Normal &
- and H = Hold.
- Default: Hold File, Msg Normal.
- <Addr> : [<Zone>:]<Net>/<Node>[.<Point>]
- <Zone> : Destination Zone (the Zones
- statement must be enabled)
- <Net> : Destination net.
- <Node> : Destination node.
- <Point>: Destination point. <Will force
- LotechMailer Mode>
- <Pwd> : Password for destination node.
-
- "Forward C:\NETF\INFO.* C230/101,2:231/34.13".
-
- Note the full Zone:Net/Node.Point address.
- The above will file-attach any files matching
- NODEDIFF.* in the C:\OPUS\NETF directory to
- 230/101 and 2:231/34.13. Please note, that each
- node-number should be separated by a comma (,) -
- Not a space or anything else.
- You can specify as many forward statements as you
- like, and you may specify up to 20 nodes on each
- forward statement, but the length of each forward
- line may not exceed 255 characters.
- If any point address has been specified,
- LotechMailer mode will automatically be enabled.
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 45
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- ForwardMsg: The path to the forward message to be sent
- following a file when using the LotechMailer
- command. If you decide to use wildcards in the
- filename, X_List will pick one of those files for
- this session. Here are some examples:
-
- "ForwardMsg C:\OPUS\CTL\FORWDMSG.TXT"
- "ForwardMsg C:\OPUS\CTL\FWDMSG*.TXT"
-
- The format of the ForwardMsg file will be
- discussed later on page 50 and page 53.
-
-
- LotechMailer: When forwarding files to other systems you might
- want to write a message to the SysOp that he has
- received the file. This command makes X_list
- create messages with file attaches instead of .HLO
- files in the outbound directory.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 46
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
-
- Name: When using the ForwardMsg the messages sent with
- the file will by default be sent to SysOp. You may
- use this statement to change 'SysOp' the name of
- the sysop of one or more nodes by adding one or
- more statements like this:
-
- "Name 2:230/101 Mik Tuver"
- "Name 231/34.13 Kristian Ottosen"
-
- You may also choose to disable the Message for one
- or more nodes (unless it is an '.XMG' file or the
- LotechMailer Statement has been enabled:
-
- "Name 2:230/22 /N Per Holm"
- "Name 2:231/34 /N Johnny Odgaard"
-
- IF You wish to force a LotechMail and LotechMailer
- has been disabled for a given node, you may add
- the /L to the line:
-
- "Name 2:230/901 /L Henrik Dermund"
-
- If you decide to send Secured Forwards for a
- specified node, you need a password for the node,
- this is done by using the Name statement like
- this:
-
- "Name 2:230/101 /PTEST Mik Tuver"
-
- 'Name [/S[<PWD>]] [/N] [/L] <Name>'
- /N Do not send Forward Messages.
- /L Do File Attach for this node.
- /P Send Security file.
- /P<PWD> Send security file with password.
- <Name> Name of the receiver.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 47
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- Move: Move or copy a file from one directory to another.
- 'Move E:\In\Fnews*.arc D:\File /T /F /X /S<Node>
- /P<PWD> /C<Txt>'
- /T Touch the file after moving it.
- /F Forward the file after moving (don't
- check the date).
- /X Copy the file instead of moving it.
- /N Move new files. Move file if it is dated
- after last X_List session.
- /S<Node> Check file i inbound for security,
- the sender must be <Node>
- /P<PWD> Security Password, the password must
- match the one in the .PWD file.
- /C Insert file into FILES.BBS in the
- destination area, without any comment.
- /C<TXT> Comment the file with <TXT> when adding
- it to the FILES.BBS in the destination
- area. Don't start the text with a space.
-
- ** /C must be the last option in this line **
-
- Tick: If you are a member of any Software distribution
- network, like HFDN (Ham File Distribution
- Network), SDS or PDN, you may enable this option,
- X_List will now process a Tick compatible Tick.CFG
- (look at page 55 for information on the special
- tick control file).. The current version of X_LIST
- does NOT support FLEA files.
-
- ForwardReport: Will generate a report of all files processed by
- the Move, Forward and Tick/Pwd file handlers.
- 'ForwardReport [/M] [/C] [/D] [/X] [<ReportFile>]'
- /M : Mail the report in DR Area.
- /C : Send copy to CoSysOps.
- /D : Delete ReportFile after it has been sent.
- /A : Append to existing reportfile.
-
- "ForwardReport /A D:\Reports\Fwd.Rep'
- "ForwardReport /A /D /C /M D:\Reports\Fwd.Rep'
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 48
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- Report: If you have some text files you would like to have
- as reports for yourself or some of your CoSysOps,
- you may use this statement.
-
- Report <flags> File
-
- /D : Delete file after sending.
- /S : Send copy to SysOp.
- /M : Enable Meta-String support...
- /1 : CoSysOp Flag 1
- /2 : CoSysOp Flag 2
- /3 : CoSysOp Flag 3
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 49
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- NEW MESSAGE TEXTFILE FORMAT.
-
- When designing the messages for the users, you have a powerful
- tool, the meta-strings.
-
- The following meta-strings are available in this version:
-
- %name Name of the user/receiver.
- %fname Firstname of the user/receiver.
- %lname Last name of the user/receiver.
- %dzone Destination zone.
- %dnet Destination net.
- %dnode Destination node.
- %dpoint Destination point.
- %daddress Destination Address.
- %sysop Name of the Sysop (SysOp).
- %fsysop Firstname of the Sysop.
- %lsysop Last name of the Sysop.
- %from Name of the message sender (MsgFrom).
- %ffrom Firstname of the message sender.
- %lfrom Last name of the message sender.
- %board Boardname.
- %zone The zone where the board is located.
- %net The net number.
- %node The node number.
- %point The node point number.
- %address Address of board
- %date Current date.
- %file Insert all the Filenames.
- %size Insert the total file size in kilobytes.
- %bsize Insert the total file size in bytes.
- %hsize Insert half of the total file size in kilobytes.
- %bhsize Insert half of the total file size in bytes.
- %\ Insert soft <Cr> in the end of the line.
-
- The following meta-strings have special restrictions:
-
- %subject Subject for the message (this option is not
- available when forwarding messages using the
- LotechMailer statement). (This meta-string must be
- placed at position one in one of the three first
- lines in the message textfile).
-
- %prolog Specifies a text file to be copied into a message
- before the message text. (This meta-string must be
- placed at position one in one of the three first
- lines in the message textfile).
- "%prolog C:\X_list\Prolog.Txt"
-
-
-
- X_LIST 2.14 - PAGE 50
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- %epilog Specifies a text file to be copied into a message
- after the message text. (This meta-string must be
- placed at position one in one of the three first
- lines in the message textfile).
- "%epilog C:\X_list\Epilog.Txt"
-
- %repeat repeat line until file-count reached. (this meta-
- string must be placed at position one in the
- textline).
-
- When using the %subject command you may wish to add all filenames
- in the subject line.
-
- %file Insert the filenames in the Subject line.
-
- If you deal with Upload messages you may use the %repeat option,
- this will generate a sequence of lines (with or without soft
- <CR>) one entry for each of the files which the message concerns.
-
- %repeat in messages.
-
- %file Insert current file name.
- %size Insert current file size in kilobytes.
- %bsize Insert current file size in bytes.
- %hsize Insert half of current file size in kilobytes.
- %bhsize Insert half of current file size in bytes.
- %fdate Insert the date from the current file.
- %area Insert areas number.
-
- You may also define a left or right margin for the meta strings
- like this:
-
- <meta-string>:<marginlength>L : Use Left Margin
- <meta-string>:<marginlength>R : Use Right Margin
-
- <marginlength> may not be larger than 30.
-
- "%size:12R" could result in this: " 123456"
- "%size:10L" could result in this: "123456 "
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 51
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- WELCOME, THANX, DUPE & EXE-MSG FILE OLD FORMAT.
-
- This old format is kept for downward compatibility, and will be
- removed in a later version.
-
- You can use the following meta-strings in the textfiles to be
- sent as messages:
-
- %1 Users first name.
- %2 Filename(s) (uploaded files).
- %3 Total size of the file(s) in kilobytes.
- %4 Half of the total filesize(s) - Also in KB.
- %5 Your name. This is taken from the 'MsgFrom' statement
- explained above.
-
- Sample textfile:
-
- Hi %1!
- I can see that you've uploaded %2 to the system. Sure hope
- that other users will enjoy that %3 Kb of arc'ed stuff.
- Cheers %5.
-
- May result in:
-
- Hi Viggo!
- I can see that you've uploaded OEXE_110.ARC to the system.
- Sure hope that other users will enjoy that 237 Kb of arc'ed
- stuff.
- Cheers Kristian Ottosen.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 52
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- FORWARD MESSAGE FILE OLD FORMAT.
-
- You can use the following meta-strings in the textfiles to be
- sent as messages:
-
- %1 Users first name.
- %2 Filename (forwarded file).
- %3 Total size of the file(s) in kilobytes.
- %4 Date and Time.
- %5 Your name. This is taken from the 'MsgFrom' statement
- explained above.
-
- Sample textfile:
-
- Hi %1!
-
- During my daily cleanup in the fileareas i found %2
- floating around in my inbound area. Since I am short on
- diskspace I would like you to save these %3 Kilo Bytes for
- me.
-
- Thanx - %4.
-
- May result in:
-
- Hi Mik!
-
- During my daily cleanup in the fileareas i found Z2-DIFF.A06
- floating around in my inbound area. Since I am short on
- diskspace I would like you to save these 21 Kilo Bytes for
- me.
-
- Thanx - Per Holm.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 53
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- OPUS LANGUAGE SUPPORT
-
- If you are using OPUS ver 1.1x, you have an additional option of
- language support in messages generated by X_LIST for the users
- (Welcome, Thanx, Dupe, Exe and ExtMsg).
- To enable this option three things need to be handled.
-
- - You need a program to place the information in the OPUS.LOG
- file, one such program is another utility from Bifrost
- Unltd. named 'OpIntTop'. You need Ver 1.13... The logLine
- must have the following format.
-
- + <Date> <Product> User language <language Number>
-
- - You need to generate some extra text files for the User
- messages (welcome, dupe, please arc messages). And name
- these in a special way.. The first character in the
- extension of the filename must be the language number (you
- have the numbers 1..7 available). If you miss a file for a
- secondary language (2..7), the primary language will be used
- instead.
-
- - You need to enable the language support for each message
- function, this is done by adding a '#' as the first
- character in the file extension.
-
- "WelcomeMsg C:\XLST\Welcome.#xt"
- "ThanxMsg C:\XLST\ThanxMsg.#xt"
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 54
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- PWD SECURITY FILE FOR FILE-FORWARD & DISTRIBUTION
-
- Since there is almost no security on forwarded files i.e.
- nodediff's, FNEWS and many others in FidoNet we do have a
- security problem..
-
- The Security file is a textfile with the following format:
-
- From: X_List@<Node>
- To: X_List@<Node>
- File: <FileName>
- Password: <Password>
- Size: <FileSize in bytes>
- Subject: <Filecomment>
- Origin: <Origin Node>
- CRC: <Crc32 calculated checksum>
- Area: <File Distribution Area>
- Path: <Node1> <UnixDate> <Date String>
- Path: <Node2> <UnixDate> <Date String>
- Seen-By: <Seen by Node1>
- Seen-By: <Seen by Node2>
-
- The keywords should not be case sensitive.
-
- From: The important field in the 'From:' statement is the
- origin nodenumber, the senders name may be anything,
- like the name of the product which made the .PWD file.
-
- To: The important field in the 'To:' statement is the
- destination nodenumber, the receivers name may be any
- name you choose..
-
- File: The name of the file sent, no path or wildcards are
- allowed.
-
- Password: The <Password> may contain up to 8 ASCII characters. If
- no password has been specified, this field should be
- left out of the .PWD file..
-
- Size: The size of the file to be transmitted (used to check
- if it is the correct file in the inbound directory of
- the receiving system.
-
- Subject: The Subject line contains a short description of the
- file. This description may then be added to the
- FILES.BBS for the area where the file has been placed.
-
- Origin: Will contain the address of the originating system..
- ** Only in Area support **
-
- CRC: When available this line will contain a CRC32 value for
- the file distributed...
- If the CRC checking is enabled in the TICK controlfile,
- this field is mandatory if the file are to be accepted.
- ** Only in Area support **
-
- X_LIST 2.14 - PAGE 55
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
-
- Area: Used when supporting Routing of FileAreas...
- ** Only in Area support **
-
- Path: Used to show the path a File went, to get to your
- system. Only used when the Area statement are active..
- ** Only in Area support **
-
- Seen-By: List of nodes who saw this file along the path.
- ** Only in Area support **
-
- Other lines might be added in the future..
-
- The file will be placed in the OutBound area, the extension will
- be xxxxxxxx.PWD, where xxxxxxxx will be a hex value of the number
- of seconds, that has past since Jan 1st, 1970.
-
- The security files will be placed on hold right after the file it
- describes... This is done to ensure the whole file was received..
-
- The receiving system should have the possibility to check if one
- or both the Password and the origin nodenumber are correct.
-
- A sysop may get the same file from different sources, and would
- like to have a password for the file, but all nodes should be
- allowed to send the file to his system, as long as they use the
- correct password..
-
- Another Sysop may decide to use the origin address, and no
- password for the file...
-
- As soon as the files have been received on the destination
- system, a program should check if the files are from valid
- systems, and move these to the destination areas, (this should be
- done to prevent the mailer from renaming the files in case of
- dupes), and bad files should be moved to another area or
- deleted.. X_List will check all files with extension .PW? to see
- if it is a valid password file, and the files will be deleted
- from the inbound area as soon as they have been read...
-
- Here is some examples of Password files:
-
- From: X_List@2:230/22
- To: X_List@2:230/101
- File: FNEWS706.ARC
- Password: SECRET
- Size: 4321
-
- From: X_List@2:230/22
- To: X_List@2:230/101
- File: FNEWS707.ARC
- Size: 6543
-
-
-
-
- X_LIST 2.14 - PAGE 56
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- From: X_List@2:230/22
- To: X_List@2:230/113
- File: BOARDS11.ZIP
- Password: HERMAN
- Size: 38606
- Subject: This is a test
- Origin: 2:231/34
- Area: TESTPER
- Path: 2:231/34 653526857 Sun Sep 16 23:14:17 1990 GMT
- Path: 2:230/22 665578787 3 Feb 91 10:59:47 GMT
- Seen-By: 2:231/34
- Seen-By: 2:230/22
- Seen-By: 27:345/1
- Seen-By: 2:230/113
-
-
- From: X_List@2:230/22
- To: X_List@27:345/1
- File: BOARDS11.ZIP
- Password: GERTRU
- Size: 38606
- Subject: This is a test
- Origin: 2:231/34
- Area: TESTPER
- CRC 9EF43A81
- Path: 2:231/34 653526857 Sun Sep 16 23:14:17 1990 GMT
- Path: 2:230/22 665578787 3 Feb 91 10:59:47 GMT
- Path: 57:45/0 665578787 3 Feb 91 10:59:47 GMT
- Seen-By: 2:231/34
- Seen-By: 2:230/22
- Seen-By: 57:45/0
- Seen-By: 57:45/1
- Seen-By: 2:230/113
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 57
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- TIC SECURITY FILE FOR FILE-ROUTING
-
- TICK file distribution is widely used for the File Distribution
- Networks within FidoNet, and X_List has been expanded to handle
- .TIC files as well as it's own .PWD files.
-
- A .TIC file must have the following format:
-
- Area <Distribution Area>
- File <FileName>
- Desc <FileComment>
- Origin <Origin Node>
- From <Node that sent it to you>
- CRC <Crc32 value>
- Size <Size of file, X_List only>
- Replaces <not used by X_List>
- Release <unixdate for release, Not supported>
- Restrict <RestrickFlags, X_List only>
- Created <Software that created the .TIC file>
- Path <Node1> <UnixDate> <Time String>
- Seenby <Node1>
- Seenby <Node2>
- Pw <Password>
-
- Here is a sample .TIC file..
-
- Area TESTPER
- File TESTFILE.ZIP
- Desc Just a test
- Origin 2:231/34
- From 2:231/34
- CRC 123456AC
- Created by X_List Ver. 2.14 - (C) .....
- Path 2:231/34 653526857 Sun Sep 16 23:14:17 1990 GMT
- Seenby 2:231/34
- Seenby 2:230/22
- Pw TEST
-
- The TICK file format has been developed by Barry Geller
- More information about the TICK format may be found in the TICK
- documentation..
-
- Also you must keep in mind that X_LIST may not preserve
- additional information in the .TIC files...
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 58
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- FILE DISTRIBUTION CONTROL FILE (XL_TICK.CTL)
-
- The X_List file distribution controlfile are a subset of the
- TICK.CFG control file for usage with the TICKET program.
-
- Area: Distribution File Area Description. Used to
- specify areas and nodes that are connected.
-
- AREA <Directory or AreaNum> <AreaName>
- <Node1> <Password> <Flags>
- <Node2> <Password> <Flags> <Ext>
-
- <Flags> * : Accept Files.
- & : Don't Send Files.
- ! : Toggle CRC testing.
- P : Send as Pwd.
- F : Send as Flea. (Future)
- H : Send as HOLD.
- C : Send as Crash.
- M : Send follow-up message.
- A : Announce new files from this node.
- T : Forward without .TIC or .PWD file.
-
- <Ext> /R - Add Restriction flags for this node
- Look at page 66 for more information
-
- Sample:
-
- AREA D:\tmp SPECIAL
- 2:231/34 HIPER *
- 2:230/31 HELLO *&H
- 27:27/0 HELLO *
-
- AREA 21 EEGGNET
- 97:946/0 HIPER H
-
- Local: Add area specific statements, it must be located
- immediately after the AREA statement, and before
- the list of nodes active in the area.
- The Local statement must be followed by an
- additional control statement. This statement will
- only be active for the area it belongs to.
-
- Local CRC: This statement will enable CRC32 checking.
-
- AREA d:\Ham_News HAM_NEWS
- Local CRC
-
- Local Restrict: If you wish to enable the Restrict option for an
- FileArea you may add this statement after the
- AREA control statement.
-
- Local Restrict [<flags>]
-
- For more detailed information look at page 66
-
- X_LIST 2.14 - PAGE 59
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
-
- Local Info: Up to 40 characters of area information. This
- information may be included in the announce
- messages by the %info meta-string.
-
- Local News: Generate a message with information on new files
- in this particular area. Overrides the global
- News statement.
-
- Local News <path> [<folder>]
- Local News <areanumber>
- Local News AREA:[<echoname>]
-
- If you wish to announce new files in several
- message areas you may ad extra Local News
- statements, one for each area.
-
- If you have a group of file areas to be announced
- in the same messages, you may instruct X_List to
- do so by this statement:
-
- Local News =<AreaName>
-
- The following 'Local' statements are active for the
- last 'Local News' statement entered for the area.. You
- may use these to touch the outcome of each message.
-
- Local To: Address the news message to a special username,
- instead of the default name 'All'
-
- Local To You Too
-
- Local Subject: You may wish another subject for the message.
-
- Local Subject <subject for message>
-
- Local Prolog: This statement will allow you to insert a text
- file before the announcement of the new files.
-
- Local Prolog <file>
-
- Local Epilog: This statement will allow you to insert a text
- file after the announcement of the new files.
-
- Local Epilog <file>
-
- Local Format: This statement will allow you to define your own
- format for the announcement of the new files in
- the message. see also Format statement (pp 63).
-
- Local Format <Format description>
-
-
-
-
-
- X_LIST 2.14 - PAGE 60
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- Sample area/local sequence:
-
- AREA D:\HAM_HAM HAM_HAM
- Local CRC
- Local News C:\Msg\News\
- Local Subject HAM Net Files at 230/22
- Local Prolog C:\X_List\Prolog.TXT
- Local Epilog C:\X_List\Epilog.TXT
- Local News C:\Msg\Ham\
- Local Subject HAM Net Files at 230/22
- Local Prolog C:\X_List\Prolog.TXT
- Local Epilog C:\X_List\Epilog.TXT
- Local Format %file (%size) Area: %area
- 2:230/41 HI *HA
- 2:231/87 MOJN *H
-
- AREA D:\HAM_PCKT HAM_PCKT
- Local CRC
- Local News =HAM_HAM
- 2:230/41 HIPER *HA
- 2:231/87 MOJN *H
-
-
- Hold: Directory to hold the .TIC and .PWD files
- generated when forwarding distribution files.
-
- Hold D:\Traffic\Hold\
-
-
- News: Announce new files in the message area specified.
-
- News 1 ; Use Opus Area one for messages
- News c:\Msg\Local\ ; or the Path
-
- When using a QuickBBS or RemoteAccess system you
- place the messages into a QBBS/RA compatible
- message database.
-
- News c:Ra\Msgs\ 1 ; Add to folder 1
-
- You may also chose to generate .PKT files to be
- placed in the inbound area for tossing to the
- correct area. Here is how to handle this:
-
- News AREA:LOCAL ; Or Echo Mailname .PKT
- News AREA: ; This is for the Matrix Area
-
-
- *** Note that if you are using the AREA: options
- you must set the 'InBound' Directory, and 'AREA'
- must be in uppercase.
-
-
-
-
-
- X_LIST 2.14 - PAGE 61
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- Subject: Subject to be used in messages generated by News.
-
- SUBJECT New EEGGNET Files.
-
-
- Prolog: You may add a textfile in the top of the News
- messages. this command is used to specify the name
- of the prologue file..
-
- PROLOG C:\X_List\Prolog.TXT
-
-
- Epilog: You may add a textfile in the bottom of the News
- messages. this command is used to specify the name
- of the epilogue file..
-
- EPILOG C:\X_List\Epilog.TXT
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 62
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- Format: This statement will allow you to define your own
- format for the announcement of the new files in
- the message.
-
- Local Format <Format description>
-
- The format description may include the following
- meta-strings:
-
- %name : File name.
- %size : File size.
- %area : Area name.
- %info : Area information,
- %origin : Origin node.
- %desc : File description.
- %crlf : <CR><LF> sequence.
-
- <meta-string>:<marginlength>L : Use Left Margin
- <meta-string>:<marginlength>R : Use Right Margin
-
- <marginlength> may not be larger than 30.
-
- "%size:12R" could result in this: " 123456"
- "%size:10L" could result in this: "123456 "
-
-
- CRC: This statement will enable CRC32 checking for all
- areas (you may use the user flag ! to toggle for a
- single node).
-
- "CRC"
-
- AREA d:\Ham_News HAM_NEWS
- Local CRC
- Temp: Allows you to specify where X_List will write its
- temporary files.. Usage of a ram-disk will result
- in a better performance..
- If no TEMP statement is used and the 'TMP'
- environment variable is defined, X_List will use
- the path specified here. If no TMP environment
- variable are specified, X_List will use the
- default directory..
-
- TEMP E:\RamDrive\
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 63
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- The following commands are accepted by the controlfile
- interpreter, but currently taken from X_LIST.CTL file:
-
- IN, ZONE, NET, NODE, AKA, MAIL
-
- The following command are accepted by the controlfile
- interpreter, but currently taken from an Environment variable:
-
- TZ
-
- The following commands are accepted by the controlfile
- interpreter, but currently not used by X_LIST:
-
- STOPDUP, FLEA, FIDO, Logpath, QDIR, LineFmt, ListName,
- LOGSEEN, LogCRC, Crc2Dup, NoWait.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 64
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- HATCHING FILES
-
- If you're a member of a File Distribution net, and wish to submit
- a file into a distribution area, you may use the Hatch function
- at the X_List command line.
-
- Before calling X_List you need to move the file you wish to hatch
- into the dos directory for the area where you wish to submit the
- file.
-
- You also need to update the FILES.BBS file with the description
- of the file to be submitted.
-
- When you have moved the file and updated the Files.BBS file, you
- may call X_LIST like this:
-
- X_LIST <RouteCtl> /H<FileName> /A<AreaName>
-
- <RouteCtl> : Is an X_List control file with the Tick
- statement enabled.
- <FileName> : Name of the file to be submitted.
- <AreaName> : Name of the are where the file is to be hatched.
-
- Here is an example:
-
- "X_LIST FileRout.Ctl /Hhfdnpol.arc /Aham_news"
-
- The following command line switches are available when hatching
- files into distribution networks.
-
- /H<File> : Hatch a file for File Distribution for more
- information see page 65.
-
- /A<Area> : Area where a file should be hatched.
-
- /R<flags> : Special Restriction flags for Hatched files.
-
- /T<Tick> : Use another TICK control file (see also page 48
- and page 55 for additional information).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 65
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- RESTRICTED DISTRIBUTION FILES
-
- Some Programs are only allowed for distribution in limited
- geographical areas, others may only be usable in a limited
- geographical areas (i.e. TAX programs)..
-
- X_List offer you an option to limit the distribution of files
- using the Restrict option...
-
- The basic idea is to define Group or Area tags, and add these to
- the .TIC/.PWD files..
-
- To add these restrict tags you need the /R option on X_List when
- hatching new files. Below is an example limiting a file to DK, N,
- S and SF (could be Denmark, Norway, Sweden and Finland).
-
- X_LIST FileRout /hNordic.LZH /aHAM_NEWS /rDK,N,S,SF
-
- To install the Restrict option you need to modify the XL_TICK.CTL
- file..
-
- You need to add the line 'Local Restrict' to all areas where you
- wish to enable this option.
-
- Local Restrict [<Flags>]
-
- 'Local Restrict' must be enabled in EACH area..
- 'Local Restrict <Flags>' is only usable after a 'Local News line'
-
- Area C:\HAM_NEWS HAM_NEWS
- Local News C:\Local
- Local Restrict All <-- Announce all files in area Local.
- Local News C:\DKNews
- Local Restrict DK <-- Announce DK files in area DKNews.
- Local News C:\ScanNews
- Local Restrict DK,S,N,SF,SC <-- Ann. DK,S,N,SF and SC files.
- Local News C:\WrldNews <-- Announce non restricted
- files.
- 2:230/41 TEST1 *HA /RDK,SC
- 2:231/87 TEST2 *HA /RAll
- 2:230/137 TEST3 HA /RDK,S,N
- 2:253/173 TEST4 HA <-- Non restricted files.
-
- Area C:\HAM_PCKT HAM_PCKT
- Local Restrict <-- Enable restriction for this area.
- Local News =HAM_NEWS
- 2:230/41 TEST1 *HA /RDK,SCAN
- 2:231/87 TEST2 *HA /RAll
- 2:230/137 TEST3 HA /RDK,S,N
- 2:253/173 TEST4 HA <-- Non restricted files.
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 66
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- Announcements:
- Non restricted files will be announced in all news areas.
- Restricted Files will be announced in NewsArea if one or
- more flags are equal.
- All files are announced in News area if 'Local Restrict All'
- are used..
-
- Distribution:
- Non restricted Files are sent to all nodes.
- Restricted files are sent if one or more flags are equal.
- Restricted files are sent to all users with 'All' flag set..
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 67
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- INCLUDED X_LIST UTILITIES
-
-
- MAKEXDIR
-
- A small utility program is supplied with X_List. It is primarily
- intended for use by people with a lot of files, but limited
- diskspace.
-
- It will make X_List list the size and date of the missing files
- in the public list. Whenever a missing file is found in a
- FILES.BBS file, X_List looks in a file named X_LIST.DIR and takes
- the size and date of the missing file from this control-file and
- puts in the public list. If the file missing is found in
- X_LIST.DIR it will be flagged with an exclamation point (!)
- between the filename and filesize.
-
- FILE1.ARC ! 54728 24-12-88 This file was in X_LIST.DIR
- FILE2.ARC missing This file was not in X_LIST.DIR
- FILE3.ARC 32767 28-02-88 This file is online.
-
- For more information read the MakeXDir.DOC file in the X_List
- distribution archive...
-
- Of cause it is pure non-sense to run MakeXDir for an area that
- the users can't reach when they are online!
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 68
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- X_VANVAB
-
-
- X_VanVab<Tm> uses the well known VanVab<Tm> technology to add a
- little Avatar-color to the file listings generated by X_list
- (both the Public and News-List).
-
- ** NOTE SYSTEM MUST BE ABLE TO HANDLE THE AVATAR EMULATION **
-
- Usage : X_VanVab <Inputfilename> <Outputfilename> [<Flags>]
-
- <Inputfilename> : Filelist generated by X_LIST
- <Outputfilename> : Colored output file.
- <Flags> : /A - use ansi output, not avatar.
- /1 - use extended color palette.
-
-
- Keep em' online!!
-
-
-
- ADJUST
-
-
- Small program to add or subtract to the users upload and download
- counters..
-
- For more information see page 37. Or have peek into the
- ADJUST.DOC file in the X_List distribution archive...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 69
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- OTHER X_LIST UTILITIES
-
- X_NEW
-
- X_NEW (C) Bifrost Unlimited and Per Holm.
-
- X_New is a small on-line X_LIST utility for the following BBS
- systems OPUS 1.03, OPUS 1.1x and Maximus 1.02.
-
- The purpose of X_NEW is to show the users a list of files arrived
- since the last connection (The user may optionally set another
- date to be used)..
-
- The information about the new files, are found in a filelist
- generated by X_List...
-
- X_NEW is distributed in an archive named X_NEW###.LZH where ###
- are the three digits in the version number.
-
- X_NEW101.LZH will contain X_NEW version 1.01..
-
-
- OPINTTOP
-
- OpintTop (C) Bifrost Unlimited and Per Holm.
-
- OpintTop is a small on-line TOP-10 utility for OPUS CBCS (version
- numbers below 1.10 is for OPUS 1.03, higher version numbers are
- for OPUS 1.20).
-
- OpintTop version 1.13 has a special feature for Opus 1.1x
- language support, it may place a special line in the OPUS log
- file with information about the language the user has chosen to
- use..
-
- OpintTop is distributed in an archive named OITOP###.LZH where
- ### are the three digits in the version number.
-
- OITOP113.LZH will contain OpintTop ver. 1.13
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 70
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- HISTORY
-
-
- Ver. 2.00
-
- o Feel free to compare the documentation with the
- documents from the older versions.
-
-
- Ver. 2.03
-
- o Introduced the Licence statement to get some extra
- facilities.
-
- o Read system information from the Opus.Prm file.
-
- o Matrix Mail supported for Forwarding and Daily reports.
-
- o You may send a copy of the daily report to your
- Co-SysOp.In the regular area or by MATRIX (might be
- your point-net).
-
- o You may want to send a matrix message along with the
- files forwarded.
-
- o You may customize the texts used in letters.
-
- o X_LIST will now delete it's own messages when received.
- This does not include messages written by earlier
- X_LIST versions.
-
- o Adding comments for new files adopted in the Files.Bbs.
-
- o You may replace special characters in the public list
- and FILES.BBS, useful for special characters like the
- Danish.
-
- o X_LIST will tidy your FILES.BBS in different ways etc.
- by splitting descriptions that are too long to be
- displayed by Opus<Tm> into separate lines with spaces
- inserted to get the indent right.
-
- o Customizing of the public list.
-
- o Option to delete old copies of files.
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 71
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- Ver. 2.04
-
- o Dropped the Licence statement stuff again.
-
- o Files with extension .XMG will be forwarded as a Matrix
- Message, containing the contents of the file (which
- must be in text format).
-
- o Touch facility (Set Date and Time on files).
-
- o Mark newest files (Less than X days) with a star in the
- file list.
-
- o Make an extra filelist with only the new files.
-
- o Delete empty (0 Byte) files from the file areas.
-
- o Generate a weekly Master-Index file (For future use).
-
-
- Ver. 2.05 - Never released
-
-
- Ver. 2.06
-
- o 'Level' now accepts values 0-32767 for QuickBBS
- support.
-
- o Added 'AreaFile' to read a QuickBBS area description
- file.
-
- o Improved the 'Forward' facility.
-
- o X_List is not case-sensitive with filenames from the
- Files.BBS files anymore.
-
- o Fixed problem with change of year.
-
- o Fixed problem in NewsList. The old version had some
- problems deciding what was comments.
-
- o Fixed some other minor problems.
-
-
- Ver. 2.07-Gamma - Test release of ver 2.10 expired Oct 15, 1989
-
-
- Ver. 2.08 to 2.09 - Skipped these versions.
-
-
- Ver. 2.10
-
- o The bug in the Dupe message function has been fixed.
-
- o New Dupe criteria (more relaxed).
-
- X_LIST 2.14 - PAGE 72
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
-
- o Option to write messages depending on the file
- extension to the uploaders.
-
- o May now write a logfile of the X_List Session.
-
- o Option to do some House Cleaning in the Outbound area.
-
- o New CoSysOp statement.. The old ones has been removed..
-
- o Almost no upper limit on number of 'Forward, Touch,
- KeepLatest, Crap, FreeFile, Name, CoSysOp lines.
-
- o Option to skip missing files from the Public List only.
-
- o Make new version's of program available under magic
- filenames (Ex. the nodelists, and diffs.).
-
- o Touch is now able to handle wildcards.
-
- o Crap is not case sensitive any more.
-
- o Crap files will be deleted before the Public list is
- generated for the current area.
-
- o Able to generate .PKT files to be tossed into a message
- database (for use with QuickBBS).
-
- o Able to analyze QuickBBS log file
-
- o Full Zone:Net/Node.Point support in matrix messages.
-
- o Full Zone:Net/Node support in .HLO and Echo-mail (.PKT)
-
- o Full Zone:Net/Node.Point support for CoSysOp Address.
-
- o Full Zone:Net/Node.Point support on Forward statement.
-
- o Added Support for FrontDoor OkFile "Mailer FD".
-
- o MagicFix function for magic filenames (Binkley).
-
- o Adjust fixed for QuickBBS files.BBS "BBS QuickBBS"
-
- o You may now define your own CommaFile format.
-
- o More user (SysOp) friendly message files.
-
- o New ADJUST program able to handle either an OPUS or an
- QuickBBS userfile. Made by Stig Jacobsen (2:231/16).
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 73
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- Ver. 2.11
-
- o New address for the Postcards to Kristian Ottosen.
-
- o Added support for random selected messages to the users
- (Welcome, Thanx, Dupe, Exe, Ext and Forward messages).
-
- o Added option to disable the Forward message to some
- nodes (Using a /N in the NAME statement).
-
- o Added Opus 1.10 Support.
-
- o Added RemoteAccess support.
-
- o Added support for moving files from one directory to
- another.
-
- o Added support for Secured file forwards.
-
- o The 500 file limit in each area has been removed.
-
- o Now finally available in an overlay version.
-
- o Fixed the QuickBBS mode Bug from ver 2.10..
-
-
- Ver. 2.11a - Maint update!
-
- o Fixed bug with message bundles (.PKT files)
-
- o Fixed errors in the .CTL sample files.
-
- o Added some missing files to the distribution archive.
-
-
- Ver. 2.12
-
- o Added some support for Max 1.02.
-
- o The name statement got a new flag '/L' (LotechMailer)
-
- o Fixed area number in lists (now three digits).
-
- o Fixed /F problem for the Move statement.
-
- o Fixed bug with deleted files (wrong name was passed to
- the log file).
-
- o Fixed the bug in calculation of percentage of free
- space on large harddisks. (uses code by Gerard de Haan
- 2:286/251)
-
- o Trailing backslash on the path in the FLSearch file are
- no longer necessary.
-
-
- X_LIST 2.14 - PAGE 74
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- o Added support for Opus style log from RA.
-
- o Far better log analysis, optionally mail session report
- when using the OPUS or Binkley mailer. The report may
- be placed in the DailyReport, or in separate file/msg.
-
- o You may now add an alternative filename for the system
- information file when using Maximus or RemoteAccess
-
- o Added option to mail dupe & orphan reports in the Daily
- Report area, and/or send a copy to the CoSysOp(s).
-
- o Improved the CoSys statement with optional reports to
- be sent in the morning (or whenever you're X_Listing).
-
- o The NewsList will now show if F.REQ are possible for
- the areas, just like the public list does...
-
- o Added support to write direct into a RA/QuickBBS
- message base...
-
-
- Ver. 2.13
-
- o RSPFiles support now in documentation, was already
- implemented in version 2.12..
-
- o New extension on temporary files '.$$$'
-
- o Will now translate ALL lines when using the Convert
- statement, not only the lines with filenames.
-
- o Fixed several small problems in the BT Log analysis.
-
- o Fixed bug with the Adjust file...
-
- o You may now specify up to 11 Address lines (10 Aka's).
-
- o Added Hold/Normal/Crash flag for forwarding of files.
-
- o Removed limit of 10 Include areas..
-
- o Fixed problem in Dupe and Orphan reports, could hang
- the system.
-
- o Fixed problem with last Max Area.
-
- o Fixed Problem moving file in MSDOS 4.0x.
-
- o Enabled wildcards in Crap statement.
-
- o Improved usage of Show, Skip, Adopt, Reflow, Rewrite
- and RemMiss statements, Single area support..
-
- o Added FileMode statement for LAN support.
-
- X_LIST 2.14 - PAGE 75
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
-
- o Added TICK compatible file routing.
-
- o Expanded the .PWD files to handle areas.
-
- o Option to forward files received from .TIC to .PWD
- files and the other way around...
-
-
- Ver. 2.14
-
- o Added SuperBBS support.
-
- o When generating messages, X_List will be able to divide
- huge text files into several messages.
-
- o Added two new meta strings %prolog and %epilog.
-
- o More powerful meta-string options.
-
- o Added Forward Report.
-
- o Added more feature to the Move, DailyReport,
- SessionReport and CosSysOp control statements
-
- o Improved tick support, several new options.
-
- o Fixed FreeFile problem.
-
- o Fixed RA Log analyze problem (new users).
-
- o Fixed problem with .PWD files, could not find the
- Subject for File distribution.
-
- o Added support for CDRom in Maximus mode.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 76
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- NEW IDEAS FOR FEATURES THAT MIGHT SHOW UP LATER
-
-
- o Handling of wildcards in FILES.BBS
-
- o Option to create a list of files not arc'ed.
-
- o Enhanced shirt ironing capabilities.
-
- o Support for user flags in areas.
-
- o Support for handling .FLE files to an area.
-
- o Far better log reporting and message info.
-
- o More QuickBBS, Remote Access and SuperBBS support.
-
- o More Opus and Maximus CBCS support.
-
- o Improved type checking on control file commands..
-
- o Handle <TAB> in .CTL files.
-
- o Generate list of Uploads.
-
- o New and more powerful X_VanVab program.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- X_LIST 2.14 - PAGE 77
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- INDEX
-
-
- .PWD Format 55 Lan-We 43
- .TIC Format 58 Lan-Wt 43
- ADJUST 37, 69 Lan-Yg 43
- CONTENTS 2 Last 26
- Control File Level 24
- Address 20 License 15
- Adopt 28 LogFile 34
- AdoptComment 31 LogLevel 17
- AreaFile 16 LotechMailer 46
- BBS 18 Magic 33
- BoardName 19 Mailer 19
- CommaFile 22 MarkLast 26
- CommaFormat 23 MatrixPath 44
- Convert 31 MaxAreas 26
- CoSysOp 36 MaxDrive 20
- Crap 29 MaxFiles 23
- DailyReport 34 Move 48
- Debug 20 MsgArea 38
- Download 34 MsgDrArea 38
- Drives 20 MsgFrom 38
- DupeMsg 41 MsgSize 38
- DupeReport 30 Name 47
- EuroDate 26 NewsList 22
- ExeMsg 42 OkFile 32
- ExtMsg 42 OkHeader 32
- FileMode 18 OrphanReport 30
- First 26 Outbound 44
- Footer 24 OutFile 22
- ForceIntl 44 Password 32
- Forward 45 PrmFile 15
- ForwardMsg 46 QNewAll 37
- ForwardReport 48 ReFlow 29
- FreeFile 37 RemMiss 29
- Header 24 Report 48
- Hindustan 21 Rewrite 28
- HouseClean 44 RSPFiles 39
- InBound 39 Secure 29
- Include 36 SessionReport 35
- Index 23 Show 25
- KeepLatest 31 Skip 25
- KillReceived 43 SysOp 15
- Lan-Dr 43 SystemPath 15
- Lan-Fa 26 ThanxMsg 39
- Lan-Fl 27 Tick 48
- Lan-Fp 27 Touch 31
- Lan-Fr 27 Upload 34
- Lan-Mi 27 UserAdjust 37
- Lan-NF 27 WelcomeMsg 39
- Lan-Pa 43 XListData 16
- Lan-Th 43 XLogFile 16
- Lan-Ud 26 ZapZero 30
- Lan-Ul 43 Zones 45
-
- X_LIST 2.14 - PAGE i
-
-
-
-
-
-
-
- X_LIST V 2.14 (C) DUGFRISK UnLtd. & BIFROST UnLtd. - 1988-1991.
-
- Control Tick X_NEW 70
- Area 59 X_VANVAB 69
- Epilog 62 X_NEW 70
- Format 63 X_VANVAB 22, 69
- Hold 61
- Local 59
- Local CRC 59, 63
- Local Epilog 60
- Local Format 60
- Local News 60
- Local Prolog 60
- Local Subject 60
- Local To 60
- News 61
- Prolog 62
- Subject 62
- Temp 63
- CONTROLFILE
- Area Maint. 28
- Forward 38
- General 15
- INFO 14
- Log Analysis 34
- Matrix 38
- Message 38
- Okfile 32
- Public List 22
- Distribution archive 8
- FILE-DISTRIBUTION 59
- HATCHING FILES 65
- HISTORY 71
- INTL 44
- INTRODUCTION 10
- Language support 26, 27,
- 39, 40-43, 54, 70
- LICENSE 6
- MAKEXDIR 68
- MaxAreas 26
- Maximus
- Area handling 26
- MESSAGE
- Dupe 52
- Exe 52
- File Format 50
- Forward 53
- Thanx 52
- Welcome 52
- Meta-string 50, 52, 53
- NetMail 43
- OPINTTOP 70
- REQUIREMENTS 12
- Utilities
- ADJUST 69
- MAKEXDIR 68
- OPINTTOP 70
-
- X_LIST 2.14 - PAGE ii
-
-
-
-
-
-