*************************************
** T.A.G. 2.7b Maintenance Release **
*************************************
Yes, this one has been a long time in coming for such a minor upgrade. We
apologize for the delay and hope it is in no way an indication of how long we
are going to take for the next major upgrade. I'm sure a couple intentionally
unnamed support sites will keep us on our toes and moving in the right
direction now that we are alive again.
Take care,
The Tag Team
Upgrading
---------
This maintenance release of T.A.G. is a patch to the 2.7 Standard release.
The rebuilding program will refuse to execute on any other version of T.A.G.
except the indicated version. NOTE: Test sites should unarchive the 2.7
Standard release executables in order to upgrade to this version.
To upgrade your system to T.A.G. version 2.7b, place the included files in
your Main BBS directory and type:
TAG27B.BAT
After the patch is complete, you may delete the TAG27B.BAT batch file. The
upgrade batch file deletes all other files which are no longer required except
itself and this documentation file.
If you run a multi-node system or have multiple copies of the T.A.G.
executables on your system, follow the same procedures for each of your main
BBS directories.
A new MSTRDEF.TXT file has been included with one string change. Please see
the first entry in the addition/change section for information on modifying
your string override files (MSTRMSG.TXT, MSTRCLR.TXT and/or MSTRRIP.TXT).
Place the default string file in your alternate text files directory and make
any necessary changes to your override string files. After complete recompile
your string files by executing the TAGSTR.EXE program in your alternate text
files directory.
Version 2.7b Additions/Changes
------------------------------
o The LOGON_NAME_NOT_FOUND string has been changed slightly to include the
name of the user and actual verification question to make ANSI/RIP
screens a little easier to create. A new default MSTRDEF.TXT has been
included with this release, but any SysOp's who have an override for
this string must modify their override file(s). For your reference, the
default string file contains (left justified of course):
*LOGON_NAME_NOT_FOUND
Name NOT found in user log.
'^UJ' <-- Is this correct (Y/[N]) ? @@@
*
o Added support for Remote Access "PAGE.RA" style chat calls (why someone
would want to change T.A.G.'s pleasant sounding chat call is beyond us
(-:). The script file should be named "CHAT.DAT" and placed in the
alternate text file or multi-user directory.
Additionally, a page length configuration was added to the system
configuration under general variables. This setting affects BOTH the
internal chat call as well as the new "CHAT.DAT" script method. The
default setting is 20 seconds. The "CHAT.DAT" script will be played
repeatedly until the time limit is reached.
CHAT.DAT sound data-file format:
Verbs:
TONE [hz] [1/100's sec] (sounds hz)
WAIT [1/100's sec] (sounds nothing)
Note Frequencies
---- --------------------------
C 45 134 268 536 1071 2145
C# 71 142 284 568 1136 2273
D 75 150 301 602 1204 2408
D# 80 159 319 638 1275 2551
E 84 169 338 676 1351 2703
F 90 179 358 716 1432 2864
F# 95 190 379 758 1517 3034
G 100 201 402 804 1607 3215
G# 106 213 426 851 1703 3406
A 113 225 451 902 1804 3608
A# 119 239 478 956 1991 3823
B 127 253 506 1012 2025 4050
o With the addition of RIP graphics mode the following command line
parameters have changed:
- Generic command line parameters, parameter 6
"0" = None "1" = ANSI "2" = RIP
- Multi-user chat command line parameters, parameter 1
"0" = None "1" = ANSI "2" = RIP
o When RIP mode is active, the system forces the user into one key input
mode so that RIP screens can be standardized.
o Using the "(U)ser information" command on a read message menu now looks
up "Failed Logon" users similar to the Control-U user editor command.
o Though not a very clean fix, the file section editor now accepts the use
of the "\" character in file names to allow placing *.DIR files in
subdirectories. The field only has room for 8 characters so keep them
short!
Version 2.7b Corrections
------------------------
o Considerable work was done to limit overlay trashing and insignificant
activity during message scanning and reading. This should increase
message scanning speeds most noticeably when no new messages exist.
o The infamous 30000 minute usage problem should now be corrected. We
only wish our systems could be that busy! (-:
o When a user is on past midnight, system and user information is now
updated in relation to midnight and not when the system noticed it was
past midnight (e.g. if the user was in a long download till 12:30am, 30
minutes will now be applied to the new day and not the previous day).
o User name lookups now search for an exact match on the name before going
into partial name search mode. This should make users with short
handles happy.
o The file section editor again allows special characters to be entered in
file section file names (e.g. '`', '@', '+')
o Corrected a number of serious problems related to having more than 1000
file sections (Paul and ahhhhhh ummmmm ........ <grin>)
o Clearing the phone number on systems which require phone number entry
will no longer ask the user to enter the last four digits of their
number when logging on (oops).
o Utilities are once again allowed to modify the "adjtime" field in the
user record while shelled from the system. This value was inadvertently
stored in memory and any changes to the user record would be ignored.
o Adjusted time is now correctly used when users calls back on systems
with time restrictions per day (most systems). This could have caused
problems with losing chat/upload/timebank adjustments on their next
call.
o The file "RIPFILES.TXT" is now closed properly after being used. This
should eliminate some random run-time errors.
o When moving a file to another section which already contains a file with
the same name, the system will now ask whether you wish to move the
listing entry if you choose not to move the file (it originally moved
the listing automatically).
o After block deleting a group of messages, your active message number is
no longer left sitting on top of a message which doesn't exist.
o Illegal logons are now reported correctly again.
o Origin lines now contain point information again.
o The "/READ" command now follows the security level in the system
configuration instead of the CoSysOp level.
o "ANSI Only" required commands now execute correctly when the user has
ANSI.
o When viewing certain corrupted ZIP files the system should no longer
generate a run-time error.
o JAM fixes:
- The display of non-standard FTS_KLUDGE lines now works correctly
when there are more than one of them.
- Destination information is no longer added to JAM style messages
when not needed (e.g. echos).
o Many minor display/operational problems corrected.