Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Trlog\]\s+TR688\s+and\s+Two\s+Orions\s+\-\s+odd\s+behavior\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Trlog\]\s+TR688\s+and\s+Two\s+Orions\s+\-\s+odd\s+behavior\s*$/: 2 ]

Total 2 documents matching your query.

1. [Trlog] TR688 and Two Orions - odd behavior (score: 1): Author: kd4d@comcast.net; Date: Mon, 19 Nov 2007 22:23:36 +0000; Hi everyone: I added "USE IRQS = TRUE" to my logcfg.dat file and started 6.88. I think TR complained about one line in my logcfg.dat file so I removed it. It read and controlled both Orions fine. As; /archives//html/TRLog/2007-11/msg00040.html (7,334 bytes)
2. Re: [Trlog] TR688 and Two Orions - odd behavior (score: 1): Author: John Unger <w4au@verizon.net>; Date: Mon, 19 Nov 2007 20:02:50 -0500; Hmmm... strange behavior, Mark, and I thought I had seen everything from TR! When you say, "...fourth character in the logging line...", do you mean the call sign entry or the exchange line? I'll try; /archives//html/TRLog/2007-11/msg00042.html (8,221 bytes)

Current List: 1 - 2
Page: [1]