home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
GEMini Atari
/
GEMini_Atari_CD-ROM_Walnut_Creek_December_1993.iso
/
files
/
bbs
/
fn132bin
/
conv
/
conv33d.doc
< prev
next >
Wrap
Text File
|
1991-09-02
|
6KB
|
125 lines
Documentation for the STadel 3.3d to Fnordadel converter:
-----------------------------------------------------------
[ Since conv33d.tos is a use-it-once, throw-it-away hack, I figure a nice
neat man page is a waste of time too, so here goes... --aa ]
What The Program Is For:
------------------------
Conv33d.tos will take an STadel 3.3d system and convert its data files
to formats acceptable to Fnordadel. If you're using some other version
of STadel:
o If it's 3.4a, then conv33d may work; if it doesn't, we can
probably arrange to hack it a bit to make it work. I don't
know if 3.4a ever saw the light of day, so it may be that
nobody has a system running it.
o If it's something else, then conv33d will almost certainly NOT
work. If you're in this position, you can either (A) Find a
copy of an STadel 3.3d distribution and run whatever conversion
programs were in there to take users of previous versions up
to 3.3d, and THEN run conv33d, or (B) Beg and plead with us and
we'll see what, if anything, can be done.
PLEASE NOTE: You must use the version of conv33d that came with whatever
version of Fnordadel you'll be using; if data files have changed between
Fnordadel revisions (as often happens) then using a converter from a
different version of Fnordadel isn't going to help you very much.
Stuff You Must Do First:
-----------------------
1) MAKE BACKUPS. Conv33d munches on your BBS, and although it was well
behaved when I tested it, one never knows...
2) Place a copy of conv33d.tos in the directory which contains the
ctdltabl.sys file from your STadel system. Conv33d expects to be run
from this directory, just like all the normal STadel programs.
THEN:
----
3) Run conv33d by double-clicking or, if you're a winner and use a shell,
by typing 'conv33d'. The program will munch your sysfiles, producing
lots of noise. Make sure that none of the noise looks threatening.
When it's finished, it will have done the following in your #sysdir:
o The STadel rooms file, 'ctdlroom.sys', will be renamed to
'ctdlroom.33d' and in its place will be the Fnordadel room
files, one per room, named "roomnnnn.sys" where 'nnnn' is a
number from 0000 to 0063.
o The STadel log file, 'ctdllog.sys' will be replaced with the
new Fnordadel one; the old one will be renamed to
'ctdllog.33d'. The new one will be slightly smaller.
o The STadel floors file, 'ctdlflr.sys' will be replaced with
the new Fnordadel one; the old one is left as 'ctdlflr.33d'.
The new one will be slightly smaller.
And the following will have happened in #netdir:
o The STadel net list, 'ctdlnet.sys', will be replaced with the
new Fnordadel one, and the old one will be renamed to
'ctdlnet.33d'. The new one should be a bit smaller.
Stuff You Must Do Afterwards:
-----------------------------
4) You should delete the file "ctdlloop.zap" from your #netdir, if it
exists. This file contains the data for the loop-zapper; Fnordadel
uses a different format for this data than does STadel. If you wish
to recreate a loop-zapper database from your existing message base,
you can use the Fnordadel utility "makezt.tos"; refer to makezt.man
for details. Otherwise you can just let the loop-zapper rebuild itself
over time.
5) You MUST MUST MUST edit ctdlcnfg.sys! Many things are different, so
the best idea is usually to print out a copy of your old ctdlcnfg.sys
file from your STadel system, or keep it in a second editor buffer,
for reference while you edit a copy of the Fnordadel ctdlcnfg.sys
file. A fully commented version is distributed as "ctdlcnfg.doc".
Please note especially that you MUST define the ctdlcnfg.sys variables
"maxrooms", "mailslots" and "sharedrooms" as 64, 58 and 16 respectively.
These values were fixed under STadel; they may be edited to anything
you like under Fnordadel, but since you already have a running system
based on those values (64, 58, and 16), you must use one of the
supplied utilities to change any of these values. Do NOT simply edit
one of these values in ctdlcnfg.sys and attempt to reconfigure; it will
cause a rude message from configur at best, chaos at worst.
6) You must delete your old ctdltabl.sys file, and then run the
Fnordadel configur.tos program to generate a new ctdltabl.sys.
BE VERY CAREFUL not to mix up STadel and Fnordadel binaries! Best thing
to do is nuke the old STadel ones and move the Fnordadel ones into their
places.
Other Random Stuff You Should Do or Know:
-----------------------------------------
o Your STadel help files directory should be replaced wholesale with the
Fnordadel help files. A few files will need editing (some .blb files,
localbbs.hlp, and so on) and you can probably keep some of your old .blbs.
o You should go through the net list and make sure that everything is as
you think you left it; maybe edit each of the nodes to make sure that
all is well. For all systems in your net list who run Citadel-86 or
a direct variant (i.e. Citadel-68k for the Amiga), you should toggle
the "C-86" flag in their net entries; this is done by editing the node
and typing 'T'. This helps Fnordadel network better with such systems.
If you have any problems with the conversion process or with the Fnordadel
system after conversion, drop us a line and we'll try to help.
-Adrian Ashley (elim @ secret)
Royce Howland (Mr. Neutron @ RT)