home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
DOGF_206.ZIP
/
DOGFIGHT.DOC
< prev
Wrap
Text File
|
1992-02-20
|
30KB
|
1,182 lines
DOGFIGHT 2.06
FIDO Net Message Import/Export For Spitfire V3.xx
Copyright(c) 1990-92, C.S.Tyson, All Rights Reserved.
Written By:
Chris Tyson
22 Talbot Road
Charford, Bromsgrove
WORCS, B60 3PA
England
44-(0)527-76025
License Agreement
=================
DOGFIGHT ('The software') is Copyright(c) 1990,91,92 by Chris Tyson, All rights
reserved. The original purchaser ('you') is granted a license to use DOGFIGHT
only, subject to the following restrictions and limitations.
1) This license agreement is granted to the original purchaser only.
It is not transferable under any conditions.
2) This software may only be used on a single computer system. You may not
use this software on more than one computer system.
3) You may make back-up copies of DOGFIGHT for your own protection, subject
to the limitations of this license.
4) You may not engage in, nor permit third parties to engage in, any of the
following :
A) Providing or permitting use of or disclosing the software to third
parties. (The exception being that users of your system may use
the software as long as it is running on your system.)
B) Making alterations or copies of any kind in the software.
(except as specifically permitted.)
C) Attempting to disassemble, decompile, or reverse engineer the
software in any way.
D) Granting sub-licenses, lease or other rights in the software to
others.
The author reserves the right to terminate this license if there is a
violation of its terms or default by the original purchaser. Upon termination
for any reason, all copies of the software must be destroyed, and the original
purchaser will be liable for any and all damages suffered as a result of
the violation or default.
The author of this software is not liable for damages suffered as a
result of the improper use, proper use, or inability to use this software.
Registration
============
If after using DOGFIGHT for a period of 30 days you decide to keep it,
then registration is required.
The registration fee is fifteen pounds sterling (£15.00).
Postal-orders or international money orders in UK funds should be made
payable to Christopher Tyson, and sent to the address above.
NO personal cheques from persons outside the UK please - as it costs a lot
to cash them.
For this you get:
A personally compiled copy of your registration details file.
Unlimited support - you can phone me any time voice on the above number.
Duplicate message checking will become operative.
All command line parameters will become operative.
NOTE FOR REGISTRATION FROM THE UNITED STATES
===========================================
Due to the apparently ridiculous cost of sending funds
from the United States to England, Michael Martell Sysop
of Wolfs Moon BBS (207-772-9093 /9600/24hrs)
(207-773-5791 /9600/24hrs)
Fido Node 326/211
has agreed to act on my behalf and accept registrations from persons
within the US for the Dogfight software.
Therefore, the full cost of registration within the US will
be 35 dollars, payable to
Michael Martell
5 Pineledge Terrace
Portland, Maine 04103
(207) 772-5625 6:00-11:00PM EST
This will cover the registration fee, plus a small amount
towards administration and the cost of sending the fee to
me.
I'm sure you will agree, this cost is far below the cost of
sending the registration fee direct to myself, in UK funds.
US Address
Acknowledgements
================
Many thanks to Mike Woltz of Buffalo Creek software, without whom Dogfight
could not have been completed.
Thanks to Michael Martell for support and encouragement, whithout whom v2.06
would never have come about.
Dogfight uses Buffalo Creek's BCSHARE file sharing/locking unit.
DOGFIGHT was written using Borlands Turbo Pascal v5.5.
Special thanks again to Michael Martell for acting on my behalf in the USA.
Introduction
============
In the past, if Spitfire sysops wished to be part of FIDO Net then a
'door' type program (i.e. SMLNET) had to be used to maintain the message
base completely separate from the Spitfire message base.
DOGFIGHT was written to enable Spitfire sysops to import/export FIDO
messages to and from the Spitfire message base.
Things you need to know -
When you set up your Spitfire conference areas to hold echo
messages, please ensure you set the netmail toggle ON.
DFDECOMP must be ran prior to DFIMPORT to ensure your inbound
mail has been decompressed. Failure to do this will cause
unpredictable results. Please read the section on DFDECOMP.
DOGFIGHT comprises the following executable programs :
DFCONFIG to create the DFCFG.??? configuration file.
DFDECOMP to decompress inbound mail bundles.
DFIMPORT to import FIDO Net messages directly from .PKT, .MO?,
.TU? etc files into the Spitfire message base.
DFEXPORT to export messages from the Spitfire message base directly
into a FIDONet compatible .OUT file and compress this file
if required, and to create .REQ file request and .FLO file
send files. (See below)
DFDB used for systems running D'Bridge front end mail to convert
FIDO files to D'Bridge format.
DFRESEND - sysop utility to re-export messages if required.
Command Line Parameters
=======================
L - This will create either DFEXPORT.LOG or DFIMPORT.LOG giving the number
of messages imported/exported from/to each area.
(registered versions only)
I - This will create DFIMPORT.INF or DFEXPORT.INF showing which FIDO areas
will be imported/exported from which Spitfire message conferences.
(registered versions only)
NOSTRIP - As a default DFIMPORT removes SEEN-BY: and PATH: lines from
inbound messages. Adding the NOSTRIP command line parameter will
cause DFIMPORT NOT to strip these lines.
(registered versions only)
DFCFG.??? - Used to specify which config file to use (ALL DF??????.EXE
programs - defaults to DFCFG.001).
RF - Used in conjunction with DFRESEND. The RF parameter will cause DFIMPORT
to create a text file called DFRESEND.CNF listing each conference and
the number of messages imported in the format:
{conference number} {number of messages} i.e.
10 15
11 30
12 33
etc. etc. etc..
DFRESEND can then be ran with the RF paramter, and will mark these
messages as not sent, so DFEXPORT can export them if you so wish.
Features
========
Import strips Seen-By and Path lines from messages as well as message control
information (i.e. PID: REPLY:) so leaving the message 'clean'. If NOSTRIP is
specified Seen-By and Path lines will NOT be removed.
Export allows direct addressing of NetMail messages to be sent to the
recipients net/node.
File requests allowed from your NetMail message conference, addressable to
ANY system.
File sends allowed from your NetMail message conference, addressable to ANY
system.
Log files showing the number of messages imported/exported by Dogfight
(registered versions only).
Information files showing which FIDO AREA's will be imported/exported
to/from which Spitfire conference(registered versions only).
Outbound packets 'mashed' if required or standard .OUT files built for
processing by an external 'message masher' for netmail and echo message
packets.
Standard .REQ and .FLO files built for file requests/sends.
Full file sharing/locking for multi-node systems.
Multi-hub operation. Each echo area can be configured to be exported to
a specific hub.
Multi-config files. For use by Hub's. You can specify NOT to mark each
message as sent, therefore allowing re-exporting of messages to other
systems using additional DFCFG.??? files. Up to 999 config files.
Full zone support - netmail messages, freq's & sends can be sent to
any zone (up to zone 999 for BinkleyTerm - 99 for D'Bridge).
AREA: names up to twenty characters long.
Duplicate checking. Dogfight maintains a check on the last 4000 messages
imported and will not import duplicate messages.
Will import/export to/from up to 255 Spitfire conferences.
Allows messages up to 500 lines by 80 characters to be imported.
DFCONFIG.EXE
============
DFCONFIG.EXE must be ran prior to anything else to create the
configuration file required by all the Dogfight programs.
USAGE: DFCONFIG [DFCFG.???] (defaults to DFCFG.001)
The following menu will be presented when DFCONFIG is ran:
--------------------------------------------------------------
DOGFIGHT Configuration Utility
Copyright(c) 1990,92 C.S.Tyson, All Rights Reserved.
Using : DFCFG.???
1) First Time Configuration
2) View/Edit System Data
3) View/Edit Conference Data
4) View Edit External Program Data
5) Quit
Please select 1-5 :
--------------------------------------------------------------
When running DFCONFIG for the first time, please select option 1. This
will take you through each of the menu items one at a time.
SYSTEM DATA Screen
==================
Option 1) Sysop Name- This the name of the BBS sysop. It is used to replace
messages from 'Sysop' during export.
Option 2) - If selected this will toggle between 'Inbound messages addressed
to {sysopname} will be re-addressed to Sysop' and 'Inbound
messages addressed to {sysopname} will NOT be re-addressed to
Sysop'.
Option 3) - You can specify to whom inbound messages addressed to Sysop will
be re-addressed to using this option. You will be prompted to
enter the name. If re-selected it will revert to '...Sysop will
remain unchanged'.
Option 4) Your Zone - Enter your FIDONet Zone number.
Option 5) Your Net - Enter your FIDONet Net number.
Option 6) Your Node - Enter your FIDONet Node number.
Option 7) Your Point- Enter your FIDONet Point number.
Option 8) Your HUBS Net - Enter your hubs Net number. This will be your
'primary' hub when configuring your echo areas.
SYSTEM DATA Screen (cont.)
==================
Option 9) Your HUBS Node- Enter your hubs Node number.
Option 10) Origin Line - This will be appended to outbound messages. It is
usually a short 'advert' for you BBS.
Option 11) Path to Outbound Directory
- This is where DFEXPORT will place outbound mail/file reqs/sends
for you front-end mailer to process (see DFDB for D'Bridge!!).
Option 12) Path to Work Directory
- This is where DFIMPORT will look for .PKT files to import to your
Spitfire message base.
Option 13) Path to Message Base
- This is the path to your Spitfire message base.
Option 14) - If selected this will toggle between '...message bundles will be
deleted after decompression' and '....will NOT be deleted...'
This is used by DFDECOMP. NOTE: If this is set to 'NOT deleted'
you MUST remember to have the bundles moved/deleted prior to
running DFDECOMP again, or DFIMPORT will try to re-import the
same messages.
To change any of the options simply enter the option number and press return.
Options 2,3 and 14 have defaults that will not need changing during normal
operation. Unless you know what your doing I'd recommend they are left alone.
After completing all the changes you require, enter Q to quit.
CONFERENCE DATA Screen
======================
When running DFCONFIG for the first time you will be presented with a blank
screen, and the following options:
Add, Edit or Delete Conference or Exit? (A/E/D/X) :
Selecting 'A' will give you the following:
Spitfire Conference Number : - Enter the conference number you wish
to configure.
FIDO Area Name : - Enter the FIDO AREA you wish imported
into the above conference. This name
is critical - Please Check it!
Net to send to (Enter for primary Net/Node) :
- This is used for multi-hub operation.
If you are not running multi-hub press
return and your 'primary' hub net/node
will be used. For multi-hub, enter the
net to send to and press return, you will
be prompted for the node.
Mark exported messages as sent? (Y/n) :
- This is used in conjunction with multiple
DFCFG.??? files for HUB systems, allowing
the re-exporting of messages. The default
is 'Y'. If you are not a HUB leave this
as the default 'Y'.
If you select E (edit) or D (delete) you will be prompted for the conference
number you wish to edit or delete. Delete will ask for confirmation of the
delete. Edit will allow you to change the Spitfire Conference number, the FIDO
AREA name or the net/node to send this conference to.
After each addition/change, the full list of configured conferences will be
displayed, 9 lines at a time.
After completing all the additions/changes you require select option X to
exit.
Special Conference Areas
========================
There are two special conferences used by Dogfight, these are:
NETMAIL - If this conference exists, any inbound netmail messages will be
placed in this conference. To allow file requests/sends and
direct addressing of netmail messages you MUST have the NETMAIL
conference configured, as netmail and/or file sends/requests cannot
be sent from other conferences.
BAD_MSGS - When DFIMPORT comes accross a message for which a conference
has not be configured, one of two things may happen. If you have
a conference called BAD_MSGS configured, the message is placed in
in this conference. If you do NOT have BAD_MSGS configured,
DFIMPORT will write the message to a text file called NOTKNOWN.MSG
located in your Dogfight directory.
Long Messages
=============
Dogfight will import messages up to 500 lines in length.
Messages longer than 500 lines will be trucated to 500 lines and written
to NOTKNOWN.MSG.
EXTERNAL PROGRAM DATA Screen
============================
The information entered here is used by both DFDECOMP to de-compress inbound
mail bundles and DFEXPORT to 'mash' outbound mail (if required).
The programs entered here MUST be accessible via your PATH environment
string.
Please give the FULL program name including the program extension (.EXE or
.COM) and any command line parameters (in upper or lower case as required)
needed for correct execution. In most cases the defaults already shown
will work.
These commands are critical .. incorrect commands will cause stray packets.
(NOTE: If you are using SEA's ARC.EXE to decompress .ARC files, I have had
to 'fiddle' with DFDECOMP as SEA's 'ARC.EXE x' command will not allow
a target directory to be specified. DFDECOMP will unARC the file into
the CURRENT directory, then will use the program specified in option
7 to copy ALL .PKT files from the current directory into your work
directory!)
Option 8) If you are using D'Bridge front end mailer, toggle this option to
true. Option 9 will automatically be set to N (none). Please
remember to run DFDB.EXE after DFEXPORT to create the D'Bridge
files.
Option 9) You can specify whether you want outbound mail to be
compressed and the packing method required (Zip/Arc/Lzh).
Or left as standard .OUT files for an external message masher
to mash (select N (none)).
After making any changes you require enter Q and press return to exit to the
main menu.
After returning to the Main Menu and making any changes you require, enter
Option 5) Quit. You will then be asked whether you wish to save the changes
you have made. Press Y to save.
NOTES ON DFCFG.??? FOR HUB'S
============================
Under normal operation all the DF??????.EXE programs will default to
reading DFCFG.001.
To allow messages to be exported more than once (for HUB's) the following
procedure MUST be followed.
DFCFG.??? files must be created for each net/node you wish to export
messages to. You can either create each file from scratch, or copy DFCFG.001
to DFCFG.002 / DFCFG.003 etc.. then amend the conference data in each
config file.
When amending the conference data:
For each area you wish exported more than once
Amend 'Net to send to' and 'Node' to the net/node you wish the
messages exported to.
Toggle the 'Mark exported messages as sent ? (Y/n)' to 'FALSE'
i.e. select 'N'.
Do this for each DFCFG.??? you create EXCEPT THE LAST ONE.
The last DFCFG.??? *MUST* have all the 'Mark exported messages as sent?'
toggled to TRUE. This will ensure that once all messages are exported to
your various nodes, DFEXPORT will mark the messages as sent.
The export portion of your batch file will then look like this :
CD\DOG
DFEXPORT L DFCFG.001 -| 'Mark exported messages as sent?' toggled to
DFEXPORT L DFCFG.002 |-- FALSE for those conferences to be re-exported.
DFEXPORT L DFCFG.003 |--'Net to send to' and 'Node' amended to the net/
DFEXPORT L DFCFG.004 -| node of the recipient system.
etc..
etc..
DFEXPORT L DFCFG.nnn ---- ALL 'Mark exported as sent?' toggled to TRUE.
NOTE: Dogfight was not intended to be used by a hub system, the above is
only satisfactory when exporting to a non-Dogfight using system, or a
system which will not re-export messages to another system.
Example of multiple DFCFG.??? files:
DFCFG.001 Conference data contains:
Conference 10<->FIDO area AMSTRAD (Exported to 256/97) Mark Sent=TRUE
Conference 11<->FIDO area BBS-NEWS (Exported to 256/97) Mark Sent=FALSE
Conference 12<->FIDO area BUY (Exported to 256/97) Mark Sent=FALSE
Conference 13<->FIDO area COMMS (Exported to 256/97) Mark Sent=FALSE
Conference 14<->FIDO area GAMING (Exported to 256/97) Mark Sent=FALSE
Conference 15<->FIDO area HARDWARE (Exported to 256/97) Mark Sent=FALSE
( Conference 10 is exported to 256/97 ONLY and will NOT be re-exported.
Conferences 11 to 15 are exported to 256/97 and WILL be re-exported.)
DFCFG.002 Conference data contains:
Conference 11<->FIDO area BBS-NEWS (Exported to 256/27) Mark Sent=TRUE
Conference 12<->FIDO area BUY (Exported to 256/27) Mark Sent=FALSE
Conference 13<->FIDO area COMMS (Exported to 256/27) Mark Sent=FALSE
Conference 14<->FIDO area GAMING (Exported to 256/27) Mark Sent=FALSE
Conference 15<->FIDO area HARDWARE (Exported to 256/27) Mark Sent=FALSE
( Conference 11 is re-exported to 256/27 and will NOT be re-exported.
Conferences 12 to 15 are re-exported to 256/27 and WILL be re-exported.)
DFCFG.003 Conference data contains:
Conference 12<->FIDO area BUY (Exported to 256/90) Mark Sent=TRUE
Conference 13<->FIDO area COMMS (Exported to 256/90) Mark Sent=TRUE
Conference 14<->FIDO area GAMING (Exported to 256/90) Mark Sent=TRUE
Conference 15<->FIDO area HARDWARE (Exported to 256/90) Mark Sent=TRUE
( Conferences 12 to 15 are re-exported to 256/90 and will NOT be
re-exported.)
The export portion of the batch file will look like this:
CD\DOG
DFEXPORT L DFCFG.001
DFEXPORT L DFCFG.002
DFEXPORT L DFCFG.003
DFDECOMP
========
DFDECOMP must be ran in the same directory as DFCFG.???
DFDECOMP is a utility that will check you inbound mail directory for
.MO?, .TU?, .WE?, .TH?, .FR?, .SA?, .SU? and .PKT files.
If any files with these extensions are found, DFDECOMP will attempt to
decompress them using the programs you have defined in the External Program
Data screen of the DFCONFIG program.
If the decompression is successful the source file is deleted if Option
14) of the System Data screen of DFCONFIG has been toggled to do so.
In the case of .PKT files, if the file was not compressed in either .ZIP,
.ARC, or .LZH format then the file is copied (using the program defined in
the External Program Data Screen Option 7)) to the target directory.
(This is because .PKT files should not be compressed, however I have
received compressed .PKT files so have added this for that reason.)
For DFDECOMP to work correctly the external programs defined in DFCONFIG
must be accessible through your PATH environment string.
(If not then DFDECOMP will not decompress or delete the file, or in the
case of uncompressed .PKT files, copy the file).
USAGE:
DFDECOMP {source directory} [target directory] [configfile]
{source directory} is obligatory, if [target directory] is not specified
DFDECOMP will decompress the files into the current DOS directory.
If configfile is not specified DFCFG.001 is used.
NetMail
=======
A NetMail message is created by entering a message in your NETMAIL
message conference ONLY. If you have not configured a netmail conference
this option is not available to you.
To address a message to be sent directly to the addressee you enter the
following the SUBJECT: field of your message -
<NM>2:256/97 Which stands for <NetMail>Zone:Net/Node.
Note: If Zone: if not entered the message will default to your zone.
Zone:Net/Node being the FIDO address of the system you wish the message
to be sent directly to.
You MUST leave at least one space after zone:net/node before entering
any text for the remainder of the subject
i.e. '<NM>2:256/97 New Year Party'
File Sends/Requests
===================
A file send or request is created by entering a message in your
NETMAIL FIDO message conference ONLY. If you have not configured a netmail
conference this option is not available to you.
To request a file the following must be entered in the SUBJECT: field
of your message :
<FR>2:256/97 (NO SPACES before or after this, and NO point)
Which stands for <File Request>Zone:Net/Node.
Note: If Zone: if not entered the f'req will default to your zone.
You then enter the files you wish to request in the main body of the message
i.e
NODEDIFF.A??
FILES
etc..etc..
Each file name must start at the beginning of the line, and only 1 per line
is allowed.
File sends are practically identical :
<FS>2:256/97 (Again NO SPACES before or after, and NO point)
Means <File Send>Zone:Net/Node
Note: If Zone: if not entered the send will default to your zone.
The body of your message would then contain the FULL path to each file you
wish to send, 1 file per line.
i.e.
C:\SF\DOCS\ALLFILES.BBS
C:\UTIL\MYPROG.ZIP
etc..etc..
Notes: The To: field can contain anything you wish, as it is not used.
For some reason Spitfire requires that you enter the subject twice
when entering <FS>net/node or <FR>net/node.
NOTE ON ZONE SUPPORT
====================
If a message, f'req or send is entered for a zone other than your own, the
resulting packet is placed into a new directory.
This new directory is based on your 'Path to Outbound Directory' directory
name, plus an extension of the zone.
So, in my case, my 'Outbound Directory' is C:\BINKLEY\OUTBOUND, if I enter
a message to zone 5, it will be placed in C:\BINKLEY\OUTBOUND.005
A message to zone 7 would be placed in C:\BINKLEY\OUTBOUND.007 etc etc
If the relevant directory does not exist, it will be created.
SETTING IT ALL UP (BinkleyTerm)
===============================
All the Dogfight files must be placed in the SAME directory.I would also
recommend creating a work directory that will be used to hold the .PKT files
prior to importing.
I use BinkleyTerm as a front-end mailer and the relevant portions of my
batch file are :
FOR THE EXPORT FUNCTION:
========================
(At 2am BinkleyTerm is configured to poll my hub to pick up any mail -
at 1.55am BinkleyTerm shells to :Exp_Mail)
:Exp_Mail
CD\DOG
DFEXPORT L
CD\BINKLEY
GOTO BT_Start
FOR THE IMPORT FUNCTION:
========================
(BinkleyTerm shells to :Mail_Rec in the event of receiving inbound mail)
:DFIMPORT
CD\DOG
DFDECOMP C:\BINKLEY\INBOUND\ C:\DOG\WORK\
DFIMPORT L
IF EXIST NOTKNOWN.MSG ECHO **** NOTKNOWN Message File Exists!! ****
CD\BINKLEY
GOTO BT_Start
For setting up Dogfight for use with D'Bridge, please see the enclosed
DFDB.DOC file.
Comments, suggestions, problems etc should be sent to me at my home address,
or to Mike Martell at Wolf's Moon BBS.
Thank you for taking the time to try DOGFIGHT.
Index
Acknowledgements ...............................................3
BAD_MSGS ......................................................10
Command Line Parameters ........................................5
Conference Data Screen .........................................9
DFCFG.??? ......................................................5
DFCFG.??? FOR HUB'S ...........................................12
DFCONFIG .......................................................4
DFCONFIG.EXE ...................................................7
DFDB ...........................................................4
DFDECOMP ...................................................4, 14
DFEXPORT .......................................................4
DFEXPORT.INF ...................................................5
DFEXPORT.LOG ...................................................5
DFIMPORT .......................................................4
DFIMPORT.INF ...................................................5
DFIMPORT.LOG ...................................................5
DFRESEND .......................................................4
D'Bridge ......................................................17
External Program Data Screen ..................................11
Features .......................................................6
FIDO Area Name .................................................9
File Sends/Requests ...........................................15
I (Command Line Parameter)......................................5
Introduction ...................................................4
L (Command Line Parameter)......................................5
License Agreement ..............................................2
Long Messages .................................................10
Message Base ...................................................8
NETMAIL ...................................................10, 15
Netmail toggle .................................................4
NOSTRIP (Command Line Parameter)................................5
Origin Line ....................................................8
Outbound Directory .............................................8
PATH: ..........................................................5
Registration ...................................................3
Registration from the United States ............................3
RF (Command Line Parameter).....................................5
SEEN-BY: .......................................................5
Setting it all up (BinkleyTerm) ...............................17
Special Conference Areas ......................................10
Spitfire Conference Number .....................................9
Sysop Name .....................................................7
System Data Screen .............................................7
Work Directory .................................................8
Your HUBS Net ..................................................7
Your HUBS Node .................................................8
Your Net .......................................................7
Your Node ......................................................7
Your Point .....................................................7
Your Zone ......................................................7
Zone Support ..................................................16