Mail Archive Search: <+from:k6xx@k6xx.com>

Results:

References: [ +from:k6xx@k6xx.com: 7 ]

Total 7 documents matching your query.

1. [WriteLog] Learning WriteLog (score: 1): Author: "Bob Wolbert, K6XX" <k6xx@k6xx.com>; Date: Tue, 21 Feb 2023 11:48:51 -0800; I promised to learn WL for a contest this summer and have been struggling with it since December. It is difficult for a new user to adopt WL. Help is unhelpful-a prime example: writelog.ini is discus; /archives//html/WriteLog/2023-02/msg00031.html (11,350 bytes)
2. Re: [WriteLog] Learning WriteLog (score: 1): Author: "Bob Wolbert, K6XX" <k6xx@k6xx.com>; Date: Tue, 21 Feb 2023 13:51:04 -0800; Keith, Thank you. Yes, I've spent hours on both sites. K9JY was especially helpful and the most up-to-date, but is still way behind on version differences! The ini file location is especially importa; /archives//html/WriteLog/2023-02/msg00035.html (13,870 bytes)
3. Re: [WriteLog] Learning WriteLog (score: 1): Author: "Bob Wolbert, K6XX" <k6xx@k6xx.com>; Date: Tue, 21 Feb 2023 17:15:22 -0800; Randy, I was hoping you'd respond as I recall you describing your love of "shoveling" (your term?), and I simply could not see anyone efficiently doing that the way I have WL configured. More below..; /archives//html/WriteLog/2023-02/msg00041.html (18,710 bytes)
4. [WriteLog] Learning WL: INI Mysteries no longer as mysterious (score: 1): Author: "Bob Wolbert, K6XX" <k6xx@k6xx.com>; Date: Sat, 25 Feb 2023 08:24:58 -0800; Thanks to the helpfulness of the subscribers, my WriteLog is behaving itself and acting as a logger should. I needed that information on the .ini file since, as all of you know, a proper .ini is cruc; /archives//html/WriteLog/2023-02/msg00056.html (8,421 bytes)
5. [WriteLog] Ending K3/K4 DVR Messages (score: 1): Author: "Bob Wolbert, K6XX" <k6xx@k6xx.com>; Date: Sat, 25 Feb 2023 14:53:54 -0800; Mike, That single change did the trick and didn't even mess up CW! Thank you very much. FWIW, with another logger, one may access the second bank of K3 messages by programming the F key to send the B; /archives//html/WriteLog/2023-02/msg00060.html (9,546 bytes)
6. [WriteLog] JIDX Sends Exchange Twice (score: 1): Author: "Bob Wolbert, K6XX" <k6xx@k6xx.com>; Date: Fri, 7 Apr 2023 17:51:09 -0700; Set up for JIDX CW later this evening, but the program is sending the exchange twice. After repeating the exchange, it sends the TU message properly. I am using ESM. Sequence: 1. Input callsign, hit; /archives//html/WriteLog/2023-04/msg00006.html (7,219 bytes)
7. Re: [WriteLog] JIDX Sends Exchange Twice--Problem solved. (score: 1): Author: "Bob Wolbert, K6XX" <k6xx@k6xx.com>; Date: Fri, 7 Apr 2023 18:19:42 -0700; Thanks Ed. Cursor is in the exchange field, as it should be. That wasn't the problem. A few minutes after sending my message I thought about the Edit QSO Exchange Fields window. There are differences; /archives//html/WriteLog/2023-04/msg00008.html (8,949 bytes)

Current List: 1 - 7
Page: [1]