home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
CEL202R.ZIP
/
CEL202-3.ZIP
/
UPGRADE.DOC
< prev
Wrap
Text File
|
1994-08-26
|
5KB
|
96 lines
Upgrading to Celerity v2.02
~~~~~~~~~~~~~~~~~~~~~~~~~~~
The upgrade for Celerity BBS v2.00/2.01 to Celerity v2.02 is virtually
transparent. You can either select the "Upgrade Celerity BBS" option from the
INSTALL program, or you can copy the following files over your old files:
CEL202-1.ZIP : CELERITY.EXE, CELERITY.OVR
CEL202-2.ZIP : CELSETUP.EXE, SYSTEM.KBD
You will also need to update your language files. You can import the
TEXTCODE.UPG file (contained in CEL202-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 CEL202-2.ZIP, or obtain additional language/menu sets
elsewhere.
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.
Current versions of some third party utilities may be found in the CEL202-4.ZIP
and CEL202-6 archives. Extract them for details on upgrading to current
versions.
Read the bottom of the REVISION.DOC file for details pertaining to 202 and for
which items in CELSETUP you should pay particular attention to.
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.DOC
pertaining to version 2.00 and 2.01. A lot of this information is rather
dull, but it is important for beta sites to have an understanding of how
2.0 works and why it works.
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.02 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 2.01 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.
7: I have probably left out quite a few details of what you need to do to get
2.0 up and running with your old data. Please consider that I have never
converted a 1.42 BBS to 2.0 - 2.0 has developed along the way. Help and
the experiences of other sysops will be available on the technical support
BBSes following the release.