🚀 go-pugleaf

In article <DAVE.91Jan5171933@slam.InterLan.COM> dave@interlan.interlan.com writes:
>In article <1991Jan4.231850.24022@maytag.waterloo.edu> dmurdoch@watstat.waterloo.edu (Duncan Murdoch) writes:
>>   Don't use PKLITE 1.03 on the files TPCX.EXE or TD286.EXE that come
>
>The reason for this is simple.  These programs contain overlays.  Think
>about it -- overlays are loaded off the disk as needed.  Unless your
>compressor/decompressor (PKLITE, LZEXE, etc.) hangs around and responds
>to all accesses to that particular file, when an external module is
>required and loaded, it will be loaded in *compressed* form.  Naturally,
>the software will (+poof+) at that point.

No, PKLITE works fine on many (but not all) programs with overlays. It doesn't
attempt to compress the overlay code, so it's not spectacularly effective,
but it does work.  It depends on the assumption that the overlay manager doesn't
care about the length of the .EXE file, it counts back from the end.

This is true about Borland's overlay manager, but it might not be true of
Microsoft's:  one program I've got that was compiled under some version of
MSC complains that it can't find the overlay after PKLITE has compressed it.
It works fine if I just undo the compression.

Duncan Murdoch