|
|
1.1 root 1: LIBWHERE searches along LIBPATH for filenames matching the specification on
2: the command line. If LIBPATH were an environment variable, the WHERE utility
3: could be used to search along it for the desired files. Since this is not
4: the case, LIBWHERE must look in the appropriate CONFIG.SYS file and extract
5: the path following the string "libpath=". LIBWHERE then creates an
6: environment variable with this path and invokes WHERE to search along it. The
7: path is easy to find in protect mode, since OS/2 knows which is the boot
8: device and can look in the root directory for CONFIG.SYS. If LIBWHERE is run
9: in real mode or if you wish to examine a different CONFIG.SYS, you must
10: specify which CONFIG.SYS you wish to use with the /c switch.
11:
12: Informative messages are sent to STDERR, while the list of filenames is sent
13: to STDOUT. This means that the list of filenames can be redirected to other
14: programs which take a list of filenames from STDIN (eg. EXEHDR).
15:
16: Examples:
17:
18: LIBWHERE *.dll
19:
20: Works in protect mode to find all filenames with a .dll extension in the
21: directories listed in the LIBPATH set in the CONFIG.SYS file in the root
22: directory of the boot device.
23:
24: LIBWHERE *.dll | EXEHDR -
25:
26: Finds the files *.dll as in the previous example and feeds them to EXEHDR
27: for analysis.
28:
29: LIBWHERE /c c:\config.sys *.dll
30:
31: In either protect or real mode, find all filenames with a .dll extension
32: 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.