       Ŀ
        ECF_FDN: The *NEW* Ezycom File Distribution Network 
       

ͻ
 WHO ARE WE? 
ͼ

The Ezycom FDN grew from a need for an organized system for distributing
the Ezycom BBS programs and Utilities. The Ezycom files were being sent out
via EzyNet, not everyone was able to get the files due to the geographic
restrictions of the U.S.A, Australia, and Europe! By starting and maintaining
the Ezycom FDN, the files are available to all sysops in general. This will
greatly increase the access to all the latest Ezycom BBS programs and utilities.

ͻ
 HOW IT WORKS 
ͼ

ECF_FDN is listed on both the FIDO filebone and IFDC filegate. Files are
submitted to the filegate only.

The Fido filebone is an echo system for files, that works much like Fido
echomail for message areas.  Files are sent to hubs, who send them to
downlinks, etc.  File echos are carried on Planet Connect, and most of
them are stored on the Internet at ftp.fidonet.org.

The IFDC Filegate Project is also an echo system for files. Filegate
files pretty much follow the same paths as do the Filebone and will
normally arrive through your echomail feed. File echos are carried
on Planet Connect, and most of them are stored on the Internet at
ftp.filegate.net.

Files are sent with .TIC files, which may optionally be used by the
receiving system to toss the files into BBS File Areas.  You do NOT
have to have TICK installed to receive the files, however!  You are
free to manually move the files and just delete the .TIC files.


ͻ
 HOW TO GET A FEED 
ͼ

Fido Sysops who wish to obtain a filebone feed should either obtain a
copy of FILEBONE.NA and contact one of the filebone hubs named at the
bottom, or netmail me at 1:114/635 and I will try to help you out.

Non-FIDO sysops may need to work out an arrangement with their mail/file
uplink to get access. If this cannot be done, email me at the address
below and we both can try to get things resolved. :)


ͻ
 TICK PROCESSORS 
ͼ

Any program that can process a *.tic file is useful, but if you need/want
an Ezycom compatable TIC processor then I recommend EZYTICIT. You can get
it using one of the following methods:

Freq the file from 1:114/635 with the magic name EZYTICIT
or email a request through trav_ler@tds.net
(allow at least 24 hrs for a response. sometimes I sleep. :)

Via the Internet: http://members.netunltd.com.au/users/panda,
homepage of Stephen Gibbs, EZYTICIT's author.

Via anonymous FTP at: ezycom.sytes.net, path to: EZYCOM/EZYUTILS
filename ETI_V2*.EXE


ͻ
 RECEIVING EZYCOM FILES 
ͼ

Once you have a filebone feed established, be sure to ALLFIX (or whatever
your hub uses) for ECF_REL for the Ezycom BBS Program Files and ECF_UTIL for
the Ezycom utility files, developed by third party authors. The files will
then start coming to your system when they are received by your hub (or your
hub may ask you to poll for them).

As I said, a .TIC file will accompany each file as a convenience to you.
You can use them or delete them.

If you run a TICK processor at your site, be sure to set REPLACE to active
in the Ezycom file echos.  New versions of programs, corrected versions of
Ezycom Release/Utilities may make it necessary to re-send a file or one
with the same name.


ͻ
 SENDING FILES 
ͼ

The filebone requires one node to be the Headquarters of each FDN.  That
is me, Patrick Vittori at 1:114/635. If you or your users have files
you'd like to have sent out over the filebone, they need to be sent to
me through ECF_UPLINK. If you plan on sending in submissions then
connect to this echo!

Please, do not send programs/utilities that are not compatable with Ezycom,
are commercial software, or something that you do NOT have the author's
permission to send. *I* would probably like your recipe files if they work
with Meal-Master, but the people down line might get a bit confused.
(If you -do- have recipes, I can be reached at the email address below. <G>)

An alternative would be for you to netmail or email file attach (f'attach)
the file(s) to me with a note that you want them hatched (sent) into the
Ezycom filebone feed.

It is desirable that any uplinked files have an internal description file
(file_id.diz), but not mandatory. This just gives the receiving nodes a
better description of what the file is used for and can be a LOT bigger
than the short description inside of the .tic file that accompanies the
programs you send in.

Files submitted through ECF_UPLINK must have a .TIC file to be processed
properly.

PLEASE, do not hatch files into the ECF_REL or ECF_UTIL echos yourself
as they will bounce!!


ͻ
 HOW TO CONTACT ME 
ͼ

email: trav_ler@tds.net.

Address netmails to Patrick Vittori:

For Fidonet systems send netmail via

The Shaman's Inn
1-928-927-6254
FIDO 1:114/635

Non-FIDO systems can reach me through one of the following nets:

JustaXnet:    510:441/3
ZeNet:        92:602/103
AEONet:       93:93/0
              93:15/0

ͻ
 AREAS AVAILABLE 
ͼ

Here are the current areas as defined in FILEBONE.NA.

                        FDN: Ezycom Network - Ezycom BBS and Utility Releases
               Headquarters: Patrick Vittori, 1:114/635
                  Info File: ECF_FDN.ZIP
       Backbone Conferences: EC_SUPPORT and EC_UTIL
        Related Conferences:
             Planet Connect: Yes
                   Internet: Yes

Area ECF_REL     0     !      ECF: Official releases of Ezycom BBS files
Area ECF_UTIL    0     !      ECF: Ezycom BBS 3rd party utilities
Area ECF_UPLINK  0     *&     ECF: 3rd Party utility uploads to ECFHQ 1:114/635



Here are the current areas as defined in FILEGATE.zxx:


 FDN:          EZYCOM FDN
 Coordinator:  Patrick Vittori, 1:114/635 (trav_ler@tds.net)
 DIST:         PC   PAO  FB
               Yes  Yes  Yes
 PATH: 1:114/635
 HUB: No
 Backbone conferences: EC_SUPPORT and EC_UTIL
 Info File: ECF_FDN.ZIP

 Fileecho                    Description
 -------------------------------------------------------------------------
 Area ECF_REL     0     !      ECF: EzyCom Files
 Area ECF_UTIL    0     !      ECF: EzyCom 3rd Party releases
 Area ECF_UPLINK  0     *&     ECF: 3rd Party utility uploads to ECFHQ 1:114/635


ͻ
 ECHO DESCRIPTIONS 
ͼ

Ŀ
 ECF_REL - ECF: EzyCom Files 


These files are releases from the Ezycom Beta Team. The only files allowed
in this area are certified releases FROM the Beta Team programmers.

Support for these programs can be recieved through the FIDO backbone echo
EC_SUPPORT.


Ŀ
 ECF_UTIL - ECF: EzyCom 3rd Party releases 


These are programs written that work directly with the Ezycom BBS System.
Other programs that can be used with Ezycom are to be distributed through
their respective FDN echos. If the program is NOT available through the
filebone/filegate, contact me about upload procedures -before- sending
a copy through the echo listed below.

Support for these programs can be recieved through the FIDO backbone echo
EC_UTIL.


Ŀ
 ECF_UPLINK - ECF: 3rd Party utility uploads to ECFHQ 1:114/635 


This is the ONLY path allowed for submissions of 3rd Party utilities.
All submissions will be received at 1:114/635, virus checked, checked
for usability with Ezycom, and then uploaded to the filegate distribution
network.


If you are a new/long time Ezycom utility programmer it is highly advised
that you areafix EC_SUPPORT and EC_UTIL. In EC_SUPPORT you will get to
know the Sysops who use Ezycom. EC_UTIL is where the Sysops get to know
-you- and is designed as a place for you as the author to gain feedback
on the operation of your program and provide help to those who need it.



ͻ
 NOTES 
ͼ

1. Ezycom is (C) Copyright 1991-2002 by Peter Davies.

2. Any typographical errors are not intended nor are they
   the fault of my computer. They appear because I type with
   the keyboard on my lap. :)

