   LogToBill History File
   ======================
   BoLuSoft


   History
   -------
   
----------------------------------------------
|  31st May 1992       LogToBill 1.00        |---------------------------------
----------------------------------------------

   The first release.
   
   
----------------------------------------------
|  29th Jul 1992       LogToBill 1.01        |---------------------------------
----------------------------------------------

# implemented average cost for one call information


----------------------------------------------
|   2nd Aug 1992       LogToBill 1.02        |---------------------------------
----------------------------------------------

# in TOS 2.06 it didn't waited after execution so user couldn't read error
  messages, fixed
# made minor changes in code, so program is little shorter
# English manual added


----------------------------------------------
|  17th Aug 1992       LogToBill 1.03        |---------------------------------
----------------------------------------------

# fixed serious bug - till few days ago I thought that GEMDOS saves registers
  A1-6, D1-7. Unbelievable. I found only one program that caused LOGtoBILL not
  to work. It was TurboHST by (c) LEC. Thanks to LEC for noticing.
# in addition, LOGtoBILL is now about 150 bytes shorter


----------------------------------------------
|  31st January 1993   LogToBill 1.04        |---------------------------------
----------------------------------------------

# cost of every call is now rounded up to integer number (implemented on
  request of Jiri Lamac)


----------------------------------------------
|  18th February 1993  LogToBill 1.05        |---------------------------------
----------------------------------------------

# logfile can be in other folder than current now without any problems
  (reported by Jiri Lamac, thanx) (Substantially, these problems appeared only
  when logfile wasn't on current _drive_; this is due to TOS's Frename).
# speeded up and shortened, doesn't create any TMP file


----------------------------------------------
|  ??  March 1993      LogToBill 1.06        |---------------------------------
----------------------------------------------

   Unreleased version. Only one bug fixed.


----------------------------------------------
|  17th April 1993     LogToBill 1.10/beta-1 |---------------------------------
----------------------------------------------

# program rewritten into C language (so it's about ten times larger :-( )
# -e switch extended statistics implemented
# -b switch - creates BAcKup
# Czech manual is no longer part of L2B


----------------------------------------------
|   2nd May 1993       LogToBill 1.10/beta-2 |---------------------------------
----------------------------------------------

# -o<FILE> switch forces processed log to be written to given file
# optimized sorting
# fixed bug which caused misfunction when L2B and processed log were
  on different logical drives (reported by J.Lamac)


----------------------------------------------
|   7th May 1993       LogToBill 1.10/beta-3 |---------------------------------
----------------------------------------------

# support of config file implemented; when there are no arguments on command
  line, L2B looks for file L2B.CFG in current directory. If it can be found, it
  is loaded and mode of operation is set accordingly to configuration. Keywords
  are following:
  
     Backup, Extended, Logfile <filename>, Output <filename>
  
  Each keyword must be on its own line. L2B.CFG is not case sensitive.
  
# -c<CONFIG> switch can be used to force L2B read config file from another file
  than L2B.CFG
# using unknown switch now displays short help
# -s[<file>] switch allows to save current state of switches into config while
  which can be later used by -c switch or when no arguments are given. When
  there's -s switch with no file specified, then standard L2B.CFG is written.
  When this switch appears on command line, no actions execpt config save are
  performed. In such case, command line is only pattern for config file. Note,
  that -c switch has higher priority, so if it appears in conjunction with -s,
  then no config save is performed (due to when -c is encountered, all cmd is
  forgotten and config file is searched).


----------------------------------------------
|  14th May 1993       LogToBill 1.10/beta-4 |---------------------------------
----------------------------------------------

# there was stupid mistake which caused L2B.TMP not to be renamed after proces-
  sing. But Jiri Lamac is patient...
# another way configuring L2B was implemented: environment. When program finds
  no switches and no config file in current directory, then examines, if
  there's defined variable L2B in the environment. The value of the variable is
  string witch switches without preceding '-' or '/' divided by ','. There
  can't be no spaces! The example follows:
  
     L2B=b,e,lF:\FIDO\SYSTEM.LOG,oG:\LIST.LOG
  
  I hope you have an idea how it works.


----------------------------------------------
|  16th May 1993       LogToBill 1.10/beta-5 |---------------------------------
----------------------------------------------

# new pair of switches implemented: -re, -ri. They are used for selective
  cleaning the log. Their syntax is:
  
     -reLogId1,LogId2,...LogIdN
     -riLogId1,LogId2,...LogIdN

  The LogId is the four-character identification of program which created an
  entry in log (for example: BINK for BinkleyTerm, CLST for Callista and so on)
     -re switch erases all lines with entry matching one in its list.
     -ri erases all line except those listed.
  Note, that you can't use both switches at a time, even it would make some
  sense. These switches are pretty of L2B's concept: they can destroy
  information needed for statistics. They're primarily meant for publishing
  logs: when you want, for instance, show someone the mailers' sessions, the
  other party won't probably be interested in echomail-processing. So using
  L2B you can easily cut unwanted info away. Because it is meant to use only
  manually, these switches CANNOT be saved to configuration file or be set up
  in environment variable L2B. Using these switches at a commandline will
  prevent L2B from processing logfile for statistics. Nice thing about these
  two switches is, that they can be used on ANY Opus-style log, not only
  Binkley's one.
# another switch is here: -r<nn>, where <nn> is decimal number. It says 
  of maximal age in days of log entries. Entries older than <nn> days are
  thrown away from log. For example:
  
     L2B SYSTEM.LOG -oPROCESSD.LOG -r10

  will create file PROCESSD.LOG, where entries up to 10 day old will be copied


---------------------------------- END ----------------------------------------