ÚÄÄÄ¿                                                  ÚÄÄÄ¿
          ³ ÚÄ´ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄijĿ ³
          ÀÄÃÄÙ                                                  ÀÄÃÄÙ
            ³                                                      ³
            ³      Û           ÜÛ         Û   Û            ÛÛßßßÛ  ³
            ³     Ûß  Û    Û   Û   Û  Û  Ûß ÜÜÛÜÜÜ ÜÛÛÛÛÜ  Û    Û  ³
            ³    Ûß   Û    Û  ÛÛ   Û Û  Ûß    ÛÝ   Û    ÛÝ ÛÛÜÜÜÛ  ³
            ³    Û    Û    Û  ÛÛ   ÛÛ   Û     ÛÝ   Û    ÛÝ ÛÝ      ³
            ³     Û   ßÛ   Û  ÛÛ   Û Û   Û    ÛÝ   Û    ÛÝ Û       ³
            ³      Û   ßÛ  Û   Û   Û  Û   Û   Û    ßÛÛÛÛß  Û       ³
            ³    ÛÛß    ßÛÛß   ßÛ       ÛÛß                        ³
            ³                                                      ³
          ÚÄÃÄ¿                                                  ÚÄÃÄ¿
          ³ ÀÄ´ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ[’. KA0T]ÄÄÄÄÄÄ´ÄÙ ³
          ÀÄÄÄÙ                                                  ÀÄÄÄÙ



ÄÍ Introduction ÍÄ

   I am sorry for my bad english, I am only a lame german :)
   SuckStop is called a protector, a program which encrypts EXE-files
   remaining them executable. I, the author of SUCKSTOP, thought that
   there's missing a protector like SUCKSTOP. First it was only used
   for internal purposes, but then I decided to make it public. The
   first tries of SUCKSTOP (v0.1á - v1.05) were bad. They had good
   antidebugging tricks in them, but they were too incompatible so they
   ran only on my machine :) and on some few other ones. SUCKSTOP is not
   secure against generic unpacker because I thought writing/using an
   generic unpacker is easy but to crack SUCKSTOP by your own will be a
   challenge.


ÄÍ Disclaimer ÍÄ

   The author is NOT responsible for any damage caused by SUCKSTOP. In
   case SUCKSTOP fucks your girlfriend do not claim you have not been
   warned :)


ÄÍ Usage ÍÄ

   I think it is easy to handle SUCKSTOP. Just type SS [FILENAME.EXT] and
   SUCKSTOP will try to protect it. In case it has overlays or it is a COM
   file you will get an error message. If it is a COM file just use the
   tool COM2EXE which is part of suckstop to convert COM files into EXE format


ÄÍ Technical notes ÍÄ

   SUCKSTOP will need a CPU +386 because it uses some 386-opcodes.
   SUCKSTOP is able to protect real EXE files. COM files are not yet included.
   I think it is difficult to bypass SUCKSTOP with a debugger like TD or
   WIN- / SOFTICE. Sure, it can be bypassed by several generic unpackers. I
   did not have the time to test all ones on SUCKSTOP. CUP 3.2, AUTOHACK,
   INTRUDER, XPACK -UX, UPC 1.05 and SNAPSHOT could not unpack SUCKSTOP when 
   I testet them. More anti general unpacker code will be added later. First 
   the mainthing is that SUCKSTOP works on all machines and is safe against 
   debuggers. Try to write a generic unpacker for SUCKSTOP and let me know 
   about it, or just release it. In the way of time I will get it :)


ÄÍ Personal greetings ÍÄ

   rAND0M         -      Thanx for some tips
   GHOSTBUSTER    -      Anti debugging tricks
   Marquis        -      Random's FAQ rulz :)
   +All from UCF
   R0SE           -      write an unpacker for SS!
   All people from
   #cracking,
   #UCF96         -      Thanx for your great help in testing SUCKSTOP!
   PSA            -      Lemme see your S-ice patches