Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+Winkey\s+and\s+Writelog\s+Issues\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+Winkey\s+and\s+Writelog\s+Issues\s*$/: 2 ]

Total 2 documents matching your query.

1. [WriteLog] Winkey and Writelog Issues (score: 1): Author: "John Warburton G4IRN" <qrz@dxdx.co.uk>; Date: Wed, 10 Feb 2010 00:21:15 -0800; All Please excuse me if these issues have come up on the reflector before, I have tried to dig them out without any success. I am using a Microkeyer II unit with Writelog version 10.74 and get the fo; /archives//html/WriteLog/2010-02/msg00031.html (8,004 bytes)
2. Re: [WriteLog] Winkey and Writelog Issues (score: 1): Author: "Joe Subich, W4TV" <lists@subich.com>; Date: Fri, 12 Feb 2010 02:32:57 -0500; There is a finite amount of time - generally one word space - that the WinKey chip will signal that the paddles are in use following their use. WriteLog and many other programs use the "paddle busy"; /archives//html/WriteLog/2010-02/msg00038.html (10,636 bytes)

Current List: 1 - 2
Page: [1]