World of Ham Radio 1997/WOHR97_AmSoft_(1997-02-01).iso/log/contest/con_12/amsoft.iii

Text File | 1997-02-01 | 22KB | 353 lines

FD LOGGER -1200f (PC) written by Harry Bump  KM3D.
                    PO Box 392
                    Richland  PA   17087
Ladies & Gentlemen!

Here is the 1995 edition of the FD-1200 logging program.
There are some definite improvements and enhancements.  Operators
may now configure screen colors from the PRE.EXE menu to fit
personal tastes and monitor types.  There is a 'keyboard mirror'
that always shows the most recent 75 keypresses - an automatic
scratchpad!  The operator is notified immediately upon logging a
new multiplier along with a tally of multipliers worked.  Also.
dependence on the 'CAP-LOCK' key has ended.

If you find this program of value and use it in Fieldday
a donation of $10.00 is requested.

The program is distributed complete and fully documented. as was
previous versions.  Your donation will make the distribution
of future program enhancements possible. and makes available my
technical support  PRIOR TO and AFTER the contest.

As I am also an active Fieldday contester. technical support
WILL NOT be available during the test - MAKE SURE YOU SETUP.
RUN. AND UNDERSTAND the program BEFORE THE CONTEST WEEKEND!

There are three executable files in this program:

    PRE.EXE
    LOG.EXE
    POST.EXE

Most is self-explanatory.  The program is supposed to be SIMPLE
to operate.  You should be able to concentrate on CONTESTING.
not computering.

The program was written using Borland's Turbo-Basic on a 386-SX
VGA system and tested on a 286-monochrome system.  A hard drive
is a real asset and a necessity if you want 'real-time' speed.
The program does not use extended or expanded memory.  It will
permit you to log up to 1250 QSO's if you have 640 kb RAM.  After
the 1250th QSO you will be able to edit and view your QSO's and
to check dupe status of any new contacts with the first 1250 but
you're done logging on the system and your printed reports will
only show and summarize QSO's to the 1250 limit.

INSTALLATION:  If you have a hard drive. create a subdirectory
and then copy the contents of this floppy into it.  Make the
subdirectory your current directory and type 'PRE.EXE'.  Select
'A' to modify your contest setup. ie.  name. call. address.
contest name. etc.  The last two lines of this screen show the
directories where you have your program and data files.  These
MUST indicate the proper path to the subdirectory you have
created. When you answer the prompt 'OK' the program will write
the CONTEST.DAT file into your program directory.  Note: this
may be done at any time. For example. after the contest you may
copy your files from hard to floppy disk. change the path to
your files (here). and then run POST.EXE from the floppy drive.
If you attempt this make sure you understand what you're doing.

Next. select 'B' to initialize your data files (erases any
previous data).  If you wish to put program or data files on a
floppy disk put the disks into the appropriate drives before
modifying the setup (A).

Example:  If you have copied the program files into subdirectory
FDLOG on drive C and you wish to put your data on drive A. the
last two lines of your setup would look like this:

            PGM FILES:    C:\FDLOG\
            DATA FILES:   A:\

Note: Unless you understand thoroughly what you are doing and
have a specific reason for doing so. you should put your data
files in the same drive\path as your program.

            PGM FILES:   C:\FDLOG\
            DATA FILES:  C:\FDLOG\

LOG.EXE is the actual logging program.  The main menu shows the
major functions.  Experiment!  When logging QSO's. input errors
are easy to correct.  During input. the BACKSPACE key may be
used to undo keying errors.  If you don't like the contents of a
previously entered field. simply press <ENTER> with NO INPUT in
the current field - your input prompt will backup to the
previous field.  After the last field is entered. you will be
asked if the data is OK.  The ONLY input that will log the QSO
is 'Y' - any other key will back you up to the previous field.
Upon entering 'Y' the program WILL WRITE THE CONTACT TO THE DATA
DRIVE.

Errors found after the contact is entered completely may be
corrected using F5 from the main menu.  The QSO shown at the top
of the screen is edited by pressing <ENTER>.  The page up. page
down. and arrow keys will move you through the data. or you may
enter a QSO number and enter to go to that QSO.  Any data may be
changed EXCEPT your qso number. which has been logged.  The QSO
may not be deleted.  Duplicate contacts may be flagged by
entering 'DUPE' in the section field.  The computer also writes
the corrections to the data disk when you leave the corrections
screen.

You may be surprised to find that when your cursor gets to the
class field. the class and section name are already there!  If
you have previously worked a station on another band or mode.
the info will be pulled into the fields of your current entry.
By pressing <ENTER>. you can accept that input.  Any character
key will clear the field and begin new input.  Pressing F6 will
get you the section summary screen.  You may use the arrow keys
there to select a section.  <ENTER> will pull that multiplier
down into the section field. <ESC> will take you out of the
multiplier screens without pulling a multiplier.


When working mobile or portable stations. enter ONLY the
callsign.  When a station is worked for the second or more time.
the 'dupe' window will pop up and show you where he has been.
Enter 'Y' to override and log the QSO if he is in a 'new'
section.  Any other key will clear the call and allow new input.

The program will accept '/m' etc - but will not show a duplicate
QSO if you have logged W3ABC and W3ABC/m (or W3ABC/3.. whatever).

When leaving the LOG.EXE program make sure that you use the F9
key. the computer saves several print files upon leaving the
logger.  If you have an other than normal termination of the
program. these will not exist and the POST.EXE print program
will not run.  If this happens. simply re-run the LOG.EXE
program and then press F9.  The POST.DAT file that is printed
upon leaving LOG.EXE is a copy of the QSO.DAT file net of
corrections (CORR.DAT).

The only file that can be lost in the event of a power failure
is the dupe index.  It will be on the disk but will result in a
dupe sheet that is NOT alpha-numeric.  This file can be
re-created AFTER (or during) the contest from the selection on
the POST.EXE menu.  It can be quite time-consuming. I recommend
that you continue to operate and then take the time to rebuild
the index after the contest is finished.

The POST.EXE program will let you print a summary. multiplier
list. logs. and dupe sheets.  The log is printed
chronologically. the dupe sheets by band and mode.  The dupe
index rebuild must be used ONLY if you have had a system lock-up
or power failure. it will sort and create the index necessary to
print the QSO's alphabetically by band and mode.  When printing
the log entries or dupe sheet. after pressing 'P' to pause. you
can reset the delay.  that is. the rate at which data is sent
from your pc to the printer.  The minimum is set at 100 (fastest
transfer) to 999 (slowest transfer).  This was made available
because of the various transfer rates of machines and printer
buffer sizes.  If the delay is set properly. the print buffer
will be mostly empty. so that if you must stop the printer.
entering 'P' will pause the program with no data sitting in the
printer buffer.

There is also an option for export in several formats.  The first
is for ARRL reporting. the second is an ALPHA4(tm) database and
the third is for LOGIC(tm) database. written by Dennis Hevener.
WN4AZY. of Personal Database Applications.  The files. ALPHA4.XFR
and LOGIC4.XFR are both delimited with the tab character between
fields and each record terminates in a carriage return.  The ARRL
reporting file is an ASCII file with a single field for each QSO
one line in length.  Below are charts showing the field names for
the FD-1200f and the corresponding fields for the export files.
along with the file structure definition for POST.DAT. which may
help you with any other specific use you may have for the
program.

I am a LOGIC4(tm) user and am always pleased to hear from other
contesters who are also LOGIC(tm) users.

I hope you enjoy using this program. and that it makes a
positive change in your participation (and score).  Enhancements
and changes will be made as suggested and practical.

            73 and good contesting.

            Harry Bump. KM3D.
            PO Box 392
            Richland. PA   17087















































            DATA FILE USE

    PRE.EXE            LOG.EXE           POST.EXE
----------------------------------------------------------------
READS:

    CONTEST.DAT        CONTEST.DAT       CONTEST.DAT
    COUNTIES.DAT       BANDS.DAT         BANDS.DAT
    SECTIONS.DAT       COUNTIES.DAT      COUNTIES.DAT
    COLORS.DAT..       SECTIONS.DAT      SECTIONS.DAT
    ............       QSO.DAT           POST.DAT
    ............       CORR.DAT          SCORE.DAT
    ............       DUPE.DAT          CTYWKD.DAT
    ............       COLORS.DAT..      SECWKD.DAT
    ............       ............      COLORS.DAT

and WRITES:
    CONTEST.DAT        QSO.DAT
    BANDS.DAT          CORR.DAT
    QSO.DAT            DUPE.DAT
    CORR.DAT           POST.DAT
    DUPE.DAT           SCORE.DAT
    COLORS.DAT..       CTYWKD.DAT
    ............       SECWKD.DAT




            POST.DAT  -  FILE STRUCTURE

Each record in POST.DAT is a single field and is not less than
38 characters in length.  The following data may be used to write
your own customized export utility or export directly into a
program capable of manipulating the data.  For example. the data
may be directly imported by Lotus 1-2-3(tm) as text and then
columns in the spreadsheet may be created to display parts of the
field using the string functions available in Lotus - LEFT  MID
and RIGHT.  The column holding the source data may be hidden and
the data may be manipulated to suit the needs of the user.

LENGTH    DESCRIPTION

10    Callsign
2    Band/Mode - record number from BANDS.DAT file
10    Date - MM-DD-YYYY
8    Time - HH:MM:SS
4    Class
1    New multiplier flag
3     Section








            ALPHA4.XFR

    ALPHA4(tm)        from FD-1200f
--------------------------------------------------
 1    CALLSIGN               CALLSIGN
 2    QSO_DATE (DD/MM/YYYY)  QSO DATE
 3    QSO TIME (HHMM)        QSO TIME
 4    BAND                   BAND
 5    MODE (SSB/CW)          MODE
 6    REPORT          59(9)
 7    NAME            ----
 8    QTH            ----
 9    COUNTRY            ----
10    CONTINENT        ----
11    ITU ZONE        ----
12    CQ ZONE            ----
13    REGION            ----
14    PROVINCE        ----
15    DIG_NO_         ----
16    AGCW_NO            ----
17    HSC_NO            ----
18    MEMBER_OF        ----
19    AWARDS          ----
20    SPEC_EVENT        ----





            LOGIC4.XFR

    LOGIC4(tm)        from FD-1200f
--------------------------------------------------
 1    CALL            CALL
 2    QSO_DATE        QSO DATE
 3    TIME_ON            QSO TIME
 4    TIME_OFF        ----
 5    RST_SENT        59(9)
 6    RST_RCVD        59(9)
 7    NAME            ----
 8    QTH            ----
 9    MODE            MODE (SSB/CW)
10    FREQ            ----
11    BAND            BAND
12    STATE            ----
13    COUNTRY            ----
14    QSL_SENT        ----
15    QSL_RCVD        ----
16    COMMENT            FIELDDAY # - CLASS ARRLSECT:
17    VIA            ----
18    OPERATOR        CONTEST STATION CALL
19    CONTEST_ID        FIELDDAY
20    NOTES            ----
21    ADDRESS            ----
22    PWR            ----