
                        - INFO ON DGi FILE-ECHO SYSTEM -
 ==============================================================================

  	1.0 General Info
		1.1 Hatching criterias
		1.2 Announcing the new release

  	2.0 File-echo processor
		2.1 Fast-Install and hatching with FileMgr
		2.2 Fast-Install and hatching with Allfix
                2.3 Connecting/Disconnecting a file-echo area

	3.0 Closing Words


	1.0 General info

  File-echo system is a part of DGi. It offers you a very powerful and fast 
  way of distributing your group's productions. And vice versa, you will
  receive the hottest productions by the other groups. File-echo system is
  designed for new productions only, files are -1-2 days old and quality.
  Ofcourse, if you don't want file-echos, you're free to disconnect from them.

  DGi file-echo system is not only for demos and intros. For example musics
  and graphics by your group's artists are welcome. You should info your
  group's artists of this unique opportunity of gaining a lot of publicity
  world wide easily.

		1.1 Hatching criterias

  Every DGi node is allowed to hatch as long the stuff fills some simple 
  criterias:

  1) Intros/Demos/DiskMags/Utils must be new, the same day as it released 
     in public or day before (-1/0d). Programming Stuff, Txtfiles, Gfx and
     Musics can be little older as they don't usually spread fast by other
     ways.

  2) Stuff must be of good quality, no crap please.

  3) Stuff must be hatched to the right area. Check out areas.DGi file.

  4) Stuff must be packed with PkZip! No other format packages allowed.

  5) No duplicates - if your group has several boards in DGi, decide
     who does the hatching.

  6) Check the file with major virus scanners before hatching (f-prot,
     mcafee scan, ...) to prevent viruses spreading! Be also sure that 
     the package is not in any other way corrupted.
  
		1.2 Announcing the new release

  It is encouraged that after hatching the stuff to DGi file-echos you
  would announce it in DGi.new_productions message area. It gives your
  product more publicity, people can send bug reports and discuss about
  the release and it also will help other DGi SysOps. Posting the prod's
  file_id.diz to DGi.new_productions is commonly used and very handy.

  Even if you won't hatch the product to DGi for some reason, you're
  welcome to announce it in DGi.new_productions.

  	2.0 Installing a file-echo program
            (pros can skip this)

  If you're just a node, you can receive file-echos without installing
  any file-echo program. However, to forward files to your nodes/points
  and for hatching, you will need to install one. I'll now introduce
  two most commonly used file-echo processors in short, though there 
  are also other good ones around. Anyways, you should read the manual
  for the maximum advantage of the processor.

		2.1 Fast-Install and hatching with 'FileMgr'

  Because of a lot of features, the setup may seem very hard procedure.
  But the basic setup is easy and fast. Just fill the "System Info" with
  care. Especially remember the right paths, eg. make a new directory for 
  'outgoing files'. Next step would be the "Group Manager", install DGi
  group. Then move to "Area Manager", which is the core of the program.
  Enter the file-echo area names, seen-by's and export-list just like in
  a message-echo processor. Next and last step for basic installation
  is the "Node Manager" like in message-echo processors. Now you should
  be ready to hatch without probs. Enter 'filemgr hatch' from the dos
  prompt, fill the file info and let FileMGR to hatch it. Afterwards you
  should see a ".TIC" and the file itself in the 'outgoing files' dir and
  a file-attach message in the netmail folder. If the paths and status
  are right (eg. not 'hold' status if a node) you have succeeded. If any
  problems occurs, ask your Hub/Host for help, or read the manual..

		2.2 Fast-Install and hatching with 'AllFix'
                    (written by Zteel)

  Start ASETUP.EXE - Go into the System Data entry, and edit the
  following: System AKA, setup your DGi address here. Group Names,
  make a group called DemoGroups Interchange or alike. Now, go to
  the main menu, choose the entry called Node Manager. Here you make
  a new entry; System is your uplinks DGi address; Sysop is your uplinks
  name, as in the nodelist; File echo pwd and Areamgr Pwd is the
  passwords arranged between you and your uplink; Authorized groups
  should be DemoGroups Interchange (as entered in the System Date) and
  choose to use your DGi AKA. The last questions should be obvious, as
  the are like any other mailtosser available for HMB and alike. Now you
  should set up the conferences. Go to the main menu, enter the File
  Echo Manager field. Make a new entry. Name: DGI_SYSTEM, Comment: DGi
  Nodelists, Dest: C:\DGI\SYSTEM\ (or choose your own path), Area#:
  what BBS filearea to update when newfiles arrives, Group#: Choose
  the DGi Group, Use AKA: Your DGi Address, Keep#: Max Number of files
  to keep, Message Announcement: What file to include in netmail
  announcements (not needed), then choose the options which you find
  suitable for your system. The last thing is the connections. They are
  vital. Make a new entry, choose SYSOP; then you can browse the Entries
  in the Node Manager. Now choose your DGi uplink. Choose send mode as
  BOTH, so you can recieve and send files to/from your uplink.

  If you have followed the above, you should have the most basic AllFix
  system, which is ready to recieve files from DGi. AllFix is a very
  complex and huge program. It might scare some people off to easier
  programs, but when you first have understood the main idea behind it,
  it really is a great program. If you want any help setting it up, please
  feel free to write to Rene Christensen in the DGi Sysops area, or send
  me a netmail at 68:450/0 or simply call my board and we'll have a chat.

		2.3 Connecting/Disconnecting a file-echo area

  It's easy to change the status of the file-echo areas you're entitled
  to collect from your host/hub. This can be handy, if you eg. want the
  control the file kb flow. You just have to send a netmail message to
  your host/hub's file-echo prosessor (filemgr, allfix ...)
  ----------------------------------------------------------------------
  from   : You, 68:???/???                                (your address)
  to     : FileMgr, 68:???/???                  (your host/hubs address)
  subject: PASSWORD                 (if your host/hub has installed one)
  ----------------------------------------------------------------------
  +DGI_DEMOS                                         (connects the area)
  -DGI_DEMOS                                      (disconnects the area)
  %help                      (gives you help on all available functions)

  If you encounter any problems, ask your host/hub for help.

	  3.0 Closing Words

  If you're able to hatch your group's productions when released: do it. 
  Or ask your hub/host to do it for you. It's definitely worth it. It's
  not only for your own benefit, but it also makes the scene better as the
  productions are easy to obtain and discuss about.

--
signed,
crack/extreme