Upgrading from v2.03 to v2.04
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The upgrade for Celerity BBS v2.03 should be pretty simple. You can either
select the "Upgrade Celerity BBS" option from the INSTALL program, or you can
copy the following files over your old files:

CEL204-1.ZIP :  CELERITY.EXE, CELERITY.OVR
CEL204-2.ZIP :  CELSETUP.EXE

You will also need to update your language files.  You can import the
TEXTCODE.UPG file (contained in CEL204-3.ZIP - the documentation directory)
into your existing language file with the Alt-F6 command in the language
editor.  If you do not maintain your own language files, you may either
download a language/menu set from the support BBS, use the default LANGUAGE.*
and MENU.* from CEL204-2.ZIP, or obtain additional language/menu sets
elsewhere.

Current versions of some third party utilities may be found in the CEL204-4.ZIP
and CEL204-6 archives.  Extract them for details on upgrading to current
versions.

Read the bottom of the REVISION.TXT file for details pertaining to v2.04,
including a list of bug fixes, new features, improvments, changes, and for
which items in CELSETUP you should pay particular attention to.



Upgrading from v2.02 to v2.04
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Upgrading from v2.02 to v2.04 will be similar to the above, except that there
are some additional considerations you will need to take into account.

There were some language file changes in 2.03 which are not included in the
current TEXTCODE.UPG.  If you use the default 2.04 language files you should
have no problems.  If not, you should get the TEXTCODE.UPG from the v2.03
package and import those changes as well.

You will need to change all instances of the @XFERLEVEL@ command directive to
@XLEVEL@.

The access level control system changed somewhat from 2.02 to 2.03/2.04, and
may not be completely compatible with your old access conditions - please test
all access to critical areas to ensure that there are no problems.  Review the
"Celerity Access Conditions" in the documentation for details.  Sysops are no
longer exempt from all access checks, but using the temporary sysop key WILL
cause the account to pass any access checks for testing.  ALL OF YOUR "SL=10"
TYPE ACCESS CHECKS SHOULD BE REPLACED WITH "SL>=10", or users with an access
level greater than 10 will be excluded from this check!

User transfer statistics have been changed from a byte-based system to a
kilobyte-based system (some BBS' had problems with users who had uploaded more
than 2.2 gigabytes).  This means that if you have any older utilities which
affect a user's transfer statistics, you should get updated versions before
running them on a v2.03 user list.  Your top ten listing will also be out of
whack.  You can delete the TOPTEN.DAT file from your DATA directory and it will
eventually be recreated, or run the FIXTOP.EXE utility which will conver the
top ten data for you.

Please be aware that Celerity now tracks the user's upload/download ratio via a
seperate set of statistics, rather than her total upload and download
statistics.  These can be edited in the user custodian, and these are what
should be changed if you wish to change the ratio that the user has (not the
required ratio, which is changed normally).

Your NODESC.BBS file (in the DISPLAY directory) is no longer used and can be
erased.

A new file type, with an .LST extension, may begin to appear in your user save
(Email Uploads) directory.  These are saved batch download queues, and may be
deleted without harm.

You need to move your PROTOCOL.DAT file from your DATA directory to your NODE
directory (all node directories in a multi-node system).


Upgrading from v2.00/2.01
~~~~~~~~~~~~~~~~~~~~~~~~~
It is recommended that you locate some 2.04 certified language and menu files
if upgrading from such an old version (LANGUAGE.* and MENU.* from the
CEL204-3.ZIP archive will work).  If you really want to preserve your old
files, you can download the TEXTCODE.UPG files from each release through the
present and import them into your existing language file with the Alt-F6
command in the language editor.

Additionally, you will need to delete all *.QS? files from your DATA directory,
and users will be required to re-configure their global newscan / QWK
configurations.


Upgrading from Celerity v1.xx
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Due to the huge number of changes in Celerity v2.0, it is recommended that you
set up a completely new BBS to run 2.0, and migrate your old information into
it rather than just throwing the new .EXE into your Celerity directory.  Some
files do not work in the way they used to, some data files will no longer be
used (and thus take up storage space), and some files have changed location.
All electronic mail will be lost.  All information scripts will be lost.  All
message sections and conference setup will be lost.  File areas and
descriptions may be converted.

1:  Download the README.200 file from the Celerity Support BBS at 310-693-9405
    and read the file in its entirety.  Also read the entries in REVISION.TXT
    pertaining to all versions from 2.00 through the version you are
    installing.  A lot of this information is rather dull, but it is important
    to know how things have changed for a better understanding of why things
    work the way they do.

2:  Set up the new Celerity 2.0 BBS.  The install program will do this in an
    automated fashion for you.  You may install the demo files if you wish,
    although they are not required when you upgrade, they may help you learn
    how 2.0x conferencing works.

3:  Copy your USERS & SETUP.DAT files to the BBS directory and node directory
    of the 2.0x system.  SETUP.DAT is roughly compatible, and will be updated
    when you run CELSETUP.EXE.  The user data file (USERS) from versions 1.42,
    1.50, 2.00, and other 2.0x versions will be automatically converted when
    Celerity is run.

4:  Copy the following from your old BBS directory to your new DATA directory:
    HISTORY.DAT, ONELINER.DAT, TOPTEN.DAT

5:  Delete the following files which are incompatible with 2.0x:
    BBS Directory: DOORS.DAT
                   GALLERY.DAT
                   USERVOTE.DAT

6:  Run the 2.0 BBS.  Log on, move around a bit.  You will need to create a new
    conference tree for your message bases and transfer sections.  If you wish
    to "import" your old file areas, you should do the following (and also look
    in README.200 at around line #800):

    a: go ahead and create sections in the conference tree where you want your
       old transfer conferences to go.  Make a note of the data name (*.XFR)
       given to the file.

    b: Copy your old AREADIR.* files over the newly created *.XFR files (ie:
       AREADIR.1 will be copied over  XFRCNF1.XFR, for example)

    c: Back up all your .DIR files.  Run the CONVFILE.EXE utility from the
       directory where the .DIR files reside.

    d: Run the BBS and enter each new transfer conference to make sure they
       function.

    e: You may wish to change the attributes of the different areas, as well as
       possibly changing the pathname of the DATA files if you have them in a
       new location.  The FIXFILE.PAS and FIXFILE.EXE utilty and source will do
       this in a bulk manner.


