The big step in contesting for most of us is obtaining RTTY by WF1B software. But there are other software programs available suitable for RTTY contesting and and have been endorsed by contesters: HAM by OH2GI, EasyTerm by W1EOR, Scotchlg by WA7EGA, WriteLog by W5XD, Log-EQF by N3EQF, Lan-Link by W3/G3ZCZ, COMPRTTY by David Rice, and Marathon by N0IOS for the Macintosh. Others have used dual systems such as Windows Terminal for operating and CT for logging. Hopefully, what follows will be largely applicable to all contesting programs. Which brings me to the most important suggestion: READ THE MANUAL! Read it AGAIN! Read it before every contest. Nobody knows the program like the author.

Internet access is crucial for the contester; It's where you find the rules, the results, the schedule, ask questions, learn late news items, and generally become aware of what is happening on the RTTY contest scene.

Murphy's law is at it's peak during a contest. There are some techniques that will protect your log files (.BIN, .NDX, .WKS) with backups. Actually, a combination of techniques is needed for 100% protection.

* AUTOSAVE ON Type this into the callsign box each time you reboot the program. You must have a diskette in the A drive. It will immediately write a copy to the diskette and every hour on the hour thereafter. As the logs get bigger, the write time will take longer and it can be disconcerting when you are in the middle of a contact at xx00 hours and the computer goes into autosave mode. 500 QSO takes about 10 seconds. This method still leaves up to an hour of contacts without backup.

* SAVELOG A Type this at frequent intervals when free. This will supplement or replace the AUTOSAVE hourly save.

* PRINT ON Type this to send each logged call to the printer. This gives a nice record that can be manually typed in to add the few calls logged since the last save to diskette ... but you may not like the noise. Another option to protect those last few calls is to use a shareware program:

* PRN2FILE.EXE This little TSR program can be used to intercept the printer output and store it in a file instead of actually printing it. I use PRN2FILE but there are many more available by an Inet search or E-Mail to me.   (Download Now) It is best implemented in the batch start up file. If you have to reconstruct some calls, print them out, enter as a normal contact into WF1B and then correct the time/date with alt-E.

When you start using some of the program bells and whistles, it's easy to forget something. I like to start up with a batch file which can be quickly created with any editor; the DOS EDIT program is fine. For instance, I am gearing up for BARTG97, I'll be using RITTY by K6STI, and I want my printer output to be redirected to a file d:\rtty\bartg97.sav. I have a very large FRIEND.INI file and want to limit the reserved QSO memory to 1000 contacts to make lots of room for the friend.ini file and RITTY.

Type EDIT to start the DOS editor and enter the following lines:

DATE                     :: Push enter if OK
TIME                      :: get it right via WWV
C:\MISC\PRN2FILE
D:\RTTY\BARTG97.SAV             :: installs PRN2FILE Utility
LH RITTY I                    :: installs RITTY TSR
COPY RTTY.SAV RTTY.INI                  :: I keep master copy as rtty.sav
CALL RTTY -1K BARTG97                  :: Start RTTY with 1000 QSO max
RITTY U                                                  :: removes TSR when I quit RTTY
C:\MISC\PRN2FILE /U                          :: removes prn2file TSR

Then press alt-F, save as, and call it BARTG.BAT

Now, typing BARTG will automatically load everything and bring you to the profile data page; select the proper contest, TNC, etc as usual, the first time. You will have to type in AUTOSAVE ON, PRINT ON, etc when the main screen appears EACH TIME you fire up.

The macros on PF keys 1-10, shift-PF 1-10, and alt-B, can all be customized for the responses, techniques, contingencies, and styles you wish to use in a contest. This page contains a long article on WF1B macros.

     Different points in a contest require different responses. If you are running a low rate (<30/hr), longer responses with repetition of your call sign is helpful for other listeners. Long CQ's are needed to catch the occasional tuner-by. However, when the QSO rate starts to rise, shorter CQ's are useful .. and you won't even need to CQ if you have a run going. With long responses, it is hard to log much more than one call per minute, regardless of the the pileup. When running a pileup, much shorter responses are used by the leading contesters. They will typically send their call and the the other only once in the entire exchange. This presumes that people are in line and know what is happening and who's frequency it is. It is time well spent to watch the responses of the big scorers in a run.  You might want to write down what they use .. your day is coming.
     I (a little gun) typically use the shift-PF macros to give a longer version of the normal macro for the hard of hearing. An equally valid use is to make the shift-PF keys a shorter version for strong stations and when time is of the essence, such as S/P while simultaneously running a freq, particularly powerful with a two-rig station. Also, a long CQ can be transmitted by simply pressing the short CQ key twice. HAM by OH2GI permits selecting a general short-medium-long mode for selected macros, which allows rapid adjustment to conditions. See the programmable keyboard in the Advanced paper for even more options.

Ever get the radio on a different band than WF1B is set for and mis-log a contact? This can cost contacts not to mention the WRK B4 fingers. The solution is using the Rig Control feature of WF1B. If you have a suitable radio, changing the band on the radio will automatically change the main screen band for logging; and changing the band on the screen will change the radio VFO to a frequency you have pre-selected for each band. Really great at 3 AM.

Rig control requires another COM port, an adapter cable to convert from RS 232 levels to the levels used by your radio (I use the MFJ's, $50), a capable radio (most newer ones), and some set-up info in the RTTY.INI file. Detailed instructions are in the manual; for my rig, I had to add a COM port specification as it is non-standard, and a radio section:

[COM4]
BaseAddr=$2E8
IrqNumber=5
HandShake=none

[RADIO]
Type=kenwood
Comport=4

80=3578
40=7075
20=14070
15=21075
10=28080

I use the bottom edge of the band to start as I do a quick tune thru looking for any new ones before CQing; you may want to use your favorite run frequency. In the big contests, you will want to start lower down. If you are in Europe or feeling lucky, 7030 is a better place to start. RTTY by WF1B will get very upset if you turn off the radio while it is active.

A hint from Mark (WM7D):   I found something in the RTTY source that I think is useful. In the RTTY.INI file, add a line that says POLL=15 for rig control. I have never liked programs that poll the rig constantly, and the POLL line allows you to set a time interval (in seconds) for polling the rig.

If you are using one of these TNC's, you have a choice of using it in HOST or COMMAND mode. Picking the TNC from the profile page as PK 232 or PK 900 will cause it to be used in the HOST mode, where only a few commands programmed into WF1B can be set by alt-T. Many prefer to be able to change the TNC around on the fly with the full command set; selecting AEA CMD SET as the TNC permits this. I like to be able to switch RFRAME on and off as needed, for instance. If you are using the HOST mode and the computer crashes so you can't exit WF1B normally, the TNC will be left in the HOST mode, a very dumb state. To get it back to normal, run AEAUTIL provided with WF1B.

You may want to change the screen colors from the default; to do this, exit WF1B and run the COLORSET utility. This will be a little bit of trial and error to find a combo you like. I prefer a black background with yellow type to ease eye-strain. Be sure the Callsign block is highly readable in the highlighted mode. Make notes of the setting numbers you like in COLORSET; if you upgrade to a newer level, they are reset to default. My favorites (which may be hideous to you):

======Wyvern Technology    Color modification for RTTY.EXE=================



    Window     Frame      Header     Prompt     String     Ctrl       HiLite

     14         9           3          10        12         67         36

I keep a steno notebook of my boo-boos in logging and other notes of interest as the contest goes on. I make the changes to the log as soon as I have a moment using alt-E. But some are mysterious like "Why was ZL2 at 2221 not a new multiplier?". These require investigating afterward. When you have made all the changes you can with alt-E, EXIT the program and then restart. The changes you made are not recognized until you re-load. Then type WRITELOG to prepare all the paperwork automatically.

The results at this point are probably good enough for HCS listing but a closer examination is prudent. I make a copy of the files for auditing in a separate directory. First, examine the rules again for exactly what must be submitted to the contest committee. WF1B often prints out more files than are required for the contest; but they may be useful for your own checking. A good text editor with sort capability is essential; I like the shareware BOXER editor. Using a COPY of the testxx.ALL log, sort all the lines by the callsign. If you see, for instance, that you worked AB5KD on 80,40, and 15 meters but only AB5KDD on 20 meters, it is time for intense retrospection.

As the callsign prefixes change and new ones are added, check that a multiplier was given; especially states/provinces when they count. Worked a rare one or an unusual callsign? Check that the country code is correct; these are forever changing. You can modify the prefix list with the COUNTRY routine. Check the number of NEW COUNTRIES against the multiplier used in calculating your score. Watch the WF1B reflector; other competitors may post any problems they found. Look at your log with a suspicious eye and understand it all. If something strange still remains, put a comment on your summary sheet pointing out the possible problem; much better than them finding it.

The Summary Sheet should be extensively enhanced; be sure Low Power class is indicated explicitly if so; include your operating times if required; add some nice words (or at least from the heart) for the committee. Make the summary page as polished, complete, and accurate as your attached log; it creates the first impression. Mail it First Class Airmail overseas. An Example

73 de Dick, N1RCT