home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
CEL202R.ZIP
/
CEL202-4.ZIP
/
CTOSV111.ZIP
/
CELTOSCN.DOC
next >
Wrap
Text File
|
1994-08-16
|
72KB
|
1,658 lines
Celerity BBS v2.x FidoNet Tosser Scanner v1.11 [08/16/1994]
(C)opyright 1993-94 Ted R. Spaulding & Asylum Associates [All Rights Reserved]
BBS For Support/Orders - Wacky's Asylum (716) 872-5887
┌────────────────────┐
│PROGRAM DESCRIPTION:│
└────────────────────┘
This Tosser/Scanner Should provide the manipulation of data required
to accomplish the task of reading/writing Fido .MSG style messages to/from
Celerity v2.x .BSE/.DAT/.IDX file formats. This FreeWare release
includes full support for Fido "Echo Mail" to include conferencing to
and from Celerity Message Bases. Also included in this release is full
support for TRUE FidoNet style NetMail, via Celerity's Electronic Mail
area. This provides a means of sending and recieving "Private" Mail to
and from other nodes on the network.
With This release, A Mailer [Such as FrontDoor, BinkleyTerm, D'Bridge,
or InterMail], and a Tosser/Packer [Such as TosScan (Commercial),
FastEcho, Squish, or GEcho IS REQUIRED (Unless you are running
D'Bridge). Inbound traffic will be recieved by the mailer,
depacketized by the Tosser/Packer, and converted to Celerity by
CelToScn. Outbound traffic will be written out to .MSG's by CelToScn,
Bundled by the Tosser/Packer, and transmited to your Hub/Fido
Connection via your mailer. Future releases of TCMail will include the
packetizing functionality, releasing the need for a "Middle"
Tosser/Packer AND add USENet newsgroup capabilities (ie.. The
InterNet).
Table Of Contents
» Program Description................................ Header
» Table Of Contents.................................. Page 1
» Disclaimer......................................... Page 2
» Program Registration And Author Contact............ Page 3
» Archive Packing List............................... Page 3
» Installation
Preperation...................................... Page 4
Install/Setup.................................... Page 5
SAMPLE CTSetup Screen for a FidoNet Test Area.... Page 6
Message Base Configuration....................... Page 6
SAMPLE CTSetup Screen for Net Configuration...... Page 7
Multiple Network Configuration................... Page 7
» Normal Execution/Command Line Parameters........... Page 8
» Bug Reports / Suggestions.......................... Page 9
» FidoNet Technical Specifications Conformity........ Page 9
» The FidoNet STARTUP Kit
Disclaimer / Required Files........................ Page 10
» Front Door---
Unpacking the FD Archive......................... Page 11
Modifying CONFIG.SYS / AUTOEXEC.BAT.............. Page 11
Miscellaneous Files.............................. Page 11
» FrontDoor SetUp (FDSETUP.EXE)
Running For The First Time..................... Page 12
Global Options................................. Page 12
Mailer Options................................. Page 14
Editor Options................................. Page 15
Terminal Options............................... Page 15
Modem Options.................................. Page 15
Printer Options................................ Page 16
The Event Manager.............................. Page 16
Overview of Events............................. Page 18
» InterMail---
Installing From The Distribution Diskette........ Page 19
Modifying CONFIG.SYS/AUTOEXEC.BAT................ Page 19
Miscellaneous Files.............................. Page 19
» InterMail SetUp (IMSETUP.EXE)
SetUp Options.................................. Page 20
The Event Manager.............................. Page 21
Sucutity Options............................... Page 22
» BBS SetUp........................................ Page 23
» CelToScn SetUp................................... Page 23
» TosScan(M) (c) SetUp
UnPacking The TosScan Archive.................... Page 24
» Running TSetup
General Setup Options.......................... Page 24
The TosScan Area Manager....................... Page 25
» FastEcho SetUp
UnPacking The FastEcho Archive................... Page 27
» Running FESetup
General Setup Options.......................... Page 27
The FastEcho Systems Manager................... Page 30
The FastEcho Area Manager...................... Page 31
» Testing Your Setup............................... Page 33
» A Final Note....................................... Page 34
Page 2
┌───────────┐
│Disclaimer:│
└───────────┘
Ted R. Spaulding & Asylum Associates disclaims all warranties relating to
this software, whether express or implied, including but not limited to any
implied warranties of merchantability and fitness for a particular purpose.
Neither Ted R. Spaulding or Asylum Associates shall be liable for any
indirect, consequential, or incidental damages arising out of the use or
inability to use such software, even if Ted R. Spaulding & Asylum Associates
has been advised of the possibility of such damages or claims. In no event
shall Ted R. Spaulding & Asylum Associates liability for any damages ever
exceed the price paid for the registration fee for this software, regardless
of the form of the claim. The person or persons using this software bear
all risks as to the quality and performance of this program.
It is your responsibility to determine if this program will work reliably
on your computer system and your software environment. This program is
available in a freeware form for the purpose of evaluation. By registering,
you acknowledge that it works to your satisfaction.
Page 3
┌────────────────────────────────────────┐
│PROGRAM REGISTRATION AND AUTHOR CONTACT:│
└────────────────────────────────────────┘
Registering this program is not possible as it is FreeWare. A
Much more feature rich version is available under the name "TCMail",
and is marketed as Limited ShareWare. Please acquire that program if
you are interested in more than "Basic" functionality for a Celerity
<-> Fido Interface.
This program is released as freeware. You are authorized to
fully use this program in Release form for a unspecified period of time.
This program will be fully functional for an unspecified amount of time.
I DO REALIZE THAT *MOST* BBS OPERATORS ARE HOBBYISTS. You may use
THIS, basic program as long as you wish, without the need to EVER
upgrade to TCMail. TCMail's registration price is herein set at a
minimum of $25.00 US. That price will include upgrades and program
support for a minimum of 1 full year.
╓─────────────────────────────────────────────────────────╖
║ SEE The distribution file REGISTER.DOC included with ║
║ the TCMail Program for the Registration form and mailing║
║ address. ║
╙─────────────────────────────────────────────────────────╜
┌───────────────┐
│Included Files:│
└───────────────┘
CelToScn Files:
CELTOSCN.EXE - The Main Utility
CTSETUP.EXE - The CelToScn Configuration/Setup Utility.
CELTOSCN.DOC - The Main Doc File/Fido Setup Kit Docs. [You are Here :)]
REVISION.DOC - Revision Notes from Version to Version.
UPGRADE.DOC - Upgrade Notice of EXTREME importance.
FidoNet Startup KIT Files:
ROUTE.FD - The Sample FrontDoor Routing Control File.
FDNODE.FD - Sample FrontDoor Node Compilation Control File.
FRODO.BAT - Sample FrontDoor/Celerity Batch File.
ROUTE.IM - The Sample InterMail Routing Control File.
FDNODE.IM - Sample InterMail Node Compilation Control File.
IMRUN.BAT -\
EXEBBS.BAT -/Sample InterMail/Celerity Batch Files.
Miscellaneous Files:
FILE_ID.DIZ - File Description
FILE_ID.CLR - File Description in Color Format
CELTOSCN.EXE, CTSETUP.EXE are the only files in this archive
that are required to run this utility. All Data files are created on
install.
Page 4
┌─────────────────────────┐
│PREPERATION/INSTALLATION:│
└─────────────────────────┘
I have attempted to make this program as versitile as possible.
CELTOSCN.EXE and CTSETUP.EXE should be runnable from any drive/path.
*PREPERATION*
Setting up a network requires you to do things in a "Orderly"
Fashion. Before setting up this utility, you should have allready
installed your Mailer (FrontDoor/InterMail/D'Bridge etc..) and if
you need to (FrontDoor/InterMail), installed a Tosser/Packer. Help for
installing theses utilities can be found at the end of these DOC's.
You should also have allready set up atleast a Test Network area in your
Celerity BBS (Or by using Sicko's CMT utilities) that is setup as a "Fido"
type message base. If you have not done all of the above, please do so now.
Page 5
*INSTALL/SETUP*
You will need to know the path to your Celerity "Network" directory
(As defined in CelSetup) before installing this utility.
Copy the files that were contained in this archive to your
Celerity Network directory. Minimum Needed - CELTOSCN.EXE and
CTSETUP.EXE.
If you have registered this program, place your 00???T10.KEY file
that you recieved in your Celerity Network Directory as well.
You can press ALT-H at anytime within CTSetup for a help screen.
Run CTSETUP.EXE for the first time with 1 parameter, the path to
Celerity's Network Directory as specified in CELSETUP.EXE.
Ex: CTSETUP C:\Celerity\Network\
The Program will ask you a couple basic questions about the network you
are on, and the Celerity BBS that you run. These questions are fairly
straight forward. The first is the path to the Celerity SETUP.DAT file
that governs this network. If you are running multiple nodes with
multiple networks, using more than 1 USERS file, this question becomes
VERY important. Simply respond with the full path (ie.. C:\CELERITY\NODE1).
For The Address Questions, Here is an example Fido Style Adderess:
1:2613/171.0
The 1 that preceeds the : is the "Zone Number" and identifies
The net that you are running.
The 2613 is the region or "Network Number". It identifies your
physical location within the Zone.
The 171 is the "Node Number", every Fido system has a unique Node
number with the exception of Point nodes.
The 0 is the "Point Number". If you are not familiar with
"Points", then are NOT one. enter a 0 for point ## if you are
unsure.
Next, it will ask you for the Zone portion of your network address.
Respond with the number in your net address that preceeds the :. ie..
in a standard FidoNet Network, an example address would be 1:2613/171.0
The Zone for this address is 1. Then proceed to answer the next question
with the Network portion of your address. ie.. 2613 in our example
above. Then move on to the node number (171 in the above example), and
finally the Point number which SHOULD be Zero for most of you. If your
board is a "Point" address, you would know it. Then, it will ask you
for A Short description of the network. this is informational only,
enter whatever you wish (ie.. FidoNet, Intellec, CCiNet, etc...).
Page 6
*SAMPLE CTSetup Screen for a FidoNet Test Area*
File Celerity v2.x Tosser/Scanner v1.09
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░╒═════════════FidoNet Test Area══════════════╕░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░│ │░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░│ Toss Dir: C:\CELERITY\FIDONET\FIDOTEST\ │░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░│ Kill Sent .MSG: [Y] Crash Priority: [N] │░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░│ Kill Recd .MSG: [Y] Hold For Pickup: [Y] │░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░│ Private Allways: [N] Network: FidoNet │░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░│ │░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░╘═════════════════FIDO-TEST══════════════════╛░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░[Editing Current Bases]░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Alt-X Exit Alt-H Help │ [ALT-F]-Menu
Next, the program will scan all of your current message bases looking
for "Fido" subs. When it does find one, it will prompt you for the "Toss"
directory. The Directory you enter here should be the same directory for
this message base as set up in FastEcho/TosScan/Squish/GEcho/D'Bridge,
or whatever Tosser you choose. IF YOU DO NOT MATCH THIS DIRECTORY WITH
THE ONE SETUP IN YOUR TOSSER/PACKER, THE TOSSER/PACKER WILL NEVER SEND
OR RECIEVE NETWORK TRAFFIC. The Setup program will then ask you for
the properties of this "Echo Mail" area (Such as Hold, Crash, Delete
when Sent, Delete when Tossed, ...etc...). I default all
settings to recommended settings. If you are unsure, The default will
probably work just fine. Simply specify Yes or No to each option based
on personal preference. At the end of every record, hit F10 to save
the record. When Finished, a two data files will be written to your
Celerity Network directory. IF YOU DELETE IT, you WILL have to run
setup again. CTSETUP may be run multiple times, such as when you add
new bases.
Page 7
You may configure your "Multiple" networks from within CTSETUP. Hit
ALT-F from anywhere, and select "Network Config".
*SAMPLE CTSetup Screen for Network Configuration*
File Celerity v2.x Tosser/Scanner v1.09
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░╒════════════════════Network #1════════════════════╕░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ │░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ Network Address: 1:2613/171.0 │░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ Network Name: FidoNet │░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ Cel v2 Setup Path: C:\CELERITY\NODE1\ │░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ FD / IM Main Path: C:\IM\ │░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ NodeList Path: C:\IM\NodeList\ │░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ NodeList Name: NODELIST.??? │░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ Process Private NetMail? [Y] │░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ NetMail Toss Path: C:\IM\Mail\ │░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ Ext. NodeList? [Y] Real Names? [Y] │░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ Kill Sent .MSG: [Y] Crash Priority: [N] │░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ Kill Recd .MSG: [Y] Hold For Pickup: [Y] │░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ Origin Line: Asylum Assoc. Sys 1 - Rochester, NY │░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ │░░░░░░░░░░░░░░░
░░░░░░░░░░░░░╘══════════════════════════════════════════════════╛░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░[Editing Current NetWorks]░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Alt-X Exit Alt-H Help │ [ALT-F]-Menu [INS]-Insert Net [DEL]-Delete Net
If you plan to process private NetMail, It is important that you
set up one record here for each Net that you carry. This is NEEDED for
Zone/Domain matching, so that CelToScn Knows which NetMail belongs to
which Network. There is extensive HELP available from within this
configuration screen, USE IT. If you need help with a field, just hit
ALT-H. Remember to hit [F10] to save the entries as you move along. I
will be expanding this interface in the future, but this will do quite
well for now.
YOU WILL NEED TO RUN CTSETUP EVERYTIME YOU ADD FIDO BASES INSIDE
OF CELERITY! If you do not, those new bases will NOT be scanned for
messages.
Page 8
┌─────────────────┐
│NORMAL EXECUTION:│
└─────────────────┘
During normal operations, you will need this program to perform 2
basic functions, Toss Fido Messages into Celerity, and Scan Celerity for
new messages to send out. The Command line for these 2 funtions remains
simple. Specify the switch, and the directory to the Celerity Network
directory [As specified in CELSETUP].
SYNTAX: CELTOSCN /Function [/PPath] [/N###] [/M]
Where- /Function = /SCAN - Scan Celerity Message bases for new OUTBOUND
Messages to send.
/TOSS - Toss INBOUND traffic into the Celerity message
Bases.
/BUILD - Build Celerity Compatible Nodelist from your
Networks "Distribution Nodelist".
/PPath - - The FULL path to the CELTOSCN configuration
files. If you ommit this parameter, The
program WILL search the current directory.
/N### - - Used to scan a particular Relative Network
Number.
/M - - Including this parameter will force the program
To NOT scan for Inbound/Outbound NetMail.
Ex: CELTOSCN /TOSS /PC:\Celerity\Network\
This will scan all networks for any INBOUND traffic (EchoMail and
NetMail). C:\Celerity\Network\ will be searched for the data files.
Ex: CELTOSCN /SCAN /PC:\Celerity\Network\
This will scan all networks for any OUTBOUND traffic (EchoMail and
NetMail). C:\Celerity\Network\ will be searched for the data files.
If you wish to process Private NetMail, You will need to run
"CELTOSCN /BUILD", atleast once, to create the initial nodelists for
verifying network addresses. You *SHOULD* run CELTOSCN with the /BUILD
paramater everytime you recieve a nodelist update for that network.
This parameter may be combined with the /N parameter. Example - I
have my .BAT file set up to automatically run XLAX (A FidoNet Nodelist
compiler), every Friday, when I recieve my FidoNet Nodelist Update. At
the same time, I would run "CELTOSCN /BUILD /N1", assuming that
FidoNet is My Network #1.
Page 9
┌─────────────────────────────────────────┐
│Support & Bug/Problem/Suggestion Reports:│
└─────────────────────────────────────────┘
I am an active member of the Celerity v2.0x Beta Testing Program, I
can be found on The Support BBS (Orange Archives) at least once, usually
twice a day. You may leave messages, E-Mail, and BUG/Problem reports for
me there, I WILL get them. If You wish, you may call my BBS at
(716)872-5887. All new users are validated within 6 hours.
NetMail may also be sent to me at my BBS through FidoNet. Address to
Ted Spaulding @1:2613/171. The current revision of CelToScn can be
FREQ'ed from my fido node (1:2613/171) under the "Magic" file name
"CELTOSCN".
┌─────────────────────────────┐
│FidoNet Technical Conformity:│
└─────────────────────────────┘
All FTS and FSC documents should be obtainable from your local Hub
and/or NEC.
This FidoNet Utility Conforms to the following FTS (FidoNet Technical
Standard) and FSC (FidoNet Standards Committee) Policies:
FTS-1 [v15 30-Aug-90] - A Basic FidoNet(r) Technical Standard
FTS-4 [v3.31 12-Dec-87] - The Conference Mail System
FTS-5 [v1 05-Feb-89] - The Distribution Nodelist
FSC-53 [v2 08-Dec-92] - Specifications for the ^aFLAGS Field
This FidoNet Utility Has PARTIAL Support [Will be expanded] for the
following FTS (FidoNet Technical Standard) and FSC (FidoNet Standards
Committee) Policies:
FTS-9 [v1 13-Mar-90] - MSGID / REPLY - Reply Linkage / Dup Detect
FSC-58 [v2 01-Nov-92] - A New Way of Addressing in FidoNet(r)
FSC-68 [v1 13-Dec-92] - A Proposed Replacement for FTS-4
These Specification Conformities will expand in the future to include
type 3, charset proposal, and numerous others.
Page 10
Purpose:
This doc set will guide you through setup of FidoNet using either
FrontDoor v2.02+ or InterMail 2.20+ as a mailer and TosScan(M) v1.0 or
FastEcho v1.40+ as a Tosser/Packer.
Disclaimer:
These SUGGESTIONS/Procedures were compiled from multiple
sources as well as from person experience [In InterMail]. There are NO
Guarentees implied, these settings have worked for myself and others.
These Directions ARE NOT a substitue for Reading the FidoNet POLICY4
Document, your mailer's Documentation and Your Tosser/Packer's
Documentation.
WHAT YOU NEED:
» Front Door version 2.02,2.10+
or InterMail v2.20+ (Commercial) [2.27 is current as of 05/01/94]
» TosscanM v1.00
or FastEcho v1.40
or Fido->.MSG Compatible Tosser/Packer
» CelToScn v1.00+ [Included with Celerity v2.0x]
» Your System's Fido/Fido Compat Node Number
» Your Hub's Fido/Fido Compat Node Number
» Current Fido/Fido Compat Echolist
» Current Fido/Fido Compat Nodelist
» Celerity v2.0x+
» Patience & Time!
SOME IMPLEMENTATIONS:
-If You run a Mailer that requires a Fossil (FD Does, IM Does NOT)
X00.SYS Fossil Driver with XU.exe
or BNU Fossil driver
Page 11
FrontDoor Setup:
STEP ONE - Create Your System Directories
1) Enter the following commands EXACTLY, starting off in \ of the
drive that you are installing to. (ie.. C:\ or D:\ ...etc).
From here on out, I will assume that you are installing to C:\FD.
MD FD
MD X00
CD FD
MD DOCS
MD FILE
MD PACKET
MD NETMAIL
MD NODELIST
CD NETMAIL
MD BADECHO
2) UnZip FrontDoor into the C:\FD directory.
3) UnZip X00 into the C:\X00 directory.
STEP TWO: Autoexec, and Misc Files
-Add the following to your AUTOEXEC.BAT
SET FD=C:\FD
C:\X00\XU Port:1:On FIFO:Off
^This corresponds to Com 2, if you are using a
different port change this number to that port.
I.E. Com1=0 Com2=1 etc...
-Add the following to your CONFIG.SYS
DEVICE=C:\X00\X00.sys E B,1,38400 T=2048 R=512
^Once again this corresponds to the port
You are using.
2) Change to C:\FD\NODELIST, and copy the FDNODE.FD [Included] into
that directory. Rename FDNODE.FD to FDNODE.CTL.
4) Copy the FidoNet/Fido Compat Nodelist(s) into C:\FD\NODELIST\
3) EDIT The FDNODE.CTL to suit the Area Code that you are in as well
as change the NODELIST line and the PVTLIST lines to suit your
needs. You MUST have an entry for the NODELIST line, the PVTLIST
lines are optional.
5) Copy the ROUTE.FD into C:\FD. In every instance where you see
1:2608/0 in the ROUTE.FD, change it to the node number of your hub.
Page 12
STEP THREE: FrontDoor Setup.
1) From the C:\FD directory, type FDSETUP{enter}. You will see a screen
with Windows-like pop-up menus. Become familiarized with moving
around, then proceed to the first menu, GLOBAL. From here on, I will
simply state the Menu type (IN BOLD), followed by the Menu option ("In
Quotes"), followed by what should be contained inside that option.
GLOBAL
"ADDRESS"
"Address"
Main - {enter your assigned node number here}
Aka 1 - {unused, unless you have other nets online}
"Site Info"
Simply enter all your system information, Name, Location, etc.
For FLAGS.... Enter
CM,XA,
followed by any of the following, separated by commas...
HST if you have a USR HST modem.
V42 " " " V42 error correction.
V32 " " " V32 " " "
MNP " " " MNP/5 " "
IE: If you have a USR Dual Standard (v32, v42), you would enter:
CM,XA,HST,V32,V42
Also: If your modem has BOTH v42 and v42bis (or v32 and v32bis),
there is no need to put BOTH. Entering V42 automatically
assumes having V42Bis. If your modem is LAPM, enter V42.
"Domains"
Add a domain line for each Network that you are in.
FidoNet's domain is "fidonet.org", all others don't REALLY
matter, unless they are gated into/out of other networks.
If you are in Fido, the first line should read:
ZONE DOMAIN
1 1 fidonet.org
"AKA Matching"
You MUST set this up if you run Multiple nets!
When it asks you for the AKA #, AKA #0 is your main address.
Mine looks like:
ZONE:NET AKA
1 1:0 1:2613/171
2 203:0 203:203/2
A net of Zero tells it ALL nets in that zone.
Page 13
"FILENAMES"
System - C:\FD
Netmail - C:\FD\NETMAIL
Files - C:\FD\FILE
Packets - C:\FD\PACKET
Logfile - C:\FD\FD.LOG
Banner - C:\FD\FDBOOT.MSG
^^^note: you must create this file yourself, it
is the file that is displayed after users hit
escape twice after login. You *MAY* Leave this
field blank if you do not wish a banner be
displayed.
Nodelist - C:\FD\NODELIST
In-Event - C:\FD\INEVENT.MSG
^^^note: create this file also...this file is
what is displayed to users while your system
is in it's nightly event, should they get
through. You *MAY* Leave this
field blank if you do not wish a banner be
displayed.
Msg Base - C:\CELERITY\CONFER
^^^note: This field is basically useless under
Celerity at this point in time. Fill it in
With Celerity's Conference directory though,
I may decide to use it in the future.
Swapping - C:\FD\FILE
"GENERAL"
Country Code - 1
all other options, your preference.
"USERS"
Enter the following:
{enter}{your handle}{enter}{any password}{enter}{select
SUPERVISOR}{enter}{ESC}
Page 14
MAILER
Note: All following menus will show correct setups from TOP TO BOTTOM.
Ie: For Miscellaneous, YYYYNN... would mean reading from TOP to
BOTTOM you would see Yes, Yes, Yes, Yes, No, No, etc....
"MISCELLANEOUS"
YYYYNNYYYNN,255,5,120,N,2,{Your System Name},11,1,N
"LOG"
YYNYNNYYNYYYNN
"FILE REQUESTS"
No Requests
C:\FD\FILE.FRQ <<ignore it, -Used for filebasing (See Tic2Cel.ZIP)
next four lines - blank
0,60,1024,2400,Yes,22:00-06:00,MTWT--S-
FDServer, External Mail, Display, Colors, Hidden Dial Info, and
Function Keys - - - IGNORE.
"ERRORLEVELS"
All Except Received Mail should be 200. Set Received
Mail to 150, and Create Bat = YES.
"AUDIO CONTROL"
Setting YES to an item causes a LOUD beep. Set to your
own preferences, or turn all sound off.
"SWAPPING"
Swapping = YES
If you have EMS or XMS (Extended OR Expanded Memory), and at least
256K of it is free at ALL times, set EMS/XMS = yes.
Page 15
EDITOR - Ignore ALL Options Except:
"ORIGIN LINES"
Enter the origin line #1, a short line with your bbs name & maybe
number, to be printed at the bottom of certain messages. (This
origin line doesn't really accomplish anything. Your bbs should
allow you to enter origin lines for each sub, and there is a place
in tosscan for it also. This is in case NEITHER your bbs nor
tosscan puts in an origin line for you).
"SWAPPING"
Duplicate previous "SWAPPING" menu option.
TERMINAL - The terminal program provided with FrontDoor is an extremely
powerful one. Setup and use of it is WAY beyond the scope
of this text, but full documentation for it is included with
FrontDoor. I recommend you at least try it out, it's the
ONLY terminal program I use anymore.
MODEM
"HARDWARE" - top to bottom
{your COM port # for your modem},{Max Baud Rate},{Lock Port YES if
HST with locked Fossil},YNNN,128,0,0
"MESSAGES"
Copy from your modem's instructions.
ie 2400 is usually CONNECT 2400,etc....
"COMMAND STRINGS"
Escape Code +++~~|~~
Return Online ATO|
Onhook ATH0|
Offhook ATM0H1|
Dial ATD
Prefix T
Suffix |
Delay 1
Init String 1 Take directly from your bbs setup. If there is
2 a V0 statement anywhere, change it to V1.
Down ATM0H1|
Reset ATZ|
"ANSWER CONTROL"
Yes,ATA|,5,No,00:00,00:00
Page 16
PRINTER - Set These to suit your Printer.
MANAGER
"EVENTS"
There should already be one entry;
0 @ -------A * 00:00 00:01 0 0 -1 0
Hit enter. At the bottom of the screen, move the cursor to
BEHAVIOR. Hit enter, and the popup should say:
YYNYYNYYNYNNNN
Hit escape, escape again. Hit insert, and create the following:
Tag X
Days -------A
Modifier Ignore Eventbase (*)
Start Time 00:00
Length 00:01
Errorlevel 250
Min.Cost 0 < Never bother with these two... they should
Max.Cost -1 < never be changed. [Unless your hub is LD]
Behavior NYN
Retry Delay 0
Insert one more.
-This one is for FidoNet Polling.
Tag F
Days --------A
Modifier Ignore Eventbase (+)
Start Time 03:00
Length 00:59
Errorlevel 150
Behavior YYNYYNYYNNNNNYN
Retry Delay 2
Insert one more.
-This one is for DragonNet Polling. [Only needed if you have 2
or more Networks]
Tag D
Days --------A
Modifier Ignore Eventbase (+)
Start Time 05:00
Length 00:59
Errorlevel 150
Behavior YYNYYNYYNNNNNYN
Retry Delay 2
Page 17
Insert One More.
-This one is for Fido Zone Mail Hour, you only need this
one if you are in Fido @1.
Tag Z
Days --------A
Modifier Ignore Eventbase (+)
Start Time 04:00
Length 01:00
Errorlevel 150
Behavior NNNYYNYYNNNNNYN
Retry Delay 0
Insert One More.
Tag X
Days -------A
Modifier Ignore Eventbase (+)
Start Time 06:00
Errorlevel 150
Behavior NYN
...and insert one more...
Tag B
Start Time 01:00
Length 23:00
Errorlevel 150
Behavior YYNYYNYYNNNNNNN
Retry Delay 0
Escape, SAVE CHANGES (Y/N) = Yes.
Go BACK in... You should see:
# T Days M Start Length Lev Min Max Delay
0 @ -------A * 00:00 00:01 150 0 -1 0
1 X -------A + 00:00 00:01 250 0 -1 0
2 F -------A + 03:00 00:59 150 0 -1 0
3 D -------A + 05:00 00:59 150 0 -1 0
4 Z -------A + 04:00 01:00 150 0 -1 0
5 X -------A + 06:00 00:01 150 0 -1 0
6 B -------A + 01:00 23:00 150 0 -1 0
Page 18
***The general Idea of this setup is as follows:
I will start with event 1, as they use event 0 for nothing in this
scenareo.
event 1-Midnight, exit w/errorlevel 250. This goes to the bat file
which, as set up now will call "C:\Celerity\EXTERN.BAT", The
Celerity event batch file.
event 2-3:00am, event Tag "F", this will go to the ROUTE.FD file for
information on this event. ROUTE.FD Tells it to unhold all
echo mail bould for Zone 1 (FidoNet), and to poll our hub.
event 4-4:00am, event Tag "Z", This time slot occupies what is
commonly known in the Fido community as "ZONE MAIL HOUR", by
FidoNet POLICY4, all nodes in FidoNet MUST NOT allow human
callers during ZMH.
event 3-5:00am, event Tag "D", this will go to the ROUTE.FD file for
information on this event. ROUTE.FD Tells it to unhold all
echo mail bould for Zone 169 (DragonNet), and to poll our hub.
event 5 and 6-I have no idea what the origional authors of this doc
wished to accomplish with thoses events. Event 6 Encoumpasses
the ENTIRE day. Other events will overide this event at their
proper times. A GOOD use of a 24 hour even is in the case of
running a "CRASH" Network, where you would want to send mail
at EVERY opportunity during the day.
***Note By Ted Spaulding- I have NO IDEA what the origional writers
of these docs are accomplishing with Event #5, I BELIEVE that it is
NOT needed. You can also modify event "@" to accomplish the
same thing that B does by setting up event "@" like this:
Tag @
Days --------A
Modifier Ignore Eventbase (*)
Start Time 00:00
Length 24:00
Errorlevel 150
Behavior YYNYYNYYNYNNNYN
Retry Delay 0
Then you could get rid of event 6, tag "B".
THIS IS JUST A SUGGESTION - as I do NOT run Front Door.
***End of Note...
If they all are correct, then you are done. If anything is different,
then move your cursor to the incorrect event and change it so that it
matches this table.
2) Exit Out of the setup (SAVE CHANGES = YES!!!!!!!!!!), and type
*********** COPY SETUP.FD FD.SYS ************
THIS IS EXTREMELY IMPORTANT, Tosscan will only 'see' FD.sys. Whenver you change
anything in Frontdoor, you must "copy setup.fd fd.sys"
3) From the same directory (C:\FD), type FDNC{enter}. It should say
that it's compiling the nodelist, then finish saying something like
"25,142 Nodes Compiled". (if it doesn't, then go back to the beginning
and verify that everything is perfect! The Number will be over 25,000
for FidoNet @1, it will be MUCH lower for individual, smaller nets.
Page 19
InterMail Setup:
-Install InterMail as directed by your InterMail manual.
ie.. Place InterMail Diskette into Drive A: or B:.
Type "A:INSTALL [ENTER]" (Or B:)
Follow the screen prompts.
Do not worry about the IM settings too much here, we will go
through them in detail in a minute.
-Change to C:\IM\NODELIST, and copy the FDNODE.IM [Included] into
that directory. Rename FDNODE.IM To FDNODE.CTL.
-Copy The IMRUN.BAT and the EXEBBS.BAT files [Included] to your
C:\IM directory and edit Drives/Paths as necessary.
-Copy the FidoNet/Fido Compat Nodelist(s) into C:\IM\NODELIST\
-EDIT The FDNODE.CTL to suit the Area Code that you are in as well
as change the NODELIST line and the PVTLIST lines to suit your
needs. You MUST have an entry for the NODELIST line, the PVTLIST
lines are optional.
-Copy the ROUTE.IM into C:\IM\SYSTEM. In every instance where you see
1:2608/2 in the ROUTE.IM, change it to the node number of your hub.
After you configure your events (Below), adjust the ROUTE.IM file to
suit your needs, per your InterMail Manual.
Page 20
-Go to the drive that you installed InterMail to (ie.. "C:[ENTER]").
-CD to the directory that it is installed to. (ie.. "CD \IM")
-Type "IMSETUP" and hit [ENTER].
-I Suggest you stick with MOST of the parameters as install placed them,
with the following exceptions -
Menu-Global
SubMenu-Address
Setting-Add additional AKA's as necessary (1 per Net that you are in)
Menu-Global
SubMenu-FileNames
Setting-If you run TosScan (Not sure about GEcho), TosScan WILL NOT
Search your secure files directory for inbound packets. For
This reason, I suggest that you set Files and Secure Files to
The same directory.
Setting-BANNER-Add a banner file if you wish (Displayed when user
Hits Escape Twice to enter BBS) - Not Necessary.
Setting-IN EVENT-Add a "In Event" file if you wish (Displayed when
user connects and the BBS is "In An Event" - Not Necessary
Setting-SEMAPHORE-I use C:\IM\SEMA, although a RAM disk would do well
here. This directory is used for inter-program commu-
nication. Used mostly in a MultiNode configuration.
SubMenu-Site Info
-Please ENSURE that the info here is correct for your system. The Phone
number in this area MUST be in 1-AAA-PPP-XXXX where AAA=Area Code,
PPP=Prefix, and XXXX=4 digit phone extension. IT MUST BE PRECEEDED BY
A 1-
SubMenu-Users
-You may make a user for yourself, If you are security conscious, and
give yourself Supervisor access - This will also allow you to write
NetMail with IM's Editor. Suggested, but not required.
Menu-Mailer
SubMenu-Miscellaneous
Setting-Trigger exit upon reciept of NetMail-
Set this to yes.
Setting-Upon reciept of ANY file-
Set this to yes (Will allow you to process new fido NodeLists)
Setting-Retry Delay-
I have set this to a more "Reasonable" Level. I use 180.
Setting-Days to keep Mail history-
7 Days will make for BIG log files. I use a 2 here.
Setting-BBS Software Name-
The name of your system should be here-PURELY cosmetic.
This is displayed when they connect.
(ie.. "Hit ESC twice to enter xxxxxxxxxxx")
SubMenu-ErrorLevels
Setting-Recieved Mail- Set to 150
Setting-Create BAT File- Set to Yes
Menu-Modem
SubMenu-Advanced Setup-
SubMenu-Connect Strings-
-Set all BBSEXIT levels to 200.
Page 21
*Events are the worst part of setup. Below is a template for a 2 network
setup. If you run more, simply expand, if you run just one, eliminate the
second net's setups...
*This setup is FOR A CRASH MAIL SETUP, who will poll twice daily, at 3am and
5pm on the first net and at 5am and 6pm on the second net. If you wish to
"CRASH" everything to your hub, modify event "@" in the ROUTE.FD file to
dial your hub..
*Substitute ALL cases of 1:2608/85 with your Primary net Address.
*If you run 2 nets, substitute the 169:315/3 with your sencondary Net Address,
Otherwise, do not add those events...
*I use event "F" standing for "F"idoNet,
"D" standing for "D"ragonNet,
"Z" standing for "Z"one Mail Hour and
you MUST use "X" for eXternal events.
*These events are governed further in your ROUTE.FD file.
Menu-Manager
SubMenu-Events- [Now the fun begins!]
You are provided with one default event, "@", edit it to look like
this:
0 @ -------A * 00:00 24:00 0 0 1:2608/85 [FidoNet]
The behavior for this event should read [from top to bottom]:
Y,Y,N,Y,Y,N,N,Y,Y,N,N,N,Y,N,N,N
You will have to [INS] insert the rest of these events, one by one..
1 X -------A * 00:00 00:01 250 -1 1:2608/85 [FidoNet]
Behavior- N,Y,N
-This event is for your Midnight Celerity Event (.BAT file)
2 F -------A * 03:00 00:59 0 -1 1:2608/85 [FidoNet]
Behavior- Y,Y,N,Y,Y,N,N,Y,Y,N,N,Y,Y,N,Y,N
-This event is for FidoNet Polling. NOTE: If you have a LD Hub, you
Will NEED to increase The Max Cost. Mine is local.
3 Z -------A * 04:00 01:00 0 -1 1:2608/85 [FidoNet]
Behavior- N,N,N,Y,Y,N,N,Y,N,N,Y,N,N,N,Y,N
-This event is for FidoNet Zone Mail Hour. If you are NOT in Fido,
You do not need this event. If You are in Fido @1, You MUST Observe
"Zone Mail Hour", in which you MAY NOT recieve human callers.
Note:Zone Mail hour varies from Dailight Saving Time To Standard Time,
as it is based on Greenwich Meen Time. Check with your local NEC for
The current observed ZMH.
Page 22
4 D -------A * 05:00 00:59 0 -1 169:315/3 [DragonNet]
Behavior- Y,Y,N,Y,Y,N,N,Y,Y,N,N,Y,Y,N,Y,N
-This event is for DragonNet Polling. NOTE: If you have a LD Hub, you
Will NEED to increase The Max Cost. Mine is local.
5 F -------A * 17:00 00:59 0 -1 1:2608/85 [FidoNet]
Behavior- Y,Y,N,Y,Y,N,N,Y,Y,N,N,Y,Y,N,Y,N
-This event is for FidoNet Polling. NOTE: If you have a LD Hub, you
Will NEED to increase The Max Cost. Mine is local.
6 D -------A * 18:00 00:59 0 -1 169:315/3 [DragonNet]
Behavior- Y,Y,N,Y,Y,N,N,Y,Y,N,N,Y,Y,N,Y,N
-This event is for DragonNet Polling. NOTE: If you have a LD Hub, you
Will NEED to increase The Max Cost. Mine is local.
***The general Idea of this setup is as follows:
event 0-This Event runs 24 hours a day, EXCEPT when other events
are being run. You may use this event in a "CRASH" type
environment to poll your hub ALL DAY, everytime you have
outgoing mail. Mine is not set up that way, but this
one could me modified to operate that way with a couple
simple modifications to the ROUTE.IM file.
event 1-Midnight, exit w/errorlevel 250. This goes to the bat file
which, as set up now will call "C:\Celerity\EXTERN.BAT", The
Celerity event batch file.
event 2-3:00am, event Tag "F", this will go to the ROUTE.IM file
for information on this event. ROUTE.IM Tells it to
unhold all echo mail bound for Zone 1 (FidoNet), and to
poll our hub.
event 3-4:00am, event Tag "Z", This time slot occupies what is
commonly known in the Fido community as "ZONE MAIL HOUR",
by FidoNet POLICY4, all nodes in FidoNet MUST NOT
allow human callers during ZMH.
event 4-5:00am, event Tag "D", this will go to the ROUTE.IM file
for information on this event. ROUTE.IM Tells it to
unhold all echo mail bould for Zone 169 (DragonNet), and
to poll our hub.
event 5-5:00pm, event Tag "F", this will go to the ROUTE.IM file
for information on this event. ROUTE.IM Tells it to
unhold all echo mail bound for Zone 1 (FidoNet), and to
poll our hub.
event 6-6:00pm, event Tag "D", this will go to the ROUTE.IM file
for information on this event. ROUTE.IM Tells it to
unhold all echo mail bould for Zone 169 (DragonNet), and
to poll our hub.
Menu-Manager
SubMenu-Security-
If you use session level passwords to connect to your hub, configure
them in this section.
Page 23
BBS Setup:
**From here on out, I will walk you through setting up a FidoNet Test Base.
1) Set up a Directory for the Net you intend to carry.
Example: My FidoNet Message Bases are in C:\CELERITY\FIDONET.
2) Create Subdirs for each Sub you wish to carry.
If you look at the echo listing, I have found it easiest
to use the first part of the Conference (Ex. The BBS Discussion echo's
Conf Name is BBS-DISCUSSION, The dir it is in is BBS-DISC, Simple.)
3) Go to the BBS and set up the message bases [This can also be done from
within Sicko's CMT Utilities. They are set up the exact same way as
local ones with 1 exception.
-> Network Options: You will be presented with a
variety of questions in this order.
Base Network Type (0=Local, 2=Fido)? 2
Network Address (Format ZONE:NET/NODE): 1:2608/85
-Place YOUR Network address here......^^^^^^^^^
This ADDRESS MUST BE CORRECT!
Network Echo Name (ex. BREIP-SYSOPS): FIDO-TEST
-Place The Fido Conference name here^^^^^^^^^ - This will be our
FidoNet Test Base.
Network Identifier (ex. CelerityNet): FidoNet
-Place the NAME of the Network here.^^^^^^^ (Cosmetic ONLY!)
CelToScn Setup
PLEASE REFER TO THE top of this CelToScn.DOC Documentation for
information on setting up CelToScn.
Page 24
TosScan Setup
1) Unzip Your TosScan copy into the C:\FD [For Front Door] or
C:\IM\SYSTEM [For InterMail]
directory.
3) When you unzip TOSSCANM.ZIP, you will see TS8088.EXE, TS286.EXE,
TSU8088.EXE and TSU286.EXE. If you have an 8088, delete the 286
versions and rename TS8088.EXE to TOSSCAN.EXE, and TSU8088.EXE to
TSUTIL.EXE. If you have a 286, 386, or 486, delete the 8088 versions,
and rename TS286.EXE -> TOSSCAN.EXE, TSU286.EXE -> TSUTIL.EXE.
1) From C:\FD or C:\IM\SYSTEM, type TSETUP{enter}. Setup procedures
follow the same guidelines as with Front Door setup.
SYSTEM DATA
[FrontDoor]: "PATHNAMES"
Dup C:\FD\NETMAIL\BADECHO
Out C:\FD\PACKET
Log C:\FD\TOSSCAN.LOG
[InterMail]: "PATHNAMES"
Dup C:\IM\NETMAIL\BADECHO
Out C:\IM\PACKET
Log C:\IM\SYSTEM\TOSSCAN.LOG
"COMPRESSION PROGRAMS"
1 PKZIP -ao
"DECOMPRESSION PROGRAMS"
Use only ZIP =
PKUNZIP.EXE -o
"MISCELLANEOUS"
'Delete Duplicates' and "ARCMail Compatible' flags turned ON, Keep
Mail for 14 Days [Preference here].
"SWAPPING"
Same as in FDSetup or IMSetup.
[FrontDoor]: Path - C:\FD\FILE
[InterMail]: Path - C:\IM\FILES
Page 25
*NOTE: This setup is ONLY for end-point nodes. If you are a hub, or you
"Pass" echo's thru you, GET HELP! :-)
AREA MANAGER
You will need to create individual entries for EVERY SINGLE
ONE of the echoed subboards in your system.
Here is one sample entry. The only things you will change from
subboard to subboard are the PATH, FILENAME and COMMENT.
.............................
Name: FIDO-TEST
Comment: FidoNet Test Conference (Comment is OPTIONAL)
Origin: should show the one you defined in FDSetup or
IMSetup
Path: C:\CELERITY\FIDONET\FIDO-TES
^^^NOTE: this path should be THE SAME PATH you
defined in CelToScn msgbase setup. If you
screwed up with the pathname, tosscan WILL
say that it couldn't find the path. Check it.
Group: F # Days: 0 # Msgs: 0
^^^ NOTE:Once again, I use "F" for FidoNet, purely
cosmetic.
┌──────────────┐
│ 1:xxxx/0 <<--Your node number should appear here. Hit enter.
│ 169:xxxx/0 │
└──────────────┘
┌───────────────┐
│ 1:2608/2 ■ <<--Select The Hub for this Base
│ 169:169/1 │ (a BOX (■) means it is selected)
└───────────────┘
Enter, F10, ESC, now you're done with ONE ENTRY.
(Don't feel bad. I have 432 echoed subboards on my system.
How do you think I felt?)
-------
When you are finished entering ALL of your subboards, then hit
F2 (Global - if it says "Export" then hit ESC, then F2).
Hit INSert, and type in your hub's node number. It will say
Groups to include in search: ABCDEFGHIJKLMNOPQRSTUVWXYZ_
Now, delete all the letters (A-Z), then just type F.
It should then say Change status on all areas in "F" (or
"ABC...Z") (Y,N) Select Yes, and it will say "Working..."...
Eventually, it will reply "Added {node #} to xx areas."
*Once again, I use "F" as my flag for FidoNet.
Page 26
Next, hit A)dd Status. You will see:
F1-Passthru F2-Security F3-Visible F4-Seen-By F5-CPP F6-Tiny F7-Pvt
Hit F3, F4 and F5, then Groups to Include in search A..Z...
Delete all the letters (A-Z), then just type F.
It should then say Change status on all areas in "F" (or
"ABC...Z") (Y,N), yes, "Working...", "Changed xx areas -
Press ESC"... Now, select R)emove Status, this time select
F1, F2, F6, and F7, and follow the same procedure as with Add.
You are finished.
2) Once done with the Areamanager, hit Escape, SAVE CHANGES = YES!!!!
NODE MANAGER
Insert an entry for each hub that you poll.
ie.. I poll 1:2608/2, My fido Hub, My first entry looks like this:
SYSTEM: 1:2608/85
PASSWORD:
GROUP: F
PROGRAM: PKZIP -ao
STATUS: NONE
My second entry (For my second net) looks like this:
SYSTEM: 169:169/1
PASSWORD:
GROUP: D
PROGRAM: PKZIP -ao
STATUS: NONE
Through with Tosscan setup.
Page 27
FastEcho Setup
1) Make a directory under your C:\FD for C:\IM called FastEcho.
ie.. "MD \FD\FASTECHO" - For Front Door
"MD \IM\FASTECHO" - For InterMail
2) Unzip Your FastEcho copy into C:\FD\FASTECHO [For Front Door] or
C:\IM\FASTECHO [For InterMail]
3) From C:\FD\FASTECHO or C:\IM\FASTECHO, type FESETUP{enter}.
Setup procedures follow the same guidelines as with Front Door
and InterMail setup.
THESE ARE SUGGESTED SETTINGS ONLY! I Realize that if you do NOT
have FastEcho Registered, there are *SOME* parameters that you
can NOT set.
SYSTEM
"Network Addresses"
Main - {enter your assigned node number here}
Aka 1 - {unused, unless you have other networks online}
I Suggest ALLWAYS placing you Fido Node Number (If
you have one) as your primary Address.
Place the domain name on this line as well (If You
Know it/Need it) The domain for FidoNet Proper is
"fidonet.org".
"User Names"
Just put your name on Line one. FastEcho will use this as
"Miscellaneous"
Mailer - If you use a Mailer that FastEcho has Support
for, Select it up here.
BBS Software - Set to NONE.
Swapping - Same as in FDSetup or IMSetup.
Be 'Quiet' - None
"Pathnames"
[FrontDoor]: NetMail - C:\FD\NETMAIL
[InterMail]: NetMail - C:\IM\MAIL
Messagebase- C:\HUDSON
This is used by FastEcho to Lookup The HudsonBase.
If You do NOT use Hudson, It will tell you that NO
Hudson Base exists, and ask you if you wish to create
one. Go ahead and say yes.
[FrontDoor]: Inbound - C:\FD\FILE
[InterMail]: Inbound - C:\IM\FILES
Temp. Inb. - { Set this to a RAMDrive *IF* you have one. }
[FrontDoor]: Secure Inb.- { Leave Blank, FD Does NOT support Secure Inb. }
[InterMail]: Secure Inb.- C:\IM\SECURE
[FrontDoor]: Outbound - C:\FD\PACKET
[InterMail]: Outbound - C:\IM\PACKETS
Temp. Outb.- { Set this to a RAMDrive *IF* you have one. }
[FrontDoor]: Semaphores - { DOES FD Support Semaphores *YET*??????? }
[InterMail]: Semaphores - C:\IM\SEMA
BBS Config - Leave Blank
DB Queue - Leave Blank
Swapping - { Set this to a RAMDrive *IF* you have one. }
Page 28
"FileNames"
[FrontDoor]: Logfile - C:\FD\FASTECHO\FE.LOG
[InterMail]: Logfile - C:\IM\FASTECHO\FE.LOG
[FrontDoor]: AreaFix Log- C:\FD\FASTECHO\FE_AF.LOG
[InterMail]: AreaFix Log- C:\IM\FASTECHO\FE_AF.LOG
[FrontDoor]: Statistics - C:\FD\FASTECHO\FE_STATS.TXT
[InterMail]: Statistics - C:\IM\FASTECHO\FE_STATS.TXT
"Parameters"
Duperecords - PURELY Preference. I have mine set to 50000.
Maximum open .QQQs- Leave at 0, Unless you have problems.
I *HIGHLY* Suggest setting DOS Files to
ATLEAST 50 if you are an end node.
HIGHER if you are a hub, or run
MultiNode.
Messagebuffersize - Leave at 0, UNLESS you have Memory restrictions.
Maximum .PKT size - Leave at 0, Unless one of your Uplinks/Down-
Links Bitches. 98% of todays Tossers
have NO limitation.
Compress after - 0
Compress free - 0
"Advanced Options"
Retear - No
Auto-Area-Create - NO! Leave at NO, unless you are
ABSOLUTELY POSITIVE you know what you
are doing. This parameter is an
ACCIDENT WAITING TO HAPPEN!
Kill Empty Netmail- No { This is a preference }
Kill Dupes - No { Again, Preference. I like to see
My Dupes }
Share HMB - No { Set to YES if you use the HMB }
Force Mailer Rescn- Yes
Respond to RRQ - Yes
Use EMS for Buffer- Yes
Check .PKT Destin.- Yes { Set to NO if you Route packets
for other nodes!}
Security - Normal { BIG Preference, Hit F1! }
Logging - Full
Graphical Tossing - ?? { Preference, I use No, slows things
down, a little }
Toss Buffers - Large { Reduce if you have Memory
restrictions }
"ARCmail Options"
"Archive Extentions"
Inbound - 0-9&A-Z { Change ONLY if your HUB Bitches }
Outbound - 0-9&A-Z { Change ONLY if your HUB Bitches }
"Mailer's Semaphores"
Check - YES
Create - YES
Check complete Files - Yes { If your registered }
Page 29
"FEUtil Parameters"
"PURGE"
This WHOLE Section is PURE preference, Hit F1
Use Arrival Date - No
Autorenumber at - 0
Exclude Users - No
Exclude SysOps - No
Keep NetMails - No
Kill grunged date - No
"Compression Programs"
These should ALL be fine left at default.
"DeCompression Programs"
These should ALL be fine left at default.
"External Programs"
I Do NOT use these.
"Groups"
PURE Preference. I Have 2 Groups set up right now -
Group C) CelNet Message Bases
Group F) FidoNet Message Bases
"Origins"
Just put one in that SEMI-Describes your system.
FastEcho will tack this on to ANY message that does NOT
allready have a Origin Line on it.
Page 30
DATA
"Node Configuration"
[INS]ert 1 entry in here for each Uplink/Downlink That
you have. Here is a Good Entry to use as a "Default Entry":
NOTE: Obvoiselly, You will have to replace The Address with
YOUR Hub's, The Group with whatever groups you want
this node to have access to. Match the AKA up with
YOUR address that matches the ZONE: of the Hub.
FESetup System Data Export Import F1 Help
░░░░░░░░░░░░░░░░░░░░░░┌─────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░╔══ 1/14 ═══════════════════ Node-Manager ════════════════════════════╗░░░░░
░░░░║ ║░░░░░
░░░░║ Address: 1:2613/5.0 4D/Type 2+: Y ║░░░░░
░░░░║ ║░░░░░
░░░░║ Name: Mother - Net2613 Mail Server ARCmail 0.60: N ║░░░░░
░░░░║ TosScan: N ║░░░░░
░░░░║ Your Aka: 1:2613/171.0 ║░░░░░
░░░░║ Convert Umlaut: N ║░░░░░
░░░░║ Passwords ║░░░░░
░░░░║ ARCmail: Allow Area-Create: N ║░░░░░
░░░░║ AreaFix: ******** New Area Default Group: F ║░░░░░
░░░░║ Status Export By Name: N ║░░░░░
░░░░║ ARCmail: None Allow Remote Maintenance: N ║░░░░░
░░░░║ AreaFix: None Allow Rescan: Y ║░░░░░
░░░░║ Packer: ZIP Send Notify: Y ║░░░░░
░░░░║ Send Help: Y ║░░░░░
░░░░║ Groups: F ║░░░░░
░░░░║ Passive: N ║░░░░░
░░░░║ Security: 0 Automatic Passive: 0 ║░░░░░
░░░░║ ║░░░░░
░░░░╚════════════════════════════════════════════════════════════════════╝░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Enter-Edit F2-Routing F3-Browse F4-Area List F5-Copy Ins-New Entry Del-Delete
Page 31
"Area-Manager"
[INS]ert 1 entry in here for each Echo Area That you have,
PLUS One for "BADECHO" and one for "DUPEECHO"
- Set Up a "BADECHO", With ATLEAST the following Parameters-
Type: Badmail
Storage: Fido *.MSG
Path: C:\IM\MAIL\BADECHO { Or Wherever you want to put it }
Use AKA: Whatever, Just use your First One.
- Set Up a "DUPEECHO", With ATLEAST the following Parameters-
Type: Dupeboard
Storage: Fido *.MSG
Path: C:\IM\MAIL\DUPEECHO { Or Wherever you want to put it }
Use AKA: Whatever, Just use your First One.
*NOTE: This setup is ONLY for end-point nodes. If you are a hub, or you
"Pass" echo's thru you, GET HELP! :-)
Here is a SetUp AREA for our "Test Echo"
╔══════════════════════════════════ Edit Area ═════════════════════════════════╗
║ Name: FIDO-TEST Group: F ║
║ Comment: FidoNet Test Conference { Comment is OPTIONAL } ║
║ Origin: Asylum Associates - (716) 872-5887 - [Webster, NY] ║
║ Type: Echomail ║
║ Storage: Fido *.MSG Board: ║
║ Path: C:\CELERITY\FIDONET\FIDO-TES <-NOTE: this path should be THE SAME ║
║ Use Aka: 1:2613/171.0 PATH you defined in CelToScn Setup. ║
║ ║
║ Mandatory: N Keep SEEN-BY: Y Tiny SEEN-BY: Y CPD: Y Passive: N ║
║ Convert Umlaut: N Keep users: N Kill read: N Disable Passive: N ║
║ Manual changes: N Hide area: N Keep netmails: N ║
║ ║
║ Purging # Msgs: 1000 # Days: 8 # Rcvd Days: 8 ║
║ Security Read: 0 Write: 0 ║
║ ║
║ Seen-by: 1:2613/171 <<--Your node number should appear here. Hit enter. ║
║ Export to: 1:2613/5 Tag ALL of the AKAs that are in the SAME ZONE! ║
║ ^^^^^^^^ ║
║ This is Your HUBS Node Number, Should pop up in a Pick List ║
║ ║
║ ║
╟──────────────────────────────────────────────────────────────────────────────╢
║Press F10 to save or ESC to abort editing... ║
╚══════════════════════════════════════════════════════════════════════════════╝
F10, now you're done with ONE ENTRY.
(Don't feel bad. I have 432 echoed subboards on my system.
How do you think I felt?)
Put in One ENTRY for EVERY Echoed Message base that you have.
Page 32
"AreaFix Options"
Allow %RESCAN - Yes
Allow %PWD - Yes
Allow %PKTPWD - Yes
Allow %COMPRESS - Yes
Keep Requests - Yes
Keep Receipts - No
Scan Before Tossing- Yes
Detailed %LIST - Yes
Max. Receipt Size - 0
AreaFix %HELP File - Set To C:\IM\FASTECHO\AREAFIX.HLP
You will need to Create/Update this
File
Forward Requests - I Have None Set Up
SAVE IT! Through with FastEcho setup.
Page 33
TEST!
1) Your FRODO.BAT (OR IMRUN.BAT) should be in a directory somewhere in
your path. (Preferably, C:\FD (or C:\IM), which you should have
inserted into your path at the beginning of this pain-in-the-but
text).
2) Type frodo (or imrun){enter}.... It SHOULD load up FrontDoor (or
InterMail), and deposit you in it's WFC screen.
3) Type ALT-Q, and you should see >>USER BREAK, and you are dropped to DOS.
4) Logon locally to your bbs and enter one message (THIS IS A TEST) in the
FidoNet Test Message base. Exit out, and rerun frodo.bat (or
imrun.bat).
5) This is the same procedure you will use any time you wish to test
and make sure the net is working:
-Hit ALT-Z (dos shell) from WFC.
-Go to your Celerity Network Directory. (Or wherever you installed
CelToScn.
-Type CELTOSCN /SCAN /PC:\CELERITY\NETWORK
It should find 1 message in the Fido Test area. If it doesn't then
recheck your CTSetUp parameters, and make sure that ALL path names
are correct.
-Go to your ForntDoor or InterMail directory.
[TosScan]- - FrontDoor-Type tosscan scan.
InterMail-Type system\tosscan scan.
[FastEcho]- - Change Dir to FastEcho {CD FASTECHO}
Type fastecho scan.
-It should run through a list of ALL of your FidoNet subs, and end up
finding ONE message (the one you just posted), and zip it up as
outgoing mail. If it DOESN'T, first, check through your ENTIRE
TSETUP or FESETUP setup, make sure all paths, etc, are perfect.
If tosscan/FastEcho still finds no outbound messages, then
something IS screwed (a good test here, if it messed up, is to
change to your bbs directory, then goto C:\Celerity\FidoNet\FIDOTEST.
Do a directory, there should be a 1.MSG in there (this shows
that CelToScn did it's job - if not, then CelToScn is messed
up). Re-Check CTSETUP.
-Type EXIT, and you should see, in the center, message area of the
screen, {hub's node number} <1> (the number in brackets
doesn't matter... Just as long as you see Outbound Mail: {hub node #}
or something like that)...
6) Once done with this, your system is ready to receive calls. I highly
recommend scanning through the FD.DOC or the InterMail manual at least
once, it really helps familiarize you with things (there is also a VERY
good terminal program included in the FrontDoor/InterMail package. I
no longer use ANY of the commercial term programs; FDTerm is plenty for
me (has Z-Modem MobyTurbo xfers, autodialing, text capture, scrollback
buffer, macros, virtually everything most users would need. But a
tutorial on that feature is WAY beyond the scope of this Setup Pack.)
7) GOOD LUCK! Hope everything works well for you!
Page 34
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
YOU'RE FINISHED! With any luck, you should now be able to run your net. Enjoy!
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
That's It!!! See you on the Nets!
The Fido Setup docs were composed IN PART from an origional Doc set
composed by Midnight Sorrow, which was updated by Pappy Boyington.
They are responsible for most of the Front Door and TosScan Setups...
InterMail Setup, CelToScn Setup, FastEcho Setup and Celerity v2.0x
Setup was Done in whole by Ted R. Spaulding AKA Wacky Rabbit. No
donations, If you want to donate, Acquire and REGISTER your TCMail.