Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-df02.r1000.mx.aol.com (Internet Inbound) with ESMTP id 7043238000092; Sat, 17 Nov 2012 09:21:35 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1TZjFz-0003s8-4a for rs_out_1@blacksheep.org; Sat, 17 Nov 2012 14:20:27 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1TZjFy-0003rz-71 for rsgb_lf_group@blacksheep.org; Sat, 17 Nov 2012 14:20:26 +0000 Received: from nm2.bt.bullet.mail.ird.yahoo.com ([212.82.108.233]) by relay1.thorcom.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1TZjFw-0001vu-Ce for rsgb_lf_group@blacksheep.org; Sat, 17 Nov 2012 14:20:25 +0000 Received: from [212.82.108.231] by nm2.bt.bullet.mail.ird.yahoo.com with NNFMP; 17 Nov 2012 14:20:23 -0000 Received: from [217.146.189.77] by tm4.bt.bullet.mail.ird.yahoo.com with NNFMP; 17 Nov 2012 14:20:23 -0000 Received: from [127.0.0.1] by smtp827.mail.ird.yahoo.com with NNFMP; 17 Nov 2012 14:20:23 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btinternet.com; s=s1024; t=1353162023; bh=kOeQS60KpmJdAbuj5ALySTm6QOLsyJogdMwuBcKoma8=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE; b=DcdRNiCl68nwR9u6ldYMvzi8JrJ68/JJwwKockg5SOtXhKF/ybj7vaDvg+VMmNq3sJAmr54Y5vNyheaOWKMjD86W95po/U1o/Kr7PfJwLIV50PDtOAHgtSV1IqKhNz6CTIx8YzzIfqGCQU1Puu909lJOyYAevTBPUeQ0p6p8w2g= X-Yahoo-Newman-Id: 554014.16341.bm@smtp827.mail.ird.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: PsKQhYIVM1lll9GD6GfWXUMCceq5XguFMDMOO1gNct2bSsT iCr0ylC_8F1dbyycbY6typz_3DAw8H5IXMTHZG34zqODELbU0lQ9TA5uKwDe XjJ9gOUrewqRVWx.xI0VVv7wITFxdbUvv1etqTiPgzFNK.jlcNtD_rPQOk5k KIvynxXbzgzopr6t3PmCb__DG8Tu9H53FQAgLWVYz06YLcrFfRtjy2.6QOet efaO1oUf8GqGsYgRc8yt943qRkqkJFTrugm7RGWZX467E5b3RsGTBwtgmZpU vtoM7wPzX.X5CJxPpDafbJ7klQObZMFS16oZqusjLSVwBHZ5DupNpguRr51Z Smbx1.gSGauOKZNd5_okTlJniIqb5zaCEiZ9Iy0g06lI2uxJLgFh5gLqpl4i 9YQEWStNoYppw1mEojpJ3YO9I_Mtelx0WjS5mQXtCy5LGkXEgB6LjgPCT8sT xMxNAS6QnWA-- X-Yahoo-SMTP: khKbo3qswBAevJSEf.Soeh08VpP3pgtFENUUoUzoJw6opDkeTsHZWXMBHg-- Received: from 64683d74b6134b3 (robertgjbennett@81.159.15.156 with login) by smtp827.mail.ird.yahoo.com with SMTP; 17 Nov 2012 06:20:23 -0800 PST Message-ID: <398B7ECA60D0434288BF3E423B406884@64683d74b6134b3> From: "Robert Bennett" To: References: <50A77D76.6030206@psk31.plus.com> <50A78C84.5040804@psk31.plus.com> Date: Sat, 17 Nov 2012 14:20:22 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-Spam-Score: 1.6 (+) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Eddie This idea might be complete nonsense, but a couple of years ago I was using for WSJT a computer which had a clock which drifted. Provided the 'clock updater' did its job with regularity, everything ran fine, but if the interval became extended, when the 'update' eventually happened it caused the program to crash........I assume that the 'large' time correction disrupted some aspect of the software. [...] Content analysis details: (1.6 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [212.82.108.233 listed in list.dnswl.org] 1.0 HK_RANDOM_FROM From username looks random 0.6 HK_RANDOM_ENVFROM Envelope sender username looks random 0.0 HTML_MESSAGE BODY: HTML included in message 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid 0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay lines X-Scan-Signature: 0cdfd8d5ce44f1724c623c4ac9f44df6 Subject: LF: Re: TEST JT9-2 500khz + 1400hz OFF Content-Type: multipart/alternative; boundary="----=_NextPart_000_001B_01CDC4CE.ADD050B0" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: ** X-Spam-Status: No, hits=2.1 required=5.0 tests=FORGED_MUA_OUTLOOK,HTML_40_50, HTML_MESSAGE autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false x-aol-global-disposition: G X-AOL-SCOLL-AUTHENTICATION: mtain-df02.r1000.mx.aol.com ; domain : btinternet.com DKIM : fail x-aol-sid: 3039ac1d40d650a79d6e6e78 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none This is a multi-part message in MIME format. ------=_NextPart_000_001B_01CDC4CE.ADD050B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Eddie This idea might be complete nonsense, but a couple of years ago I was = using for WSJT a computer which had a clock which drifted. Provided the 'clock updater' did its job with regularity, everything ran = fine, but if the interval became extended, when the 'update' eventually = happened it caused the program to crash........I assume that the 'large' = time correction disrupted some aspect of the software. I think I have seen some references to your clock drifting.........I = don't suppose that the 'crash' coincides with a clock update?? Just a thought 73 Robert ----- Original Message -----=20 From: g3zjo=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Saturday, November 17, 2012 1:09 PM Subject: LF: TEST JT9-2 500khz + 1400hz OFF Now OFF, decodes failed after 1 hour. Eddie ------=_NextPart_000_001B_01CDC4CE.ADD050B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Eddie
 
This idea might be complete nonsense, = but a=20 couple of years ago I was using for WSJT a computer which had a = clock which=20 drifted.
 
Provided the 'clock updater' did its = job with=20 regularity, everything ran fine, but if the interval became extended, = when the=20 'update' eventually happened it caused the program to crash........I = assume that=20 the 'large' time correction disrupted some aspect of the = software.
 
I think I have seen some references to = your clock=20 drifting.........I don't suppose that the 'crash' coincides with a clock = update??
 
Just a thought
 
73 Robert
 
 
----- Original
 
 Message -----
From:=20 g3zjo=20
Sent: Saturday, November 17, = 2012 1:09=20 PM
Subject: LF: TEST JT9-2 500khz = + 1400hz=20 OFF

Now OFF, decodes failed after 1=20 hour.

Eddie

------=_NextPart_000_001B_01CDC4CE.ADD050B0--