Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+\[RTTY\]\s+Cut\s+Numbers\s+Revisited\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+\[RTTY\]\s+Cut\s+Numbers\s+Revisited\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: [WriteLog] [RTTY] Cut Numbers Revisited (score: 1): Author: Steve Dyer <w1srd@yahoo.com>; Date: Tue, 7 Jan 2014 14:25:05 -0800 (PST); This is probably not about cut numbers in RTTY. What you are seeing is usually caused by the LTRS shift being lost and leaving the decoder in FIGS mode. OH in FIGS should be 9# not 9h. Not sure why; /archives//html/WriteLog/2014-01/msg00032.html (9,821 bytes)
2. Re: [WriteLog] [RTTY] Cut Numbers Revisited (score: 1): Author: "K2MK" <k2mk@comcast.net>; Date: Wed, 8 Jan 2014 09:18:00 -0500; Hi Dick, Other posters have advised how a lost character can cause 599 to print as TOO. So we can all ignore TOO since we know what it means. The tougher problem is when there is a serial number foll; /archives//html/WriteLog/2014-01/msg00037.html (8,662 bytes)

Current List: 1 - 2
Page: [1]