EXECUTABLE FILES PROTECTOR

       ÛÛÛÛÛÛÛ ÛÛ   ÛÛ ÛÛÛÛÛÛÛ ÜÛÛÛÛÛÜ ÛÛ   ÛÛ ÜÛÛÛÛÛÜ ÛÛÛÛÛÛÜ ÛÛÛÛÛÛÜ
       ÛÛ      ßÛÜÜÜÛß ÛÛ      ÛÛ      ÛÛ   ÛÛ ÛÛÜÜÜÛÛ ÛÛÜÜÜÛÛ ÛÛ   ÛÛ
       ÛÛßßß    ÛßßßÛ  ÛÛßßß   ÛÛ ßßÛÛ ÛÛ   ÛÛ ÛÛßßßÛÛ ÛÛßßßÛß ÛÛ   ÛÛ
       ÛÛÛÛÛÛÛ ÛÛ   ÛÛ ÛÛÛÛÛÛÛ ßÛÛÛÛÛß ßÛÛÛÛÛß ÛÛ   ÛÛ ÛÛ   ÛÛ ÛÛÛÛÛÛß

                               Version 1.3.

                   Copyright (C) 1996-97 by Ivanov Vadim

                               USER MANUAL

      ÄÍÍ[ 1  EXEGUARD ver 1.3 ]ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÄ

      1.1 Intruduction.
      ----------------
      EXEGUARD  protects  EXE  files  against hacking,  analysis and
      unpacking. EXEGUARD uses a variety of different anti-debugging
      tricks to prevent hacking of your programs.

      EXEGUARD is FREEWARE.You can therefore use,copy and distribute
      it freely.  You can also utilize it commercially, i.e. you can
      use  it  on programs you intend to sell.  However, the sale of
      EXEGUARD itself and any modifications are forbidden.


      1.2 How To Use ExeGuard?
      ------------------------
      The command-line syntax for ExeGuard is the following:

                  EXEGUARD  [/NB]  < filename.EXE >
                    ( WildCards are not available )

                 Option  /NB - Dont Create BAK Files

 
      1.3. How Does It Works ?
      ------------------------
      ExeGuard adds some piece of code at the end of your program. If you
      ever  have  programmed in assembler  you will know that even 1KB of
      anti-debugger code is a lot of stuff to trace through! :-)

      I suggest  first to compress your program with your favourite com-
      pressor and  then protect it with ExeGuard.

      ExeGuard will only protect  "EXE" files ( in this version ) !
      If you want to protect COM file - convert it to EXE.

      Please note  that a  file cannot be expanded after being protected
      with ExeGuard. So please preserve a backup file until you are sure
      that the  protected file  runs correctly.  Some  incompatibilities
      may possibly arise  with  certain files, especially  with overlaid
      EXE programs.


      1.4 Files That Can't Be Protected with ExeGuard
      -----------------------------------------------
      Windows and OS/2 files cannot be protected by ExeGuard. Also - due
      to  the  structure of  ExeGuard - files  larger  than  the 600  KB
      neighbourhood  cannot be ExeGuarded  because  the entire  file has
      to be able to fit in the  memory once  when it  loads.


      ÄÍÍ[  2 TECHNICAL NOTES  ]ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÄ

      2.1 Requirements
      ----------------
      The requirements to run ExeGuard are:
      DOS 3.30, an IBM PC with 128 KB, etc...
        ( isn't this FUN ??? )
   

      2.2 About ExeGuard
      ------------------
      ExeGuard is written in BP 7.0 + TASM 4.0.  I have tested ExeGuard
      on my 486 DX2/66 and many machines with different DOS versions.


      ÄÍÍ[  3 IN CLOSING  ]ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÄ

      3.1 Disclaimer
      --------------
      I have no responsbility for any damages caused by using of EXEGUARD.
         IF (You Disagree) THEN (Please Remove This Software Now).


      3.2 Epilogue
      ------------
      "EXEGUARD is not unhackable  (like ANY other :-).
       If  you  want to improve your protection against
       unpacking - try to modify  Start up code of your
       High-Level language ( C,PASCAL,.. )"


      3.3  Enhancements In Future Versions
      ------------------------------------
                þ    80386 anti debugger code.
                þ    More traps and different debugging macros.

                     -=  HAPPY EXEGUARD'ing !!!   =-

                                            Sorry for bad English :-)