Uedit V1.2

   Scientific/Business Systems, P.O. Box 566095,  Atlanta, GA 30356-6002

           ((Use shift-downArrow, to see more of this file.))

Files on this disk:
Uedit           (editor)          Spooler         (print spooler)
Uedit.info      (icon)            Spooler.info    (icon)
Uedit.dat       (Uedit makes this)  

To load, press CTRL & mouse-click these names:

Uedit.manual    (manual)          Uedit.cfg       (defaults & commands)
Uedit.help      (HELP file)       Uedit.funcs     (functions used in commands)
Uedit.doc       (technical)       Uedit.examples  (command examples)
demo            (demo)            Spooler.doc     (how to use)
Uedit.tutorial  (how to use Uedit)

1.    Make  two  copies of this disk.  Keep one to use for recopying purposes,
so you won't be endangering the original everytime you decide to  make  a  new
work  disk,  and  use the other for work.  There isn't much room left for your
text files on Uedit's disk, so you may want to remove  all  of  Uedit's  files
except the following:

       Uedit  Uedit.info  Uedit.help  Uedit.dat
      
The absolute bare bones is Uedit and Uedit.dat.  (No icon, no Help.)

You  can  create  additional  room  on  your work disk by deleting most of the
programs in the "c" subdirectory.  If you do this, be  sure  and  keep  "Say",
"Run" and "Execute", because Uedit needs them.  

Probably  you will want to keep "Copy", "Delete", "Dir" and "Rename" also.  If
you've got two drives, you can clean out everything on the  work  disk  except
Uedit's files.

2.   To  run the demo, press shftAltCtl-d.  To STOP any process, including the
demo, press Amiga-esc.  If you stop the demo before it is finished, make  sure
to select "Load config" in the menu, so as to get rid of the demo stuff stored
in Uedit.  The demo does this automatically, if it is allowed to finish.

3.   This release does not permit selecting different fonts.  It uses the font
of the WorkBench.  

WARNING:  The font must  allow  80  characters  across  the  screen.   Uedit's
displaying  is  based on this font size.  A font with larger characters (sixty
per line instead of 80 per line) will make Uedit  write  beyond  the  screen's
dimensions  and  will  cause  unpredictable  results!   (The WorkBench font is
selected by running Preferences in the WorkBench.)

4.   Uedit can recover in most cases, when it runs out of  memory.   It  packs
buffers and frees any unneeded space it can find.

There are two ways you can crash the Amiga with Uedit:
   1)  You defined a menu without any valid items under its header  and  then
   try to use the menu.  The manual explains this area in great detail.
   2)  There  is  a  severe shortage of memory, or memory is badly fragmented
   after you have done a very long search and replace operation, and  you  do
   something  that  causes  the  Amiga to have to paint either a dialog/alert
   box or a menu.

Remember  that  whenever  the  Amiga  draws  a menu or a dialog/alert box, it
needs RAM in which to paint what you are seeing!

If  you  think there is a severe shortage of memory, avoid anything that will
ask the Amiga to paint a dialog/alert box or a  menu.   In  other  words,  do
whatever  you  can  with  function  keys which will free up as much memory as
possible.  Using function keys keeps the Amiga from having to paint the menu.

Use F2 to save each file.   After  each  file  is  saved,  use  F3  to  close
whichever  ones  you  can  let  go  of.   Especially,  if you just did a long
search and replace or  very  long  insert/delete  operation,  such  as  using
learn  mode, then close that file, in order to free up its fragmented memory.
Then you can reload it again.  Memory won't be fragmented as before.

Until you have done the above:
   1.) Avoid using the menus, because that requires the Amiga to paint  them.
       Don't even press the right mouse button near the title line, because a
       menu may be painted, causing the Amiga to crash.
   2.) Use   function  keys  to  save all files and to close the ones you can
       close.  Avoid function keys which ask a question using a dialog box!

Once the Amiga system software is fixed so that it handles  RAM  shortage  in
a safe, graceful manner, this problem will go away.

5.  If you are writing commands and find a bug in Uedit, please check out your
command first very carefully and look at the documentation  provided  (config,
funcs,  manual,  doc,  and examples).  If you feel certain that you've found a
bug, please report it to us.  Your help will be appreciated.

If you write useful commands, send  them  in.   We'll  distribute  them  in  a
newsletter and along with new releases of Uedit.

6.   Obsolescence:  It is our policy to provide updates to Uedit at lower cost
to purchasers of earlier releases.  Also every effort will be made to  see  to
it  that  whatever  commands  you  are  using  won't  become obsolete with new
releases of Uedit.

7.  Copy protection:  Uedit is not copy protected.  We feel strongly that copy
protection  is  petty  and  a nuisance.  If we provided a paperback manual, we
would  not  be  ripped  off  as  much as we leave ourselves open to by putting
everything on the distribution disk like we do.  But it costs a lot to print a
paperback.   Besides,  why  have  to  kill  trees  to  print a paperback, when
everything you need can be on-line, ready to be pulled into the editor anytime
you need it?  

We are counting on you to support us in our policy of openness.