Mail Archive Search: <+from:dawley@execpc.com>

Results:

References: [ +from:dawley@execpc.com: 6 ]

Total 6 documents matching your query.

1. [TRLog] Feature request (score: 1): Author: dawley@execpc.com (Scott Dawley); Date: Wed, 1 Dec 1999 13:39:24 -0800 (PST); If this is already in TRLog, forgive my intrusion on the bandwidth. I built a "Radio Shack Special" DVK that I trigger via TRLog. It uses the radio's VOX, not the PTT circuit. I'd rather have TR swit; /archives//html/TRLog/1999-12/msg00005.html (7,285 bytes)
2. [TRLog] Serial #, Pathological behavior in a network (score: 1): Author: dawley@execpc.com (Scott Dawley); Date: Mon, 8 Nov 1999 07:06:56 -0800 (PST); I was playing around last night after the contest to simulate two radios in the SS, each radio pausing when/if the other is finishing a QSO. What I found is that EVEN IF you keep only one transmitter; /archives//html/TRLog/1999-11/msg00094.html (8,544 bytes)
3. [TRLog] Serial #, Pathological behavior in a network (score: 1): Author: dawley@execpc.com (Scott Dawley); Date: Mon, 8 Nov 1999 10:20:30 -0800 (PST); Yup...Daniel has described exactly the scenario I was testing, but instead of knocking on a wall, wait, and vice-versa. But the serial #'s got hosed in the process if either op was in the middle of a; /archives//html/TRLog/1999-11/msg00100.html (13,720 bytes)
4. [TRLog] Serial #, Pathological behavior in a network (score: 1): Author: dawley@execpc.com (Scott Dawley); Date: Mon, 8 Nov 1999 10:37:45 -0800 (PST); I concur...I tested this leaving LOTS of time between exchanges on the two computers, and the serial #'s still got hosed. "Lots of time" = 30 seconds +/-. == Please direct any replies to dawley@execp; /archives//html/TRLog/1999-11/msg00104.html (9,739 bytes)
5. [TRLog] Uneven CW on callsign (score: 1): Author: dawley@execpc.com (Scott Dawley); Date: Thu, 18 Nov 1999 14:05:19 -0800 (PST); Gentlemen, and others ;-), I just acquired a 33mhz 386 or 486. When TRLog is sending the other station's callsign in the exchange, the CW is uneven and choppy. Once their callsign is sent, the rest o; /archives//html/TRLog/1999-11/msg00198.html (6,943 bytes)
6. [TRLog] Time discrepencies, NT (score: 1): Author: dawley@execpc.com (Scott Dawley); Date: Sun, 5 Sep 1999 08:16:51 -0500; Last night during the Sprint, TrLog was reporting the incorrect time. The time on my laptop was correct (I had the clock open so I could keep track) but as QSO's progressed, the reported time in TrLo; /archives//html/TRLog/1999-09/msg00007.html (6,962 bytes)

Current List: 1 - 6
Page: [1]