Contents of the CDIR.DOC file
CDIR -- A Cascading DIRectory for Networks and hard drives.
Russel Havens 7-24-90
This little utility recurses ('cascades') through subdirectories and
displays all files matching the command line argument.
I have included CDIR.COM, which uses DIRECT screen writes for speed,
as well as BW_CDIR.COM, which uses bios screen writes for compatibility
with the CTTY command and non-standard video adapters. If you don't know
what I'm talking about, you probably won't need BW_CDIR.COM.
(Portions of this DOC file were liberally plagiarized from the documentation
of UDEL, another program of mine.)
-- Rights --
I retain all rights to CDIR.COM, but please use it as if it were
public domain. This goes for commercial as well as private users.
If it's useful, don't send any money (unless you REALLY want to....)
because it's FREEware. (Besides, I wouldn't feel like such a
philanthropist if everybody paid me for such a simple little utility
-- Disclaimer (or "Don't shoot! I'm on your side!")--
I really don't see HOW this could possibly do any damage, but I will
nonetheless make the standard disclaimer:
I will take no responsibility for the misuse of this program. There
are no warrantees, guarantees, promises, oaths, or other bonds
attached to this program, and by using it you agree to take all
responsibility for what it does (or what it does not do), upon your
(Wow! You'd think I had a law degree or something....)
-- What does it do? (or "A Primer on Cascading") --
On a Novell file server, files and directories are usually organized
In this situation, the VOLUME: is (as far as DOS & Netware are
concerned) the root direcory (referred to in DOS as "\"). The next
level up, the "FIRST_DIRECTORY_FROM_ROOT" level, is where users have
their rights granted. A typical directory tree might look like this:
FILE_SERVER VOLUME DIRECTORIES---------------------------------------
Within these levels, rights granted are "cascading." For example,
Obviously, your boss, Bob Thurmond (BOBT) needs rights to modify
files in his directory. His rights will "cascade" down to all of his
subdirectories (WP, LOTUS, and MISC_DATA). Not everybody needs to
have rights to \PROGRAMS\PAYROLL, but those who do, will need to work
on both subdirectories, so their rights will "cascade" down.
Anyway, you can see that on a big network, there may be a need to find
files only in your subdirectories. For example, suppose that Sally
Williams (SALLYW) wants to find all the .BAK files in her directories.
She would not want a global file find utility, but a cascading utility
would be very handy. Such a utility is CDIR. (Novell provides a VERY
beefed-up directory program that will do this, but NDIR can be SLOW
because of all the options that are built into it)
Now that you uderstand "cascading", you can understand the usefulness
of CDIR. Since I work on a network, I have my hard drive organized
much like the network, so I find it useful here as well. For network
managers who have to deal with software upgrades (or pirated software
for that matter) relatively often, this is an ideal utility for
finding files such as QED*.*, PSERVER.EXE, etc. (or DIGDUG.EXE for
-- How to use it (or "Just pull the trigger...") --
Type CDIR /? or CDIR -? or CDIR /h or CDIR /H or CDIR -h or CDIR -H for
help. Easy enough? See for yourself:
Usage: CDIR [/NP or -NP or /SR or -SR ]
is any valid filename and wildcards are allowed.
The /NP (or -NP) switch is used if you do not want a pause for each
file to be found. It is optional.
The /SR (or -SR) switch is used if you want to find all matching
files in ALL directories on the disk -- not just the cascading ones.
Use CDIR [/? or -? or /H or -H ] for help.
-- How to contact the author (or "Who the heck is this guy, anyway?") --
If you have any questions, please let me know by E-Mail or letter at:
1999 N. University Ave., #76
Provo, UT 84604
BYU CCC-INFO BBS
(then type then "C CCCINFO" when connected)