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