fds-cp v0.4a
ÍÍÍÍÍÍÍÍÍÍÍÍ

yew....

this is my simple .COM cryptor :)

nothing much to say about it, other than lamers will not be able
to break through it, but any good cracker can trace through it
easily.... well, there is nothing what good crackers cannot break ;)
and don't yell me that it's too easy to break.. everything is!
you can't make really hard anti-unpacking/debugging code without
eliminating compatibility with nearly every operating system and
memory managers... I don't think you would like to reboot to pure
dos without any memory managers to run a protected file.

features:
ÄÄÄÄÄÄÄÄÄ
- can handle only .COM files smaller than 50000 bytes
- multiple layer encryption
- various anti-debug tricks
- full real mode anti-debug
  (int 1 self-tracing, int 3, int 0, int 4 (into)...)
- lame playing with DRx registers
- anti-Soft-ICE
- semi-random encryption keys
- anti-CUP386
- calculates and checks a checksum over the encrypted code

the protected files were tested and worked (for me) under:

  þ MS-DOS 6.22 (with EMM386 and without EMM386)
  þ Caldera OpenDOS 7.01 (with EMM386 and without EMM386)
  þ Windows 95 (with EMM386 and without EMM386)
  þ Windows NT

this is v0.4a what means this is a really first version, without any really
advanced things..

new stuff to come soon:

- EXE support
- mutation engine
- merging FDS-CP into PCU (my comunpacker with a nize shell)

tested with the following unpackers:
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

Note: There should be no need to test FDS-CP against not generic unpackers
like X-TRACT... Of course they cannot unpack it.

  FDS-UNP v1.1a               cannot detect and unpack this version
  CUP386 v3.2 /1              saves garbage
  CUP386 v3.2 /3              locks up the system
  CUP386 v3.2 /7              locks up the system
  UNP 4.11 /t                 locks up the system
  Intruder v1.30              saves garbage
  UPC v1.04, v1.05, v1.06.3   reboots the system
  UNCOM by ka0t

notes about special unpackers:
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  Memory dumpers:   Mem dumpers like MegaDevil's lame com unpacker will work
                    if you don't erase the program code from the
                    memory before exiting. So just don't forget to overwrite
                    the code in the memory before returning to DOS, otherwise
                    every lamer can unpack your poor code.

known fds-cp unpackers:
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
  - the first and only winner is -=ðDaRkúsTAlKeR 97ð=- [UCF]
    with his FdS-CRP Unpacker v1.0a..

    notes to DStalker:

        * it's not FdS-CRP.. it's FDS-CP ;-))
        * fds-unp is very nice :)
        * but the detection is ugly a bit. it is allowed to remove or
          modify that end signature freely, thus fds-unp will fail
          to detect it ;(
        * fds-unp v1.0a can't unpack FDS-CP v0.2 or later :(    (or :-))

    yeah! DStalker released fds-unp v1.1a! It can unpack v0.4. It cannot
    unpack v0.4a, the only news in this version is that I fixed DStalker's
    backdoor.

greetz
ÄÄÄÄÄÄ
no greetings here.. you gotta be enough good to unpack FDS-CP and read
the greetings inside ;)

i hate writing dox, so here's the end,
  - fds0ft -

e-mail: fdsoft@mail.gyor-ph.hu