To: rsgb_lf_group@blacksheep.org
References: <1450944D2563430FBFDFC41F0C27432C@AGB>
 <55D917DC.3030206@posteo.de> <A3E35AFE457A4E268ADCA6B06AB2D9B2@AGB>
 <55DA09C0.7040407@no3m.net> <26DFFCAE71834363A5151450F1E96059@AGB>
 <55DA1737.2030605@no3m.net> <54DED26E6C7A45FD9447C9CF327159AA@AGB>
From: Eric NO3M <no3m@no3m.net>
Message-ID: <55DA2428.2030202@no3m.net>
Date: Sun, 23 Aug 2015 15:51:05 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <54DED26E6C7A45FD9447C9CF327159AA@AGB>
Subject: Re: LF: last 12 Hours on 477 OP8
Content-Type: multipart/alternative;
 boundary="------------030700050504090402050503"
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Status: O

This is a multi-part message in MIME format.
--------------030700050504090402050503
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

ALL_MEPT.txt and ALL_WSPR.TX are just log files, not updated from the 
web nor referenced in decode process.

However, in original WSJT directory (EME modes, etc), there exists a 
CALL3.TXT, which is the callsign list you refer to :)  But WSJT is 
neither WSPR related and pretty much superseded these days with WSJT-X 
(which also now includes WSPR with two-pass, signal subtraction decoder 
by K9AN).

At any rate... anxious for conditions to settle and start getting some 
TA action.  Hams should have 630M in US by next spring! ... maybe.

73 Eric NO3M / WG2XJM

On 08/23/2015 03:30 PM, Graham wrote:
> Now you  come  to  mention it , taking a look  , there are actually 
>  two  text files with  call  sign's  ive  detected in  my  wspr  
> folder  , ''ALL'' and ''MEPT'', no  one minds a bit of the   'Old 
> Jaspers'  as  long as its not take too seriously
> G,
>


--------------030700050504090402050503
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    ALL_MEPT.txt and ALL_WSPR.TX are just log files, not updated from
    the web nor referenced in decode process.<br>
    <br>
    However, in original WSJT directory (EME modes, etc), there exists a
    CALL3.TXT, which is the callsign list you refer to :)  But WSJT is
    neither WSPR related and pretty much superseded these days with
    WSJT-X (which also now includes WSPR with two-pass, signal
    subtraction decoder by K9AN).<br>
    <br>
    At any rate... anxious for conditions to settle and start getting
    some TA action.  Hams should have 630M in US by next spring! ...
    maybe.<br>
    <br>
    73 Eric NO3M / WG2XJM<br>
    <br>
    <div class="moz-cite-prefix">On 08/23/2015 03:30 PM, Graham wrote:<br>
    </div>
    <blockquote cite="mid:54DED26E6C7A45FD9447C9CF327159AA@AGB"
      type="cite">
      <title></title>
      <meta content="text/html; charset=windows-1252"
        http-equiv="Content-Type">
      <meta name="GENERATOR" content="MSHTML 8.00.6001.23588">
      <div>Now you  come  to  mention it , taking a look  , there 
        are actually  two  text files with  call  sign's  ive  detected 
        in  my  wspr  folder  , ''ALL'' and ''MEPT'', no  one minds a 
        bit of the   'Old Jaspers'  as  long as its not take too 
        seriously </div>
      <div> </div>
      <div>G,</div>
      <div> </div>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------030700050504090402050503--