home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
RBBTIC39.ZIP
/
WHATSNEW.39
< prev
Wrap
Text File
|
1993-04-06
|
7KB
|
167 lines
Version 3.9
Version 3.82 had the wrong RBBTIC.EXE
bundled in. Version 3.9 is the bug
free version, from all reports, that
Version 3.82 was supposed to be.
If you have version 3.7 to 3.82,
you need only plug in this version
of RBBTIC.EXE and run with it.
Version 3.82
Made adjustments for NDOS users. NDOS
directory listings are different than
MS or PC Dos and caused RBBTIC. to
fail to output properly, or even run
through at all on one system. One
more working of the error trapping.
Corrected an inadvertent error in
the recoding of Version 3.7 that
caused RBBTIC to fail with error
9 or not output files on a fair
number of systems.
If RBBTIC does not find a matching
AREA Tag in your TICK.CFG file or
RBBTIC.AREA file, it will no longer
bomb. Instead, it will output the
description of the TK*.TIC in FMS
format and append 3 periods in
place of the FMS category (...).
This will alert the sysop there
are incoming Tick files for which
there is no areatag defined in the
TICK.CFG or RBBTIC.AREA file.
Unless I get reports of some real
snaffu on common systems, this will be
the last of RBBTIC as currently known.
It is now time to complete RBBTIC
Deluxe which will handle description
files within the programs delivered
by TICK, such as SDI and DIZ. RBBTIC
Deluxe will be some major reworking
so it will be a little while.
From this point forward, support for
RBBTIC will be available to registered
users only. I have taken in 16$ on
RBBTIC to date and spent more than that
on long distance support to non-registered
users (who were very helpful in getting
the kinks out for different systems).
Comments of course, are welcome from all
users as are suggestions for RBBTIC
Deluxe. 1:387/697 or 8:931/697.
Version 3.7
Corrected an ERROR 9 report generated
when no Tic.Cfg areatag matches are
found. Added error for this by comparing
Tick.Cfg and incoming TK??????.TIC files;
this condition is now logged to RBBTIC.LOG,
identifying the absent AREATAG in Tick.cfg.
Of course, Tick, will mark the *.TIC file as
*.BAD when no match is found. Finally, FMS1.APP
continues to be processed even for absent
Tick.CFG areatags, using ... as an fmscode.
This keeps you from having to rerun RBBTIC
if the areatag is missing or misspelled;
instead, just edit the code once in FMS1.APP.
Version 3.5
Corrected error in Non-Reverse Mode which
resulted from code written to accomodate
Share Command. This should be the last
bugfix for RBBTIC.
Version 3.4
Adjusted code to run on Lan's and multi-tasking
systems using the the Share Command. Please
note, RBBTIC is not Lan aware, but, it has
been tested on a Lantastic system without
problem.
Version 3.3
Corrected FMS1.APP not being output to the
directory indicated in the RBBTIC.CFG file.
There were 2 sysops reporting this problem.
Corrected an untrapped error that would
occur on some systems reporting FILE
ALREADY OPEN.
Increased the number of FMS?.APP files that
can be stored to 50. In lieu of some sysops
going on vacation for 2 weeks and assuming
they have 2 incoming Tick file sessions per day,
they would need at least 28 RBBTIC sessions and
should something go awry on their system they
would need FMS?.APP(end) files to insure no
loss of the file descriptions.
Added a catchall error trap for extremely rare
and unusual DOS errors.
Version 3.0
RBBTIC now outputs the FMS description file
to a file called FMS1.APP. It does this because
ver. 3 now renames any leftover FMS?.APP files
it finds to a higher number (up to 21) and does
NOT overwrite previous FMS?.APP files. If for
some reason, you want to let the descriptions
accumulate, you may do so, PROVIDED the accumulation
does not exceed 50 previous FMS?.APP files.
Version 1.1 of RBBTIC had a flaw in the occasional
circumstance that a Tick file description exceeded
186 characters. This has been corrected and will
truncate file descriptions after 184 characters
(4 description lines). Few Tick files have
descriptions this long.
*****************************************************************
PLEASE MAKE THE APPROPRIATE NAME CHANGE TO YOUR BAT FILES IF YOU
USED TO APPEND FMS.APP TO YOUR FMS.DIR FILE. THIS IS THE ONLY CHANGE
REQUIRED FOR UPGRADING FROM VERSION 1.1 TO VERSION 3.0.
*****************************************************************
RBBTIC now prints to screen the status of its
run and total Tick files seen, total processed,
and number unprocessed due to the absence of the
Tick Program File which should, (but, does not
always) accompany the TK??????.TIC description file.
Expanded error handling to catch more DOS reported
errors and greatly enhanced the program to trap
errors and report them with suggestions as to how
to correct the error condition. Errors are written
to the RBBTIC.LOG.
Log file is now created by RBBTIC called RBBTIC.LOG
(surprise) and the stats for each run as well as any
error messages are printed to the log.
Code condensed to speed up the program execution.
I received a report of RBBTIC failure from one SYSOP.
Finally determined that the problem was that he had
RBBTIC running from the subdirectory where his output
file was to be placed. There is no fix for this at this
time. DO NOT PLACE RBBTIC.EXE in your \RBBS\DIR
subdirectory IF that is where you told RBBTIC to output
the FMS.APPend file.
PEACE, David Remer