Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-mi03.r1000.mx.aol.com (Internet Inbound) with ESMTP id 2B52638000264; Mon, 29 Oct 2012 16:58:04 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1TSwOe-0000zq-1j for rs_out_1@blacksheep.org; Mon, 29 Oct 2012 20:57:20 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1TSwOd-0000zh-J4 for rsgb_lf_group@blacksheep.org; Mon, 29 Oct 2012 20:57:19 +0000 Received: from ppa02.princeton.edu ([128.112.128.216]) by relay1.thorcom.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1TSwOZ-0002k2-Rz for rsgb_lf_group@blacksheep.org; Mon, 29 Oct 2012 20:57:18 +0000 Received: from csgsmtp200l.Princeton.EDU (csgsmtp200l.Princeton.EDU [128.112.130.131]) by ppa02.Princeton.EDU (8.14.4/8.14.4) with ESMTP id q9TKvErP016203 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 29 Oct 2012 16:57:14 -0400 Received: from [192.168.1.3] (pool-173-61-149-45.cmdnnj.fios.verizon.net [173.61.149.45]) (authenticated bits=0) by csgsmtp200l.Princeton.EDU (8.13.8/8.12.9) with ESMTP id q9TKvDkp017629 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 29 Oct 2012 16:57:14 -0400 Message-ID: <508EEDA9.7070905@princeton.edu> Date: Mon, 29 Oct 2012 16:57:13 -0400 From: Joe Taylor User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:6.0) Gecko/20110812 Thunderbird/6.0 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org, rsgb_lf_group@yahoogroups.co.uk References: <508D92BE.2040500@broadpark.no> <508ED047.1000504@broadpark.no> In-Reply-To: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855,1.0.431,0.0.0000 definitions=2012-10-29_04:2012-10-29,2012-10-29,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=quarantine_notspam policy=quarantine score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1210290246 X-Spam-Score: -2.9 (--) 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: G3XBM wrote: > Running the new version I had the program crash out after about 3 minutes. > I had sent one cycle of JT9-2 (CQ G3XBM) on 500kHz and was receiving in the > next slot only to have the whole window close. Tried it a second time and > had the same issue again. [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, medium trust [128.112.128.216 listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record -0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Scan-Signature: 66d07794ca19cd68f7d6cc289cd4ac18 Subject: Re: LF: WSJTX 01r2702 JT9 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=none 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-sid: 3039ac1d7b8b508eeddc1928 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none G3XBM wrote: > Running the new version I had the program crash out after about 3 minutes. > I had sent one cycle of JT9-2 (CQ G3XBM) on 500kHz and was receiving in the > next slot only to have the whole window close. Tried it a second time and > had the same issue again. Comments like "the program crashed" are not very helpful by themselves. (Needless to say, the program has not crashed for me, or I would not have release it.) Please do what you can to establish a reproducible method leading to the bug you have found. Explain what the program was doing, just before it died. Ideally, run the program from a command-prompt window and report any error message left behind. Now, a few last comments before I go QRT. Please note: I may be QRT for some days, owing to the very big storm just now arriving. 1. Does anyone besides Eddie see "ghost signals" in the sequence following reception of a stropng signal? If so, please document what you see and save example *.wav files. 2. Re suggestion by Andy, G4JNT: It seems to me that the MF/LF group needs something like "LiveCQ", a utility used by EME people on 144 MHz. See http://www.livecq.eu/ . LiveCQ uses output from my program MAP65, similar to that also provided by WSJT-X in file wsjtx_rx.log. The LiveCQ program monitors the file and reports decodes of CQ messages to the Live CQ web site, where they are displayed. 3. It seems to me that the MF/LF group could also use a "chat page" dedicated to bands below 160m. It's much more efficient than lots of emails saying things like "I copy you now", etc. Something like http://www.chris.org/cgi-bin/jt65emeA for EME, or perhaps http://www.on4kst.org/chat/login.php?band=4 for "Low Bands". However, the ON4KST low band page is too full of 1.8 and 3.5 MHz traffic. Maybe ON4KST could be persuaded to make one more page, for 500 kHz and down. The storm here is rather frightening, already, and the worst is yet to come. We in central New Jersey are near the center of the expected path. Here's hoping for the best! The good news: if we're still here and still EME-capable on Friday, all leaves should be off the trees and I should be several dB better off for weekend #2 of the ARRL EME contest. :-) -- 73, Joe, K1JT