WHEREIS.EXE

by Keith Ledbetter


I know you've seen tons of WHEREIS programs, but I think you'll like this
one. It is around TWICE as fast as any other I've seen. Also, you can
tell WHEREIS to search all .ARC files for a file match, too. For each file
match that is found, you will be shown a "directory-type" listing of:

a. the file size
b. the date of the file
c. the time of the file
d. the full path name
(or .ARC name if it's in an ARC file).


Invoking WHEREIS is simplicity itself. If you do not specify a path,
then WHEREIS will search the entire default drive. If you specify a
starting path, then the search will occur from that path downward (only).


Another nice feature of WHEREIS is the "-a" switch, which tells the
program to search all .ARC files for a match on the filename (the
.ARC files are searched in addition to the normal, un-ARC'ed files).


Here are some command line examples:


whereis ab*.c search entire default drive for any filename
matching "ab*.c".

whereis \turboc\ab*.c search downward from the \turboc\ directory
on the default drive looking for "ab*.c".

whereis d:*.dat -a search entire drive d: and all .ARC files
on drive d: looking for "*.dat".

whereis myprog search entire default drive looking for
"myprog.*" (WHEREIS will append a ".*" to
a filename with no extender specified).

whereis myprog*.c -a search entire drive and all .ARC files for
a match on "myprog*.c".



ONE WORD OF CAUTION.
--------------------

One thing that makes this WHEREIS much faster than most other programs of
this type is that the program "cheats" a little bit when searching for
subdirectories. It does this by doing a search in each directory for
a filename of "*." instead of "*.*". By doing this, the program doesn't
need to weed through tons of "normal" files, since (a) almost all files have
some type of extenders, and (b) nobody makes directories with extensions.

What this means is that if you create a subdirectory named, for example,
"mycode.dir", then WHEREIS ==will not== find any files in that subdirectory.
I can't imagine this being a problem for any but a handful of users; in my
4 years of working with IBM PC's, I've never seen anyone have a directory
named with an extension.

After benchmarking both ways (looking for subdirectories with "*.*" and
"*."), I decided that the BIG speed advantage purely outweighed the
possibility of a directory name having an extension.

I hope you enjoy it. If you need to get in touch with me, I can be
reached at:

CompuServe: 76701,124
GEnie : K.LEDBETTER

Keith Ledbetter