*************************************
** T.A.G. 2.7d Maintenance Release **
*************************************
Upgrading
---------
** Please make sure that no copies of T.A.G. are running while following **
** these procedures. **
This maintenance release of T.A.G. is to be directly copied on top of your
current standard installation of T.A.G. versions 2.7 or later. Simply copy
TAG.EXE and TAG.OVR to the main T.A.G. directory.
You must also copy the MSTRDEF.TXT and TSTRDEF.TXT files to your
AFILES/GFILES directory and run TAGSTR.EXE to finalize the installation.
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.
Version 2.7d Additions/Changes
------------------------------
o T.A.G. now supports passing the user's first and last names to an
external protocol. To add these fields in the protocol editors, simply
use Control-P, N for the first name and Control-P, L for the last name.
Version 2.7d Corrections
------------------------
o Major problems with the JAM message format were solved. In one case
the last kludge field would not display (often the subject field).
In another error sometimes T.A.G. would think messages were deleted
and, in fact, they were valid messages and it would not display them.
o When prompted to clear a field (ie: make it blank), if you answered
"No", T.A.G. still cleared the field.
o If the computer description was longer than 26 characters the SysOp
window would display incorrectly and overwrite other information.
o In the file section editor the help section did not include help on
the "A - CD-ROM Section" command.
o In the message area, if you were in the first message section and hit
"previous section", T.A.G. would state that you were in the last
valid message section rather than the first.
o In the modem configuration result codes were allowed to be entered as
64 characters even though T.A.G. only supports 50.
o On files larger than 9 megabytes, T.A.G. would cut the size when
displaying the file listings. (ie: a 23 megabyte file would show up
as three megabytes.) T.A.G. now uses dynamic file sizes when listing
files. It will report a file in megabytes, kilobytes, or bytes,
depending on how much room it has to work with.
o When browsing files, T.A.G. now allows more room to display fields
such as number of downloads and size.
o Newer, faster, and friendlier file copying routines are now used
(ie: when copying CDROMs and in MiniDos)
Version 2.7c Additions/Changes
------------------------------
o T.A.G. now will check for the CHAT.DAT file in the data files directory
or the multi-user directory. This will enable a SysOp to easily create
separate CHAT.DAT's for each node. Previously it this file could be
located in the alternate text files directory and thus may have to be
moved.
Version 2.7c Corrections
------------------------
o The batch protocol editor is once again usable. Obviously this option
doesn't get used very often. Oops!
o The event system message files (@filename) have been corrected to
function similar to the menu print file program key. If you were having
trouble printing files in the event system, it should now work as
expected.
o A rare case where a local logon, without the "LOCAL" parameter, caused a
long delay after the ANSI question was corrected. T.A.G. was still
sending something to the modem.
o A couple minor display/operational problems were corrected.
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.
[EOF]