home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
LCNT150U.ZIP
/
WHAT'S.NEW
< prev
Wrap
Text File
|
1992-11-27
|
17KB
|
357 lines
LOGCOUNT - the ultimate Files.Bbs counting utility. +++++
see LOGCOUNT.CFG for all the latest options..
November 27, 1992
Included a new program, LOCATER. It is designed to search
Filelists that contain DOS style date information as part
of the description. (eg 11-27-92 ). This program uses FOSSIL
routines while running remotely. It uses default (normal)
Maximus colours only if user has ANSI active. Sample
.MEC files included that can be used to let users search
for files by date. see LOCATER.DOC in LOCATER.LZH for
complete details.
November 1,1992
Fixfbbs Catalog mode has been enhanced to support Filelist that
contain filesize and dates as part of their descriptions. The
catalog function will work whether or not you have download
counters or not! Descriptions lines will be justified accordingly.
The catalog function no longer relies on the formatting (-TM) logcount
performs. It'll now work on any description formatted with -TN,
-TM, or -TR. Previous versions didn't handle the -TN formatting.
October 19, 1992
Major improvements for use with CDrom and FILELISTS. Fixfbbs and
LOGCOUNT are both aware of all the new functions. Added another
feature of the Fixfbbs Catalog function, Now you can create an
Avatar Coloured (standard Maximus colours) display file of the
top 100 new files (or less), as well as the the top 100 downloaded
files (but not at the same time as).
May 9, 1992
I have no valid network addresses and am about to move to a new
location.
Added support for RA expanded logfile formats. Added new option
to allow leading zeros instead of the normal leading spaces
in the download counts. This is primarily for RA since it has
a nasty habit of killing whitespace when displaying multiple
line file descriptions. The -TR option does not seem to be working
properly with RA v1.1x. I am a loss to figure out why.
changed the logic involved with the Maximus freebytes/time invisible
specifiers (/bt, /b, /t etc..). A file must already have a valid
or a blank download count, else the invisible characters will be put
in the description field. This will prevent smart ass users from
including those invisible characters as part of an upload description.
Of course if they put invisible stuff as well as a valid download
count there isn't much that can be done. I suggest the use of avatar
colour as part of the download count inclusion characters, not too many
users know how too insert avatar codes into a description.
March 9,1992
The move from Ottawa to Vancouver was a success, My new addresses
are 1:153/703 and 89:683/109. Please send all reports, suggestions
etc. to these new addresses.
Jan 3, 1992
Added a few more features.
fixed a problem with dynamic enclosure sizes and free file specifiers.
Seems the routine that rescanned a files.bbs after the count went from
say 9 to 10, or 99 to 100 was not properly recognizing the /bt, /t
specifiers. oooops.. hope it's working better.
added extra routines to recognize path information in the filenames
that Maximus allows in a FILES.BBS file. This information is probably
only usefull if you have a CDRom, but Maximus allows you to specify
complete path information for a file in any Files.Bbs, as long as
the file pointed to exists, Maximus will display it as if it were in
the current file area. Special Files in other directories can be made
available to all users using this technique. Anyways since this feature
is undocumented in Maximus v2.00, I'm only speculating on it's usage.
The -j options previously only applicable to mailer specific functions now
have a CBCS function. If the specified 'simple' filename (no path info)
matches the file in the CBCS log then that file will still be counted as
a download (if applicable) but these files will no longer go into the
history log files. There can be as many as 25 such "-Jfilename.ext" in
a LOGCOUNT.CFG file. Wildcards using '?' can also be used. do *not*
expect '*' type wildcard filenames to work. Only '?' type are supported.
The "-X' and "-Y" options have been enhanced. There is no good reason for
this except it allows you to choose a different colour or character or both
for the Maximus FREE FILES, files that have a /bt, /t, /b, /whatever as the
first part of the description. "-X[, <" means use "[" for normal files and
use "<" for free files. Should be selfexplanatory. If confused don't attempt
to use this options. FIXFBBS should also be given the same information (lines
2 and 4 of FIXFBBS) must be exactly the same as your enhanced -x and -y
options (without the "-x" and "-y" stuff of course).
whole new feature, "-@" directory name translation. This is a little tricky
to explain, but I'll try. The intent of this option is to support CDRom
but it has other purposes. Basically what you do is supply 2 pieces of
information. The first being the path name that will be found in the
logfile being read by LOGCOUNT. The second being the full pathname of
a file containing the file descriptions. Sounds simple enough eh!
for example
-@ C:\max\files c:\descriptions\filarea.one
anything in a logfile with the path of "c:\max\files" will be assumed to
have it's description in the file FILEAREA.ONE in directory c:\descriptions
this is a direct translation. ( c:\max\files\filename.ext )
-@ C:\max* c:\descrpt\filarea.two
^^^^^^
this is an example of a WILDCARD, if the part to the left of the
asterick ("C:\Max") can be found in the path in the logfile entry
then the description of the filename is assumed to be in the
specified file.
So things like
c:\max\max.exe
c:\max\files\filename.ext
c:\max\olr\node01\maximus.qwk
c:\maximus\files\filename.ext
c:\max\etc.....
^^^^^^
are all gonna be found in the file c:\descrpt\filearea.two
finally
-@ * c:\max\files.bbs
Usually this will be your very last "-@' option. The single asterick
indicates that any file that can not be found in a files.bbs in the
directory indicated as it's download path, or if all other directory
translations fail, then this is the last place to look for a description
for the file. Orphans are sure to show up in here.
The translatable directory stuff need not to be too exact, but the
filenames with the descriptions must be exact "drive:\path\filename.ext"
entries. It's a good idea to ensure that these files really exist. The
usual names for these files is "FILES.BBS" but any legal DOS filename
is acceptable. These files can contain full drive/path/filenames as well
as simple filenames and of course the associated descriptions.
FIXFBBS has also been upgraded to support all these new features, but
read FIXFBBS.DOC for more information. Happy LOGCOUNT-ING.
This is probably the last version of this program, I will be moving from
Kanata, Ontario to somewhere in Vancouver, B.C. early in the new year.
See ya later.
Dec 19, 1991
Discovered some strange behaviour concerning FD systems connecting with
my BinkleyTerm Mailer. Something to do with blank multiple blank characters
in the system ID being sent by FD. Causing lots of confusion in the correct
identification of the remote system's address. I know exactly why this
happens, and adjusted the code accordingly. Had something to do with the
'3 spaces' between the filename and the sysop-info/user name in the history
files. LOGCOUNT now performs the check for white space after identifying the
remote system's address. This was an obscure bug, the check for '3 space
characters' only purpose was so that you could rescan your history files in
case something else (disk failure etc...) had destroyed your FILES.BBS. Well
that's it for now.
Nov 15, 1991.
Added `invisible' support for the new Maximus Files.Bbs switches /t and /b.
If these are the very first thing in the the Files.Bbs line immediately
after the filename and one or more spaces then Maximus will not display
them and are in fact invisible. They have specific meanings. /t is supposed
to allow that file to be downloaded with no time penalty and the /b option
is supposed to allow the download with no byte penalty. And the combinations
/tb or /bt are also allowed. LOGCOUNT recognizes /t, /b, /tb, /bt. That's all
the possible combinations presently supported. LOGCOUNT will seperate the
actual description from these 'invisble' characters by a blank space. If
future versions of Maximus support more options, then just include them and
leave a single blank space before the real description. LOGCOUNT first
checks for a space character after the invisible string, this is FAST, but
it will also recheck for it's known possible combinations if the invisible
characters are attached to the description. Nobody has probably got a clue
about this obscure option. But ........ there it is!
August 21, 1991
-------------------------------------------------------------------------
added a check for node address information obtained from FD log files.
if the data between the ':' and the '/' is in fact numeric then a valid
zone/network/node address has been located. lines starting with a `+'
sign always contain the Remote System's name and address.
+ ...... Unknown System, 1:999/999
^^^
^^^
if this is numeric. Address is Vaild.
hopefully this will prevent LOGCOUNT from misinterpretting things
that do not indicate network address. Command line parameters
associated with `+ ..... Service: etc...' that `look' like address
information should be ignored.
added a new commandline/configuration file option `-K'. This instructs
Logcount *not* to include the SysOp's name in the history logfiles, only
the node address will be written.
the default value of the `-A' option is now `-A60'. it was `-A62'.
-------------------------------------------------------------------------
Have a nice day. Send me money.
Jan 21, 1991
-------------------------------------------------------------------------
Fixed a few problems with the FD options. Now checks 'lastrun' information
more carefully. Previous a simple check of the 'time' was used to determine
if the entire logfile should be read. This didn't work if the logfile had
many days of entries. Hopefully that is now fixed. It wasn't easy to do.
Also will strip '@fidonet.org' etc. If it is part of the address. Who cares
about that information anyways. It really screwed up the Database format.
Also added some extra checking to make sure the address of the incoming
call was correct. I hope it's the last thing on the line after the last
occurence of a comma. (the remote system could have commas in their ID line
and this meant extra, non numeric information may have been included in
the network address.)
Dec 23, 1990.
Due to popular demand, another option has been added. This option allows you
to override any 'global' inclusion sizes in a specific directory FILES.BBS
This new option is a variant of the '-M#' option.
for example in logcount.cfg
---- rip here -----
-m3 % always create and maintain 3 digit inclusions.
-m4 C:\UPLOADS % always have 4 digit inclusions in this area only.
-m0 c:\inbound % maintains 'minimum' size in this area only.
---- rip here -----
- Overrides any 'global' inculsion size in this area
only. This area is 'fixed' at 4 digits. The characters
':\' must be in the directory name. That's the only way
to distinguish a directory from a comment. FILES.BBS
must be present in the specified directory, or else
it is ignored.
- Maximum of 15 directories can be listed with this
override option. Should be plenty.
- value of the number attached to the letter 'm' can be
higher or lower than any declared 'global' inclusion
size.
October 30,1990.
-------------------------------------------------------------------------
1. Added a new switch '-TR#', this is very similar to the '-TN' switch in
that it does not truncate long descriptions. '-TR' will not truncate long
lines but will adjust them so that they display RA multi-line descriptions
in a more eye appealing manner. You'll see what I mean.
note: '-TR' really means '-TR0', this number '0' indicates an offset
factor to calculate. The default is '0', but if filedates or
filesizes is not being displayed then adjust the 'number' part
accordingly. Positive numbers means the description part of
the line is longer than normal, negative numbers means that
your display is less than normal (80 characters). etc.
----------------------------------------------------------------------------
October 1, 1990
1. Added a new switch '-TM#', this is very similar to the '-TN' switch in
that it does not truncate long descriptions. '-TM' will not truncate long
lines but will adjust them so that they display Maximus 3 line descriptions
in a more eye appealing manner. You'll see what I mean.
note: '-TM' really means '-TM0', this number '0' indicates an offset
factor to calculate. If for instance Maximus is not displaying
filesizes and dates, then the description field normally would
start 18 characters sooner. use '-TM18' and logcount will adjust
the description to display properly. If your descriptions always
seem to be confused, experiment with the offset factor, or set
your Maximus screen size to 80.
2. The '-X' and '-Y' custom inclusion characters can now also contain
'invisible' colour code characters. Invisible means that Maximus won't
display them to non graphic callers. (Avatar codes for example).
-Xë[Å % Avatar Brackets lightblue,'[',white
-Yë]ï % Avatar brackets lightblue,']',lightcyan
Maximus will display the Filename, the filesize, the fileDate, the '*' if
file is new and then the rest of the description. In the above case, the
left bracket is Intense Blue, the actual numeric count is White, the right
side bracket is Intense Blue, and then the rest of the description is
displayed in intense Cyan.
3. FIXFBBS is a utility that will allow you too change the inclusion
characters in your existing, processed by Logcount FILES.BBS files. It is
a quik and dirty little program. The required .CFG file must be created
in the exact format required. Failure to do so will result in disaster.
Read the FIXFBBS documentation carefully before attempting to implement
AVATAR codes as part of the inclusion characters.
July 28, 1990
Added QBBS support as a CBCS logfile, parameter -L.
Mailer DataBase now works with FD 1.99 as well as FD 2.00
July 16, 1990.
With the release of BinkleyTerm 2.40, a few minor changes have
been made. Logcount will now identify Z-modem, Janus, and
FTS-0001 entries in one execution. The '-R' and '-S' options
are still supported in case there are some other protocol
options that are unknown to me, (such as SEAlink). Logcount
will convert all expected transfer entries to Z-modem format.
This has no effect on the program and the only unexpected
results will be in the BINKLAST.BBS file. It will always have
Z-modem as the Transfer Protocol for the last file sent/rcvd.
All valid entries are converted to Z-modem before LOGCOUNT
compares the entry with the last run history file, no problems
will arise.
NOTE: When using the '-S' and '-R' options to overide the
default Z-modem protocol transfer identifiers, LOGCOUNT
will still convert Janus and FTS-0001 log entries to
Z-modem format. It is therefore impossible to search for
entries like 'Sent-J/32' or 'Sent:', using the '-S'
parameter option on a BINKLEYTERM log file.
If anybody knows what log entries using X-modem, or Sealink or
any other unknown Protocols look like, forward a sample to me and
I will include them in the program. Until that time you can still
use the override options to search for them.
July 14, 1990.
Support has been added for RA (Remote Access) CBCS log files.
Identify the RA log file as a '-F ' Frontdoor log file. The
format of the RA log file is all most identical to a FrontDoor
Log file. LOGCOUNT will convert those 'Upload [??????]' and
'Download [??????]' entries to the familiar 'Sent' and 'Rcvd'
entries on the fly, and then treat the entries as the regular
FrontDoor format entries.