Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+Re\:\s+\[TRLog\]\s+NAQP\s+Experiences\s+\-\s+Omni\s+VI\+\s+\&\s+TRLog\s+6\.72\s*$/: 3 ]

Total 3 documents matching your query.

1. [WriteLog] Re: [TRLog] NAQP Experiences - Omni VI+ & TRLog 6.72 (score: 1)
Author: k4sb@earthlink.net (K4SB)
Date: Wed, 15 Jan 2003 03:55:04 +0000
You guys without an OMNI VI go away. As background, about a week ago, my OMNI VIB+ just started refusing to return the frequency on every contest program I have. Nothing would make it work, so I call
/archives//html/WriteLog/2003-01/msg00242.html (10,812 bytes)

2. [WriteLog] Re: [TRLog] NAQP Experiences - Omni VI+ & TRLog 6.72 (score: 1)
Author: k4sb@earthlink.net (K4SB)
Date: Wed, 15 Jan 2003 04:01:35 +0000
For some reason, the reflector bounced this message. So, here's a requote.
/archives//html/WriteLog/2003-01/msg00243.html (12,285 bytes)

3. [WriteLog] Re: [TRLog] NAQP Experiences - Omni VI+ & TRLog 6.72 (score: 1)
Author: jbrannig@optonline.net (Jim Brannigan)
Date: Wed, 15 Jan 2003 05:53:16 -0500
Interesting, it is a great diagnostic tool. I have never seen this before. I'll give it a try. The slow "handshake" explains why the OMNI VI+ is a little flaky with some software. Now that it is "out
/archives//html/WriteLog/2003-01/msg00245.html (10,189 bytes)


This search system is powered by Namazu