Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+Bug\s+update\s*$/: 13 ]

Total 13 documents matching your query.

1. [TRLog] Bug update (score: 1)
Author: n6tr@teleport.com (n6tr@teleport.com)
Date: 1 Dec 1999 18:45:52 -0000
1. ICOM Frequency Errors - I am taking a new approach and working with VK5GN to isolate the problem. I am going back to a previous version to establish that it didn't have the problem - and then will
/archives//html/TRLog/1999-12/msg00002.html (9,056 bytes)

2. [TRLog] Bug update (score: 1)
Author: K4RO Kirk Pickering <k4ro@k4ro.net> (K4RO Kirk Pickering)
Date: Wed, 1 Dec 1999 13:57:53 -0600 (CST)
What exactly are the ICOM Frequency Errors? I've been running a 761/765 pair for the last several contests, and haven't experienced any of the NONSSB or related problems. I used to be plagued with ra
/archives//html/TRLog/1999-12/msg00003.html (8,358 bytes)

3. [TRLog] Bug update (score: 1)
Author: k3ww@fast.net (Charles Fulp)
Date: Wed, 1 Dec 1999 20:34:13 -0000
I might as well chime in. I saw some of those NON ..something loggings for mode, and got 0 points until I edited them. I thought perhaps I forgot to set the NO POLL WHEN PTT or something.. I have an
/archives//html/TRLog/1999-12/msg00004.html (7,949 bytes)

4. [TRLog] Bug update (score: 1)
Author: n4zr@contesting.com (Pete Smith)
Date: Wed, 01 Dec 1999 22:13:58 +0000
OK, and here I come to confuse things. During SS, I had some weird things happen, including watching the NONSSB mode come and go again transiently (staying for just a second), coupled with the QSO an
/archives//html/TRLog/1999-12/msg00006.html (8,930 bytes)

5. [TRLog] Bug update (score: 1)
Author: n4zr@contesting.com (Pete Smith)
Date: Wed, 01 Dec 1999 22:04:54 +0000
Tree, the thing that puzzles me is that this did not happen to me last year in CQWW, when I had 2100 QSOs in the log, nor did it happen in SS this year, when I had 950. I don't recall what version I
/archives//html/TRLog/1999-12/msg00007.html (8,764 bytes)

6. [TRLog] Bug update (score: 1)
Author: k1ky@bellsouth.net (Tom Delker)
Date: Wed, 01 Dec 1999 19:39:50 -0600
This is the problem that I reported earlier that has been giving fits with the IC-735. Seems to be pretty much specific to that model and maybe certain interfaces. I think it was 6.43 or earlier that
/archives//html/TRLog/1999-12/msg00008.html (8,553 bytes)

7. [TRLog] Bug update (score: 1)
Author: marionh@jps.net (Marion J. Henson)
Date: Wed, 01 Dec 1999 17:24:28 -0800
Here's my 2 cents worth... Until August 11, 1999 I was using an IC-735. After resolving the intial setup problems with TR I have not experienced any problems with the 735 however I purchased an IC-74
/archives//html/TRLog/1999-12/msg00010.html (8,148 bytes)

8. [TRLog] Bug update (score: 1)
Author: k7zum@teleport.com (ken k7zum)
Date: Thu, 2 Dec 1999 02:31:53 -0800
these are intresting comments, as i have had the same problems with trlog coming up with the same nonssb messages, both here in my shack this weekend for c.q.w.w., and also as fs/k7zum last month for
/archives//html/TRLog/1999-12/msg00011.html (9,932 bytes)

9. [TRLog] Bug update (score: 1)
Author: fullgraf@kcc.com (Fullgraf, Chuck)
Date: Thu, 2 Dec 1999 06:45:52 -0600
To add to the confusion, I saw the jump to non-SSB and back on my Yaesu FT920 on a fairly regular basis (regular enough to see it). It never caused any logging or radio problems so I have not tried t
/archives//html/TRLog/1999-12/msg00015.html (9,778 bytes)

10. [TRLog] Bug update (score: 1)
Author: kl7ra@ptialaska.net (kl7ra)
Date: Thu, 2 Dec 1999 08:47:35 -0900
The Icom problem is not RFI as I saw it on two 781 radios with the "don't poll" feature on. Unlike Chas, I had a little more problem then just editing the log. I had to wait until the radio was polle
/archives//html/TRLog/1999-12/msg00016.html (8,643 bytes)

11. [TRLog] Bug update (score: 1)
Author: K4RO Kirk Pickering <k4ro@k4ro.net> (K4RO Kirk Pickering)
Date: Thu, 2 Dec 1999 12:48:34 -0600 (CST)
Are you Icom users certain that you have the internal TRANSCEIVE DIP switch set to OFF? While I do see the NON-SSB and "no-bands" screen flicker by occaisionally, it is no longer causing a problem. A
/archives//html/TRLog/1999-12/msg00019.html (8,594 bytes)

12. [TRLog] Bug update (score: 1)
Author: ua9cdc@dialup.mplik.ru (Igor Sokolov)
Date: Thu, 2 Dec 1999 23:43:34 +0500
I also see that happening and had to turn auto S&P off. The configuration here is IC-751a, no poll during ptt, 1200 baud. Who setthe prize. That sounds interesting. I just thought of getting some ne
/archives//html/TRLog/1999-12/msg00023.html (8,382 bytes)

13. [TRLog] Bug update (score: 1)
Author: juhan@chem.ut.ee (Juhan P&otilde;ldvere)
Date: Fri, 03 Dec 1999 00:54:45 -0800
Rich KL7RA: ...with a new version of the winning BUG. GL! -- Juhan, ES5QX -- FAQ on WWW: http://www.contesting.com/trlogfaq.html Submissions: trlog@contesting.com Administrative requests: trlog-REQUE
/archives//html/TRLog/1999-12/msg00024.html (7,823 bytes)


This search system is powered by Namazu