Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+RE\:\s+WriteLog\s+digest\,\s+Vol\s+1\s+\#199\s+\-\s+2\s+msgs\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+RE\:\s+WriteLog\s+digest\,\s+Vol\s+1\s+\#199\s+\-\s+2\s+msgs\s*$/: 3 ]

Total 3 documents matching your query.

1. [WriteLog] RE: WriteLog digest, Vol 1 #199 - 2 msgs (score: 1): Author: dick.green@valley.net (Dick Green); Date: Thu, 22 Nov 2001 14:09:13 -0500; Barry, I wouldn't blame Writelog for this problem. I believe the design evolved from what other programs do. CT and NA also depend on an external relay, triggered by a signal on the LPT port, to rout; /archives//html/WriteLog/2001-11/msg00466.html (10,033 bytes)
2. [WriteLog] RE: WriteLog digest, Vol 1 #199 - 2 msgs (score: 1): Author: clive@gw3njw.fsworld.co.uk (Clive Whelan); Date: Thu, 22 Nov 2001 20:45:15 -0000; But TR doesn't *and* supports multiple LPT ports for keying. I also use the W5XD+ keyer, which is a fine device, but it shouldn't really be necessary to do that just to employ SO2R. I migrated to WL,; /archives//html/WriteLog/2001-11/msg00467.html (7,351 bytes)
3. [WriteLog] RE: WriteLog digest, Vol 1 #199 - 2 msgs (score: 1): Author: jjreisert@alum.mit.edu (Jim Reisert); Date: Tue, 27 Nov 2001 23:23:36 -0500; CT has supported COM port CW from almost the beginning. Look in the manual, you will find instructions for a COM-port based CW keying interface, alongside the one for LPT ports. -- Jim Reisert AD1C,; /archives//html/WriteLog/2001-11/msg00550.html (7,276 bytes)

Current List: 1 - 3
Page: [1]