                         TaskMaster   Xemik, July 1992
                         ==============================

Version v0.38a Release Notes
----------------------------
TaskMaster is of greatest value if it is installed on a hard-disk and
loaded when the computer is booted.  (A text file '!BootTxt' containing
the appropriate lines is included in the documents directory.)  Provided
you do not mind inserting the disk occasionally, TaskMaster will run quite
happily on a floppy-only system.

The program checks the variable <TaskMaster$Dir> to ensure that it is not
already loaded.  The program unsets this variable when it is exited cleanly
and after an internal error. It will also reload after a soft-reset, if the
'Unset' line is included in the !Boot file.


Yes, but what does it do?
-------------------------
TaskMaster works by executing '*' commands from within the desktop
environment. In fact, because most things on the Archimedes can be run
by the use of '*' commands, this can very useful.

TaskMaster provides the following facilities:

 - the ability to run frequently used Applications, or open frequently used
   directories, without the user needing to go through the directory
   structure.
 - a user-created menu to run all those indispensable utilities from
 - the facility to open directory viewers and/or !Application directories
 - a file deletion utility
 - free memory display
 - internal speaker on/off toggle
 - save CMOS setting

So how do I use it?
-------------------
TaskMaster uses three text files to store the user's commands:-

Apps  : Applications which will load onto the icon bar
Dirs  : Directory paths to be opened
Other : Other OS commands / utilities, etc.

The files should contain only the commands indicated above, but any valid
OS Commands may be entered in the Apps & Other files. However, ONLY valid
directory paths must be entered in the Dirs file, because the program will
prefix each directory path with the OS 'Filer_OpenDir' command.

One of my requirements for the program was that it must not take up more
than 32K of memory, i.e. one page on a 4Meg machine.  For this reason, and
to keep the menu structure to a sensible size, a maximum of 20 commands
will be read from each file.

If any of the above files do not exist, it will be created.  When the file
has been created, or if it exists but is empty, the menu option associated
with the file will not be selectable.

Each command in the file must be entered on a separate line.  The form
required is a brief description of up to 12 characters, separated from the
OS command by a comma, (i.e. <description>,<command>)

It is not possible to enter a more than one OS command at each option.
By creating a command file or an obey file, and saving this in the (say)
library directory, more complex commands are possible.  The file can then
be run by using the file name as the command.


THE MENUS IN DETAIL
===================

Applications Menu
-----------------
This menu is intended for applications which will install themselves onto
the Icon Bar.  The full path of the Application is required, but systems
variables are allowed as part of the path name, e.g. <Graphics$Dir>!Paint.

NB If an application runs but its icon has not installed on the Icon Bar,
   this is probably because the application's icons have not been loaded.
   Try adding the following line to its !Run file:

          IconSprites <Obey$Dir>.!Sprites

     OR

          Run <Obey$Dir>.!Boot


Directories Menu
----------------
The Directories menu allows frequently used directories to be opened using
the OS Filer_OpenDir command.  The full path is required, but unlike the
Filer_OpenDir command, system variables ARE allowed.  So, from the above
example, <Graphics$Dir>!Paint will OPEN the !Paint application directory.

!Applications may also be opened by dragging the application's icon from
the Filer window onto the TaskMaster icon.

The Directories menu does not, however, observe the Acorn convention of
remaining open when items are selected with the Adjust button.  This is
because a Filer window may obscure the menu structure when it is opened.
(If anyone knows how to prevent the Filer window from overwriting the menu
structure, I would like to hear from you!)


Other Menu
----------
This menu is intended for those useful odds and ends that make using the
computer a little easier.  For example, to reconfigure the computer, or
may be (say) to backup from :0 to :0.


Utilities Menu
--------------
This menu allows selection of commands provided by TaskMaster.

Currently these are:
Eraser         - re-installs Eraser after it has been QUIT
Memory Free    - toggles the free memory display. Although TaskMaster only
                 takes less than two polls per second, it may be worth
                 noting here that if the free memory is NOT displayed, null
                 polls will not be returned to TaskMaster. (Free memory can
                 still be checked by viewing 'Info' from the main menu)
Speaker on/off - the current speaker state is checked when the menu is
                 opened, and the command is set appropriately.  Please note
                 that this will show the action that will be performed if
                 the option is clicked on.  It is NOT the current speaker
                 state, but rather the opposite of it
Save CMOS      - save current CMOS settings to a file in the resources
                 directory
System Reset   - performs a system reset via software. If the file 'CmosRam'
                 exists, its contents will be loaded to the CMOS before the
                 reset is performed. Otherwise, the reset will be performed
                 using the current settings.
                 (N.B. Because of ROM speed problems (RISC OS 3.1) which
                  Acorn seem unable to redress, this is not included in the
                  release version.  However, a RESTORE CMOS option will
                  replace it.)


Building the files
------------------
TaskMaster allows the user to drag applications to a setup window for ease
of setup.  To prevent excessive memory overheads, a restriction of 128
characters has been placed on the path which can be dragged to the window.
This allows a directory structure of about 10-deep.
Some commands may not require a file to be dragged onto the Setup Window,
so the Command box can be edited as required.  It is up to the user to
ensure that valid commands are entered.  The new commands are always added
at the end of the file.  However, the files are in text format, and so can
be edited as required.

Click <SELECT> on the TaskMaster icon to open the setup window.

NB This version of TaskMaster must be QUIT, and reloaded to utilise the new
   commands.  The release version updates the menus immediately.  However,
   TaskMaster CANNOT remove commands from the files.  Delete them using a
   text editor.  (Come on now, do you want me to make the coffee as well?)
   Although there is a restriction on the path size, this version does not
   check that this is exceeded.

The easy way to lose your files!
--------------------------------
Eraser allows you to delete files by using the ADFS *WIPE command. Thefour
wipe options can be selected from the 'Wipe Options' sub-menu.  The current
settings can be saved by selecting 'Save Options' from the Eraser main menu
and they will become the default settings when TaskMaster is next run.
Eraser will be disabled by selecting 'Quit' on the Eraser main menu.  To
re-activate Eraser, select 'Eraser' from TaskMaster's 'Utilities' sub-menu.

NB If Eraser is removed and re-activated, the default settings will NOT be
   reloaded.  The last WIPE options selected will remain active.

   Because each file / directory has to be passed to the *WIPE command,
   using the Confirm or Verbose option becomes a pain after a while. Try
   it and you'll see what I mean.  Don't blame me, that's the ADFS for
   you.  Personally, I use Force and Recurse only.
   
   Eraser can be used with other filing systems.  ADFS only allows a 
   maximum of 77 objects per directory.  TaskMaster DIMensions an array of
   77, so in filing systems which allow a greater number, e.g. MultiFS, DO
   NOT selected more than 77 objects for deletion.  (If this number is
   exceeded TaskMaster will simple generate an error, and closedown, 
   leaving the desktop unaffected.  BUT DON'T TAKE CHANCES.  If you're not
   sure, delete a small selection at a time.)


TaskMaster and the ARM3 (Release version only)
-----------------------
TaskMaster will toggle the ARM3 cache by clicking <ADJUST> on the
TaskMaster icon.  (Although RISC OS 3.1 is required for this facility,
TaskMaster works unchanged on systems with RISC OS 2.00 and/or no ARM3.)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Finally, thanks to Chris Dawson of Supreme Software Support for the
extensive testing of all pre-release versions, and for his comments and
suggestions, MOST of which were greatly appreciated.