rtsi.com/2014.01.www.rtsi.com.tar/www.rtsi.com/OS9/OSK/MISC/speedisk.lzh/quikdoc

Text File | 1994-04-01 | 5KB | 114 lines

               - - - - - - - - - - - - - - - - - - - - - -
               - - - - - >   Speedisk  v2.10   < - - - - -
               - - - - - - - - - - - - - - - - - - - - - -


Included in this archive:
    - quikdoc:        This file.
    - sddemo:        Disk de-fragmenter (demo version only)


Quick Documentation for Speedisk:
=================================
To get a quick summary of Speedisk usage, type "SDDemo -?":


Speedisk v2.10 (Demo) -- Copyright (c) 1994 by Dynamic Systems

Usage:    Speedisk [<opts>] [<device>] [<opts>]

        If no device is specified, the device containing the current
        working directory is used.

Options:
        -a        Accept some disk errors as okay and continue
        -b=<num>  Limit temporary file storage to <num> kilobytes of RAM
        -d        Don't put directories at the front of the disk
        -e        Don't put executable files before others
        -f        Don't use fullscreen display
        -o        Optimize now (batch mode)
        -r=<num>  Use <num> kilobytes of RAM for read/write buffer
        -t=<num>  Limit optimization time to <num> minutes (batch mode)
        -v        Verify all disk writes
        -w        Wipe free space after optimization (for security)


The options work as described.  The amount of RAM used for storing files
that have gotten in the way of other files is specified with the "-b=n"
option.  This memory is dynamically allocated as it is needed.  The
default is to use all available memory.  Setting this option to 0 will
ensure that no files are kept in memory.  Directories and bootfiles are
_never_ kept in memory regardless of this setting.

Speedisk puts directories and executable programs ahead of others for
fastest access to these important files.  To override this, use the "-d"
and "-e" options, respectively.

When running under KWindows or Termcap, Speedisk will use a nice display
that will seem familiar to anyone who has used Norton Speed Disk 4.50.
If either of the "-f" or "-o" options is specified, output will be in a
simple tty mode that uses no control characters other than <backspace>
and <cr>.

Files that are being moved from one place on the disk to another go
through the read/write buffer.  Using the "-r=n" option will set the
size of this buffer.  This memory is allocated on program startup.  The
default is currently 128k.  Set this option high if you have a lot of
large files.  Small files don't use the whole buffer and do better being
kept in the temporary file buffer (which cannot use memory allocated to
the r/w buffer).

To verify all disk writes, use the "-v" option.  This option will find
defective disk blocks by noticing that reading from that sector will not
produce what was supposed to have been written.  Speedisk will
automatically position the file around that bad cluster as well as map
it out so RBF won't try to access it.  Turning verify "on" will also
allocate another buffer equal in size to the read/write buffer for use
during verification.

If security is important, then you may wish to use the "-w" option to
have Speedisk overwrite all free disk space once the optimization is
complete.  This ensures that no sensitive data is just left lying around
on the disk.


Speedisk is intelligent and failsafe.  Before any action is performed on
the disk, it goes through a rigorous test (more so than DCheck) to
ensure that it is logically intact.  If any error is found, a message is
displayed and Speedisk will not allow optimization.

A statistics report of the disk is available.  File & Directory frag-
mentation precentages are a percentage of the number of files and
directories that have more than one segment.  Free space fragmentation
is the amount of free space that is outside of the largest block.

A boot file will automatically be placed at the end of the disk since it
is only accessed during boot and thus doesn't need fast access via the
file system.  Rules for boot files, both old and new style, are observed
when a move is attempted.  LSN0's boot record is properly updated.

Directories and boot files are NEVER stored temporarily in ram.  This
helps avoid serious disk problems in case of power failure, etc.

Speedisk will recognize hard linked files and directories and handle
them properly even though DCheck will report them as errors.  (Hard
links are multiple directory entries for the same physical file.)


To minimize problems due to uncontrollable events (such as power
outage), Speedisk tries to maintain the disk in as fit a shape as
possible throughout optimization.  Even in the event of such a
catastrophy, the disk structure and all its files (except any held in
the temp-file buffer) should still be accessible.  The biggest problem
would be the free-space map.  Unless Speedisk will give the media a
clean bill of health, do not write anything to that disk!  Speedisk has
the ability to recover the disk from any invalid state it may have left
the disk in.  Run Speedisk again with the "-a" option.  If Speedisk then
says the disk is okay you can restart the optimization and, upon
completion, the disk structure will be repaired.  If another program
were to access the disk or a disk write only partially completed, then
it is possible this step will fail.  Should this happen, copy all valid
files to another device, re-format, and copy them back.

                                        Brian