 BELLS!  A. Robert s, 1982-97 v 2.36, December, 1997
                 For Psion 3a and 3c

                       Index
                       -----
               1   Ownership
               2   Introduction
               3   Basics
               4   Contents
               5   Program installation
               6   Data files installation
               7   First time use and registration
               8   Memory usage
               9   Warnings
              10   Upgrades
              11   Upgrade notes
              12   Bugs, Improvements, Praise

1  Ownership
   ---------
This is "CharityWare", all  proceeds  go  to  the  Surrey
Association of Church Bell Ringers Bell Restoration Fund.
It is keyword protected; registration costs 10.  You may
pass  on  complete  copies  as supplied, but each must be
separately registered. Send money to me:
  Alan Roberts, 1 May Cottages, Monkswell Lane,
  Mugswell, COULSDON, Surrey CR5 3SX

2  Introduction
   ------------
The program is big, bloody huge  in  fact.  I  have  been
writing  it since 1982, on various computers. History.wrd
tells the development story on the Psion 3a  and  there's
a beginner's guide in Beginner.wrd.

3  Basics
   ------
This is a bell-ringing program, it simulates  aspects  of
tower-bell  ringing.  It  is  in five sections, each with
sub-modules; not all need to  be  installed  (for  memory
saving).
RING: rings  methods to touches, up to 10-spliced on 3-20
and call changes. Ring 4 in hand with me,  or  watch  the
St.Wally's ringers get it right
BLUE: draws lines in methods and splicing touches.
METHOD: entry/editing of place notation, over 120 on file
and SIRIL files are also available with over 10,000.
ERRATIC: does naff ringing, to test competition judges.
CONTROL:  simulates one bell to show how the tower works.
You design the tower, and then try to ring it.

4  Contents
   --------
Main program
  Bells!!!.OPA  core program
  Bells!$M.OPO  method handling and decoding
  Bells!$Z.OPO  time waster
  Bells!$Z.FON  font for time waster
  Bells!$Z.TXT  text for time waster
  Bells!$Z.OPD  data for time waster
  BellsGen.HLP  general help
  BellsMsg.HLP  error messages
  BellsVer.LST  list of latest files
Blue Lines: draw method lines
  BellsBlu.OPO  section file
  BellsBlu.HLP  help
Control: demonstrate bell control
  BellsCtl.OPO  section file
  BellsCtl.HLP  help
  BellsHit.WVE  sound of stay hit
  BellsBrk.WVE  sound of stay break
  BellsSlp.WVE  sound of grip slip
Erratic ringing: ring erratically 
  BellsErr.OPO  section flie
  BellsE$H.OPO  sound output (see Warnings below)
  BellsErr.HLP  help
Notation editor: enter/edit/load/save notation
  BellsNot.OPO  section file
  BellsN$E.OPO  module: internal format editor
  BellsN$S.OPO  module: SIRIL format editor
  BellsN$V.OPO  module: visual enter/edit
  SirilOdd.END  SIRIL codes, even bells
  SirilEvn.END  SIRIL codes, odd bells
  BellsNot.HLP  help
Ringing: ring method/call changes
  BellsRng.OPO  section file
  BellsR$R.OPO  module: text output ringing
  BellsR$W.OPO  module: St.Wally's graphical ring
  BellsRng.HLP  help
  BellsR$W.FON  St.Wally's female font
  BellsR$M.FON  St.Wally's male font
OPO files are overlays and will not run alone.

Word/text files not needed to run the program:
  !readme!.txt  this file
  History.wrd   development history
  Beginner.wrd  guided tour of the package

5  Program installation
   --------------------
Bells!!!.OPA goes in \APP\ directory on any drive and  is
installed  with Psion-I as normal. All other files (*.OPO
*.HLP,*.FON,*.MTH,*.TCH,*.END,*.TXT,*.LST,*.WVE)   go  in
\APP\BELLS\  directory.  Any  microSIRIL  files can go in
\APP\Bells\Siril\, on any drive; don't rename  them,  but
you can add extensions (e.g. *.srl).
Files  can  be spread across drives MABC if you use Drive
Scanning (see the Settings menu). Scans end on the  drive
that Bells!!!.OPA is on.

6  Data files installation
   -----------------------
Methods (Methods.MTH),  touches  (Touches.TCH), plus  two
of  SIRIL  tables (SirilEvn.END, SirilOdd.END). They are
all editable using DATA. *.MTH and  *.TCH  files  can  be
modified by the program, so should live in RAM.
The program expects *.MTH files to be in \APP\Bells\  and
lists them all under the icon.
*.TCH files can go anywhere and the TCH extension is  not
mandatory.  They are used by Ring and Line, I ask for one
only when I need it. I store the name and path  for  easy
finding next time.  You can generate files from the touch
dialogs, but they won't have the helpful  labels  of  the
supplied file.

7  First time use and Registration
   -------------------------------
Press <q> in the Top Menu,  then enter your name and code
to unlock some facilities.  A file, \APP\BELLS\Bells.reg,
is created to hold it; it is specific to you a nd  is  of
no use to anyone wanting to use Bells without paying.

8  Memory usage
   ------------
The program uses not less that 42k when caching,  more if
possible.  Modules  loaded  stay in memory until space is
needed for others, to improve speed.  I  get worried when
free  memory  drops  below 32k, and will then remove some
modules from memory to avoid crashes.
To save space, any section file can be omitted  with  its
modules  and  files.  Individual  files can be omitted as
well, e.g.:
  Graphical notation entry [BellsN$V.OPO]
  SIRIL editor [BellsN$S.OPO]
  St.Wally's [BellsR$W.OPO, BellsR$M.FON, BellsR$W.FON]
etc. Menus will omit facilities carried out by missing
modules.

9  Warnings
   --------
Caps lock: Make sure Caps lock is off.
Methods file: Some typos were corrected in version  2.29.
  I don't guarantee accuracy of methods in the file.
Erratic striking: The sound routine runs as a  background
  task  and  ignores the keyboard. It has no output other
  than sound.  It should never be left stranded,  but  if
  it  does,  go  to the System screen and select BellsE$H
  in the RunOpl list (highlighted)  and  "Kill"  it  with
  Psion-Shift-K.

10 Upgrades
   --------
Upgrades are free to existing owners. There  is  no  need
for  re-registration.  Notification  of new versions will
be given in  the  Psion  groups  on  Usenet.  The  latest
version  should  be available on Surrey's web site, or by
post on DOS 3.5" disc (you provide in SAE), or Psion  ssd
(256k  minimum, you supply in SAE), or e-mail (ZIPped and
UU or MIME encoded, state preference).

11 Upgrade notes
   -------------
From 2.33 or earlier:
  Format of touch files changed, automatic upgrade  works
  if you have a comment in the first entry.
From 2.29 or earlier:
  All files created go in \APP\BELLS\ on default drive.
From 2.28 or earlier:
  Help file format changed, old files will not work.
From 2.27 or earlier:
  Bells!$Z.OPO and BellsR$W.FON much smaller.  Help files
  *.HLP  in  new  format, won't work with Sys$hlp.opo you
  can delete it. 
From 2.26 or earlier:
  *.MTH and *.TCH now live in  \APP\BELLS\.  Files  (INI,
  OPD,  TXT, PIC) now in \APP\BELLS\, any named BELLS*.*
  in \OPD\ or \PIC\ will be moved.
From 2.24 or earlier:
  BellsLog.TXT format changed, delete previous version.
From 2.22 or earlier:
  Bells!$A.OPO no longer used, delete it.
From 2.19 or earlier:
  Now far fewer OPO files, delete all previous OPO files.
  Format of INI file for Blue Lines changed.
From 2.17 or earlier:
  INI files now not editable.  Run Convert.OPO to convert
  old files, then delete it.
From 2.15 or earlier:
  BellsB$D.OPO replaced with  BellsB$O.OPO,  BellsB$L.OPO
  and  BellsB$C.OPO.  Touches  file can have any name and
  extension, and be stored anywhere. Database  of  screen
  dumps (M:\OPD\BellsBlu.OPD) has new format.
From 2.13 or earlier:
  Bells!$F.OPO no longer needed. Methods file now  called
  *.MTH,  lives in DAT directory. Touches file now called
  *.TCH, lives anywhere.
From 2.11 or earlier: 
  Help files all now *.HLP, delete previous *.TXT  files,
  can be read only using Tom Dilbilin's Help System.

12 Bugs, Improvements, Praise
   --------------------------
Please report any bugs for correction, or new  ideas  for
improvement to me by post (address in item 1) or e-mail:
  Alan.Roberts@rd.bbc.co.uk
It would help if you tell me what version you have.  Also
please  do  a  file  check (c> from Top Menu), to confirm
(or deny) that you have correct files  before  panicking.

