Excerpted from message dated 10-03-94, David Noon to Jacob Warner:

DN>
  >                   A utility in the toolkit called EXEHDR, when run
  >in verbose mode, will tell you which DLL's are used by a given .EXE,
  >and you simply include just those ones.
  >

Ho, Dave--

    EXEHDR (in verbose mode) will let you figure out which DLLs are
called directly by an EXE, but it is still rather hard to interpret. I
once downloaded a program called CHKDLL32.EXE (file date 3/23/94) from
somewhere (where, I no longer remember), which lists the DLLs called by
the EXE directly, including their path if on LIBPATH.  Unfortunately,
neither EXEHDR nor CHKDLL32 tells you which of the DLLs required by the
EXE require additional DLLs, in turn.  You must use the program on all
the DLLs named the first time, to get the rest.

    For example, the sample PL/I program HELLO.EXE requires (first pass)
IBMR120.DLL (756218 bytes, FAT) and CEER120.DLL (180458 bytes).  But
either of these DLLs also requires CEEM120.DLL (466154 bytes).  I
imagine that if you don't include CEER120.DLL in your package, your
customer is not going to be happy.

    Incidentally, if you have any information on the origin of
CHKDLL32.EXE, I would appreciate knowing about it.  It lives on one of
my diskettes labeled "Downloaded Utilities" with no other
identification.  All I can say is that it seems to work and has never
given me any trouble.  Of course, it might be loading up my INI files
with invisible stuff!

    All the best.

               --Murray

___
 * MR/2 2.1 #120 * The wyse Plato seith: "Have a Good Day"
                                                                      
---