Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+wae\s+buffers\s+from\s+aa5au\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+wae\s+buffers\s+from\s+aa5au\s*$/: 8 ]

Total 8 documents matching your query.

1. [WriteLog] wae buffers from aa5au (score: 1): Author: jtolbert@gremlan.org (The Tolberts); Date: Mon, 5 Nov 2001 22:12:10 -0500; A couple of questions about the buffers: Can CQ be F1 instead of F2 (old habit)? I don't see a qso b4 buffer; anyone have an example? The F8 key looks like there may be a callsign stack somewhere ( Q; /archives//html/WriteLog/2001-11/msg00116.html (7,464 bytes)
2. [WriteLog] wae buffers from aa5au (score: 1): Author: aa5au@bellsouth.net (Don Hill AA5AU); Date: Mon, 5 Nov 2001 22:29:42 -0600; You can use F1 by activating CtCompatibleAccel=Yes in the writelog.ini file. Add this line: CtCompatibleAccel=Yes under [Configuration]. Refer to WriteLog help for more info. You can actually make an; /archives//html/WriteLog/2001-11/msg00117.html (9,952 bytes)
3. [WriteLog] wae buffers from aa5au (score: 1): Author: wa9als@starband.net (WA9ALS - John); Date: Tue, 6 Nov 2001 03:51:43 -0500; "The following three function keys behave as described here only if you set the CtCompatibleAccel entry in WRITELOG.INI to value "YES": F1 Sends the programmed message corresponding to F11." the let; /archives//html/WriteLog/2001-11/msg00122.html (10,242 bytes)
4. [WriteLog] wae buffers from aa5au (score: 1): Author: Ric Plummer" <ricp@alum.wpi.edu (Ric Plummer); Date: Tue, 6 Nov 2001 13:19:17 -0000; Don't forget that YES must be in all caps for CtCompatibleAccel=YES Ric KV1W or scrolling of course. %C); /archives//html/WriteLog/2001-11/msg00127.html (11,482 bytes)
5. [WriteLog] wae buffers from aa5au (score: 1): Author: w9hly@decaturnet.com (w9hly@decaturnet.com); Date: Tue, 6 Nov 2001 09:17:19 -0500; How does the contest checker handle the above situation? I log XY8YYY at 0100. Later, at 0230, the same station calls and we exchange (a dupe for me - and is marked as such). My log says we had a goo; /archives//html/WriteLog/2001-11/msg00128.html (8,289 bytes)
6. [WriteLog] wae buffers from aa5au (score: 1): Author: w9hly@decaturnet.com (w9hly@decaturnet.com); Date: Tue, 6 Nov 2001 09:28:00 -0500; How does the log checker handle the situation above? I log XX8YYY at 0100. At 0230 we log another. My log tags it as a dupe, XX8YYY logs it as a normal exchange. He gains. Do I loose? Does the checke; /archives//html/WriteLog/2001-11/msg00129.html (8,204 bytes)
7. [WriteLog] wae buffers from aa5au (score: 1): Author: jjreisert@alum.mit.edu (Jim Reisert); Date: Tue, 6 Nov 2001 06:33:29 -0800 (PST); My understanding is that computerized log checking does not penalize for dupes in your log -- dupes are treated as 0-point QSOs. Cabrillo logs by definition contain unmarked dupes. == Jim Reisert AD1; /archives//html/WriteLog/2001-11/msg00130.html (8,190 bytes)
8. [WriteLog] wae buffers from aa5au (score: 1): Author: gbaron@home.com (Gil Baron); Date: Tue, 06 Nov 2001 09:39:30 -0600; --==_334735474==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed HOWEVER this does not solve everything. Now I have to some way kill my earlier version of the QSO so that the correct; /archives//html/WriteLog/2001-11/msg00134.html (17,139 bytes)

Current List: 1 - 8
Page: [1]