ÚÄÂÂÄ¿ Ú¿  ¿ ÚÂÄÄ¿  ÚÂÄÄ¿ ÚÂÄÄ¿ ÚÂÄÄ¿ ÚÂÄÄ¿ Ú¿ ÚÄ ÚÂÄÄ¿ ÚÄÂÂÄ¿ ÚÂÄÄ¿ ÚÂÄÄ¿
   ô   ÃÅÄÄ´ ÃÅÄ    ô    ÃÅÄÂÙ ÃÅÄÄ´ ô    ÃÅÄÁ¿ ÀÁÄ¿   ô   ô  ³ ÃÅÄÄÙ
   ÀÙ   ÀÙ  Ù ÀÁÄÄÙ  ÀÁÄÄÙ ÀÙ À  ÀÙ  Ù ÀÁÄÄÙ ÀÙ  À ÀÄÄÁÙ   ÀÙ   ÀÁÄÄÙ ÀÙ
                ÚÂÄÄ¿ ÚÂÄÄ¿ ÚÂÄÂÄ¿ ÚÂÄÄ¿ Ú¿  ¿ ÚÂÄÄ¿ ÚÂÄÄ¿
                ÃÅÄÂÙ ÃÅÄ   ô ³ ³ ô  ³ À´  ³ ÃÅÄ   ÃÅÄÂÙ
                ÀÙ À  ÀÁÄÄÙ ÀÙ Ù Ù ÀÁÄÄÙ  ÀÄÄÙ ÀÁÄÄÙ ÀÙ À  1.1


 ÄÄ[1]ÄÄ[ABOUT THIS UNPACKER]ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

 THE CRACKSTOP REMOVER is able to unpack nearly *every* single file protected
 with CrackStop, both registered and shareware version are handled.
 The unpacked file will be byte-by-byte 100% the same as the file was
 before protecting it with CrackStop, only when a regged version was unpacked
 there are a few more bytes than actually needed at the end of the file but
 this doesn't affect the working of the file anyway.
 The current version has now the feature to also unpack files larger than
 the 65 KB limit. I successfully tested files with a size of up to 0.5 MB.

 ÄÄ[2]ÄÄ[UNPACKING ENGINE]ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

 CSR uses hardware breakpoints (DRx) to unpack nearly every CS version
 existing. Windows versions in the background of CSR are not allowed, which
 means you'll have to boot to DOS in order to unpack.
 The last version of CSR used 2 hardware breakpoints in order to bypass
 CrackStop, the weak point of it was, that it was based on direct adress
 breakpoints. If the offsets were wrong (in regged versions...) the unpacker
 failed to unpack the file. This time a much more powerful method was used
 to 1. bypass the 386+ code, 2. run all decryptors and 3. get the original
 filesize. This is done with a total ammount of 6 breaks using two
 breakpoint handlers from which 2 major breakpoints are neccassary for doing
 the proper unpacking.

 ÄÄ[3]ÄÄ[COMING NEXT]ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

 þ I will only release a new CSR version if there are big bugs in CSR 1.1
 þ An unpacker for HS 1.xx
 þ Maybe I'll also write a Mess 1.2? remover if this is in my might
 þ -> Send me unpacker requests

 Please notice that my free-time will be very limited in the next months and
 that I've anyway planned to reduce the time I spend with my computer... :)


 ÄÄ[4]ÄÄ[ABOUT CRACKSTOP]ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

 CS is a 8086+ based .EXE protector without relocation handling. There are
 many people speaking of "just another lame HS-rip" and Rose makes fool of
 it in his intros. The facts are that design (docs, logos..) looks very
 similar to the one of HS, CS also includes this lame nebelbombs to irritate
 disasembling (I really don't want to tell you again what I think of this
 crap :) and the general idea behind executable file protection is the same
 as Rose expressed in his docs : "My protector is nearly unbreakable..."
 Of course, every protection which still remains executable isn't that hard
 to break for sure.
 But if we take a closer look at the main program (CS itself) we can see that
 CS is of course not just a HS-rip.
 The major reason of why to choose CS and not HS is the one that CS includes
 EXE entrypoint fakes to fool CUP386 and other generic unpackers. This is
 weakest point of HS - it can be unpacked with CUP386 /3. ;)
 The big security hole CS has, is of course that there are so less
 386+ instructions and anti debugging code.

 ÄÄ[5]ÄÄ[CONTACTING CHRiSTOPH]ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

 Email : ChristophG1@Hotmail.Com
 Url   : www.thepentagon.com/trap
 IRC   : Nick: CHRiSTOPH

 ÄÄ[6]ÄÄ[GREETINGS]ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

 Stefan Esser (Author of CS), What do you say about the current CSR version?
 Ka0t (Author of UNCS), See you on Silvester 1999? Or at least on IRC. :)
 MantiC0re, For sending the DeTRAP's to the exelist.
 Vladimir G., For the DeTRAP's.
 Roy, Hope you won't get bored in Switzerland.
 Rose, I'll start the HS unpacker tommorow. So be warned. ;)
 Mad Scientiest, What is MSCC doing?
 Stone, Your homepage rules!
 LiuTaoTao, If TR would not exist, CSR 1.1 would not exist either for sure,
           I did all the major debugging of CS with it.
 Lado, LTR was *very* helpful too in testing the breakpoints and eliminating
       the many bugs CSR had in its alpha versions.
 Exelist, Everyone who sent me CS versions I did not have and everyone else!

[30.04.1999]