Delivered-To: daveyxm@virginmedia.com Received: by 10.50.33.134 with SMTP id r6csp33697igi; Sat, 10 Aug 2013 23:57:56 -0700 (PDT) X-Received: by 10.14.38.196 with SMTP id a44mr20196368eeb.78.1376204275344; Sat, 10 Aug 2013 23:57:55 -0700 (PDT) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id b43si863486eem.343.2013.08.10.23.57.54 for ; Sat, 10 Aug 2013 23:57:55 -0700 (PDT) Received-SPF: neutral (google.com: 195.171.43.25 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) client-ip=195.171.43.25; Authentication-Results: mx.google.com; spf=neutral (google.com: 195.171.43.25 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) smtp.mail=owner-rsgb_lf_group@blacksheep.org Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1V8CJ2-0004HG-6O for rs_out_1@blacksheep.org; Sat, 10 Aug 2013 17:46:20 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1V8CJ1-0004H7-C6 for rsgb_lf_group@blacksheep.org; Sat, 10 Aug 2013 17:46:19 +0100 Received: from relay.uni-heidelberg.de ([129.206.100.212]) by relay1.thorcom.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1V8CIz-00043A-JA for rsgb_lf_group@blacksheep.org; Sat, 10 Aug 2013 17:46:18 +0100 Received: from freitag.iup.uni-heidelberg.de (freitag.iup.uni-heidelberg.de [129.206.29.204]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id r7AGkGGQ025975 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 10 Aug 2013 18:46:16 +0200 Received: from [129.206.22.206] (pc206.iup.uni-heidelberg.de [129.206.22.206]) by freitag.iup.uni-heidelberg.de (8.12.11.20060308/8.11.2) with ESMTP id r7AGkFMf010029 for ; Sat, 10 Aug 2013 18:46:15 +0200 Message-ID: <52066E53.8050304@iup.uni-heidelberg.de> Date: Sat, 10 Aug 2013 18:46:11 +0200 From: =?ISO-8859-1?Q?Stefan_Sch=E4fer?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: In-Reply-To: X-Spam-Score: -0.7 (/) 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: Hi all, I'm still fighting with WSPR-15, RX wise. It simply doesn't work on my grabber PC. WSPR 2.0 works fine on LF and MF though. I thought it could be a good idea to uninstall wsjtx and wsprx, then cleaning the registry and the whole PC, then installing WSPRX (WSPR-15) again. [...] Content analysis details: (-0.7 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low trust [129.206.100.212 listed in list.dnswl.org] -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Scan-Signature: bb61bee384896e075004ae5ec954ddd2 Subject: LF: WSPRX 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 Status: O X-Status: X-Keywords: X-UID: 1212 Hi all, I'm still fighting with WSPR-15, RX wise. It simply doesn't work on my grabber PC. WSPR 2.0 works fine on LF and MF though. I thought it could be a good idea to uninstall wsjtx and wsprx, then cleaning the registry and the whole PC, then installing WSPRX (WSPR-15) again. Maybe there are some DLLs left in the registry that cause problems, some DLLs of older versions that haven't been replaced by the latest installation? Does someone know which DLLs (or other stuff) belongs to wsjtx and wsprx and where they can be found, and manually deleted? I guess there must be something in the "system32" folder but i don't the names of them... Any help is apprechiated. 73, Stefan/DK7FC