Mail Archive Search: <+from:n6tr@teleport.com>

Results:

References: [ +from:n6tr@teleport.com: 941 ]

Total 941 documents matching your query.

301. [TRLog] TR Log Version 6.45 Release Notes (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 25 Oct 1999 05:53:02 -0000; TR Log Version 6.45 has been released. It has been mailed to the distribution list and has been posted on the BBS. Check out the GETTING UPDATES chapter of the manual for more information on updates.; /archives//html/TRLog/1999-10/msg00078.html (8,864 bytes)
302. [TRLog] SS On/Off Times (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 26 Oct 1999 15:32:05 -0000; I think the plan was for the log checking software to determine the operating time based upon the log itself. However, since listening time counts as operating time, I don't see how this can be done; /archives//html/TRLog/1999-10/msg00086.html (8,201 bytes)
303. [TRLog] SS On/Off Times (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 26 Oct 1999 15:33:48 -0000; There is a problem with this with Cabrillo - as it is more than a log format... it is a complete entry format - including the summary sheet. Currently - there is no provision for including op time e; /archives//html/TRLog/1999-10/msg00087.html (7,719 bytes)
304. [TRLog] N6TR schedule (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 27 Oct 1999 14:21:45 -0000; I will not be in the CQ WW SSB - so, I will be around if anyone has any questions. However, on the 4th of November until the Monday afterwards, I will likely be out of touch from both the phone and i; /archives//html/TRLog/1999-10/msg00092.html (7,160 bytes)
305. [TRLog] SS On/Off Times (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 27 Oct 1999 18:41:07 -0000; Yup - I understand the problem. Even I, myself, world class contester extraordinare, have gone 30 minutes without a QSO in the SS - sitting in front of the rig trying. (How is that for the opposite; /archives//html/TRLog/1999-10/msg00097.html (8,118 bytes)
306. [TRLog] Packet Interface (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 29 Oct 1999 02:16:58 -0000; When you are not connected, the spots are in a different format, and currently TR doesn't understand that format. Tree -- FAQ on WWW: http://www.contesting.com/trlogfaq.html Submissions: trlog@conte; /archives//html/TRLog/1999-10/msg00110.html (7,559 bytes)
307. [TRLog] 6.45 aaarrrrgggggh! (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 29 Oct 1999 04:25:53 -0000; Oops - I moved instead of copied and the command to change the data to upper case was only present for the radio two command. This is a simple "bug" and will be fixed for the next release. Not a rea; /archives//html/TRLog/1999-10/msg00115.html (7,292 bytes)
308. [TRLog] 6.45 Mode Won't change (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 30 Oct 1999 16:06:54 -0000; If you are using a single mode contest (like the CQ WW), once you have made one QSO, the mode will be "stuck". This prevents accidentially changing the mode in the middle of a single mode contest. T; /archives//html/TRLog/1999-10/msg00123.html (7,221 bytes)
309. [TRLog] Re: (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 30 Sep 1999 23:51:28 -0000; Yes - I have received at least one report that an MP is okay? I deleted the message - but I think that is what I was told. At any rate - I have developed a neat little trick that will hopefully make; /archives//html/TRLog/1999-09/msg00002.html (6,629 bytes)
310. [TRLog] Time discrepencies, NT (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 5 Sep 1999 14:52:45 -0000; Yes - running TR under NT is difficult. This is why the CW would sound choppy - if you used the computer to send code with (which I assume you didn't). I am not an NT expert (others on list might be; /archives//html/TRLog/1999-09/msg00008.html (7,610 bytes)
311. [TRLog] shft key tuning (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 5 Sep 1999 17:30:29 -0000; Pretty much the same for all radios. The communications channel is busy with the QSY commands and can't deal with the frequency update info until you have stopped QSYing. Tree -- FAQ on WWW: http://; /archives//html/TRLog/1999-09/msg00011.html (7,017 bytes)
312. [TRLog] Wrong call (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 5 Sep 1999 17:38:35 -0000; Half of this can be cured by turning CALLSIGN UPDATE ENABLE = TRUE. This will fix your log entry. However, TR will still send the callsign that is in the call window instead of the "correct" call in; /archives//html/TRLog/1999-09/msg00012.html (7,930 bytes)
313. [TRLog] Wrong call (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 5 Sep 1999 23:33:05 -0000; Hmm - you could be right. I kind of remember doing something like that but I couldn't make it work that way. I will do a little more digging. Tree -- FAQ on WWW: http://www.contesting.com/trlogfaq.h; /archives//html/TRLog/1999-09/msg00017.html (7,744 bytes)
314. [TRLog] CW Sprint curiosity (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 6 Sep 1999 17:22:33 -0000; This indicates that the TRMASTER database knew their name. Tree -- FAQ on WWW: http://www.contesting.com/trlogfaq.html Submissions: trlog@contesting.com Administrative requests: trlog-REQUEST@contes; /archives//html/TRLog/1999-09/msg00021.html (6,814 bytes)
315. [TRLog] Rovers (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 9 Sep 1999 20:59:44 -0000; This is how it works now. Tree -- FAQ on WWW: http://www.contesting.com/trlogfaq.html Submissions: trlog@contesting.com Administrative requests: trlog-REQUEST@contesting.com Problems: owner-trlog@co; /archives//html/TRLog/1999-09/msg00035.html (7,383 bytes)
316. [TRLog] Rovers (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 9 Sep 1999 22:39:42 -0000; Calls can be up to 12 characters in total length. Tree -- FAQ on WWW: http://www.contesting.com/trlogfaq.html Submissions: trlog@contesting.com Administrative requests: trlog-REQUEST@contesting.com; /archives//html/TRLog/1999-09/msg00037.html (7,384 bytes)
317. [TRLog] crashes (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 12 Sep 1999 16:12:10 -0000; My best guess with this data is it something to do with the TRMASTER file. There were some fixes in 6.43 to improve the stability of TRMASTER operation that might explain what you have seen. I will; /archives//html/TRLog/1999-09/msg00044.html (8,272 bytes)
318. [TRLog] crashes (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 12 Sep 1999 17:01:23 -0000; Do you have the file TRMASTER? Even if you aren't using it - it will be loaded in. Can you do this: Start the program the TR TRACE and then make it fail - and tell me what characters show up in the; /archives//html/TRLog/1999-09/msg00046.html (7,624 bytes)
319. [TRLog] crashes (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 13 Sep 1999 05:21:26 -0000; The ( indicates that the program is about to do the floppy save feature. The ) character would appear if the save was done successfully. I believe you said you were using 6.42. Here is an excerpt fr; /archives//html/TRLog/1999-09/msg00048.html (7,838 bytes)
320. [TRLog] QTCs (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 13 Sep 1999 15:47:03 -0000; There is no way to do this currently - and I am sorry to say that the problem is very difficult to solve. I doubt I will be able to do anything about this in future releases. It is just a limitation; /archives//html/TRLog/1999-09/msg00052.html (7,791 bytes)

Current List: 301 - 320
Page: [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20]