Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+Re\:\s+Re\:\s+Trouble\s+with\s+COM2\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+Re\:\s+Re\:\s+Trouble\s+with\s+COM2\s*$/: 2 ]

Total 2 documents matching your query.

1. [WriteLog] Re: Re: Trouble with COM2 (score: 1): Author: "John Griswold" <kb1hdo@arrl.net>; Date: Thu, 8 Jan 2004 11:15:12 -0500; Again, thanks for all the responses - you are all very supportive. It has been suggested that I look at interrupt latency, inter-poll timing, the operating system, and loose connectors as issues, and; /archives//html/WriteLog/2004-01/msg00132.html (7,247 bytes)
2. Re: [WriteLog] Re: Re: Trouble with COM2 (score: 1): Author: dl6jz@t-online.de; Date: Thu, 08 Jan 2004 17:58:30 +0100 (CET); Hi John, I had the same problem as you described several times when I was reconfiguering WriteLog and my computers. The reason for this behaviour was always the same: There were other requests for th; /archives//html/WriteLog/2004-01/msg00135.html (8,193 bytes)

Current List: 1 - 2
Page: [1]