>>>>>> NETWORKS and POCKETD PLUS

 If  you own a network, or are responsible for looking after one,  then
 you  should take a serious look at PocketD. Managing a networked  hard
 disk  without PocketD is a bit like needlework in boxing gloves.  Once
 you  have become used to the power that PocketD provides, you may feel
 helpless without it!

>>>> How  often  has a network  adminstrator sat there and  watched  in
     disbelief as the Novell VOLINFO "Free Space" list seeped away....

     PocketD Plus can tell you WHO is swallowing up the space, and how!
     If you move to the directory where the user accounts are and type:

     D /rr:-3g%ss   This  will analyse the user directories looking for
		    files  created during the  last 3 days, plotting  a
		    (g)raphic  barchart, showing the percentage of  new
		    files  that  each  user has created,  plotting  the
		    results in order of offending user (sort by size).

     (If  the user accounts are scattered across several drives, then a
     command of the form D H:\USER1 S: Q:\USER2 /rr:-3g%ss is possible)

     >>> WHAT ARE THESE FILES?

     D /Se:-3g%ss   This  will give a  similar display, but grouped  by
		    extension  instead of user. The administrator might
		    then see that 25% of new files are *.TMP files.

     D /SQz:-3      This  will allow the administrator to browse a list
		    of  these files, with options to individually  view
		    or delete them.


>>>> You are losing space on your server. Some files MUST go!

     D H: I: *.TMP *.$$$ /Wzz
		    Will  search  the (W)hole  of drives H: and I:  and
		    delete all files matching *.TMP or *.$$$.

     D H: I: *.EXE /W:-2 [if exist $p$n.PAS del $w]RQ
		    Will  delete files  with the name XXXX.EXE  created
		    during  the  last 2  days, if a corresponding  file
		    XXXX.PAS exists in the same directory. The optional
		    "Q" parameter lets you query each deletion.

     D H: I: *.BAK /W [D $p$n.* /- .BAK .EXE .COM .OBJ [del $w]R~]R
		    This  more  general  example will delete any  *.BAK
		    file where a corresponding file with the same name,
		    excepting   extensions  .BAK  .EXE  .COM  or  .OBJ,
		    already exists.


>>>> You want to BACKUP files that may be in use by another user?

     D /WTccpio C:  Will  search the  (W)hole drive for files  modified
		    (T)oday  and (c)opy them with full (p)aths to drive
		    C:,  but  (i)gnoring  files that cannot be  opened,
		    looping  round returning to copy these later  (when
		    they become available for copying).

>>>> You want to provide a useful tool for your users?

     D /STcc A:     Will allow the users to (S)earch for all files they
		    modified (T)oday and (c)opy them to drive A:

     D              !!!  This will give the users an attractive colored
		    directory  listing, allowing them to classify files
		    by color.

     MENUD          This  gives the users a plush menu-driven interface
		    for managing their files.


>>>> You want extra helpful tool to let you monitor the network?

     It  would  be nice if your  LOGIN script could warn you if a  disk
     partition is nearly full. e.g.

	 D S: U: Z: :: /{4096k [Warning! $f has only $s bytes free!!//]

     This  will report if any of drives  S: U: or Z: have 4 meg or less
     free disk space.


>>>> You want to ensure that large files on the network are INDEXED

	 D /W!EF}200k [FLAG $w i]R

     This will find non-executable files bigger than 200k, and set them
     to  "INDEXED",  thus  somewhat  speeding up access to  such  files
     (NOVELL 2.X).

See also README.D for useful ARCHIVE examples.