BT2Fizz - BinkleyTerm to FizzBill Log Converter - v1.1 - FreeWare
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

o What's FizzBill?

FizzBill is a program that will calculate how much you have spent on you
comms phonebill, when using the Freeze Dried Terminal program.  I wrote
FizzBill for my own use, but soon realised that quite a lot of other people 
wanted to see how much they have spent on their calls. 

o What's BT2Fizz?

BinkleyTerm is the software I and a lot of other people use, when they become
a point/node.  When I changed over to Binkley from Freeze Dried, I wanted
to still be able to use FizzBill to calculate my comms phone bill, so
I wrote this program to convert the LOG file from BinkleyTerm into
log files that FizzBill could understand.

o Using BT2Fizz

First of all you need a modify the config. file, that BT2Fizz will read
when run.  Here's an example of the ascii BT2FIZZ.CFG file...

F:\BT\BINKLEY.LOG                      ! Location of Binkley Log file
G:\BTLOGS\                             ! Path to write converted logs
NO                                     ! Delete Binkley Log file [YES/NO]
5                                      ! Binkley Log Level [3/5]

The 1st line is the path and filename of the log that is generated by
BinkleyTerm.

The 2nd line is the path where BT2Fizz will write the converted log files.
Note that you MUST create this folder yourself.

The 3rd line tells BT2Fizz to delete the Binkley log AFTER the calls have been
converted, if you put YES in the line.   I'd start off with NO in this line,
until your sure everything is working ok, after which modify this to YES.
Note that one version of the log file is kept BEFORE deleteing ie. BINKLEY.OLD

The 4th line, ie. the Binkley Log level should match the LogLevel command in
your BINKLEY file *OR* set it to 3.

Save the config file.

Now run BT2Fizz.  If the config. file has been found, you should now be
told that the Binkley Log file is being read.

If any calls have been found then BT2Fizz will tell you the date that
the call was made and will write the information to a log file.  For
example, if you made a call on 1-Jun-1993 then the log created will be
called BT930601.LOG.

After the Binkley log file has been read, the log will be deleted ONLY
if you placed a YES in the 3rd line of the Config. file, but one version of
the log file is kept BEFORE deleteing ie. BINKLEY.OLD

BT2Fizz also generates a BT2FIZZ.BBS file, which contains the phone
number and the name of the bbs you called...

eg.

0-81-445-6514#The Tavern
0-81-244-9825#NeST South East

If, for example you don't like the name 'NeST South East' then just
use an Ascii editor and change the 'NeST South East' to something
like '<Fortress>', which is more meaningful.

The main reason for changing this file though is that most bbs have
different names, depending on which node address you call it on.

Eg. If you poll Node 90:102/140 -- the bbs name is 'The Tavern'
    If you poll Node 2:254/108  -- the bbs name is 'The Tavern Fido'

In the above case, it makes sense to make the two bbs names the same,
so once you've changed the name, BT2Fizz will use that name, instead
of the name used in the BINKLEY.LOG file.

You should now have some BTyymmdd.LOG files, all you do now is run
FizzBill...

o Problem/Comments

If you find any problems with BT2Fizz or want any improvements made
to the program then why not send me a message, to any of the
following networks...

 +---->      InterNet:  Steve.Basford@mettav.royle.org     <----+
 |          NeST: 90:102/108  ~  TurboNet 100:1011/0.10         |
 |         FidoNet 2:254/108.10 ~ AtariNet 51:502/100.10        |
 +---->       Part-time musicians are semiconductors.      <----+