Xref: news2.mv.net comp.os.msdos.djgpp:4863
From: stwand07 AT uctvms DOT uct DOT ac DOT za
Newsgroups: comp.os.msdos.djgpp
Subject: Re: DJP info (Why are they so fat?)
Date: 11 Jun 96 19:13:21 +0200
Organization: University of Cape Town
Lines: 16
Message-ID: <1996Jun11.191322@uctvms.uct.ac.za>
References: <29C186D7EED AT fs2 DOT mt DOT umist DOT ac DOT uk> <4pk0ea$q12 AT rs18 DOT hrz DOT th-darmstadt DOT de>
NNTP-Posting-Host: uctvms.uct.ac.za
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

In article <4pk0ea$q12 AT rs18 DOT hrz DOT th-darmstadt DOT de>, lehmann AT mathematik DOT th-darmstadt DOT de (Alexander Lehmann) writes:
> BTW, I haven't used it, but I would expect DJP to work similar to
> pklite, diet and all the other exe compressors, the executable is
> decompressed and loaded into memory at startup, so the user will not
> notice any difference (except maybe a minor delay).

Here's a quick note about DJP :
It functions exactly as PKLite, Diet, etc. so expansion of the EXE is done
automatically at run-time. It is available from the Simtel FTP site and its
mirrors, in the vendors/djgpp/v2.. subtree (I think it's in v2misc).

That should bury this "Size of EXE" thread... (DJP should be mentioned in the
FAQ, I think).

Adios
Mark Wodrich.