🚀 go-pugleaf

In article <2364@lee.SEAS.UCLA.EDU>, yee@edison.seas.ucla.edu (John Yee) writes:
> Under some circumstances, running some programs (those compiled by
> a Microsoft compiler), we get the message "Packed file is corrupt"
> (or something like that) and we found using NU that the msg comes
> from within the .exe file itself.  Our machine is a noname 486,
> and one of the ways we can get this to happen is to boot from a floppy.
> If we boot from the HD, the programs seem to run OK---sometimes.
> In both cases the program we are trying to run is stored on the HD.

There is an option in the Microsoft linker to build an executable file that
is compressed in a fairly simple minded way. The linker includes code to
unpack the file at runtime. The message comes from the unpacking code.

I believe that the unpacking code is slightly buggy - it won't work if the
program is loaded at certain memory addresses (probably near 64K boundaries).
You can solve this by altering the BUFFERS= statement in CONFIG.SYS to
change the size of resident DOS and move the program a bit. Just alter the
number by 1 either way until it loads OK (reboot after each change, of
course).

A program does exist to unpack packed files. It's bundled with one of the
other executable file compression utilities - LZEXE. It's there so that
you can undo the MS packing and apply something better.
-------------------------+-------------------------------------------------
Bob Eager                | University of Kent at Canterbury
                         | +44 227 764000 ext 7589
-------------------------+-------------------------------------------------