Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+DigiRite\s+1\.1\.10\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+DigiRite\s+1\.1\.10\s*$/: 3 ]

Total 3 documents matching your query.

1. [WriteLog] DigiRite 1.1.10 (score: 1): Author: Wayne <support@writelog.com>; Date: Mon, 17 Jun 2019 03:15:10 +0000; The DigiRite announced just a couple of days ago, version 1.1.08 has a bug that causes it to put up a fatal error message on receipt of certain FT8 messages. The latest published version, 1.1.10, fi; /archives//html/WriteLog/2019-06/msg00012.html (6,665 bytes)
2. Re: [WriteLog] DigiRite 1.1.10 (score: 1): Author: "Erik Carling" <erik.ei4kf@gmail.com>; Date: Tue, 18 Jun 2019 03:54:08 -0500; As with previous versions: After CQ and receiving call with locator, DigiRite sends R+dB report instead of dB report. At receipt of 73 the program locks up. Using DigiRite with Writelog latest versio; /archives//html/WriteLog/2019-06/msg00015.html (6,881 bytes)
3. Re: [WriteLog] DigiRite 1.1.10 (score: 1): Author: Wayne <support@writelog.com>; Date: Tue, 18 Jun 2019 14:09:19 +0000; This is because under File/Setup, you have told DigiRite to operate in contest mode where only dB reports are exchanged. Well, what gets locked up? _______________________________________________ Wr; /archives//html/WriteLog/2019-06/msg00016.html (7,047 bytes)

Current List: 1 - 3
Page: [1]