Return to libwhere.txt CVS log

Up to [OS/2 SDKs] / os2sdk / os2doc

Microsoft OS/2 SDK 12-15-1987

LIBWHERE searches along LIBPATH for filenames matching the specification on
the command line. If LIBPATH were an environment variable, the WHERE utility
could be used to search along it for the desired files.  Since this is not
the case, LIBWHERE must look in the appropriate CONFIG.SYS file and extract
the path following the string "libpath=". LIBWHERE then creates an
environment variable with this path and invokes WHERE to search along it. The
path is easy to find in protect mode, since OS/2 knows which is the boot
device and can look in the root directory for CONFIG.SYS.  If LIBWHERE is run
in real mode or if you wish to examine a different CONFIG.SYS, you must
specify which CONFIG.SYS you wish to use with the /c switch.

Informative messages are sent to STDERR, while the list of filenames is sent
to STDOUT.  This means that the list of filenames can be redirected to other
programs which take a list of filenames from STDIN (eg. EXEHDR).

Examples:

LIBWHERE *.dll

    Works in protect mode to find all filenames with a .dll extension in the
    directories listed in the LIBPATH set in the CONFIG.SYS file in the root
    directory of the boot device.

LIBWHERE *.dll | EXEHDR -

    Finds the files *.dll as in the previous example and feeds them to EXEHDR
    for analysis.

LIBWHERE /c c:\config.sys *.dll

    In either protect or real mode, find all filenames with a .dll extension
    in the directories listed in the LIBPATH set in c:\config.sys.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.