Subj : Binkley Error message
To : Nicholas Boel
From : mark lewis
Date : Sat Mar 16 2013 02:04 pm
FR> + 14 Mar 18:46:59 BINK begin, BinkleyTerm/Win32 Ver. 2.60
FR> ! 14 Mar 18:47:06 BINK SYS00000006: GetCommState()
FR> Out of the blue this error message popped up in the logs. Now
FR> every time I start up Bink, this error comes up and BT exits.
NB> I don't see any errors whatsoever.. ?
the SYS0000006 entry is the error...
FWIW: the first character of many log formats indicates the line's severity...
for binkleyterm, an ! indicates an error entry... many other systems followed
this format, as well... i can't find a document with the ones that binkleyterm
actually uses but the following section comes from frontdoor's logging setup
secrrn in the fdsetup tool...
! Fatal errors
? Other errors
$ Accounting info
* Sent/Rcvd files
+ Brief messages
- Trivial messages
: Transaction info
% Transfer messages
# Unexpected passwords
~ Session information
~ Remote system's AKAs
~ Remote system's info
= Modem responses
` Trivial FREQ messages
they were used for log analysis software... it made it real easy for the
analysis software to run thru the logs looking for only certain characters and
then tallying those stats...
