MIME-Version: 1.0
In-Reply-To: <508D86B7.1030001@princeton.edu>
References: <CAHAQVWO7X9AKEtFPnCY+coRQhUGSdSbsdjRnJyof223u1KWSbw@mail.gmail.com>
	<508D86B7.1030001@princeton.edu>
Date: Sun, 28 Oct 2012 19:58:24 +0000
Message-ID: <CAHAQVWO93Et4m+A=_JFZsT4jCoxO7wJzzfG7J4mGq8AK5YCgYA@mail.gmail.com>
From: Roger Lapthorn <rogerlapthorn@gmail.com>
To: rsgb_lf_group@blacksheep.org
Subject: Re: LF: JT9 buggy issues
Content-Type: multipart/alternative; boundary=00151750e552c2fc8c04cd23f9fa
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org


--00151750e552c2fc8c04cd23f9fa
Content-Type: text/plain; charset=ISO-8859-1

Joe,

Can you confirm the latest version is 01r2695.exe please?

73s
Roger G3XBM

On 28 October 2012 19:25, Joe Taylor <joe@princeton.edu> wrote:

> Hi Roger,
>
>
>  After about 1 minute or so, the program just closes itself and disappears
>> from the PC screen.
>>
>
> Please open a command-prompt window and start the program from there. For
> example,
>
> C:\> cd \wsjtx
> C:\> wsjtx
>
> When the program dies, send me any error message left in the
> command-prompt window.
>
>
>  I am using a SignalLink VOX controlled sound card interface that I use for
>> WSPR. Also, when I reload the program I have to reload my callsign, grid
>> etc.every time.
>>
>
> This makes it sound like you may have ignored the installation advice in
> the Quick-Start Guide: "Under Vista or Windows 7 be sure to install WSJT-X
> into its own directory (the suggested default is c:\wsjtx) rather than
> C:\Program Files\wsjtx."  Please confirm.
>
>
>  Although I very much hope to use the mode for QSOs please do not
>> underestimate the value of a weak signal beaconing function with an
>> internet database. This has proved extremely valuable on WSPR as people
>> sometimes leave a RX and PC running to monitor when they are busy and not
>> available for QSOs. There will be far more people able to receive and
>> report than TX on MF/LF. This is especially true on 136kHz.
>>
>
> Yes, I understand these points, and beacons have their place.  WSPR would
> not be there if I did not believe this.
>
> The question in my mind is the degree to which beacon-like features should
> be mixed with a mode designed for making QSOs.  If beaconing behavior is
> desired, why not use WSPR?  If it's important to have, say, 10 dB better
> sensitivity than WSPR, then maybe a "slow WSPR" mode should be developed
> and used, rather than JT9.
>
>         -- 73, Joe, K1JT
>
>


-- 
 http://g3xbm-qrp.blogspot.com/
http://www.g3xbm.co.uk
https://sites.google.com/site/sub9khz/
http://qss2.blogspot.com/

--00151750e552c2fc8c04cd23f9fa
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Joe,<br><br>Can you confirm the latest version is 01r2695.exe please?<br><b=
r>73s<br>Roger G3XBM<br><br><div class=3D"gmail_quote">On 28 October 2012 1=
9:25, Joe Taylor <span dir=3D"ltr">&lt;<a href=3D"mailto:joe@princeton.edu"=
 target=3D"_blank">joe@princeton.edu</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi Roger,<div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
After about 1 minute or so, the program just closes itself and disappears<b=
r>
from the PC screen.<br>
</blockquote>
<br></div>
Please open a command-prompt window and start the program from there. For e=
xample,<br>
<br>
C:\&gt; cd \wsjtx<br>
C:\&gt; wsjtx<br>
<br>
When the program dies, send me any error message left in the command-prompt=
 window.<div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I am using a SignalLink VOX controlled sound card interface that I use for<=
br>
WSPR. Also, when I reload the program I have to reload my callsign, grid<br=
>
etc.every time.<br>
</blockquote>
<br></div>
This makes it sound like you may have ignored the installation advice in th=
e Quick-Start Guide: &quot;Under Vista or Windows 7 be sure to install WSJT=
-X into its own directory (the suggested default is c:\wsjtx) rather than C=
:\Program Files\wsjtx.&quot; =A0Please confirm.<div class=3D"im">
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Although I very much hope to use the mode for QSOs please do not<br>
underestimate the value of a weak signal beaconing function with an<br>
internet database. This has proved extremely valuable on WSPR as people<br>
sometimes leave a RX and PC running to monitor when they are busy and not<b=
r>
available for QSOs. There will be far more people able to receive and<br>
report than TX on MF/LF. This is especially true on 136kHz.<br>
</blockquote>
<br></div>
Yes, I understand these points, and beacons have their place. =A0WSPR would=
 not be there if I did not believe this.<br>
<br>
The question in my mind is the degree to which beacon-like features should =
be mixed with a mode designed for making QSOs. =A0If beaconing behavior is =
desired, why not use WSPR? =A0If it&#39;s important to have, say, 10 dB bet=
ter sensitivity than WSPR, then maybe a &quot;slow WSPR&quot; mode should b=
e developed and used, rather than JT9.<br>

<br>
=A0 =A0 =A0 =A0 -- 73, Joe, K1JT<br>
<br>
</blockquote></div><br><br clear=3D"all"><br>-- <br>=A0<a href=3D"http://g3=
xbm-qrp.blogspot.com/">http://g3xbm-qrp.blogspot.com/</a><br><a href=3D"htt=
p://www.g3xbm.co.uk">http://www.g3xbm.co.uk</a><br><a href=3D"https://sites=
.google.com/site/sub9khz/">https://sites.google.com/site/sub9khz/</a><br>
<a href=3D"http://qss2.blogspot.com/">http://qss2.blogspot.com/</a><br><br>=
<br>

--00151750e552c2fc8c04cd23f9fa--