home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
CL14S23C.ZIP
/
CONFIG.DOC
< prev
next >
Wrap
Text File
|
1992-10-19
|
32KB
|
672 lines
Since I added alot of entries to the CALLS.CNF file, I thought it was time
I wrote a document to explain them in more detail. I will also give you an
explination of the entries that Sam Smith created.
Almost all entries have a default value and if there is not an entry or you
comment out the entry then the default will be used. The entries may be made
in any order you like and if you duplicate one, the last one will be the one
to take affect.
*---------------------------------------------------------------------------
;full name of caller input file (or NUL) - Default = CALLER
INFILE C:\PCB\MAIN\CALLER
This is the file to be read and processed. If you are running a single node
and specify NODE 1 then this will be the complete filename used. If you
specify NODE 2 (or higher) then CALLS.EXE will append a '1' to the filename
and process that file, then append a '2' and process that, etc.. until it
has processed all CALLER files uo to the value you assign to NODE.
*---------------------------------------------------------------------------
;output file to produce - Default = BLT99
OUTFILE C:\PCB\GEN\BLT11
This is the file to send the output to. If you specify BOTH or ANSI for
REPORTTYPE then a 'G' will be appended to the filename and an ANSI report
generated. If you use a full 8 character filename then when the 'G' gets
appended DOS will still interpet the same filename and you will only get 1
report in ASCII if you specified BOTH unless you specify a '.' at the end
of the filename in which case CALLS.EXE can properly append a 'G' to it.
*---------------------------------------------------------------------------
;input file of a Header to precede report - Default = NUL
;HEADER C:\PCB\GEN\BLT11.HD
This file (if it is found to exist) will be read just prior to outputing
the report and will be output to the report. It will be output just after
the @CLS@ if you have a '*' as the first character of REPORTS. If you
specify ANSI or BOTH then a 'G' will be appended to the filename and be
used for the ANSI version of the output (note the same notes regarding
the appending as above). If the 'G' version does not exist, then no header
will be used for the ANSI version.
*---------------------------------------------------------------------------
;file for saved history information (or NUL) - Default = CALLS.SAV
SAVEFILE CALLS.SAV
If not set to NUL, then this file will be read before beginning the processing
of the INFILE(s) and saved after writing the OUTFILE. This allows reading
the CALLERS file each day and then discarding it. The totals will be
accumulated in CALLS.SAV each time. Also if you like seperate bulletins to
be generated for the different reports, you can have multiple .CNF files and
in the first specify an INFILE and a SAVEFILE and the first OUTFILE. Then
in additional .CNF files set for different REPORTS, you can specify NUL for
INFILE to indicate no file processing be done, and reports wil be generated
from the totals in the SAVEFILE which allows for quick generation of reports.
Change the OUTFILE for each report to be generated.
*---------------------------------------------------------------------------
;file for outputting any unknown line for study (or NUL) - Default = NUL
UNKNOWNFILE UNKNOWN.TXT
This file is for troubleshooting and was used by me in generating data. It
allows for sending certain lines read to a file given the following conditions:
*-----
;include all unknown lines in unknown file - Default = YES
UNKNOWNREPORT YES
Any line that is not specifically recogonized by CALLS.EXE for processing will
be dumped to the file specified in UNKNOWNFILE. This allows recoginizing what
changes might need to be made to CALLS.EXE for future enhancements. It can
also allow you to spot errors in setup. I intentionally do not recoginze
certain error messages that PCBoard generates, so if they pop up in the
UNKNOWNFILE I can see them right away, whereas I might miss them when checking
the CALLERS file.
*-----
;include all Junk lines in unknown file - Default = NO
;junk lines are those recognized by CALLS and skipped over.
JUNKREPORT YES
Certain line are recognized by CALLS.EXE but not processed in anyway. They are
only recoginized to prevent them from being written to UNKNOWNFILE. If you want
to see what they are, set this to YES. If there is some data that you feel
should be reported in some useful way, let me know.
*-----
;include all Catchall lines in unknown file - Default = NO
;Catchall lines are those recognized by CALLS in the Catchall routine which
;picks up lines missed by the normal scan (some just have to be done this way)
CATCHALLREPORT YES
Some lines (like conferences joined) just had to pass thru the catchall
routine. Those that had to pass that way will not reported by setting this
to YES. Others that were in the routine, that I could not figure out why they
were there as they were already trapped for previously, will be reported if
this is set to YES and they get caught in the CATCHALL routine. If they don't
don't ever show up then I will remove those lines of code.
The way processing is done in order to speed up the recognition of the lines
is to first process the first (position 7) character of the line and then
scan for data in in a CASE statement based on the first character, if the
line is not recognized then it passes to the CatchAll routine. This is
conferences joined have to be caught in the catchall routine. The conference
name is the first thing on the line so the first letter could be anything.
*-----
;include all Door lines in unknown file - Default = NO
DOORREPORT NO
If set to YES then everything from the OPENED DOOR (xxxxx) AT HH:MM to
the BACK TO DOS AT HH:MM will be sent to the UNKNOWNFILE (if the line is
unrecognized then it will be echoed twice if UNKNOWNREPORT is set to YES).
This allows for troubleshooting the door reports or gathering info for
building your own report.
*---------------------------------------------------------------------------
;number of nodes to scan (1=single node mode) - Default = 1
NODES 1
This is the number of nodes that you want to scan and will cause a number
to be appended to the INFILE name and each file ot be processed in sequence
as described under INFILE. If you only run a single node then set this to 1.
If you run a single node but have PCBoard set for multiple nodes so that the
CALLER file is named CALLER1 then you will need to specify CALLER1 under
OUTFILE and set NODE to 1.
*---------------------------------------------------------------------------
;list of nodes (in order of desired scan, NODES should equal the number of
;nodes included in the list. If no list provided then all nodes will be
;scanned from 1 to NODES)
;NODES 3
;NODELIST 5 3 1
This allows you more control over scanning multi-node setups. You can easily
scan only some of your nodes without having to run the program several times
using a CALLS.SAV file to collect the data. Try to make sure that NODES matches
the number of of entries in the list, although provisions have been made to
ensure that CALLS will not care. If there are more entries they will be
ignored, and if there are less entries CALLS just ignore the fact, just by
being careful, you will save yourself some headaches trying to figure out why
some nodes don't show up.
*---------------------------------------------------------------------------
;list of reports to produce from the following list
; Default = ANSTBCXO!RPDEVU^-F=GY1Y2Y3Y4Y5Y6Y7Y8#HIJKLQ&M
;
; A - system statistics B - graphic modes
; C - baud rates D - hourly usage
; E - conferences joined F - bulletins read
; G - doors opened H - download protocols
; I - download efficiency J - upload protocols
; K - upload efficiency L - batch sizes
; M - files downloaded N - security statistics
; O - security level counters P - connect type analysis
; Q - free downloads *Not PCB* R - Minutes used by Security
; S - Sysop Statistics T - User Statistics
; U - User Messages V - Conf Messages
; W - Event Report X - Language Report
; Y - Door Report Z - insert a blank line
; @ - insert a @MORE@ prompt $ - insert a @PAUSE@ prompt
; % - insert a @WAIT@ prompt * - insert a @CLS@
; ! - Last Called In Report # - Message Statistics
; = - Time Spent in Doors Report ^ - User Uploads
; - - Callers Hanging Up & - Caller ID Report
;
; Door Reports are followed by number
; 1 - InstaReg 2 - PCBVerify
; 3 - Callback 4 - Depository
; 5 - MailDoor (Generic) 6 - QMail
; 7 - MarkMail 8 - User Definable
;
REPORTS *ANZSTZBCDXO!RPEVU^-F=GY1ZY2Y3ZY4Y5ZY6Y7ZY8#HIJKL&MW%
This controls which reports and in which order they will be issued to the
OUTFILE. If a '*' is placed as the first character then a @CLS@ will be sent
to the OUTFILE before anything else. Each character controls a single report
except for Y which requires two characters (Y1 ... Y8).
*---------------------------------------------------------------------------
;Exclude accumulation of Data for graph reports - Default - None
;Allowable entries are (CEFLOPQRUVWXY!=^-&)
;REPORTEXCLUDE Y
This allows you to prevent the collection of data which you will not be using
which can offer a slight speed improvement and most importantly, reduce the
size of the SAVEFILE when accululating data over long periods of time. Note:
If you exclude any report data, then it will not be accumlated and saved in
the SAVEFILE and you will not be able to report on it in the future without
rescanning old CALLER files.
*---------------------------------------------------------------------------
;Action to perform after each section
;Allowable entries are (Z@$%*)
REPORTACTION Z%*
After every report control character in REPORTS, the string in REPORTACTION
will be processed UNLESS the next character in REPORTS is one of the
characters (Z@$%*.) in which case REPORTACTION will not be processed for that
report. This allows you to perform a @WAIT@ and @CLS@ after EVERY report, yet
prevent the action from occuring on certain reports that you want to combine.
The '.' is a do nothing character that is used to stop the REPORTACTION without
the need to do anything else. The others are described in REPORTS.
*---------------------------------------------------------------------------
;Type of report to output, ASCII, ANSI, BOTH or PCBOARD - Default - BOTH
REPORTTYPE PCBOARD
This allows you to control what type of report format you output. ASCII is
a straight text file. ANSI is a colorized version using ANSI escape sequences,
and a 'G" is appended to the OUTFILE and HEADER filenames. BOTH will cause
both an ASCII and ANSI report. A setting of PCBOARD will cause a single report
(with no 'G' appended to filenames) to be output using @Xnn color codes.
In all cases the reports will be generated with @MORE@, @PAUSE@ and @WAIT@
prompts if the are specified. For ASCII and PCBOARD, a @CLS@ will be used but
for ANSI a <ESC>[2J sequence will be issued.
*---------------------------------------------------------------------------
;peak hours to report
; 1 2
; 012345678901234567890123
PEAK YNNNNNNNNNNNNNNNNYYYYYYY
This will be used to control which times are used when calcluating the
Peak Utilization %... xx.x line. The hours marked with a 'Y' will be
included in the peak calculation.
*---------------------------------------------------------------------------
;shorten graph to just percentage used - Default = no
;NO/YES/or the minumum percent to start at
SHORTENGRAPH 50
If set to NO the the full hourly usage chart will be generated. If set to YES
then only the portion that is needed (the maximum usage) will be generated.
If set to a value (0 to 100 in multiples of 5) then either the maximum usage
or the value set will be generate, which ever is higher. This allows you to
limit the number of blank lines that are generated by keeping the report to
just those lines needed without shrinking the report too small to look good.
*---------------------------------------------------------------------------
;full name of Sysop or SYSOP
SYSOPNAME GARY MEEKER
This allows CALLS.EXE to recoginze you as the SYSOP when reporting local or
remote Sysop sessions. If you have PCBoard use your name then place that here
or if you have it use SYSOP then specify SYSOP here.
*---------------------------------------------------------------------------
;First Name to Exclude from stats (RNET.EXE is always excluded)
; up to 10 entries are allowed (this is not for USER names!)
;EXCLUDENAME RNET.EXE
This allows you to specify program names that generate logons that look just
like a User from being incuded in the report or prematurely stopping the
event timing. RNET.EXE is one such example is is already handled by CALLS.EXE
and need not be specified here. You can have up to 10 entries and more will
be ignored.
*---------------------------------------------------------------------------
;Full User Name to exclude from stats (User Messages Left, Uploads and
; Caller Hungup Reports). Up to 50 entries are allowed.
; Adding '*' as first character of name will flag User as a NetUser.
;EXCLUDEUSER GARY MEEKER
This allows you to exclude Users from being included in the reports mentions
above. If you are a HUB then you can include your NODE names from these
reports or exclude yourself if you like. Flagging a User as a NetUser will
cause messages left by this User to count as Net Mail instead of Mail Door
messages. If NetUser is flagged and a message is left via PCBoard instead
of a Door then the User Name will NOT be excluded and it will not count as
Net Mail.
*---------------------------------------------------------------------------
;Conferences to exclude from stats (Bulletins Left, Conferences Joined and
; Conference messages left) Up to 50 entries are allowed.
;EXCLUDECONFERENCE 12
This allows you to exclude a conference from showing up in any of the reports.
Exclusion is done by conference number though instead of name to simplify the
program. The conferences are counted but will not show up in the lists.
*---------------------------------------------------------------------------
;Security Levels to exclude from stats (Number of Calls and Hours Used)
; Up to 50 entries are allowed.
;EXCLUDESECLEVEL 120
This allows you to exclude a security level from showing in any of the
reports.
*---------------------------------------------------------------------------
;Door to exclude from stats (Doors Opened and Time Spent in Doors)
; Up to 50 entries are allowed.
EXCLUDEDOOR REMOTE
This allows you to exclude Doors form being included in the reports. Time
spent in the Door and opening of the Door is still counted but the Door
Name will not appear in the report lists.
*---------------------------------------------------------------------------
;Label given to the Doors that are excluded. - Default = Unlisted
;NONDOORNAME Unlisted
All Excluded Doors are counted and Timed but are reported as a single entry.
This variable allows defining that label. If set to a blank then they will
not be reported and not added to the SaveFile at all.
*---------------------------------------------------------------------------
;Area Code for CALLER ID Report. If matched then is considered a Local Call.
AREACODE 404
This is used in the Caller ID report. If the Area Code matches the one defined
here, then the ID will be listed as a local call. Otgerwise, it will be listed
as a long distance call.
*---------------------------------------------------------------------------
;Save filenames & counts in the history information file YES (default) or NO
FILENAMES YES
If you don't wish to report files downloaded then you can save alot of file
space in the SAVEFILE by setting this to NO.
*---------------------------------------------------------------------------
;File mask of files to be ignored completely, wildcards allowed
; up to 10 entries are allowed (wildcard '#' matches any digit)
FILTERFILES *.GIF
FILTERFILES *.TIF
FILTERFILES *.PIC
FILTERFILES #####?.ZIP
FILTERFILES #####?.CAP
This allows preventing unwanted or sensitive filenames from being included
in the files downloaded report. Wildcards are allowed and a special wildcard
of '#' allows matching any digit to allow for filtering out .CAP files when
using the Caller Number as the filename. They wouldn't show up in the report
unless the same file was downloaded more than once (unlikely, unless you
reset the Caller Number, but why include them in the total or SAVEFILE).
Only 50 are provided for but if more are needed, let me know and I will
increase that.
*---------------------------------------------------------------------------
;number of "User Messages Left" to report
MAXUSERS 30
;number of "User Uploads" to report
MAXUL 30
;number of "Callers Hanging Up" to report
MAXHANGUP 30
;number of "Conference Messages Left" to report
MAXMSGS 20
;number of "free downloads" to report
MAXFREE 10
;maximum number of conferences to report
MAXCONF 20
;maximum number of bulletins to report
MAXBLT 20
;maximum number of doors to report
MAXDOOR 20
;maximum number of batch sizes to report
MAXBATCH 5
These control how many entries are to be reported in each report. If specified
then the report will show Top xx in the report header. If not specified then
all entries will be reported.
*---------------------------------------------------------------------------
;minimum d/l's to include a file in report
MINDL 2
This will control which filename get reported in the Files downloaded report.
Only files downloaded as many or more times as the number specified here will
be reported.
*---------------------------------------------------------------------------
;redefine protocol names
PROTOCOL A Ascii (Non-Binary)
PROTOCOL X Xmodem (Checksum)
PROTOCOL C Xmodem (CRC)
PROTOCOL O 1K-Xmodem (Ymodem)
PROTOCOL F 1K-Xmodem-G(Ymodem/G)
PROTOCOL Y Ymodem (PCB Batch)
PROTOCOL G Ymodem/G(PCB Batch)
PROTOCOL D Ymodem (DSZ Batch)
PROTOCOL H Ymodem/G(DSZ Batch)
PROTOCOL Z Zmodem (DSZ Batch)
PROTOCOL N None
This allows you to specify the Text Name used in the report for each PROTOCOL.
The leter following the PROTOCOL matches that of the associated Protocol you
have defined in PCBoard.
*---------------------------------------------------------------------------
;redefine Door Names - (I,V,C,D,G,Q,M,U)
;corresponds to report - Y(1,2,3,4,5,6,7,8)
;
; A '/' may be used to seperate Mulitple Door Names for the Same Door
; (Note: No spaces allowed) ie. DOOR I INSTAREG/RENEW
;
DOOR I INSTAREG
DOOR V VERIFY
DOOR C CALLBACK/CALLME
DOOR D DEPOSIT
DOOR G MAIL
DOOR Q QMAIL4
DOOR M MM-2/MM2/MARKMAIL
DOOR U REGISTER
This controls the processing of doors recoginzed specially by CALLS.EXE.
The default names are shown above and if you run the door under a different
name, you must specify that here or it will not be accumulated in the reports.
If you run the same door under multiple names, then specify each name here
seperated by a '/'.
*---------------------------------------------------------------------------
;Text to be added before the Security Level - Default = Level
SECLABEL Security Level
This allows you to define what text is added to the security level for the
report lines. If you want just the Security level with no other text, then
just include the line SECLABEL with no text after it.
*---------------------------------------------------------------------------
;Text to be added before the Security Level - Default = ''
;if blank then line will not be printed
NOSECLABEL No Security Level
This allows you to define what text is used to report caller entries with
no security level. If undefined or defined as NOSECLABEL with no text after
it, then this line will not be reported at all.
*---------------------------------------------------------------------------
;Maximum item length for variable length items - Default = 20
; (variable length items are defined by ITEMLEN of -1)
;
;ITEMMAX 25
This controls the maximum length that will be used of a graph item when an
ITEMLEN of -1 is specified for a report.
*---------------------------------------------------------------------------
;Item length for graphs, If set to -1 then will be set to longest item
;ITEMLEN C 10
;ITEMLEN P -1
This controls the length that will be used of a graph item. This allows
reducing the wasted space on the shorter reports and increasing the length
of the graph bars themselves. It also allows increasing the defaults so the
entire User Name would show if one exceeds the 20 character limit normally
set in CALLS. The defaults are all 20 except for:
'C' is 8
'G', 'L' and '=' are 10
'E', 'V' and '&' are 15
The length used will actually be 1 less than set as there is 1 space at the
front of all items. The parameter after the ITEMLEN is the Report Name as
listed in REPORTS and the last parameter is the length to be set. Setting
a value of -1 will cause the longest length encountered to be used as long
as ITEMMAX is not exceeded.
*---------------------------------------------------------------------------
;Report Label for Generic Mail Door - Default = Your Mail Door
;Report Label for User Definable Mail Door - Default = Any Door
;REPORTTITLE A Here's a Title
REPORTTITLE Y5 Cam-Mail Door
REPORTTITLE Y8 Register Door
This allows you to redefine the Header text of any of the reports you would
like to. If you want a more descriptive Header than provided, you can
define your own. The parameter after the REPORTTITLE is the Report Name
as listed in REPORTS and the last parameter is the title to be set.
*---------------------------------------------------------------------------
;redefine User Definable Door Text - (1-20)
;DEFDOOR 1 FIND THIS TEXT
;
; If not defined then the entry will not be scanned for regardless of
; DEFDOORTYPE or DEFREPORT entry. If defined then the text will be
; scanned for anywhere in the line. Order of variables can be important.
;
DEFDOOR 1 ADJUSTED
DEFDOOR 2 CARRIER LOST
DEFDOOR 3 KEYBOARD TIMEOUT
This allows you to define the text that is scanned for for a Door defined
by yourself. This Door corresponds to the DOOR U DoorName entry (or REPORT
Y8). You may define up to text entries to be recognized. Use as much or as
little of the text you need to identify a particular line from another. The
number corresponds to the 20 variables set aside for the door report. If the
text you specify is found then the variable will be incremented. Undefined
(unused) text entries will not be scanned for.
*---------------------------------------------------------------------------
;redefine User Definable Door Variable Type - (1-20)
;DEFDOORTYPE 1 1
;
; When DEFDOOR is defined:
; Bit 2 means Carrier lost, Doesn't count if Door Logged User Off
; Bit 4 means Door Logged User Off
; Bit 8 means Line contains HH:MM entry to stop Door Timing
;
; When DEFREPORT is NOT defined:
; Assigning a 1 means show ' ....................... '
; Assigning a -1 means show ' '
;
DEFDOORTYPE 1 1
DEFDOORTYPE 2 2
DEFDOORTYPE 3 1
This controls special aspects of the variables. It is 'bit' controlled and
you can include all or none of the bits. The bit meanings are described above.
The real use is to recoginze a CARRIER LOS entry so it can be counted properly
for the report. Also, if there is a line issued by the door that would indicate
that the door was dropping carrier or loggin the user off, this prevents CALLS
from counting a CARRIER LOST against the User. Allowance is also given to
tell CALLS to stop timing the door on a given entry. One such line exists
in PCBVerify as 'User disconnected at (HH:MM:SS)' so setting an entry to 12
would cause CALLS to recoginze that timing of the door can stop and that
a subsequent CARRIER LOST should be ignored (until a Minutes Used or a
Back From Dos at HH:MM line appears to indicate the door data has ended.
If a variable is unused you can use DEFDOORTYPE to cause a blank line to
be generated by setting as descibed above. This allows for flexible report
output to be designed. Although only 1 User Definable report is allowed, you
can combine multiple doors under it by defining DOOR U Door1/Door2/Door3
and then using the first several variables for Door1, skip 2 variables, use
some for Door2, skip 2 and then Use more for Door3. Setting the skipped
variables DEFDOORTYPE to -1 will cause a seperating blankline. Only a single
Number of times Door Opened, Time in Door, etc... report will be generated
and represent all doors combined.
*---------------------------------------------------------------------------
;redefine User Definable Door Report Text - (1-20)
;DEFREPORT 1 Found the text
;
; If not defined then the entry will not be Reported, unless DEFDOORTYPE
; is defined in which case a blank entry will be reported.
;
DEFREPORT 1 Security Level Adjusted
DEFREPORT 2 Caller Dropped Carrier
DEFREPORT 3 Keyboard Timeouts
This allows you to specify teh text that appears in the report itself for
each variable. Blank (or unused) lines will not be printed (with the noted
exception of the 1, -1 DEFDOORTYPE mentioned above)
*---------------------------------------------------------------------------
;Include Refused to Register and Access Denied - Refused Registration
REFUSEDREG NO
This allows you to have the two figures combined and reported under Refused
to Register. The purpose for this is for those of us who allow Users to
remain on the BBS at a reduced level if they don't register. PCBoard generates
a Refused to Register entry and CALLS uses that to generate a Non-Registered
Users report. Only those Users who refuse to give a full name after starting
a name entry or refuse to answer the questions after starting registration
cause a Access Denied - Refused Registration wntry to be generated which CALLS
uses to generate a Refused to Register report for. If you have the level set
to 0 for these users, then PCBoard will kick them off and you will get a
Refused to Register entry in the log for them. Setting REFUSEDREG YES will
cause CALLS to report both entries under Refused to Register (although the
entries will still be reported under Non-Registered Users also.)
*---------------------------------------------------------------------------
;redefine Language Names - 20 characters max - (1 - 30)
;LANGUAGE 5 Three Stooges (5)
LANGUAGE 1 English [Default](1)
LANGUAGE 2 Southern Style (2)
LANGUAGE 3 Three Stooges (3)
This allows you to define the name of the languges reported by CALLS to
what you call them in PCBML.DAT file.
*---------------------------------------------------------------------------
;define how event time is reported
; EVENTMODE OFF disables calculation of event duration.
; EVENTMODE BUSY calculates event duration and accounts for it
; as 'busy' time (i.e. the system was in use during this time).
; EVENTMODE IDLE calculates event duration and accounts for it
; as 'idle' time (i.e. the system was NOT in use during this time).
EVENTMODE BUSY
This allows you to consder the BBS IDLE or BUSY during the time the Event is
running.
*---------------------------------------------------------------------------
;define how Sysop chat time is reported
; CHATMODE OFF disables calculation of Sysop chat duration.
; CHATMODE BUSY calculates Sysop chat duration and accounts for it
; as 'busy' time (i.e. the system was in use during this time).
; CHATMODE IDLE calculates Sysop chat duration and accounts for it
; as 'idle' time (i.e. the system was NOT in use during this time).
CHATMODE IDLE
This was intended to allow you to define the BBS IDLE or BUSY during the
time the User was in Chat with the Sysop but it is not correct. It should
be set to IDLE or the figures might not be correct. I added it as it is
possible not to charge the User for time spent in chat but this really
didn't affect the Minutes Used time reported in the Caller log, only how
much time he was charged in the User file. I will probably remove this
section at a later date or fix it to work by subtrating time if set to IDLE
so when time is added at the minutes used line, it will have been cancelled
out already. I also left it in as it does allow suppresion of the time in
chat line if set to OFF
*---------------------------------------------------------------------------
;define how Node chat time is reported
; NODEMODE OFF disables calculation of Node chat duration.
; NODEMODE BUSY calculates Node chat duration and accounts for it
; as 'busy' time (i.e. the system was in use during this time).
; NODEMODE IDLE calculates Node chat duration and accounts for it
; as 'idle' time (i.e. the system was NOT in use during this time).
NODEMODE IDLE
This should be set to IDLE also for now as it has the same problem as above
and was added just to be compatible with CHATMODE.
*---------------------------------------------------------------------------
;Enable filtering of Modem return data
RINGFILTER ON
Sometimes the Modem returns more that just the baud rate in the way of line
noise. This causes unusal reports. Also on some office phone systems it is
posibble to get a double ring and a RING appears before the resulting in
such entries as:
Modem: CONNECT 2400 D D C C C
Modem: CONNECT 2400 ? ? ?
Modem: RING CONNECT 2400
which throws off the report. Setting RINGFILTER ON will cause the word RING
to be filtered out of the line and the connect string will be truncated at
the first space past the 'CONNECT XXXXX'.
*---------------------------------------------------------------------------
;Enable filtering of CONNECT from Modem return data - Default = OFF
CONNECTFILTER ON
Some modems return much longer Connect strings and CALLS truncates the string
making it less readable. Setting CONNECTFILTER to ON causes the word CONNECT
to be eliminated from the string, allowing more room for useful text. If the
string contains only the word CONNECT then it will not be removed (or else it
will cause a problem with the CALLS.SAV file being read back in due to the
blank line, which is normally means the end of a list has been reached.) If
you have a CALLS.SAV file and do not want to regenerate it, you can edit out
the CONNECT portion of the string manually (but don't elminate it on the
string containing only CONNECT as mentioned above, causing a blank line)
If the Connect string contains a CARRIER and a CONNECT then if CONNECTFILTER
is active, the CARRIER will be filtered out and the entire CONNECT XXXXX will
be filtered out.
==============================================================================
Of course, despite the fact that the title screen still says support is from
Samuel H. Smith, please don't refer questions regarding features added in this
version to him. I will field all support questions for the changes I made.
Gary Meeker