; Text file for DUHELP.EXE or DUHELP.COM, a menu-driven environment 
; for screen/printer output. Place DUHELP and this file in the same
; directory and type DUHELP.
;
; Except as specified in the "User-Added Information" section below, 
; no alterations may be made. Doing so violates the copyright, and may 
; make this file unusable with the help program. Use well, and enjoy.
;
; ^OL4 ^OR71 ^OJ
;
21 August 1989
9
PRINTOK
TITLE: DIRECTORY UTILITIES MANUAL
                              USERS  MANUAL

                                -- for --


          ******************************************************

                       ADVOCATE DIRECTORY UTILITIES

          ******************************************************


                Complete Directory Utilities Package: $30
                 [Individual-Program Licensing Available]
                          (c) 1989, J. W. Olsen
                           All Rights Reserved
                        Advocate Enterprises, Ltd.
                                 Chicago
~ (Menu)
   ======================  DUHELP Run-Time Menu  ======================
   =                                                                  =
   =  Q - QUIT Program                                                =
   =  A - ALL SECTIONS of File                                        =
   =                                                                  =
   =  1 - Becoming Acquainted, General Installation                   =   
   =  2 - ADIR:   The Multi-Path Directory Sorting & Display Program  =
   =  3 - ASCOUT: The Sophisticated File Finder                       =
   =  4 - ATREE:  The Expanded "Tree" Replacement                     =
   =  5 - CDX:    The "Change Directory Extended" Program             =
   =  6 - Features Common to Various DIRUTILS Programs                =
   =  7 - (User-Added Information)                                    =
   =  8 - License Agreement, Credits & Disclaimer                     =
   =                                                                  =
   ====================================================================
~ (Section 1)
             << BECOMING ACQUAINTED, GENERAL INSTALLATION >>

   Advocate   Enterprises   Directory  Utilities  ("DIRUTILS")   is   a 
   collection  of  the latest in "directory-related"  programs.  Member 
   programs are designed to run as stand-alone utilities for those  who 
   demand speed and straight-forward computing, yet may be called  from 
   a menu or shell (such as our own Advocate SHELL). They're of special 
   value to those of us who don't like large, sluggish memory hogs. Run 
   DIRUTILS  programs  by themselves, or create the "perfect"  menu  or 
   shell for you!

   This  manual  outlines usage of all member  programs.  Licenses  are 
   available   for  the  complete  package  or   individual   programs. 
   Licensing  and  ordering information is found  in  the  accompanying 
   AEORDER  program.  Note: Complete-package  licensees  presently  are 
   entitled  to  forthcoming  DIRUTILS programs as  they  are  released 
   without additional fees other than for handling (currently $10).

   The  current package contains the following programs:
          1) ADVOCATE SCOUT, The Sophisticated File Finder, goes beyond 
   all  other file-finding programs and is the one against  which  they 
   must  now  be  measured. Besides traditional  searches,  ASCOUT  can 
   locate  "close matches" when you don't recall exact names. And,  you 
   can limit searches to files created before, since or on any date--as 
   well as between two dates. So now for the first time, if you know  a 
   file's  name, ANY part of it, something CLOSE to it or  even  merely 
   its approximate DATE, you can quickly find it.
          2)  ADVOCATE DIR, The Multi-Path Sorting &  Display  Program, 
   masquerades as "just another" fast, sophisticated directory  display 
   program--until  you  need  to compare several  directories  or  file 
   specifications. Then, you may compare FOUR specifications as  easily 
   as one.
          3) ADVOCATE TREE, The Expanded Tree Replacement, is a  simple 
   but  useful  replacement for your operating system's  TREE  program. 
   (You remember it--the program nobody uses more than once!) ATREE  is 
   about twice as fast, yet far more informative and functional.
          4)  CDX, The "Change Directory Extended" Program, is  a  VERY 
   quick  way  to move between directories.  Unlike  most  competitors, 
   changing  drives normally involves just one keystroke . . .  and  on 
   most  systems, ALL of a drive's directories (more than 100)  display 
   on ONE screen. CDX doesn't require time-consuming navigation through 
   fancy  "tree" displays; and the key(s) to access a  given  directory 
   are  more  intuitive. Of course, CDX displays a  formatted  list  of 
   directories if you prefer the display method or make an error.

   If  you're  tired of all the keystrokes other programs  require  yet 
   demand  fast, complete performance, Advocate Directory Utilities  is 
   your solution!

   By  use  of DIRUTILS, you agree to the terms and conditions  of  the 
   License Agreement in Section 8.

   DIRUTILS  are  designed  to run on virtually any  MS-DOS  or  PC-DOS 
   system, v. 2.1 or later. Amount of memory and hardware configuration 
   aren't critical. Comparable CP/M programs are possible if sufficient 
   interest is expressed. (Contact information appears in Section 8.)

   DIRUTILS are exceptionally easy to use, but please take the time  to 
   browse the complete manual first--time well spent.

   INSTALLATION

   Please  ensure you received all files. A complete set  contains  the 
   following.  (If this is a registered version and you  licensed  only 
   certain  DIRUTILS  programs, unlicensed programs of course  will  be 
   omitted.   Registered  versions  also  contain   a   reconfiguration 
   program.) 

   ADIR.COM         The Multi-Path Directory Sorting & Display Program
   AEORDER.EXE      Displays product list & prints order form
   AEORDER.HLP      Text file for AEORDER.EXE
   ASCOUT.COM       The Sophisticated File Finder
   ATREE.COM        The Expanded TREE Replacement
   BEFORE.BAT       Batch file which may be used to execute ASCOUT
   BETWEEN.BAT      Batch file which may be used to execute ASCOUT
   CDX.COM          The "Change Directory Extended" Program
   DIRUTILS.FOR     Quick description of program (suitable for BBS use)
   DIRUTILS.HIS     History of revision updates
   DUHELP.HLP       Text file you're now reading
   DUHELP.EXE       Runs this text file
   ** DUREADME.COM  Optional--if provided, type "DUREADME" first
   FILEDATE.BAT     Batch file which may be used to execute ASCOUT
   SINCE.BAT        Batch file which may be used to execute ASCOUT
   TODAY.BAT        Batch file which may be used to execute ASCOUT
   WHATRUNS.BAT     Batch file which may be used to execute ADIR

   If  new  to ordering software, note that  distribution  disks  don't 
   contain "system tracks" because of their exceptional costs, which we 
   would  have  to pass along. So, to get started you'll need  to  make 
   copies  of the files before using them (which you should  do  anyway 
   for safety!). It's easy. . . .

   HARD DISK SYSTEMS: Boot your computer on the hard disk as usual  and 
   select a directory for all accompanying files. This directory should 
   be one listed on the PATH line in your AUTOEXEC.BAT file in the root 
   directory of your boot  disk. This permits your operating system  to 
   find  DIRUTILS  programs  simply by typing  their  name.  (See  your 
   computer manual if unfamiliar with subdirectories or PATH  command.) 
   Note  that ancillary DUHELP.EXE and AEORDER.EXE programs  expect  to 
   find  the  text  files  they format to  screen  or  printer  in  the 
   subdirectory containing these .EXE files. After copying ALL files to 
   your hard disk, see the "All Systems" section below.

   FLOPPY-DISK-ONLY  SYSTEMS:  Format a blank disk as usual,  add  your 
   favorite  file  copying utility, and place that disk  in  drive  A:. 
   Place  the  DIRUTILS distribution disk in drive B:.  Now,  copy  all 
   files from B: to A:. Then see next paragraph.

   ALL  SYSTEMS:  You should use ONLY the working copies  you  created. 
   Thwart  Murphy's Law by safely storing the originals--just in  case. 
   Now,  move  to the disk directory containing your  DIRUTILS  working 
   copies.  Then,  if these files contain a README.COM  (or  similarly-
   named)  program, type its name for introductory information and  any 
   notices since the last update of this manual.

   CONCLUDING COMMENTS

   We've  made a conscientious effort to accommodate a broad  range  of 
   needs. But enhancements are always possible. We'll work with you  if 
   you have ideas, run into difficulties--whatever. And, we'll send you 
   a complimentary enhanced version containing any of your  suggestions 
   we  implement. Your ideas benefit you and others. Help us  to  serve 
   you better. Contact information is found in Section 8.
~ (Section 2)
       << ADVOCATE DIR: THE MULTI-PATH SORTING & DISPLAY PROGRAM >>

   ADVOCATE  DIR  can be used like any  other  sophisticated  directory 
   program  for a fast display of filenames and their size without  all 
   the  clutter of alternatives. Simply type "ADIR" for  the  complete, 
   current directory in alphabetical order. Using an ordinary operating 
   system  wildcard  (see  your DOS manual  if  unfamiliar  with  them) 
   entering  "ADIR  *.EXE" provides only files ending with  ".EXE".  Of 
   course, you may specify a drive or PATH on the command line,  as  in 
   "ADIR C:\BIN" or "ADIR C:\BIN\*.EXE".

   But  ADIR  really  shines when you want to  COMPARE  directories  or 
   groups  of  files in the same directory. You may select up  to  FOUR 
   file  specifications  in a single execution of  ADIR.  For  example, 
   "ADIR A: C:" compares a floppy and hard disk directory. Or you might 
   type "ADIR *.COM *.EXE *.BAT" to display all executable files on the 
   current drive, something like the following. (Note: Frequently used, 
   lengthy  commands may be saved to a "batch" file for  easy  repeated 
   use later, as discussed in Section 6.) 

    ADIR   (c) 1989, J.W. Olsen
       Path 1: *.COM
       Path 2: *.EXE
       Path 3: *.BAT
    ======== 1 ============ 2 ============== 3 ============= 4 ========
    ADIR.COM   9911 | YOUR.EXE 110289 | YOUR.BAT  128 |
    YOUR.COM  10201 |                 |               |
    ===================================================================
       1: 2 file(s) of 20112 bytes (20 kilobytes used, 4922 free)
       2: 1 file(s) of 110289 bytes (108 kilobytes used, 4922 free)
       3: 1 file(s) of 128 bytes (1 kilobyte used, 4922 free)

          For  a  single  file specification,  matching  files  display 
   across all four columns; if two specs are entered, each is displayed 
   two-across. For three or four specs, each uses a dedicated column.

   Important:  To include the current DEFAULT directory (the  one  from 
   which  you  invoke  ADIR) in a  multi-directory  display,  you  must 
   explicitly  say so. While "ADIR" by itself implies "ADIR  *.*"  (all 
   files in the current directory), to display all files in the current 
   directory  AND all files on drive A:, you must type "ADIR  *.*  A:". 
   Or,  you can use a operating-system shortcut and type "ADIR  .  A:". 
   The  period  means  "default  directory."  Similarly,  "ADIR  .  .." 
   compares the "default directory" and its "parent directory."

   CONCLUDING NOTES

   Like all DIRUTILS, ADIR is designed to work on the smallest  system. 
   However,  ADIR  must  request minimal memory  work  space  from  the 
   operating system. In the unlikely event such memory isn't available, 
   an  "OUT  OF MEMORY" message is displayed before  ADIR  quits.  This 
   either means other currently-resident programs are using almost  all 
   available memory, or you should suspect system problems.

   See  Section  6  for  important  additional  information  about  the 
   program's built-in help screen, temporary or "permanent" changes  to 
   program features, use of ADIR in batch files and redirecting  output 
   to printer or disk file.
~ (Section 3)
           << ADVOCATE SCOUT: THE SOPHISTICATED FILE FINDER >>

         ADVOCATE  SCOUT is THE "file-finder" against which all  others 
   must  now  be  compared. With it you can search  for  MULTIPLE  file 
   specifications   on  MULTIPLE  drives,  use  "normal"   or   "close-
   approximation" search modes (or both concurrently!), limit files  by 
   date  and  specify  a beginning directory from which  to  begin  the 
   search for each specification or for all specifications (rather than 
   wasting time searching an entire, large drive).

   ASCOUT  offers powerful features far beyond any comparable  product. 
   But  you  needn't learn all the capabilities at  once.  Instead,  we 
   suggest  you review the complete discussion once to get a  feel  for 
   the many options, then go back and learn what you need for basic use 
   now and pick up additional capabilities as needed. We'll begin  with 
   basic syntax for now, picking up some special "shortcuts" to  reduce 
   typing and errors later. So don't worry about the sometimes  lengthy 
   command examples for now while you learn basic ASCOUT techniques. As 
   you'll soon see, it's all easy. . . .

   In  simplest usage "ASCOUT EXAMPLE.TXT" would find all instances  of 
   "EXAMPLE.TXT" anywhere on the current drive. "ASCOUT *.EXE" uses  an 
   operating  system  "wildcard" convention to find all files  of  type 
   ".EXE".  (See  your  operating  system  manual  if  unfamiliar  with 
   wildcards.)

   Like  some other programs, ASCOUT permits you to specify a drive  to 
   search, such as "ASCOUT D:*.EXE".

   But  this is where ASCOUT begins to part company  with  competitors. 
   Beyond  the above features, you may, for example, limit searches  to 
   certain directories. For example, "ASCOUT \WRITING\*.EXE" limits the 
   search to all .EXE files in WRITING and any child subdirectories  of 
   the WRITING PATH.

   A unique feature is ASCOUT's ability to locate essentially unlimited 
   file  specifications in a single execution "ASCOUT C:*.EXE  D:*.EXE" 
   finds  all  .EXE  files on two drives, for example.  The  number  of 
   specifications is limited only by what you can type on the operating 
   system command line.

   It's  important  to note that a PATH or filespec remains  in  effect 
   until  explicitly  changed. "ASCOUT C:*.EXE  *.COM  D:*.EXE  D:*.COM 
   C:*.BAT" first searches drive C: (all directories, in this  example) 
   for  .EXE  and  .COM files, then does the same for  drive  D:,  then 
   return  to drive C: for all .BAT files. (The same would be  true  if 
   you had specified a PATH--with or without drive--for each occurrence 
   of "C:" and "D:".)
          Note  that  in  the  preceding example  it  would  have  been 
   preferable to put the .BAT filespec after the first .COM filespec so 
   each   drive  would  have  been  interrogated  only   once.   ASCOUT 
   simultaneously checks the first drive and/or PATH for all  filespecs 
   UNTIL DRIVE OR PATH CHANGES. Thereafter, searching must be conducted 
   sequentially  rather  than concurrently. Note too  that  the  second 
   drive D: reference is gratuitous. ASCOUT would have assumed it if it 
   had  been  omitted. Note too that if C: is the  current  drive,  the 
   following command would have precisely the same effect as the above: 
   "ASCOUT *.EXE *.COM D:*.EXE *.COM C:*.BAT".
          As  noted,  filespecs, too, remain in effect  until  changed. 
   Thus "ASCOUT C:EXAMPLE.* D:\MAIN\" would search all of drive C:  for 
   "EXAMPLE.*" then search D:\MAIN and all of its subdirs for the  same 
   filespec.
          Applying all we've learned so far, the most effective form of 
   the  command  would be: "ASCOUT *.EXE *.COM  *.BAT  D:*.EXE  *.COM". 
   Because of ASCOUT's unique, copyrighted multiple-search features, it 
   can  typically  perform  the above search  FIVE  times  faster  than 
   competitors!

   One  of the program's most unique and perhaps most valuable  feature 
   is  "close-approximation"  or  "fuzzy"  searches.  By  preceding   a 
   filespec  with  the "fuzzy key" ("~" as released, see Section  6  to 
   alter),  close  matches will be located too. In fuzzy  mode,  ASCOUT 
   applies  up  to SEVEN sophisticated but fast sets of  logic  against 
   your filename specification. Together, they virtually ensure  you'll 
   find the file(s) desired if you only know a portion of their names--
   or even just a name "similar to" them. Details on the rules of logic 
   appear below. For now, here are a couple of examples to  demonstrate 
   use  of  fuzzy  syntax. . . ."ASCOUT ~README"  lists  all  filenames 
   similar  to "README". "ASCOUT C:\MAIN\~README" does the same with  a 
   restricted PATH, as described above. It's important to remember that 
   the fuzzy key applies ONLY to the filename to which it is  attached. 
   Thus,  "ASCOUT ~README EXAMPLE ~METOO" performs fuzzy searches  only 
   on  the first and last specification; "EXAMPLE" is  performed  using 
   conventional strict-search techniques.
          If  you DO want to perform fuzzy searches on all  files,  you 
   may use a command-line "force fuzzy mode" toggle. Doing so, you  can 
   skip the "~" entirely. Example: "ASCOUT FILE1 FILE2 /F" will  search 
   for   both  file  specifications  in  fuzzy  mode.  You   also   may 
   "permanently"  tell ASCOUT to use fuzzy mode EVERY time you use  it. 
   (Or, you could make one version which always searches in fuzzy  mode 
   and use another for conventional searches.) All of these  techniques 
   are discussed in the reconfiguration portion of Section 6.

   Another  highly  useful  feature unique  to  ASCOUT  is  restricting 
   searches  by DATE. You may list files BEFORE, SINCE or ON a date  of 
   your choice--or BETWEEN two dates. Let your imagination go--uses are 
   endless. For example, let's say you last updated your hard drive  on 
   August  1, 1989 (shame on you!). You'd rather not update the  ENTIRE 
   drive,  but instead back up just the changed files  or  directories. 
   "ASCOUT *.*+8/1/89" will list all files SINCE 8/1/89. Similarly,  if 
   you  can't  remember  a file you created today  (August  18,  1989), 
   "ASCOUT  *.*=8/18/89" will find it. "ASCOUT *.*-8/17/89"  lists  all 
   files BEFORE today. 
          As you can see, the following flags (which may be altered, as 
   discussed in Section 6) perform the corresponding date functions:
   + Files SINCE your date 
   - Files BEFORE your date
   = Files ON your date
   These  may be combined in any order. Just ensure you enter  no  more 
   than one of each for a single filespec. "ASCOUT  *.*+8/1/89-8/18/89" 
   displays all files so far this month.
          Because  you'll  often want to use today's date  to  restrict 
   searching,  ASCOUT provides a shorthand for it. "ASCOUT =TODAY"  (or 
   just "ASCOUT =T" will do) lists all files created or updated  today. 
   "ASCOUT  +8/11/89-TODAY"  would  show files of the  past  week.  (As 
   you'll also discover after reading Section 6, we've even supplied  a 
   batch  file  which will show all of today's files simply  by  typing 
   "TODAY"  . . . as well as several other batch files  for  simplified 
   performance of frequently used purposes.) Note that for the  "today" 
   function  to work, you must have previously advised  your  operating 
   system  of  the current date, either through a  hardware  "real-time 
   clock" or by using the operating system's "DATE" function. (See your 
   operating system manual if unfamiliar with the latter, or check with 
   your computer consultant.)
          Like PATHs and filespecs, dates remain in effect on all later 
   user  requests  on the command line until  explicitly  changed.  For 
   example,  use this to find all files ending with ".COM" and  "*.EXE" 
   created this year: "ASCOUT *.COM+1/1/89 *.EXE".
          In  short, all elements on a command line  (PATH,  filespec--
   which  for  ASCOUT purposes INCLUDES ANY ATTACHED  "FUZZY  KEY"--and 
   date) remain in effect for the rest of your command line unless  and 
   until explicitly changed. Example:
   ASCOUT C:*.EXE *.COM=TODAY D:
   This  command  checks drive C: for "*.EXE" (all dates)  and  "*.COM" 
   (today  only), then drive D: for "*.COM" (today only). If  a  "fuzzy 
   key"  had  been  added  immediately after  "D:"  ASCOUT  would  have 
   reported an error and aborted. This illustrates that a fuzzy key  is 
   considered part of a filespec. The following command would be valid:
   ASCOUT C:~EXAMPLE D:
   It  would search first drive C:, then drive D:, in each  case  using 
   fuzzy mode to find files like "EXAMPLE".
          Relatedly,  if  your FIRST request has no  filespec  at  all, 
   which  can  be  a  handy  shortcut,  "*.*"  (the  operating   system 
   convention for "all files) is substituted by ASCOUT. Thus, these are 
   all legal commands:
   ASCOUT C:
   ASCOUT +8/1/89
   ASCOUT C:\MAIN\=T
          The  last  example  raises a notable point. If  you  want  to 
   search all files in, say, C:\MAIN, (which is a shortcut for  "ASCOUT 
   C:\MAIN\*.*"), you MUST provide the trailing backslash.

   IMPORTANT: It's technically possible for a filename to contain  date 
   flags as legal elements (e.g., "-READ.ME"). If you encounter one  of 
   these  situations,  you have several options. If you have a  LOT  of 
   them, you can simply reconfigure ASCOUT to change one or more of the 
   flag characters or permanently disable the date function altogether, 
   both as described in Section 6. In "fuzzy" mode, you also can simply 
   ignore   the   flag  characters  altogether.   (As   nonalphanumeric 
   characters  they would be ignored during match comparisons  anyway.) 
   In the current example, "ASCOUT ~README" is the correct command.  In 
   conventional,  "strict" mode you can also use the  operating  system 
   "?"  wildcard, as in "ASCOUT ?READ.ME". Lastly, you can  temporarily 
   or  permanently "turn off" date checking altogether as discussed  in 
   Section  6.  By doing so, ASCOUT looks only for path  and  filename, 
   treating none of your request as dates. (Doing so ANYTIME you  don't 
   want date checks slightly speeds execution.)

   NOTE:   As   released,  ASCOUT  uses  the  U.S.   date   format   of 
   month/date/year.  This may be altered. Likewise, the  default  fuzzy 
   key  ("~") and date-related characters ("-", etc.) may  be  altered. 
   The  latter  may be necessary if you're in the habit of  using  such 
   characters as part of filenames. (Normally, you can get around  this 
   with  use  of operating-system wildcards and/or fuzzy mode  on  such 
   occasions.) See Section 6 for reconfiguration details.

   You now have a fairly thorough introduction to ASCOUT  capabilities. 
   With  a little use, you'll find numerous new applications for  them. 
   But  we did promise more details on the fuzzy algorithms  (rules  of 
   logic). After all, we should give our competitors a sporting  chance 
   on closing some of the ground on us! Seriously though, you'll find a 
   general understanding useful when you're forced to guess  filenames, 
   so you'll maximize chances to find an elusive file.
          The  first thing ASCOUT does in fuzzy mode is to  strip  both 
   your  request  and  a  directory  filename  of  all  nonalphanumeric 
   characters.  (In  other  words, all that are left  are  numbers  and 
   letters--no  punctuation.)  It then performs up to  seven  tests  to 
   compare  the  results  against  each  other.  If  any  of  them   is 
   successful,  the directory filename is considered "matched"  and  is 
   displayed. Those tests are:
   PERCENTAGE OF SIMILARITY: A sophisticated algorithm beyond the scope 
   of  this document determines "how similar" your and the  directory's 
   names  are to each other. As released, a 66% ratio is  considered  a 
   match.  This  algorithm catches the majority of  matches,  including 
   those  falling into the categories below. But "the  majority"  isn't 
   good enough, so if necessary ASCOUT next tries. . .
   CONTAINED  STRING:  If  the directory's name  CONTAINS  yours,  it's 
   considered  a  match. (E.g., You specify "~FILE" and  the  directory 
   name is "FILE1". They're considered a match.)
   REMOVE  DUPLICATE CHARACTERS: All duplicate letters in your and  the 
   directory's  filenames  are removed, then they're  compared.  (E.g., 
   COMUNICATE matches COMMUNICATE)
   TRANSPOSED   CHARACTERS:  One  set  of  transposed   characters   is 
   permitted. (E.g., THIS matches THSI but not HTSI.)
   MISSING CHARACTER: One missing letter is permitted--but only in YOUR 
   filename. (E.g., You specify THS and the directory name is THIS.  It 
   matches. The next directory name is TS. It doesn't match.)
   BAD  CHARACTER: One incorrect character is permitted.  (E.g.,  FILE1 
   matches FILE2, but not FILX2.)
   "SOUNDS  ALIKE": This is a complex function that matches files  with 
   similar sounds. Vowels, "H" and "W" are always ignored.  Thereafter, 
   weighted values are assigned to remaining consonants, then compared.
          Why  so many algorithms? For several reasons. . . .As  noted, 
   no  single  test  is  100% reliable  under  all  circumstances.  For 
   example,  if you search for "XY" which you THOUGHT was the name  for 
   "XZ" the main, "percentage of similarity" test would fail on such  a 
   short  filename despite the single-character error. The  "transposed 
   characters"  test,  however, would find it. Or, if you know  a  file 
   contains  "XYZ"  somewhere in it, the "contained  string"  algorithm 
   would find it.
          In  short,  ASCOUT  is designed to work  regardless  of  your 
   habits in creating filenames. But what if you don't WANT some of the 
   tests? (A good example is that you perhaps won't like the  "contains 
   strings" test. Or, it's not too unusual to have a system on which  a 
   great  many filenames "sound alike.") By making tests separate  from 
   each  other, it's possible to "turn off"  unwanted  algorithms--even 
   adjust the "percentage of similarity" value if you consistently find 
   either that too many "matches" occur--or not enough for your  unique 
   circumstances.  However,  our  prerelease  testing  suggests  you'll 
   probably  find  the default conditions well suited  for  almost  any 
   need. See Section 6.
          Relatedly,  we might note that in fuzzy mode it  is  EXPECTED 
   that  you  will find a few more "matches" than  needed.  That's  the 
   small  price for finding a file whose name you simply can't  recall. 
   According  to  our own testing, the number of  unwanted  files--even 
   with  ASCOUT configured to use all of its extensive tests--is  quite 
   small  and  manageable. On the other hand, IF your  request  can  be 
   entered  in "strict" mode, that's advisable. Save "fuzzy"  mode  for 
   when needed--then use it freely.
          Despite these extensive and sophisticated algorithms,  strict 
   and  fuzzy  searches execute at a  virtually  identical--and  fast--
   speed.

   ERROR MESSAGES

                            "Invalid filename"
                   "Invalid filename for current mode"
                         "<-- argument too long"
   ASCOUT  displays  one of the above messages before aborting  if  you 
   entered an invalid filename or, in the last case, filename or  PATH. 
   The first message is most commonly encountered if you attempt to use 
   the operating system's "." or ".." shortcut conventions incorrectly. 
   The  second  message  is most commonly encountered if  you  enter  a 
   "fuzzy"  mode  request with no alphanumeric  characters.  The  third 
   message  catches attempts to request a longer PATH or filename  than 
   the  operating  system allows. You may  have  nested  subdirectories 
   which,  when their names are combined to form a path, form a  string 
   of characters which is too long. Or, you may have forgotten the last 
   backslash ("\") between PATH and filename.

                          "Improper date format"
   If  you  enter an improper date or improper date format,  the  above 
   message  is  displayed before ASCOUT aborts. See  above  for  proper 
   format.  (If you prefer the non-U.S. format of date/month/year,  see 
   the discussion on reconfiguring ASCOUT in Section 6.) Note that  the 
   operating  system considers any file date before January 1, 1980  to 
   be  illegal, so ASCOUT rejects any request for such  date.  (Because 
   dates  after  December 31, 1999 result in a year of "00"  or  above, 
   these too are disallowed. The alternative would have been to require 
   you  to type "1989" instead of "89" for years. We decided  to  avoid 
   such  extra typing and worry about all that in another 10 years!  In 
   any  case,  you'll  want the latest and  greatest  upgrade  by  then 
   anyway, right?!)

                             "OUT OF MEMORY"
   ASCOUT requests minimal additional memory from the operating  system 
   to store information. Under normal circumstances, such requests will 
   pose  no  problem  on  even the smallest  system.  However,  in  the 
   unlikely event it does, the above message is displayed before ASCOUT 
   aborts.  This  either means other resident  programs  have  reserved 
   almost all available memory, or you should suspect system problems.

   CONCLUDING NOTES

   See  Section  6  for  important  additional  information  about  the 
   program's built-in help screen, temporary or "permanent" changes  to 
   program  features,  use of batch files for  ASCOUT  and  redirecting 
   output to printer or disk file.
~ (Section 4)
           << ADVOCATE TREE: THE EXPANDED "TREE" REPLACEMENT >>

   ADVOCATE  TREE is somewhat similar to your operating  system's  TREE 
   program but about twice as fast and much, much more useful. (We gave 
   up on "tree" programs until we wrote ATREE.) Its display is far more 
   compact  yet more readable. Its display provides  enumeration,  full 
   PATH  to  each directory on the same line, and the  amount  of  disk 
   space  and percentage of total drive a subdirectory's files  occupy. 
   After  the last subdirectory's information is displayed,  a  summary 
   provides  total  number  of  directories,  total  space  and   total 
   percentage occupied. And unlike TREE, screens (or printed pages) may 
   be automatically paused or run continuously.

   Usage  couldn't be simpler: Type "ATREE" for the current  drive,  or 
   specify  a  drive  (e.g.,  "ATREE  C:").  If,  when  ATREE  requests 
   information  about the desired drive, the operating  system  advises 
   that  the  drive  isn't active, "No such  drive  reported"  will  be 
   displayed before ATREE aborts.

   See  Section  6  for  important  additional  information  about  the 
   program's built-in help screen, temporary or "permanent" changes  to 
   program features and redirecting output to printer or disk file.
~ (Section 5)
            << CDX: THE "CHANGE-DIRECTORY EXTENDED" PROGRAM >>

   We  believe CDX is the fastest change-directory program  around.  It 
   also permits you to change drive AND directory in a single  command, 
   as simply as "CDX D:A" to move to the first directory beginning with 
   "A" on drive D:, for example. And unlike competitors which insist on 
   slow "tree" displays which often require you to page through several 
   screens, CDX generally fits all directories on a single screen (more 
   than 100!). You may use this display and built-in prompt each  time, 
   or  avoid  it entirely by entering your command  at  the  operating-
   system prompt.

   INSTALLING CDX.COM FOR A DRIVE 

   As a reminder, be sure CDX.COM is in a directory on the PATH  listed 
   in  your  AUTOEXEC.BAT  file. The whole purpose of CDX  is  to  move 
   around  the system, so obviously it must find itself no matter  what 
   the  current  directory or drive might be. For the following  it  is 
   assumed  you have followed the general installation  procedures  for 
   your system as outlined in the Section 1.

   We'll  also  assume  for now that you'll be using CDX  in  its  most 
   common  fashion--installing  it for each hard drive  so  performance 
   will  be  greatly increased in the future. Installation  is  quick--
   about 1 second per megabyte on a typical system. To do so, move to a 
   drive (any directory) on which you want to use CDX. Then, FROM  THAT 
   DRIVE, type only the program name--CDX.

   The  program will determine it has never seen that drive before  and 
   will thus interrogate its directory for its subdirectory  structure, 
   then offer to "save data to disk." Response "Y" for yes. CDX is  now 
   installed for that drive. (Competitors don't let you decide  whether 
   to  save their data files--generally a great way to litter  floppies 
   with unwanted files when competitors move to them.) Thereafter, your 
   subdirectory  list  is displayed. Exit for now  with  the  indicated 
   function key (F10).

   The next time that you type only the program name on that drive, the 
   display  and prompt will be displayed almost immediately, thanks  to 
   the  newly-created  data  file. The data file resides  in  the  root 
   directory of the installed drive and is called something similar  to 
   "CDX.100".  The number part of the name may be different, as  it  is 
   established by CDX.COM for error-checking purposes.

   If you have more than one logical hard drive, move to each in  turn, 
   installing  CDX  in  exactly the same way. You may also  do  so  for 
   floppies which contain subdirectories, if desired.

   Note:  If you operate from a shell or menu program, you may now  add 
   CDX.COM  to its list of executable programs, replacing the  built-in 
   operating system "CD" function or your former program which performs 
   this service.

   REINSTALLATION OF A DRIVE

   If  you add, delete or rename a directory on a drive, you must  tell 
   CDX. (To greatly increase run-time speed, CDX does not automatically 
   interrogate  the drive if its data file is present.)  Reinstallation 
   is as easy as installation. Either manually delete the old data file 
   in the root directory and follow the above "first-time" installation 
   instructions;  or more simply, move to the drive in  question,  type 
   ONLY  "CDX"  to reach its display and prompt, then use  the  "update 
   data file" function key (F2).

   USAGE

   CDX may be invoked in one of two ways. If you simply type its  name, 
   the  same  display and prompt you saw  after  installation  appears, 
   awaiting  your command. Alternatively, if you're a "power user"  who 
   prefers maximum speed over pretty displays, you may enter "CDX"  and 
   your  command at the operating system prompt, as in  "CDX  EXAMPLE". 
   Either  way,  the command itself is identical. (For  the  following, 
   commands are presented as though entered at the CDX prompt. Command-
   line user would simply precede each with "CDX" and a space.)

   For illustration purposes, we'll assume your drive contains only the 
   root directory and three others, as follows:

   \           DIR1           DIR2      LETTERS

   To  change directories, simply enter enough of a directory  name  to 
   distinguish it from all PRECEDING directories on the list (which  is 
   in alphanumeric order). You may enter more of a directory name  than 
   required.  PATHS are accepted but are entirely  unnecessary.  (Note: 
   The  internal CDX prompt is just long enough for a directory  name--
   and drive, discussed below--to help avoid user error.)

   So, for the above example the MINIMUM necessary commands to move  to 
   each  directory  would be: "\", "D", "DIR2" and  "L",  respectively. 
   (Note  that  "DIR1" isn't required to distinguish  it  from  "DIR2", 
   because no directory beginning with "D" precedes "DIR1".)

   You may enter a directory, drive AND directory, or simply a drive. A 
   simultaneous change of drive and directory isn't even possible  with 
   the  operating system's built-in "CD" command or  many  competitors. 
   With CDX, it's fast and efficient. Thus, if you want to change to  a 
   directory on drive C: called "EXAMPLE", you might enter  "C:EXAMPLE" 
   from  the  prompt,  even  if  EXAMPLE  is  down  a  long  PATH  like 
   \LETTERS\JACKSON\OLD\EXAMPLE. 

   If  you enter an invalid directory, CDX will move to the  drive  you 
   specify  (if any), then present the menu and prompt. (If  you  can't 
   remember the directory name, enter the drive and your best guess--or 
   simply  a question mark or other obviously invalid dirname  such  as 
   "CDX C:?".) If you enter ONLY the drive, CDX assumes you want to  go 
   to  the  default  directory of the specified  drive.  (By  operating 
   system convention, the "default" directory is the last directory you 
   used  on  a drive before leaving it--or the root directory,  if  you 
   haven't yet used that drive.)

   CDX also accepts conventional DOS shorthand for directories: "\" for 
   root directory, ".." for the default directory's "parent directory," 
   and  "." for the default directory itself. (The "." notation  really 
   is meaningless for purposes of changing directories, but . . . .)

   If  you have more than one IDENTICALLY-named directories on a  drive 
   (e.g.,  C:\DP\MARY  and C:\WP\MARY), CDX will find  them  all,  then 
   present  one at a time with a prompt for "Yes" or  "No".  Responding 
   "Y"  for "Yes" moves you immediately to that  directory.  Responding 
   "N"  for "No" displays the next identically-named directory and  the 
   same prompt.
          For  your  convenience, responding "N" to  all  possibilities 
   prior to the last one automatically takes you to that last directory 
   without prompting.

   SPECIAL NOTE

   CDX works most efficiently when installed for a drive as  indicated. 
   However,  there  may  be times you want to move  to  an  UNinstalled 
   drive, especially a floppy disk with only a directory or maybe  two. 
   Because   the  operating  system  stores  directory  names   in   an 
   essentially random order, you may need to type more than the minimum 
   directory-name characters described above for UNinstalled drives  to 
   ensure a match. 
          For  example, if the four directories in the earlier  example 
   ("\", "DIR1", "DIR2", "LETTERS") are on an uninstalled drive and you 
   use  the  command-line  prompt, "CDX \" and "CDX L"  would  work  as 
   expected.  But there is no certainty whether "CDX D" would move  you 
   to  "DIR1" or "DIR2". Either enter enough of a directory name to  be 
   SURE to distinguish it from all others, or enter just "CDX" to build 
   an  alphanumeric list, answering either yes or no as desired to  the 
   "create  data  file" query. (If you're on a different drive  at  the 
   time,  you may enter the drive and question mark as  noted  earlier, 
   e.g.,  "CDX  A:?".  Remember, "CDX A:" by itself moves  you  to  the 
   default directory on drive A:.)

   WARNING & ERROR MESSAGES

                     ** Normal Execution Messages **

                               "Working..."
   CDX  is  busy creating/updating its data file at  your  request   or 
   gathering  data after you've specified a drive change.

                            "Invalid Argument"
   The  drive or directory name--or, if entered, the PATH--contains  an 
   error.  Generally,  one of these contains too many  characters.  For 
   example,"CDX  DA:MYDIR" contains an error because a legal drive  may 
   be  only a single character. It's also possible, if you invoked  CDX 
   from  the  operating system prompt, that the length  of  the  ENTIRE 
   argument is illegally long. (Skipping PATHs avoids this.)

                         "No Matching Directory"
   CDX couldn't find a matching directory name. You may have entered  a 
   typo or in some cases an argument longer than the longest  directory 
   name.  If  the directory in fact exists, you failed to  install  (or 
   reinstall) the drive for CDX.

                            ** Fatal Errors **

   CDX  will immediately abort if it encounters any of  the  following, 
   nonrecoverable errors.

                        "MEMORY ALLOCATION error"
   Your  operating  system  reports  insufficient  memory  for  CDX  to 
   temporarily  store  information.  CDX  was created  to  run  in  the 
   smallest MS-DOS/PC-DOS system, so this either means already-resident 
   programs  are  using  almost all available  memory,  or  you  should 
   suspect system problems (frown).

                       "COMMAND.COM not executable"
                           "COMMAND.COM error"
   COMMAND.COM is part of the operating system itself, and its location 
   is suppose to be made known to other programs, such as CDX, in  case 
   they  need  it. In all likelihood, you will never see the  first  of 
   these  messages.  But if you do, it means  the  "Environment  Block" 
   provided  to  CDX doesn't contain valid COMMAND.COM  information.  A 
   manual  such as this can't diagnose the specific source of  such  an 
   external problem other than to suggest selectively removing any  TSR 
   ("terminate and stay resident") programs you may have installed, one 
   at a time. If the problem disappears, you've discovered the culprit.
          The  second message means COMMAND.COM  couldn't  successfully 
   execute the change-directory command CDX passed it. The most  likely 
   causes  are: 1) failure to reinstall a drive for CDX after  removing 
   or renaming a directory; and, 2) insufficient memory for COMMAND.COM 
   to perform its task (see above).

                            "FILE-READ error"
                            "FILE-CLOSE error"
                           "FILE-CREATE error"
                            "FILE-WRITE error"
   Each  of these messages indicates the operating system  reported  an 
   error  while performing a CDX request related to its data file.  All 
   could  mean either a temporary, minor--or serious disk or  operating 
   system--error.
          On the other hand, the latter two messages could be due to an 
   illegal  number of files in your root directory or that the disk  is 
   full, respectively. Try temporarily removing a couple of  expendable 
   files from the root directory and reinvoking CDX. (If you're  unsure 
   what  files are expendable, consult someone whose DOS knowledge  you 
   can trust. Or, if you are a registered CDX user, contact us.) If the 
   problem  doesn't  reappear,  you've discovered  the  source  of  the 
   problem and can take steps to correct it.
          If  the problem persists (after the test, in the case of  the 
   latter  two messages), it could be a serious operating system  error 
   (time  to  frown  again) or more likely a bad sector  on  your  disk 
   (which can be fixed--see your consultant or manual for details).  If 
   the problem goes away, it well may have been one of those relatively 
   rare hiccups computers have been known to have.
          Note: On encountering WRITE errors and certain CLOSE  errors, 
   CDX  attempts  to delete what probably has become a  corrupted  data 
   file.  In either of these cases (or if the integrity of data on  the 
   CDX  display  ever appears corrupted from unknown  external  cause), 
   recreate the data file by following the "Reinstallation of a  Drive" 
   subsection, above.
~ (Section 6)
            << FEATURES COMMON TO VARIOUS DIRUTILS PROGRAMS >>

   This section outlines four areas for those who want to maximize  the 
   potential of DIRUTILS programs: redirection of output from screen to 
   printer  or  disk file, operating system  batch  files,  temporarily 
   altering   default  values  (switches)   and  making  such   changes 
   "permanent."  These  features apply to all DIRUTILS  programs  whose 
   purpose is to display data--ADVOCATE DIR, ADVOCATE TREE and ADVOCATE 
   SCOUT--unless otherwise indicated. Built-in help screen for each  of 
   these  programs is discussed under switches. (CDX help is  requested 
   by a function key from its main display screen.)
   
   SWITCHES

   Like  most  quality  programs, DIRUTILS permit  you  to  temporarily 
   change  the  way  they operate during the  current  execution  of  a 
   program by command-line "switches." These switches let you do things 
   your  way rather than with default conditions most often  wanted  by 
   general users. We'll begin with a basic introduction to switches. At 
   first  reading,  usage  of switches may sound a  trifle  complex  to 
   novices;  but rest assured, as you'll soon see they're very easy  to 
   use when needed.

   In  all  cases, DIRUTILS inspect the LAST parameter on  the  command 
   line  for  switches.  ("Parameter" means  any  group  of  characters 
   preceded  by a space.) Upper- and lower-case characters are  treated 
   identically,   and  the  order  of  switches  is   unimportant.   To 
   distinguish  a switch from some other input, you must use  a  single 
   slash "/" character (not a backslash "\"), followed by the switches. 
   All switches must be grouped together (i.e., no intervening spaces). 
   Illegal  characters  in  an otherwise  valid  switch  parameter  are 
   treated  as  an  error,  causing DIRUTILS  to  display  useful  help 
   screens.
          Legal  switches and when you might want to use them  will  be 
   described  in a moment. But to illustrate how easy they are  to  use 
   here are examples of valid and invalid switch parameters, using ADIR 
   to illustrate:

   VALID:   "ADIR *.COM /T", "ADIR /SN", "ADIR \*.COM /T"

   INVALID: "ADIR /SN *.COM"  <- switches not last parameter
            "ADIR *.COM / T"  <- space within switch parameter
            "ADIR  \T"        <- backslash used instead of slash
            "ADIR *.COM/T"    <- no preceding space

   There  are several categories of switches. If more than  one  switch 
   from  a given category is entered, DIRUTILS assume you changed  your 
   mind and meant the last one.

   As  distributed, in default mode (i.e., if you use no  switches  and 
   haven't reconfigured it with an external configuration  program--see 
   below),  a  program  pauses  each  time  the  screen  becomes  full. 
   (Pressing any key moves to subsequent screens. Following  operating-
   system  conventions,  pressing control-C immediately  halts  output, 
   pressing  control-S immediately pauses. If unfamiliar with these  or 
   other  operating-system conventions, see your computer manual  or  a 
   third-party reference book. Registered DIRUTILS licensees, feel free 
   to contact us as well.) 
          For ADIR, the default mode also means filenames are displayed 
   alphabetically.

   BUILT-IN  HELP:  One switch, "/H", invokes a run-time  help  screen. 
   Example:  "ATREE C: /H". (An invalid switch also displays  the  help 
   screen.)

   For  discussion  of switches in some categories, an  asterisk  ("*") 
   denotes  default  values in distributed copies of  DIRUTILS.  Unless 
   you've  reconfigured your copy for other defaults (see  below),  you 
   will never need to use switches to obtain default performance.

   PAUSING:  These switches simply determine whether output  is  paused 
   for reading each time the screen fills. As noted above, pressing any 
   key  continues;  pressing  control-C immediately  aborts.  To  pause 
   WHILE  information is being printed to the screen,  press  control-S 
   (any key resumes). 
   M*     Pause with a "more" prompt after each screen.
   N      Nonstop display. (DIRUTILS makes nonstop display the default
          if output is redirected to a file or printer instead of the
          screen unless you override it with "/M". Redirection is 
          discussed below.)

   SORTING  (ADIR  Only): These switches determine the ORDER  in  which 
   filenames  are displayed. (In all cases, directory names are  listed 
   first, followed by "real" filenames.)
   F*     Sort alphabetically by FILENAME
   T      Sort by file TYPE (I.e., by "extension"--".COM," ".DBF," 
          etc.)
   S      Sort by file SIZE

   "FUZZY"  MODE  (ASCOUT  Only): Normally,  ASCOUT  uses  conventional 
   ("strict") methods to compare your request with directory  filenames 
   unless you precede your request with the "fuzzy key" character  ("~" 
   as released). Example: "ASCOUT ~THISFILE THATFILE" uses its  "fuzzy" 
   mode  algorithms  when  checking  for  matches  for  "THISFILE"  but 
   "strict"  algorithms for "THATFILE". But by using the "force  fuzzy" 
   switch, ("ASCOUT ~THISFILE THATFILE /F"), ALL requests are performed 
   in fuzzy mode regardless of the presence of the fuzzy key.
   F      Force fuzzy mode for all requests

   DATE-CHECKING  SUPPRESSION (ASCOUT Only): Sometimes it's  useful  or 
   necessary to force ASCOUT to skip its date-checking routines. If you 
   DON'T  want  to  search by date, using  the  date  suppression  flag 
   slightly  speeds  processing.  Date suppression is  also  useful  if 
   you're  looking for filenames with one of the date characters  ("+", 
   "-"  and "=" as distributed). With date suppression,  ASCOUT  treats 
   these characters as part of filename requests instead of date flags. 
   (Section  3  describes other alternatives to date  suppression  when 
   searching  for  filenames containing these characters.) It  also  is 
   possible to "permanently" reconfigure ASCOUT to disregard dates,  if 
   you never use that feature (see below).
   D      Date-checking suppressed

   An illustration of all we've discussed about switches: To have  ADIR 
   display all files beginning with "MA" on four drives by size without 
   screen pauses: "ADIR A:MA*.* B:MA*.* C:MA*.* D:MA*.* /SN".

   RECONFIGURING DEFAULT CONDITIONS

   Registered  users  may use an included  reconfiguration  program  to 
   "permanently"  change defaults in ADIR, ATREE or ASCOUT if  the  way 
   they  generally  run those programs is different than  the  defaults 
   listed  above. That way, they can avoid use of switches. Or  perhaps 
   they  prefer  to  keep a couple of different  versions  handy  (each 
   renamed distinct from each other) to avoid switches altogether.  The 
   reconfiguration program is quick and easy, asking you to make a  few 
   choices,  after which the related program(s) will  be  automatically 
   reconfigured in seconds. It also may be used to "permanently"  "turn 
   off"  or adjust the individual ASCOUT fuzzy-mode tests  detailed  in 
   Section 3, change ASCOUT's date and "fuzzy" mode flags, etc.

   REDIRECTION

   If  familiar with your operating system's redirection  capabilities, 
   you   may  want  to  skip  this  discussion.  If   unfamiliar   with 
   redirection,  you may want to supplement the following by  reviewing 
   your system's manuals.

   It  is often handy to send data which is normally displayed on  your 
   screen  to your printer or a disk file instead for  more  convenient 
   review, now or in the future. Doing so with DIRUTILS is as simple as 
   appending  an  appropriate instruction to the END  of  your  command 
   line.  It  must come AFTER all file or drive  specifications  and/or 
   switches. Examples:

   ATREE C: > PRN        (sends the information to your printer)
   ADIR /S  > FILENAME   (writes the information to a file)

   The ">" character is the conventional "redirect arrow" symbol. "PRN" 
   is  a  convention  used by the operating  system  to  mean  "default 
   printer."  Your printer MUST be ready BEFORE issuing  this  command. 
   For file output, any valid PATH and/or filename may be used. In both 
   cases,  nothing  will be output to your screen. Your  system  prompt 
   won't reappear until the computer has finished.
          CAUTION:  Redirection is a powerful service provided  by  the 
   operating system, but a word or warning is in order. The request for 
   redirection  is intercepted BEFORE the command line is passed  along 
   to  any  program.  So, while through a  special  technique  DIRUTILS 
   programs  use  they  can determine  redirection  is  occurring,  the 
   programs  do NOT know the destination of the redirection. So if  you 
   change  your  mind and abort (pressing control-C  or  control-break) 
   while directing output to a FILE, DIRUTILS can't close the file--and 
   unfortunately  a weakness of the operating system is that it  won't. 
   This is one reason why you may sometimes find a file with "0  bytes" 
   listed  on  directories.  So  if you abort  when  using  ">"  symbol 
   followed  by  something other than "PRN" you may want to  erase  the 
   unwanted file. Generally, it can be found in your current  directory 
   or the root directory.
          Note:  You  needn't use the "/N" switch  during  redirection. 
   DIRUTILS   automatically  make  nonstop  mode  the  default   during 
   redirection,  though this may be overridden with the "/M" switch  if 
   desired.  The  latter  should  be  avoided  entirely  for  disk-file 
   redirection.  The  only time you would want to force  pauses  is  to 
   redirect to a printer--if that printer doesn't have  continuous-feed 
   capability  and  the data might be more than would fit on  a  single 
   sheet. In that case, the "more" prompt to press any key will  appear 
   on  your  printer.  When it does, press any  key.  Because  you  can 
   capture  only two screens on a printed page, at every SECOND  "more" 
   prompt, you would change paper BEFORE pressing a key.

   BATCH FILES

   "Batch" files are a service provided by your operating system. Their 
   creative  use extends DIRUTILS convenience and power. You  may  omit 
   this  subsection  if desired; but if unfamiliar  with  batch  files, 
   there's  no  time like the present to do yourself a huge  favor  and 
   read  about  them  in your manual. Batch files  (files  ending  with 
   ".BAT" which, when their names are typed, execute commands contained 
   within them) are exceptionally easy to learn to exploit. Several are 
   provided  with  DIRUTILS to maximize your use of our  utilities.  In 
   particular,  you'll find them invaluable with ASCOUT to  find  files 
   based upon dates while avoiding the long commands otherwise needed.

   We use batch files regularly. As an illustration we've provided  you 
   with WHATRUNS.BAT--a simple but useful batch file. Its basic command 
   is reproduced below. (The file also contains a couple of  additional 
   commands. They aren't essential to include in your own batch  files, 
   but do help to refresh your memory of the purpose of the file  after 
   lengthy nonuse.)

   "ADIR %1\*.EXE %1\*.COM %1\*.BAT"

   By typing WHATRUNS and a PATH name, all executable files in the PATH 
   directory  (i.e., all files which DO something when you  type  their 
   names)  are displayed by ADIR. (Typing WHATRUNS without a PATH  does 
   the  same  thing for the root directory of your current  drive.)  So 
   typing   "WHATRUNS   \UTILITY"  displays  all   executables   in   a 
   subdirectory  called "UTILITY" off the root directory.

   Note:  If you use a hard disk with subdirectories, it's a good  idea 
   to  edit WHATRUNS.BAT and other sample batch files to  indicate  the 
   full PATH to the DIRUTILS programs themselves. This speeds execution 
   and  ensures  that  the  operating system  will  find  the  programs 
   regardless  of what drive you may be on at the moment. Simply use  a 
   word processor capable of ASCII text output to enter the PATH.  (For 
   WordStar,  use  the  "Nondocument" rather than  "Document"  mode  to 
   create  the  file. In WordPerfect, save the revised  file  to  "DOS" 
   format.) If ADIR.COM is kept in a PATH of "C:\BIN" the above example 
   would become:

   C:\BIN\ADIR %1\*.EXE %1\*.COM %1\*.BAT"

   Also, hard disk users in particular must ensure the operating system 
   can find the batch files THEMSELVES. This is done by a ensuring  you 
   have  a "PATH =" command in your AUTOEXEC.BAT file.  (If  unfamiliar 
   with  AUTOEXEC.BAT, see your operating manual about this  invaluable 
   service.) The following example is a minimal AUTOEXEC.BAT file which 
   you  may  want  to create as an ASCII file and  place  in  the  ROOT 
   directory of the disk you use to "boot" (start) the operating system 
   each time you turn it on. (Creating ASCII files is described above.)
   PROMPT $P$G
   DATE
   TIME
   PATH =C:\;C:\DIRUTILS
   The first command tells the operating system to display the  current 
   directory  whenever it awaits a new command. The next two should  be 
   used ONLY if you don't have a hardware "real time clock" ("RTC")  to 
   set  the  current date and time for you  automatically.  (If  you're 
   unsure  if  you have an RTC, simply type "DATE" after  exiting  this 
   program. If the date is January 1, 1980, you don't have an RTC.  The 
   last command tells the operating system where to search for programs 
   if they can't be found in the default directory you're currently in. 
   In  this  example (substitute your own preferences),  the  operating 
   system would first try the root directory of drive C: ("D:\"),  then 
   a subdirectory called "DIRUTILS" immediately off the root  directory 
   on drive C:. The new AUTOEXEC.BAT features won't be in effect  until 
   the  NEXT time you "boot" off of the disk on which you  created  the 
   file.  If  you  want to use the follow the suggested  PATH  in  this 
   example, you would do the following:
   1) type "C:"               (to move to drive C:)
   2) type "CD \"             (to move to the root directory if you're 
                              not already there)
   3) type "MD DIRUTILS"      (to create the new directory)
   4) type "CD DIRUTILS"      (to move to the new directory)
   5) type "COPY A:*.* /V"    (to copy all files from directory A: to
                              drive C: with copying Verified--this 
                              assumes that your new DIRUTILS files are
                              in drive A:)
   6) type "DIR C:\DIRUTILS"  (to confirm all went OK)
   After  creating this directory and pressing RESET on your  computer, 
   you'll  have access to most DIRUTILS programs and batch  files  from 
   anywhere  on the system in the future--a great convenience and  time 
   saver. The only exceptions are the informational AEORDER and  DUHELP 
   programs,  which will require you to be in the directory  containing 
   their text files to execute.

   You'll  probably find the batch files we provided which  run  ASCOUT 
   for   you  (TODAY.BAT,  BEFORE.BAT,  SINCE.BAT,   FILEDATE.BAT   and 
   BETWEEN.BAT) particularly helpful. Be sure to simply type their name 
   without  the  ".BAT"  extension  to  learn  more  about  them.  (For 
   WHATRUNS.BAT  and TODAY.BAT, it's necessary to type "WHATRUNS ?"  or 
   "TODAY ?" for further information.)

   With  a little imagination, you'll come up with a bundle  of  ideas. 
   Batch files are a "must" for repetitive tasks.
~ (Section 7)
                       << USER-ADDED INFORMATION >>

   Authorized  distributors  and licensed end users may add  notes  and 
   other information for their purposes here. IMPORTANT: Follow a basic 
   computer  precaution of editing ONLY a back-up copy  of  DUHELP.HLP. 
   You  MUST  use only a word processor capable of ASCII  output.  (For 
   WordStar, select "nondocument" rather than normal "document" mode to 
   create  your file. WordPerfect users: Save the output file in  "DOS" 
   format.) 

   IMPORTANT: All text MUST remain below "<< USER-ADDED INFORMATION >>" 
   and  above  "~(Section  8)"--a  line  which  is  not  displayed   by 
   DUHELP.EXE  but  which will appear when using  an  editor--to  avoid 
   potential  adverse  effects  when running this file  with  the  help 
   program. Relatedly, "~(Section  8)" must not be altered in ANY way.
~(Section 8)
              << LICENSE AGREEMENT, CREDITS & DISCLAIMER >>

   ADIR.COM,  ASCOUT.COM, ATREE.COM, CDX.COM, DUHELP.HLP,  AEORDER.HLP, 
   AEORDER.EXE   and  DUHELP.EXE,  plus  all   accompanying   materials 
   (together  referred to as "DIRUTILS" below) are copyright (c)  1989, 
   J.W.  Olsen  /  Advocate Enterprises,  Ltd.,  all  rights  reserved. 
   DUHELP.EXE  is a dedicated version of QHELP.EXE (QHELP.COM for  some 
   operating systems), (c) 1986-89, J.W. Olsen / Advocate  Enterprises, 
   Ltd.,  all  rights  reserved. A full-featured version  of  QHELP  is 
   available  for  sale, accompanied by instructions to  easily  create 
   help  files  on  unlimited topics for your office or  home  with  an 
   ordinary word processor. (See AEORDER for more information.)

   ADVOCATE DIRECTORY UTILITIES, ADVOCATE DIR, ADVOCATE TREE,  ADVOCATE 
   SCOUT,  CHANGE  DIR EXTENDED, QUICK HELP,  DIRUTILS,  ADIR,  ASCOUT, 
   ATREE,  CDX  and  QHELP  are trademarks of  J.W.  Olsen  /  Advocate 
   Enterprises, Ltd. 

   By use of DIRUTILS, user agrees to all terms and conditions in  this 
   section, which constitutes our full agreement.

   J.W.  Olsen  /  Advocate Enterprises, Ltd. has  taken  due  care  in 
   preparing DIRUTILS. However, no expressed or implied warranty as  to  
   accuracy, reliability or suitability for any specific purpose or use 
   is  made. In no event shall J.W. Olsen / Advocate Enterprises,  Ltd. 
   be  liable  for  damages,  including  incidental  or   consequential 
   damages, in connection with or arising from furnishing, performance, 
   support or use of DIRUTILS.

   Upon payment of the proper registration licensing fee, J.W. Olsen  / 
   Advocate  Enterprises, Ltd., will provide the latest,  full-featured 
   version of DIRUTILS (or such member program[s] as the user may  have 
   registered)  and  associated  help  files,  90  days  of  reasonable 
   telephone  and  modem  access support, as well  as  notification  of 
   certain  future  updates  and access  to  same  for  copying/mailing 
   charges only ($10 as of this writing).

   Unregistered  users  of any version may not use them  for  financial 
   gain. Others may use them at ONE SITE or by ONE INDIVIDUAL, but  NOT 
   BOTH.  Subject to the other terms and conditions herein,  registered 
   users may make sufficient copies of DIRUTILS for normal use.

   Users  who  have received a complimentary copy of DIRUTILS  may  not 
   sell  it  to  another party. Other users may  transfer  DIRUTILS  to 
   another  party,  provided such users and  the  subsequent  licensees 
   agree to all terms and conditions herein, and provided all  DIRUTILS 
   materials  are  1) transferred together and 2)  transferred  without 
   alteration.  Further,  by  resale of any copy  of  DIRUTILS,  seller 
   agrees  to  relinquish  any  right to  further  possession,  use  or 
   benefits of said copy or any duplicates made from same.

   For  further  information  and ordering  (including  bulk  rates  or 
   distributorships), see AEORDER or contact:

                 J.W. OLSEN / ADVOCATE ENTERPRISES, LTD.
                     899 S. Plymouth Court, Suite 504
                            Chicago, IL 60605
                          312/939-3300  (voice)
              312/939-4411 (24-hr. modem telecommunications)
~
