Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+INPUT\s+CONFIG\s+FILE\s+vs\s+STDCFG\.DAT\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+INPUT\s+CONFIG\s+FILE\s+vs\s+STDCFG\.DAT\s*$/: 9 ]

Total 9 documents matching your query.

1. [TRLog] INPUT CONFIG FILE vs STDCFG.DAT (score: 1): Author: n2mg@eham.net (Mike Gilmer, N2MG); Date: Thu, 05 Dec 2002 14:26:28 -0400; Having read about the difference between using INPUT CONFIG FILE vs STDCFG.DAT, I cannot see the reason why anyone would want to use INPUT CONFIG FILE setting. What kind of config info is the INPUT C; /archives//html/TRLog/2002-12/msg00024.html (7,283 bytes)
2. [TRLog] INPUT CONFIG FILE vs STDCFG.DAT (score: 1): Author: geoiii@kkn.net (George Fremin III - K5TR); Date: Thu, 5 Dec 2002 10:31:56 -0800; The INPUT CONFIG FILE was used before there was a feature that used the STDCFG.DAT file. -- George Fremin III - K5TR geoiii@kkn.net http://www.kkn.net/~k5tr; /archives//html/TRLog/2002-12/msg00025.html (7,634 bytes)
3. [TRLog] INPUT CONFIG FILE vs STDCFG.DAT (score: 1): Author: jimsmith@shaw.ca (Jim Smith); Date: 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 ex; /archives//html/TRLog/2002-12/msg00029.html (15,579 bytes)
4. [TRLog] INPUT CONFIG FILE vs STDCFG.DAT (score: 1): Author: n2mg@eham.net (Mike Gilmer, N2MG); Date: Thu, 05 Dec 2002 17:50:40 -0400; 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 overw; /archives//html/TRLog/2002-12/msg00031.html (7,943 bytes)
5. [TRLog] INPUT CONFIG FILE vs STDCFG.DAT (score: 1): Author: juhan@chem.ut.ee (Juhan Poldvere); Date: Fri, 06 Dec 2002 00:36:39 +0200; We have sometimes used INPUT CONFIG FILE to describe workplace-specific parameters in a multiop setup thus making it possible to prepare only one LOGCFG.DAT (See Ex.3 in The Manual). The reason we c; /archives//html/TRLog/2002-12/msg00033.html (7,904 bytes)
6. [TRLog] INPUT CONFIG FILE vs STDCFG.DAT (score: 1): Author: jimsmith@shaw.ca (Jim Smith); Date: Thu, 05 Dec 2002 14:58:00 -0800; 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; /archives//html/TRLog/2002-12/msg00034.html (9,443 bytes)
7. [TRLog] INPUT CONFIG FILE vs STDCFG.DAT (score: 1): Author: n2mg@eham.net (Mike Gilmer, N2MG); Date: Thu, 5 Dec 2002 20:16:36 -0500; I've learned over the years to never ask, "But why would you want to do that?" I don't know about you, but while I'm learning a program, or a contest, I need to tweak my messages. "Note, however, th; /archives//html/TRLog/2002-12/msg00035.html (8,433 bytes)
8. [TRLog] INPUT CONFIG FILE vs STDCFG.DAT (score: 1): Author: kl7ra@blizzard.gcgo.nasa.gov (KL7RA); Date: Thu, 5 Dec 2002 20:53:03 -0900; I use TRLog for single-op-single band, SO2R and multi-op contesting so I find all three configuration files handy. The stdcfg.dat holds all my color setups and I have changed many from the default. I; /archives//html/TRLog/2002-12/msg00036.html (8,345 bytes)
9. [TRLog] INPUT CONFIG FILE vs STDCFG.DAT (score: 1): Author: jimsmith@shaw.ca (Jim Smith); Date: Thu, 05 Dec 2002 21:59:29 -0800; Hi Mike, Comments interspersed. And so do I. It's taken me 2 years to get some of them right. In my defence I did say, "Once you have them figured out," but didn't say, "Even if it took 2 years." +++; /archives//html/TRLog/2002-12/msg00037.html (9,816 bytes)

Current List: 1 - 9
Page: [1]