Delivered-To: daveyxm@virginmedia.com Received: by 10.50.237.98 with SMTP id vb2csp69544igc; Sun, 9 Mar 2014 16:21:46 -0700 (PDT) X-Received: by 10.180.12.233 with SMTP id b9mr6685073wic.8.1394407305911; Sun, 09 Mar 2014 16:21:45 -0700 (PDT) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id x3si8152089wje.119.2014.03.09.16.21.45 for ; Sun, 09 Mar 2014 16:21:45 -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 1WMmOV-0007Ee-9D for rs_out_1@blacksheep.org; Sun, 09 Mar 2014 22:40:31 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1WMmOU-0007EV-QC for rsgb_lf_group@blacksheep.org; Sun, 09 Mar 2014 22:40:30 +0000 Received: from mout1.freenet.de ([195.4.92.91]) by relay1.thorcom.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1WMmOT-00038i-9g for rsgb_lf_group@blacksheep.org; Sun, 09 Mar 2014 22:40:29 +0000 Received: from [195.4.92.141] (helo=mjail1.freenet.de) by mout1.freenet.de with esmtpa (ID dl4yhf@freenet.de) (port 25) (Exim 4.80.1 #4) id 1WMmOS-0006wv-62 for rsgb_lf_group@blacksheep.org; Sun, 09 Mar 2014 23:40:28 +0100 Received: from localhost ([::1]:56092 helo=mjail1.freenet.de) by mjail1.freenet.de with esmtpa (ID dl4yhf@freenet.de) (Exim 4.80.1 #4) id 1WMmOS-0004j9-21 for rsgb_lf_group@blacksheep.org; Sun, 09 Mar 2014 23:40:28 +0100 Received: from mx15.freenet.de ([195.4.92.25]:34287) by mjail1.freenet.de with esmtpa (ID dl4yhf@freenet.de) (Exim 4.80.1 #4) id 1WMmM8-0003pt-Lw for rsgb_lf_group@blacksheep.org; Sun, 09 Mar 2014 23:38:04 +0100 Received: from blfd-4d08ed51.pool.mediaways.net ([77.8.237.81]:1817 helo=[192.168.178.21]) by mx15.freenet.de with esmtpsa (ID dl4yhf@freenet.de) (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (port 465) (Exim 4.80.1 #4) id 1WMmM8-0005MO-D9 for rsgb_lf_group@blacksheep.org; Sun, 09 Mar 2014 23:38:04 +0100 Message-ID: <531CED4B.3040604@freenet.de> Date: Sun, 09 Mar 2014 23:38:03 +0100 From: wolf_dl4yhf User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: <006b01cf3969$43a83480$caf89d80$@de> <5318C740.50901@mvnet.de> <5318D051.2080907@freenet.de> <5318DA98.7090606@broadpark.no> <5318E10B.3080701@freenet.de> <5318F763.6010607@broadpark.no> <53190028.9070900@freenet.de> <1981194039.20140309191717@mterrier.net> <531CCCC4.9060001@freenet.de> <531CE824.9080709@gmx.net> In-Reply-To: <531CE824.9080709@gmx.net> X-Originated-At: 77.8.237.81!1817 X-Spam-Score: -0.0 (/) 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 Tobias, Ok, thanks for testing. Compared to some other modifications, the serial port issue should be easy to fix. You wrote: > > suggestion : > K1JT's programs do open the serial port just at the start of each > transmit sequence and close the serial port immediately after the end > of this transmission. By this feature more than one program can run at > a time using the same serial port for PTT, as long as only one program > wants to transmit at any time. i.e. you can run WSPR-x and WSJT-x > simultaneously without the need to deactivate the (same) serial port > of the program that is on receive only. It would be nice if WSQ would > behave similar. > Ok, makes sense.. and lines up with Michel's reply which just arrived here ... but will the port's RTS and DTR output remain safely in the 'receive' state when WSQ closes the serial port after each transmit-over ? One may assume that, when closing the port all outputs switch back to the default state - or leave them as-is, until another call of the 'EscapeCommFunction'. [...] Content analysis details: (-0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [195.4.92.91 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (dl4yhf[at]freenet.de) -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Scan-Signature: 4e3b1488273adbbe9757d6bdd5adf219 Subject: Re: LF: WSQ2 new version uploaded 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 Hi Tobias, Ok, thanks for testing. Compared to some other modifications, the serial port issue should be easy to fix. You wrote: > > suggestion : > K1JT's programs do open the serial port just at the start of each > transmit sequence and close the serial port immediately after the end > of this transmission. By this feature more than one program can run at > a time using the same serial port for PTT, as long as only one program > wants to transmit at any time. i.e. you can run WSPR-x and WSJT-x > simultaneously without the need to deactivate the (same) serial port > of the program that is on receive only. It would be nice if WSQ would > behave similar. > Ok, makes sense.. and lines up with Michel's reply which just arrived here ... but will the port's RTS and DTR output remain safely in the 'receive' state when WSQ closes the serial port after each transmit-over ? One may assume that, when closing the port all outputs switch back to the default state - or leave them as-is, until another call of the 'EscapeCommFunction'. Further experimentation will show... 73 and good night, Wolf .