Well, two comments.
1. Once you have your CW messages figured out, why would you want to
edit them?
2. When you make a CTRL-J change you are offered the option of saving it
in your logcfg.dat. If you do, the change will be written to the end of
the file, i.e. after your INPUT CONFIG FILE = statement. Next time you
restart TR it does everything that logcfg.dat says to do. Because your
CTRL-J change is read after the .icf has been loaded it overwrites
whatever value was there before. So, provided you save your CTRL-J
changes they will take effect the next time you start TR.
I forgot to mention another use of .icf files. If you're running a
multi-op like, say, Field Day, then each op can have his own TR
configuration. e.g. I bring with me to FD a floppy with VE7FO.icf on
it. When my shift starts I press CTRL-V and, at the prompt,
A:\VE7FO.icf. Now TR is set up the way I like it. Next op does the
same or uses CTRL-V to load a standardized configuration.
73 de Jim Smith VE7FO
Mike Gilmer, N2MG wrote:
>The danger with using the INPUT CONFIG FILE that I see is if you put a
>CW message in it, then edit it using CTL-J, and then restart TR, the
>changes made via CTL-J will be "lost" as they will be overwritten by
>the original settings still residing in the INPUT CONFIG FILE.
>
>Mike N2MG
>
>The following message was sent by Jim Smith <jimsmith@shaw.ca> on Thu, 05 Dec
>2002 12:14:08 -0800.
>
>>Hi Mike,
>>
>>Here's a reason.
>>
>>Use stdcfg.dat for items which don't change from contest to contest.
>>
>>Make up an Input Config File for each contest for those items which are
>>specific to that contest. For example, TR provides canned CW messages
>>and menus for some contests and not for others. In any event, I have
>>come to prefer my own messages and menus to some of those built in to TR.
>>
>
>_______________________________________________
>TRLog mailing list
>TRLog@contesting.com
>http://lists.contesting.com/mailman/listinfo/trlog
>
|