home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Fresh Fish 8
/
FreshFishVol8-CD1.bin
/
new
/
comm
/
bbs
/
4d-bbsdemo
/
history.displayme
< prev
next >
Wrap
Text File
|
1993-12-28
|
33KB
|
671 lines
4D-BBS Ongoing Report
---------------------
One of the things we are trying to do is allow more awareness of what
has changed in the new versions. I will try to maintain this file with
the up-to-date info on the new versions, and what has changed.
-- V2.92d - December 21, 1993
* Made this a new version because I had to change a couple of the menu
commands! PLEASE NOTE THESE: We had three illegal menu commands, which
where !, @, and #. These conflist with menu locks, and should not have
been used as menu commands. Since the 'Y' command gives you access to
all the editors, W and X are NO LONGER editor commands. PLEASE change
you editor commands to those shown below:
:Y S Config Editor
:Y F File Catalog Editor
:Y M Message Base Editor
:Y D User Defaults Editor
:Y U User Editor
:Y B Bulletins Editor
Furthermore, you will need to change all :! to :x. The parameters are
still the same (this is the reload information command).
Furthermore, you will need to change all :@ to :o t. This is the toggle
quick list function, so I stacked it as a T parameter to the current
list files menu command.
Lastly the Send ARexx Message command was changed to ":Z A {COMMAND}". I
personally haven't used this that much, but its the SAME function we
currently use to spawn the ARexx action scripts, so it SHOULD work.
Command can be EITHER an ARexx script file, or an ARexx command.
---
ALSO WITH V2.9 OF 4D-BBS AND UP YOU *MUST* USE THE V2.80d AND UP VERSION
OF THE EDITORS. THIS IS A MUST, AND YOU MAY FIND PROBLEMS IF YOU DON'T.
--- V2.90d - December 12, 1993
* First and foremost PLEASE read carefully through the notes on V2.90a.
They all still hold true and you'll most likely be calling me and
asking a question which was answered in this file somewhere. Take
some time to read it and think about some of the things, it will
eventually make sense, I hope! :)
* Changed ALL of the editors to now use the ENV: system explained below.
Now the editors read in the config file, and use the proper paths,
rather than defaulting to the assigns. Please let me know if you run
across problems with the editors not using paths correctly.
* You should find the new installer script available now. It works
with Commodore's Installer V1.24, which is freely available (its on
out Support BBS...). You need to assign 4D-BBS_Install: to where
ever you extract the archive, or make a disk with that name, and
extract the archive to it. Let me know if you find any problems with
the installer script. I have tested it quite a bit on my second
A3000 here and haven't found any problems with it so far (that doesn't
mean there isn't any, though!).
* Fixed a couple problems which dealt with the high message (1.msg)
pointers. Both the editors and the BBS should be a LOT better
at this, and they should be updated properly. Your 1.msg files
should NEVER be bigger than about 194 bytes. The old versions were
appended the data, not overwriting it. If you see problems with
this happening again, let me know.
* Fixed a slight problem in fcl_Ed that was causing datafile problems,
and also added some new "intelligence" into fcl_ed to look at your
datafiles, and automatically fix such things as bad sizes/date, and
bad flags for public/private and online/offline. For those of you
who have wandered into the silent mode of fcl_ed, I am adding a
couple of addition CLP's to it, which are silent mode specific clps.
What this means is they are dependant on the silnet mode operation
you are doing. They are -1, -2, etc. The only current use of them
is for the silet mode addfile option. This is to replace my addfile
program which I wrote, and sometimes gives bad dates/sizes. To use
fcl_ed in this way, run it like this:
fcl_ed -s[LIB#] -la -f[FILENAME] "-1[UPLOADER]" "-2[DESCR]"
The quotes are only need if those clps contain spaces. Try a nice
little alias of:
addfile fcl_ed -s[] -la -f[] "-1[]" "-2[]"
to emulate the old addfile program. If you use other features and
want to be able to add more parameters, let me know and I can add it.
I could possibly add a couple more field for -la above, such as date,
etc, if asked for.
* Found the problems in fcl_ed which were giving enforcer hits, and
crashing systems. This mostly dealt with deleting files and adding
files. If you are still getting enforcer hits or fcl_ed crashes
please let me know!
* Changes a couple things relating to ARexx. First of all, the ARexx
command of 'userinfo W' now returns the REAL name, not the alias of
the user. Anyone know if this is correct? I changed the passing
parameters to the ARexx functions of 4D to be delimited by COMMAS,
rather than spaces. This allows you to NOT have to put quotes around
names when passing them into the ARexx scripts. New ARexx scripts
should be in the beta archive.
--- V2.90a - November 11, 1993
MAJOR CHANGES! READ BELOW AND V.289t notes VERY CAREFULLY!!!!!!
* 4D-BBS Now uses an environment systems to get the paths and such. This
works by having a directory "Env:4D-BBS" in which several pointer files
are stored. Currently there is about 6 of them:
Filename Description Contents
-------------------- -------------------------- -------------
Env:4D-BBS/Config Name of Configfile to use S:4D.Config
Env:4D-BBS/BBS Path of BBS directory BBS:
Env:4D-BBS/MENU Path of Menu directory MENU:
Env:4D-BBS/TEXT Path of Text directory TEXT:
Env:4D-BBS/DOORS Path of Doors directory DOORS:
Env:4D-BBS/USERS Path of Users directory USERS:
Several things need to be noted. ALL editors will look in env: to get
the directories they need to work with. I have added lots of things to
several of the editors, see additional notes below.
Secondly, the env directory CAN match the arexx port name, to allow you
to run more than one copy in different directories. Env:4D-BBS is the
default area, but if you are running two lines, you could use either
(Env:4D-BBS0 and Env:4D-BBS1) or (Env:4D-BBS and Env:4D-BBS1). These are
the same, sine Env:4D-BBS will be used if Env:4D-BBS0 is not found.
Next, cfg_ed accepts a parameter of /N to tell it WHAT NODE to work with.
This determines what env: set above it will use. So something like:
"cfg_Ed /N1" would mean to use the config file pointed to by Env:4D-BBS1
and its associated path pointers in Env:4D-BBS1. What this allows you to
do is have the SAME config file, but different actual directories.
* cfg_ed now has a fifth screen, which is for the datafiles. All of these
data files should NOT have a path specifier, and should be in the BBS:
(or whever you point it to) directory. These are the DEFAULT file names
4D-BBS will use (and re-load after every caller). U_ed now loads the
configuration file (pointed to by Env:4D-BBS/Config) to get some
information which it use to get via CLP. Most of the editors still allow
passing of CLPS for paths, and the CLPS WILL OVERRIDE the env: paths.
* The installer script is pretty much done. This uses Commdore's installer
program to setup 4D-BBS, and should be *LOTS* easier to setup now. You
will need to assign 4D-BBS_Install: to the place where you unarchived the
4D-BBS archive in order for the installer script to work. The installer
script will call the editors, so that you can completely setup 4D all in
one step.
* Added an ARexx command called 'closebbs' which will shut the BBS down.
Quit and Shutdown would have been better choices, but since those are
used in ARexx scripts to terminate arexx door mode, I didn't want to
overlap them. Let me know if you have a better name for this. You
should give it a number on the command line as to WHY you are closing
the BBS. 4D uses some interal numbers to determine this, and I will
try to get a list of them. (IE: Some don't actually save the on-line
user if there is one, others cleanup nice, others don't care).
* Fixed a problem with fidonet messages not getting an origin and a tear
line. Thanks Jeff Grimmet!
* If yo