Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+Reflections\s+on\s+TR\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+Reflections\s+on\s+TR\s*$/: 2 ]

Total 2 documents matching your query.

1. [TRLog] Reflections on TR (score: 1): Author: ssi@rmi.net (Bill Leahy); Date: Wed, 28 Jun 2000 17:12:08 +0000; There is a time and place for learning TR and changing logcfg data. During a Field Day or contest is not one of them. Step by step (simple) instructions were available and used by all operaters. Befo; /archives//html/TRLog/2000-06/msg00124.html (7,576 bytes)
2. [TRLog] Reflections on TR (score: 1): Author: n4zr@contesting.com (Pete Smith); Date: Wed, 28 Jun 2000 17:52:12 +0000; I don't believe there is one built into TR. You could effect a limited fix by making the logcfg.dat file read only through DOS, so that at least permanent changes could not be made and you could get; /archives//html/TRLog/2000-06/msg00128.html (7,501 bytes)

Current List: 1 - 2
Page: [1]