____   __   __                 __  __               __
        / __ \ / /  /_/                / / / /              / /__
       / /_/ // /  __   ______ ______ / /_/ /______ ______ / // /
      / __  // /  / /  / __  // ____// __  // __  // ____// _  /
     / / / // /_ / /_ / __  /_\__  // / / // __  // /___ / /| |
    /_/ /_//___//___//_/ /_//_____//_/ /_//_/ /_//_____//_/ |_|
                     By: Jay Ruyle    Version: 1.5


Intro:
    Do you have a message area or an Echo that allows the use of Alias's?
Aren't you tired of waiting for DLG 2.0 to come around which might have
this feature?  Well I have the perfect fix for that.  Contained withen
are instructions on how to setup and install AliasHack (easy as anything).

Installation:
    1.Copy AliasHack from the archive to DLG:
    2.Copy AliasHack.batch to DLGConfig:Batch/AliasHack
    3.Edit any of your Message areas you wish to change to the following:

        [6]      Signature area: No
        [11] Message translator: AliasHack

    4.You can delete everything else contained in this archive, or store
      it.

Companion:
    AliasLink   - If there is a message written to "Alias#1" which is Joe
                  Smoe, then AliasLink will properly update that users
                  WaitingMail.Dat file
    WipeWait    - When finished will check the users WaitingMail.Dat for
                  Alias messages, checks if the message was read, and if so
                  remove it from WaitingMail.Dat, if not then leave it.
    AliasIndexer- Compiles a index listing of Alias Names to Real Names
                  which is alphabetically sorted by Alias' names.
                  *** AliasLink, and ALLookUp require this index!!! ***
Other Products:
    ALLookUp    - Allows [Co]Sysop to type in a Alias Name, and if found
                  in the index created by AliasIndexer return the persons
                  real name.  Not a good idea to give to normal users, just
                  Sysops, Co-Sysops, SubOps, etc...
    FDEdit      - Same as AliasLink, but for File Areas.


Legal:
    Why do programs not written to destroy computers, sometime destroy
computers, hard drives, memory?  You got me too.  But like everyone else
I dont want to get sued, so:  Any harm this or any of my programs may cuase
in any fasion whatsoever, including physically or emotionally, I will
accept "NO RESPOSIBILITY!"  But I will try to correct any problems with
my program that may have cuased the problem, if not I will issue a warning
in DLGChat of the problem.

Contact:
    FidoNET :  1:377/31.0 (Please use the Fido Address if you can)
    AMIGANET: 40:707/10.0
    Data/Fax: 1-813-254-7493 (Fax part may or may not work)

    Jay Ruyle
    2728 Jetton Ave.
    Tampa, FL  33629