Во время соревнований

The scenario

During a contest you should know all the basic functions of the program like changing frequency, band and mode. The program should have no secrets anymore. Your only concern is making QSO's, working multipliers, having a good strategy. The manual is lying next to you but you don't need it, the key assignments (shortlist) has been printed and is hanging within visual range so when you might forget you can take a peek.

You know there are no bugs in your version because you tested it, made test QSO's. No concern during the contest. You have reported bugs long before the contest and of course these are solved long before the contest starts.

Long before the contest you have read the Key Assignments, Basic Functions, Setting up the Program, Entry Window and the Quick Tour to have basic program information. So questions have been asked and answered, the manual has been read several times.

You have made a clean database, recorded your wav files and programmed your cw messages, etc. weeks before the contest.

Nothing can happen to you, you have prepared!

Bugs

When a bug was missed during testing and comes out during the contest please report it right after the contest or during the contest if it is a showstopper. Tom participates in many contests but he also reads the mail during contests and can give hints or sometimes bring out a new version. In addition to Tom there are many other hams available who can help solving problems, giving hints etc.

Rather than writing down problems during the contest try the following:

  1. Use Alt+N to write a note that will be attached as a comment to the QSO.
    1. E.g. "This call not in master.dta."
  2. At the end of the contest, use the menu option 'View | Notes' to see all the notes you have made during the contest.