Contents of the LOG.DOC file
Copyright (C) 1988
by Jeff Parnau
P.O. Box 244
New Berlin, WI 53151
Registered users will
be notified of updates
and where to find them.
This isn't a fancy do-all program. I wrote it because I wanted a simple,
easy-to-maintain logbook. Some of the stuff out there is great, but
crashes, or is difficult to learn, or is too expensive. So for those who like
simplicity, here you have it.
The program comes supplied with sample files, all of which have the
extension ".LOG" and all of which are required. Some of them can be created
by the program itself, but CUSTOM.LOG and AIRCRAFT.LOG must be created by
the pilot or user. The sample files show working examples of these.
You may modify or recreate AIRCRAFT.LOG and CUSTOM.LOG to suit
your particular flying habits. But be sure to follow the format properly.
AIRCRAFT.LOG must look like this:
Jeffery R. Parnau
There must not be spacebands at the beginning of a line, or that line
will be your last. You must use commas as shown above. All of the
information shown is required in the format shown. You must start the
file with a single line, which is your name. You may abbreviate the
file like this if you choose:
Jeffery R. Parnau
The file CUSTOM.LOG looks like this:
2nd in Command
These entries are for custom descriptions of your type of flying. They
will be truncated to fit the screen and printout. You may have up to 14
custom entries, as shown above. You can make fewer entries than that if
In using the program, time is generally manipulated with the + - keys.
Entries on the screen in parentheses are computed automatically.
However, you may use digits to manipulate the total time.
You can increment the date with the plus and minus key.
The plus and minus keys will also scroll you through the aircraft you
have put into the AIRCRAFT.LOG.
The last flight is recorded into a file, and will pop up as the next flight
when you run the program again.
The utilities are not currently available. I'll write some if you have any
suggestions, but the program pretty well runs without any outside stuff for
The default file COLORS.LOG sets your screen in the mono mode, which may
be boring if you have color available. In that case, choose the COLORS option
and play around with it.
I'm unaware of any serious bugs in the program, although you can screw it up
if you work at it. For example, if you choose the "next" flight option, and
then don't input the next flight, the poor program tries to figure out how
you had a flight with no departure point. However, if you crash it, just
restart it. Your files will be intact.
One nice feature of this program is that you can create a "background" log
of your activity. That way, if you begin to use this program to maintain your
log, you don't have to input previous flight information. Choose Print/Main-
tain, and you'll be asked a series of questions based upon your CUSTOM.LOG.
You'll notice a lot of automatic calculating going on with the program. If
you enter IFR time, it will be deducted from VFR time for that flight. If
you add to the DUAL column, it will come off of the PIC entry. And because
most serious pilots fly mostly cross country, most of which is VFR, and
most of which is PIC, those entries default to TT unless you change them
yourself, which is easy enough. Play with the input screens for a while
before you get into officially using the program, and you'll get the
Suggestions or comments are welcome. CIS: 71555,126 or ExecPC, Jeff Parnau,
or the IFR BBS, (414) 784-6458. Blue side up!