Rick et all
Bill's suggestion about running a pretend log (I usually stack in 20 Q's or
so which gets to the backup log save routines etc......not a simulation) is
an excellent one and one I do quite often especially if I'm running a new
release of TRLog (which happens a lot! ~8^).
When you are DONE testing (or if you make major changes to the logcfg.dat
file) things to remember are, make sure you do an <ALT U> which empties and
then deletes LOG.TMP. Remember to delete the files RESTART.BIN;
BANDMAP.BIN as well as the test LOG.DAT file and what ever temporary backup
log file you may have created. These files are all created automatically by
the program with new data when you start the contest proper.
>On Thu, 10 Dec 1998 05:27:58 GMT, "Rick Bullon" <firstname.lastname@example.org>
>> I don't want to get to the end of the contest and find out my log is
>>not good became I messed something up in the setup.
>Rick, may I offer a suggestion? Whether you get your hardware wired
>up or not, always run a "pretend" contest a day or two before the real
>one, including log printouts and everything. That's the time to find
>out if everything is working - not at the end of the real contest.
>73, Bill W7TI
FAQ on WWW: http://www.contesting.com/trlogfaq.html
Administrative requests: trlog-REQUEST@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html