┌─────────────┐ ───────────── ▀▀▀▀▀▀▀▀▀▀▀▀ ───── █▀▀▀▀█
│ ┌─────────┐ │ ───────────────── █ ─────────── █
│ │ ┬ ─┐┌─┐ │ │ ───────────────── █ ▄▄▄▄▄ ▄▄▄▄▄ █▄▄▄▄▄ ▄▄▄▄▄ ▄▄▄▄▄ ▄
│ │ │ │┘ │ │ │ ───────────────── █ █ ▄ █ █ ─ █───── █ █───── █ ▄ █ █▀▀▀█
│ │ ┴ ─┘└─┘ │ │ ───────────────── █ █ ─ █ █▄▄▄█─█▄▄▄▄█ █▄▄▄▄▄ █ ─ █ █ ─ █
│ └─────────┘ │ ────────────────────────────── █
└─────────────┘ ────────────────────────── ▄▄▄▄█ Version 6.95 Standard
───────────────────────────────────────────────────────────────────────────
Copyright(C) 1990,1991,1992 - IBD Software - All rights reserved
───────────────────────────────────────────────────────────────────────────
TagScan v6.95 "What's New" Documentation / Released 08/29/92
───────────────────────────────────────────────────────────────────────────
-------------------------------
Version 6.95 Standard - Changes
-------------------------------
Melanie Meyer discovered a problem - If you did not use the default Virus
directory - TagScan was aborting with a runtime error. This was due to the
default directory begin hard - coded in the move command. We appologize
for this oversight on our part. Thanks Melanie, for reporting this problem.
If you are upgrading from any version from 6.90 - 6.94 then the
conversion will be easy. Just put the SETUP695.EXE and TSCAN695.EXE
into your \TAGSCAN directory and then execute SETUP695 from that
directory. Then [ESC] out of the program and edit your \BBS\POSTUL.BAT
file to reflect the new TagScan Version (Eg:TSCAN### %1 %2 %3 %4 %5 %6)
so that the ###=695 and you are done...
-------------------------------
Version 6.94 Standard - Changes
-------------------------------
Henry Shaw (Baltimore, MD / Flying Buffalo BBS) discovered a problem
when a VIRUS was detected. The System would reboot but the file was
never moved and written OFFLINE. We appologize for this and it has
been repaired. The correct entries were made to the LOG file warning
the SysOp of the fact that a VIRUS was detected the only problem was
that the file was not handled correctly.
If you are upgrading from any version from 6.90 - 6.93 then the
conversion will be easy. Just put the SETUP694.EXE and TSCAN694.EXE
into your \TAGSCAN directory and then execute SETUP694 from that
directory. Then [ESC] out of the program and edit your \BBS\POSTUL.BAT
file to reflect the new TagScan Version (Eg:TSCAN### %1 %2 %3 %4 %5 %6)
so that the ###=694 and you are done...
If you are installing TagScan for the first time then please refer to
the QINSTALL.DOC file.
-------------------------------
Version 6.93 Standard - Changes
-------------------------------
The only change in v6.93 was a fix to the SHARE detection and implementation
if the SysOp was running a Single-Node setup in TAG. When we detected SHARE
being loaded we would switch to a SHARE compatible filemode which was not
necessary on Single-Node Setups. If you are running TAG in a Multi-Node
setup then there is no need for you to upgrade to v6.93 unless you just
want to keep things current.
Upgrading from versions 6.90 - 6.92 is as easy as running the setup693.exe.
Once you exit the setup program all changes/conversions have been made.
Now the only thing left to do is EDIT your POSTUL.BAT file to reflect the
new TagScan version.
(Eg: Tscan693 %1 %2 %3 %4 %5 %6).
^ ^ ^ ^ ^ ^
| | | | | |
*********** (Note: There MUST be spaces between comandline parameters)
If you are currently running a version older than 6.90 then I regret to
inform you that it will be necessary to delete ALL *.DAT files and then
run the setup693.exe utility. Once this is done then you will need to
EDIT your POSTUL.BAT file to reflect the NEW version of TagScan.
(Eg: Tscan693 %1 %2 %3 %4 %5 %6).
^ ^ ^ ^ ^ ^
| | | | | |
*********** (Note: There MUST be spaces between comandline parameters)
-------------------------------
Version 6.92 Standard - Changes
-------------------------------
The only changes from v6.91 to v6.92 are some cosmetic additions which
I'm sure that you will notice right off. The other change was what we
had promised to get fixed and that is the SHARE problem. TagScan will
now work just fine if SHARE is loaded. In other words we are now "SHARE
AWARE" thanks to Tonys' brainstorming/researching.
-------------------------------
Version 6.91 Standard - Changes
-------------------------------
There was only one change made in v6.91 and it is associated with running
TAG v2.6c in Multi-Node. If the SysOp was sharing the USER.LST between 2
or more nodes TagScan would be unable to find it. Until getting v2.6c and
setting it up myself I was not aware of this problem. If you need to update
your copy of TagScan for this reason then just follow these steps, it will
only take a minute or two:
1.> Uncompress the TSCAN691.EXE and SETUP691.EXE into your \Tagscan
directory. Now delete the OLD TSCAN690.EXE and SETUP690.EXE files.
(****** DO NOT DELETE YOUR TSCAN690.DAT FILE, YOU WILL NEED IT *****)
2.> Run the SETUP691 and then just quit back out. ALL the changes will
have been made simply by executing it.
3.> Edit your POSTUL.BAT file to reflect the NEW TagScan version.
@Echo Off
C:
Cd\bbs\TagScan
Tscan691 %1 %2 %3 %4 %5 %6
4.> Your all done, thanks for running TagScan!
-------------------------------
Version 6.90 Standard - Changes
-------------------------------
1.> FileSize Updates in the *.DIR file:
The problem with the filesize being written as OFFLINE if a user uploads
a file that was, lets say, 124k TagScan would write it as "Offline"
because it is less than the 128k Block Size that TAG reads to determine
the filesize. Now if a user should upload a file that is less than 128k
it will be listed as 128k (1 Block) rather than "OFFLINE" (0 Blocks).
2.> Cleaning up the work directories:
Some compression utilities allow "ReadOnly" file attributes to be
saved when the file is compressed (ARJ is one). When TagScan would
uncompress the files and then try and clean the work directory these
"ReadOnly" files would not be deleted. We now toggle the attributes
on ALL the files in the "Work" directories before deleting them. This
will assure that the "Work" directories are cleaned up properly.
*** Please Note ****************************************************
This is done on files in the WORK DIRECTORIES only and will in
no way change files either within the archive or in the upload
directory.
********************************************************************
3.> TagScan Screen and TAGs SysOp Window:
For many versions of TagScan we have received complaints about the
TagScan screen bleeding into the SysOp Window but were unsure as how to
prevent the problem. TAG does not update this window as it does when
returning from an Online Game. We have decided to simply "Clear Screen"
just prior to exiting. This will clear the SysOp Window until the SysOp
Updates it manually but at least the TagScan Screen will be gone.
4.> Displaying files through to comport:
We have rewritten the way that files are displayed through the comport
which will now mean that ANSI files can be saved to whatever amount of
lines you wish, TagScan used to be limited to 79 lines (Suggested) but
now the file can be animated or whatever, it won't matter. This change
effects mainly the .CLR files (NOVIRI.CLR, YESVIRI.CLR and BAD-CRC.CLR).
5.> Batch Uploads/Multi-Node:
TagScan should now work fine on BATCH uploads that are converted to a
different archive type. (Eg:ZIP to ARJ). We had some problems in
previous releases where if a user uploaded a file and it was converted
the listing in the *.DIR file was not changed correctly, this is now
fixed. Also the changes should now make TagScan compatible with the
upcoming Multi-Node version of TAG at least as far as the DIR file is
concerned. We still need to find an easy way to allow TagScan do be
executed from more than 1 node without the sysop having to install
2 TagScan directories on the HD and we are working on it.
6.> Nested File Searching:
We no longer ask the SysOp how many levels of nesting to perform,
we nest until there are no more nested archives found. This will
insure that ALL all files are processed properly... All nested
files are SCANNED as they are found and uncompressed. This insures
that the nested files are truly scanned and not overwritten by
another nested file.
7.> Multi-Tasking and TagScan:
We now look for the presence of a Multi-Tasking Program such as
DESQview or Windows(Running in ENHANCED mode). If a Multi-Tasker is
detected then TagScan will NOT write directly to the screen. This will
allow TagScan to be "Well Behaved" under Multi-Taskers.
-------------------------------------------------------
Changes to the TSCFG284.EXE - (Now SETUP690.EXE)
-------------------------------------------------------
1.> We now allow 2 new paths to be configured:
Virused File Directory <-- Where to place Virused Files.
Bad-CRC File Directory <-- Where to place BAD-CRC Files.
2.> We now allow the SysOp to turn the "Beeps to the local console" on
or off. This was done to allow SysOps to get some rest while users
uploaded to their BBS, actually it was suggested by many of the users
of TagScan in the Michigan Area...
3.> All the fields can now be edited without having to retype everything.
You can now use your <Home>,<End>,<Delete>,<Insert> and <ArrowKeys>
to edit the entries.
4.> The SysOp now has the option of writing to the LOGfile using the ^P
color codes or not. Simply toggle the color to the LOG "ON" or "OFF".
5.> Fixed the problem with restoring the original entry when a SysOp would
answer "No" to the statement:
"Entry" is this correct [Y/n]?
And again, thanks for using TagScan,
Bill VanWezenbeeck