Re: [wsjt-devel] Monthly ALL.TXT archives
To Gary, ZL2IFB: I can see that because you are so active that it would be helpful to make monthly files. It seems to me that an easy way to do this is that on the first of the month, the file could be renamed to show the month it is for, and then open a new clean file to continue the data collection. I searched my ALL.TXT file in EXCEL and found your call sign 17 times. Most of these were from stations working you, but there were instances where I was copying you. 73, Roy, W7IDM On Wed, Jun 26, 2019 at 6:10 PM Dan Malcolm wrote: > I use a combination of the ALL.TXT breakup techniques. I keep it yearly > as I’m not quite so active as Gary. My ALL.TXT file ran to 1.2 TB last > year. I use a PHP app I wrote that suits me. It allows me to search by > year including the current year. About 0100 I have a scheduled copy of the > current ALL.TXT copied to a search directory. In the event I need to > search since then I have a trivial batch file that can copy the most > current version. All searches are performed on copies, not the live file. > My searches are probably complicated more than need be because the rig and > WSJT-X runs 24/7 unless there is a thunder storm or I’m on vacation. > > > > __ > > Dan – K4SHQ > > > > *From:* Gary Hinson [mailto:g...@isect.com] > *Sent:* Wednesday, June 26, 2019 5:36 PM > *To:* 'WSJT software development' > *Subject:* Re: [wsjt-devel] Monthly ALL.TXT archives > > > > Hi Roy. > > > > I am very active on FT8, clocking up about 900 FT8 QSOs per month and > monitoring open HF FT8 subbands all ZL day while I work on the adjacent > screen. > > > > My ALL.TXT typically grows to more than 30 Mb per month e.g.: > > > > > > Early each new month, I manually add the previous month’s ALL.TXT to a ZIP > archive. Luckily the ALL.TXT data structure is very simple so it > compresses down neatly to about 40 Mb per year: > > > > > > I sometimes need to check through my ALL.TXT for details of a QSO that > someone has claimed on a QSL card or by email, but doesn’t appear in my > Logger32 station log. It’s easy to open the relevant month’s ALL.TXT > section from the ZIP archive and search for the QSO in question … and > almost always I find a nearly-completed or completed QSO that for some > reason wasn’t transferred to Logger32. > > > > If you try opening the current ALL.TXT file in, say, Notepad while WSJT-X > or JTDX is still running, you’ll probably get pop-up warnings every 15 > seconds that the file has been updated when new decodes are written to it: > that doesn’t happen if you are using a closed/archived ALL.TXT file. > > > > So, monthly ALL.TXTs are worthwhile for highly active stations … and I > think they would be useful for almost everyone. > > > > 73 > Gary ZL2iFB > > > > *From:* Roy Gould > *Sent:* 27 June 2019 03:52 > *To:* WSJT software development > *Subject:* Re: [wsjt-devel] Monthly ALL.TXT archives > > > > Thanks for the education. Before you started discussing the ALL.TXT file I > did not know it existed. So I decided to check it out and see what it was > all about. Here are some things that I found out about it in my case. > > > > The file in my computer was nearly 24 MB in size. I double clicked on it > and it immediately came into Notepad on my Windows 10 computer so I could > take a look at it. I tried Finding things such as CQ FD and it found > several of those. I searched for my call sign (W7IDM) and it found it. I > discovered that beginning on 19/02/27 that the format of the data stored > was radically different and put into a much better format. So I deleted all > of the previous entries leaving only the new format and that became the > file that I am currently using. This file is about 6 MB in length. > > > > I tried loading the file into EXCEL from Office 365 and EXCEL said that it > looks like this data is in fixed width columns and asked if I agreed. I > said yes and the data came in just fine. Now that it is in EXCEL format I > have the ability to use the powerful EXCEL data base functions to do a lot > of different types of analysis. > > > > I don't see any particular need to want to break it into monthly segments. > Perhaps it would be good to save it in yearly segments. It appears that I > can easily work with a whole year of data at a time, so why break it up > monthly? > > > > So, for what it is worth, these are my observations... > > > > 73, Roy, W7IDM > > > > > > On Tue, Jun 25, 2019 at 11:55 AM Sam W2JDB via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > Hi, > > > > I recompiled the program with "openread" and
Re: [wsjt-devel] Monthly ALL.TXT archives
I use a combination of the ALL.TXT breakup techniques. I keep it yearly as I’m not quite so active as Gary. My ALL.TXT file ran to 1.2 TB last year. I use a PHP app I wrote that suits me. It allows me to search by year including the current year. About 0100 I have a scheduled copy of the current ALL.TXT copied to a search directory. In the event I need to search since then I have a trivial batch file that can copy the most current version. All searches are performed on copies, not the live file. My searches are probably complicated more than need be because the rig and WSJT-X runs 24/7 unless there is a thunder storm or I’m on vacation. __ Dan – K4SHQ From: Gary Hinson [mailto:g...@isect.com] Sent: Wednesday, June 26, 2019 5:36 PM To: 'WSJT software development' Subject: Re: [wsjt-devel] Monthly ALL.TXT archives Hi Roy. I am very active on FT8, clocking up about 900 FT8 QSOs per month and monitoring open HF FT8 subbands all ZL day while I work on the adjacent screen. My ALL.TXT typically grows to more than 30 Mb per month e.g.: [cid:image001.png@01D52C51.0A1E2AE0] Early each new month, I manually add the previous month’s ALL.TXT to a ZIP archive. Luckily the ALL.TXT data structure is very simple so it compresses down neatly to about 40 Mb per year: [cid:image003.png@01D52C51.0A1E2AE0] I sometimes need to check through my ALL.TXT for details of a QSO that someone has claimed on a QSL card or by email, but doesn’t appear in my Logger32 station log. It’s easy to open the relevant month’s ALL.TXT section from the ZIP archive and search for the QSO in question … and almost always I find a nearly-completed or completed QSO that for some reason wasn’t transferred to Logger32. If you try opening the current ALL.TXT file in, say, Notepad while WSJT-X or JTDX is still running, you’ll probably get pop-up warnings every 15 seconds that the file has been updated when new decodes are written to it: that doesn’t happen if you are using a closed/archived ALL.TXT file. So, monthly ALL.TXTs are worthwhile for highly active stations … and I think they would be useful for almost everyone. 73 Gary ZL2iFB From: Roy Gould mailto:roygou...@gmail.com>> Sent: 27 June 2019 03:52 To: WSJT software development mailto:wsjt-devel@lists.sourceforge.net>> Subject: Re: [wsjt-devel] Monthly ALL.TXT archives Thanks for the education. Before you started discussing the ALL.TXT file I did not know it existed. So I decided to check it out and see what it was all about. Here are some things that I found out about it in my case. The file in my computer was nearly 24 MB in size. I double clicked on it and it immediately came into Notepad on my Windows 10 computer so I could take a look at it. I tried Finding things such as CQ FD and it found several of those. I searched for my call sign (W7IDM) and it found it. I discovered that beginning on 19/02/27 that the format of the data stored was radically different and put into a much better format. So I deleted all of the previous entries leaving only the new format and that became the file that I am currently using. This file is about 6 MB in length. I tried loading the file into EXCEL from Office 365 and EXCEL said that it looks like this data is in fixed width columns and asked if I agreed. I said yes and the data came in just fine. Now that it is in EXCEL format I have the ability to use the powerful EXCEL data base functions to do a lot of different types of analysis. I don't see any particular need to want to break it into monthly segments. Perhaps it would be good to save it in yearly segments. It appears that I can easily work with a whole year of data at a time, so why break it up monthly? So, for what it is worth, these are my observations... 73, Roy, W7IDM On Tue, Jun 25, 2019 at 11:55 AM Sam W2JDB via wsjt-devel mailto:wsjt-devel@lists.sourceforge.net>> wrote: Hi, I recompiled the program with "openread" and "sharedenynone" but it seems that when wsjtx attempts to append to the file I received the same error message. BTW, I open the file and close the file as soon as I finish scanning the file. It is only at the end of the decode when wsjtx is attempting to append to the file while alltext.exe is still parsing the file that the error pops up. If the scan finishes before wsjtx attempts to append to the file, there is no error. Sorry, but that is the best that I can do. As I posted before, I do not use the alltext.exe while wsjtx is running. Sam W2JDB -Original Message- From: DG2YCB, Uwe mailto:dg2...@gmx.de>> To: 'WSJT software development' mailto:wsjt-devel@lists.sourceforge.net>> Sent: Tue, Jun 25, 2019 12:13 pm Subject: Re: [wsjt-devel] Monthly ALL.TXT archives Sam, alltext.exe works great, BUT there is one big disadvantage: Once the ALL.txt file is opened with alltext.exe, the ALL.TXT file is locked by Windows. And due to that WSJT
Re: [wsjt-devel] Monthly ALL.TXT archives
Hi Roy. I am very active on FT8, clocking up about 900 FT8 QSOs per month and monitoring open HF FT8 subbands all ZL day while I work on the adjacent screen. My ALL.TXT typically grows to more than 30 Mb per month e.g.: Early each new month, I manually add the previous month’s ALL.TXT to a ZIP archive. Luckily the ALL.TXT data structure is very simple so it compresses down neatly to about 40 Mb per year: I sometimes need to check through my ALL.TXT for details of a QSO that someone has claimed on a QSL card or by email, but doesn’t appear in my Logger32 station log. It’s easy to open the relevant month’s ALL.TXT section from the ZIP archive and search for the QSO in question … and almost always I find a nearly-completed or completed QSO that for some reason wasn’t transferred to Logger32. If you try opening the current ALL.TXT file in, say, Notepad while WSJT-X or JTDX is still running, you’ll probably get pop-up warnings every 15 seconds that the file has been updated when new decodes are written to it: that doesn’t happen if you are using a closed/archived ALL.TXT file. So, monthly ALL.TXTs are worthwhile for highly active stations … and I think they would be useful for almost everyone. 73 Gary ZL2iFB From: Roy Gould Sent: 27 June 2019 03:52 To: WSJT software development Subject: Re: [wsjt-devel] Monthly ALL.TXT archives Thanks for the education. Before you started discussing the ALL.TXT file I did not know it existed. So I decided to check it out and see what it was all about. Here are some things that I found out about it in my case. The file in my computer was nearly 24 MB in size. I double clicked on it and it immediately came into Notepad on my Windows 10 computer so I could take a look at it. I tried Finding things such as CQ FD and it found several of those. I searched for my call sign (W7IDM) and it found it. I discovered that beginning on 19/02/27 that the format of the data stored was radically different and put into a much better format. So I deleted all of the previous entries leaving only the new format and that became the file that I am currently using. This file is about 6 MB in length. I tried loading the file into EXCEL from Office 365 and EXCEL said that it looks like this data is in fixed width columns and asked if I agreed. I said yes and the data came in just fine. Now that it is in EXCEL format I have the ability to use the powerful EXCEL data base functions to do a lot of different types of analysis. I don't see any particular need to want to break it into monthly segments. Perhaps it would be good to save it in yearly segments. It appears that I can easily work with a whole year of data at a time, so why break it up monthly? So, for what it is worth, these are my observations... 73, Roy, W7IDM On Tue, Jun 25, 2019 at 11:55 AM Sam W2JDB via wsjt-devel mailto:wsjt-devel@lists.sourceforge.net> > wrote: Hi, I recompiled the program with "openread" and "sharedenynone" but it seems that when wsjtx attempts to append to the file I received the same error message. BTW, I open the file and close the file as soon as I finish scanning the file. It is only at the end of the decode when wsjtx is attempting to append to the file while alltext.exe is still parsing the file that the error pops up. If the scan finishes before wsjtx attempts to append to the file, there is no error. Sorry, but that is the best that I can do. As I posted before, I do not use the alltext.exe while wsjtx is running. Sam W2JDB -Original Message- From: DG2YCB, Uwe mailto:dg2...@gmx.de> > To: 'WSJT software development' mailto:wsjt-devel@lists.sourceforge.net> > Sent: Tue, Jun 25, 2019 12:13 pm Subject: Re: [wsjt-devel] Monthly ALL.TXT archives Sam, alltext.exe works great, BUT there is one big disadvantage: Once the ALL.txt file is opened with alltext.exe, the ALL.TXT file is locked by Windows. And due to that WSJT-X is showing error messages “Cannot open …ALL.TXT” because the file is in use (see screen shot). Is there a fix for this (or any workaround)? I don’t know why, but the normal Windows editor does not lock the ALL.txt. file like alltxt.exe does. 73 de Uwe, DG2YCB Von: Sam W2JDB via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> ] Gesendet: Dienstag, 25. Juni 2019 16:07 An: wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> Cc: Sam W2JDB Betreff: Re: [wsjt-devel] Monthly ALL.TXT archives Hi Rich, IN the QLOGBeta file folder is a program called alltext.exe. I use it to search the all.txt file. It has various filters and presents only the lines that meet the criteria. I use that when I need to confirm what I think is an incomplete QSO. Try it. Its pretty fast. 73, Sam W2JDB --
Re: [wsjt-devel] Monthly ALL.TXT archives
Thanks for the education. Before you started discussing the ALL.TXT file I did not know it existed. So I decided to check it out and see what it was all about. Here are some things that I found out about it in my case. The file in my computer was nearly 24 MB in size. I double clicked on it and it immediately came into Notepad on my Windows 10 computer so I could take a look at it. I tried Finding things such as CQ FD and it found several of those. I searched for my call sign (W7IDM) and it found it. I discovered that beginning on 19/02/27 that the format of the data stored was radically different and put into a much better format. So I deleted all of the previous entries leaving only the new format and that became the file that I am currently using. This file is about 6 MB in length. I tried loading the file into EXCEL from Office 365 and EXCEL said that it looks like this data is in fixed width columns and asked if I agreed. I said yes and the data came in just fine. Now that it is in EXCEL format I have the ability to use the powerful EXCEL data base functions to do a lot of different types of analysis. I don't see any particular need to want to break it into monthly segments. Perhaps it would be good to save it in yearly segments. It appears that I can easily work with a whole year of data at a time, so why break it up monthly? So, for what it is worth, these are my observations... 73, Roy, W7IDM On Tue, Jun 25, 2019 at 11:55 AM Sam W2JDB via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Hi, > > I recompiled the program with "openread" and "sharedenynone" but it seems > that when wsjtx attempts to append to the file I received the same error > message. > > BTW, I open the file and close the file as soon as I finish scanning the > file. It is only at the end of the decode when wsjtx is attempting to > append to the file while alltext.exe is still parsing the file that the > error pops up. If the scan finishes before wsjtx attempts to append to the > file, there is no error. > > Sorry, but that is the best that I can do. As I posted before, I do not > use the alltext.exe while wsjtx is running. > > Sam W2JDB > > > > -Original Message- > From: DG2YCB, Uwe > To: 'WSJT software development' > Sent: Tue, Jun 25, 2019 12:13 pm > Subject: Re: [wsjt-devel] Monthly ALL.TXT archives > > Sam, > alltext.exe works great, BUT there is one big disadvantage: Once the > ALL.txt file is opened with alltext.exe, the ALL.TXT file is locked by > Windows. And due to that WSJT-X is showing error messages “Cannot open > …ALL.TXT” because the file is in use (see screen shot). Is there a fix for > this (or any workaround)? I don’t know why, but the normal Windows editor > does not lock the ALL.txt. file like alltxt.exe does. > > > 73 de Uwe, DG2YCB > > > *Von:* Sam W2JDB via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] > *Gesendet:* Dienstag, 25. Juni 2019 16:07 > *An:* wsjt-devel@lists.sourceforge.net > *Cc:* Sam W2JDB > *Betreff:* Re: [wsjt-devel] Monthly ALL.TXT archives > > Hi Rich, > > IN the QLOGBeta file folder is a program called alltext.exe. > I use it to search the all.txt file. It has various filters and presents > only the lines that meet the criteria. I use that when I need to confirm > what I think is an incomplete QSO. Try it. Its pretty fast. > > 73, > > Sam W2JDB > > > > -Original Message- > From: Rich Zwirko - K1HTV > To: WSJT > Sent: Tue, Jun 25, 2019 10:00 am > Subject: [wsjt-devel] Monthly ALL.TXT archives > Recently, a WSJT-X users asked me how to check if a QSO was actually > completed. He had received a request to confirm a QSO which was not in his > log. I pointed him at the ALL.TXT file. He got back to me later saying that > the file size was enormous and too large for any of his text editors to > read. > > Monthly, I edit my ALL.TXT file and manually archive the decoded data for > future use. These files have been used a number of times to confirm QSOs > when a station that I work, usually a DXpedition, says I'm not in the log > and I know that it was a solid QSO. I excerpt the decodes, showing > responses to me and others, attaching the info to an email that is sent to > him. > > Unless it is kept to a reasonable size, the ALL.TXT will be useless to > most WSJT-X ops who want to check it. Why not archive the lines of decoded > data into a file with a file name reflecting the month that the data was > decoded, such as: > > 2019-06ALL.TXT > > I believe that this change should be seriously considered in a future > release of WSJT-X. > > 73, > Rich - K1HTV > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.source
Re: [wsjt-devel] Monthly ALL.TXT archives
Your suggestion does not work here with Windows 7. I tried simply typing "ALL.TXT" in the search window but the file, which resides in AppData/Local/WSJT-X, is not found. Your suggestion of using "FIND" does not allow the user to easily browse through the ALL.TXT file, which is what I want to be able to do and can do easily in the monthly files that I manually archive. What good is a humongous ALL.TXT file to a WSJT-X user if he can't easily browse through it? I was told by another local FT8 user that JTDX does what I have requested, that is archiving ALL.TXT files in separate monthly files. He also informed me that my other request that Red/Green colors be used in the 15 second count up bar also already exists in the JTDX software. 73, Rich - K1HTV = = = From: Black Michael To: WSJT Cc: Bcc: Date: Tue, 25 Jun 2019 14:05:11 + (UTC) Subject: Re: [wsjt-devel] Monthly ALL.TXT archives On Windows: find "K1HTV" ALL.TXT | find "S92HP" 190611_06190014.074 Rx FT8-17 0.1 2393 S92HP K1HTV -11 190611_06203014.074 Rx FT8-15 0.1 1106 S92HP K1HTV -11 190611_06210014.074 Rx FT8-17 0.4 1107 S92HP K1HTV -11 190611_06214514.074 Rx FT8-17 0.4 1106 S92HP K1HTV -11 190611_06220014.074 Rx FT8-15 0.4 1107 S92HP K1HTV RR73 190611_06223014.074 Rx FT8-15 0.4 1107 S92HP K1HTV RR73 On Linux grep "K1HTV" ALL.TXT | grep "S92HP" de Mike W9MDB ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Monthly ALL.TXT archives
Try Notepad++ https://notepad-plus-plus.org/ --- This email has been checked for viruses by AVG. https://www.avg.com ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Monthly ALL.TXT archives
Hi, I recompiled the program with "openread" and "sharedenynone" but it seems
that when wsjtx attempts to append to the file I received the same error
message. BTW, I open the file and close the file as soon as I finish scanning
the file. It is only at the end of the decode when wsjtx is attempting to
append to the file while alltext.exe is still parsing the file that the error
pops up. If the scan finishes before wsjtx attempts to append to the file,
there is no error. Sorry, but that is the best that I can do. As I posted
before, I do not use the alltext.exe while wsjtx is running. Sam W2JDB
-Original Message-
From: DG2YCB, Uwe
To: 'WSJT software development'
Sent: Tue, Jun 25, 2019 12:13 pm
Subject: Re: [wsjt-devel] Monthly ALL.TXT archives
#yiv6314331436 #yiv6314331436 -- _filtered #yiv6314331436
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv6314331436
{font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;} #yiv6314331436
#yiv6314331436 p.yiv6314331436MsoNormal, #yiv6314331436
li.yiv6314331436MsoNormal, #yiv6314331436 div.yiv6314331436MsoNormal
{margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;font-family:New;}
#yiv6314331436 a:link, #yiv6314331436 span.yiv6314331436MsoHyperlink
{color:blue;text-decoration:underline;} #yiv6314331436 a:visited,
#yiv6314331436 span.yiv6314331436MsoHyperlinkFollowed
{color:purple;text-decoration:underline;} #yiv6314331436
p.yiv6314331436MsoAcetate, #yiv6314331436 li.yiv6314331436MsoAcetate,
#yiv6314331436 div.yiv6314331436MsoAcetate
{margin:0cm;margin-bottom:.0001pt;font-size:8.0pt;} #yiv6314331436
span.yiv6314331436E-MailFormatvorlage17 {color:#1F497D;} #yiv6314331436
span.yiv6314331436SprechblasentextZchn {} #yiv6314331436
.yiv6314331436MsoChpDefault {} _filtered #yiv6314331436 {margin:70.85pt 70.85pt
2.0cm 70.85pt;} #yiv6314331436 div.yiv6314331436WordSection1 {} #yiv6314331436
Sam,alltext.exe works great, BUT there is one big disadvantage: Once the
ALL.txt file is opened with alltext.exe, the ALL.TXT file is locked by Windows.
And due to that WSJT-X is showing error messages “Cannot open …ALL.TXT” because
the file is in use (see screen shot). Is there a fix for this (or any
workaround)? I don’t know why, but the normal Windows editor does not lock the
ALL.txt. file like alltxt.exe does. 73 de Uwe, DG2YCB Von: Sam W2JDB via
wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Gesendet: Dienstag, 25. Juni 2019 16:07
An: wsjt-devel@lists.sourceforge.net
Cc: Sam W2JDB
Betreff: Re: [wsjt-devel] Monthly ALL.TXT archives Hi Rich, IN the QLOGBeta
file folder is a program called alltext.exe.I use it to search the all.txt
file. It has various filters and presents only the lines that meet the
criteria. I use that when I need to confirm what I think is an incomplete QSO.
Try it. Its pretty fast. 73, Sam W2JDB -Original Message-
From: Rich Zwirko - K1HTV
To: WSJT
Sent: Tue, Jun 25, 2019 10:00 am
Subject: [wsjt-devel] Monthly ALL.TXT archivesRecently, a WSJT-X users asked me
how to check if a QSO was actually completed. He had received a request to
confirm a QSO which was not in his log. I pointed him at the ALL.TXT file. He
got back to me later saying that the file size was enormous and too large for
any of his text editors to read. Monthly, I edit my ALL.TXT file and manually
archive the decoded data for future use. These files have been used a number of
times to confirm QSOs when a station that I work, usually a DXpedition, says
I'm not in the log and I know that it was a solid QSO. I excerpt the decodes,
showing responses to me and others, attaching the info to an email that is sent
to him. Unless it is kept to a reasonable size, the ALL.TXT will be useless to
most WSJT-X ops who want to check it. Why not archive the lines of decoded data
into a file with a file name reflecting the month that the data was decoded,
such as: 2019-06ALL.TXT I believe that this change should be seriously
considered in a future release of WSJT-X. 73,Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Monthly ALL.TXT archives
Hi Bill, Done. Thanks. 73, Sam W2JDB -Original Message- From: Bill Somerville To: wsjt-devel Sent: Tue, Jun 25, 2019 12:58 pm Subject: Re: [wsjt-devel] Monthly ALL.TXT archives On 25/06/2019 17:50, Sam W2JDB via wsjt-devel wrote: > I had to remove it from SourceForge as my program is not open source > And I could not figure out how to delete the project from there. Hi Sam, https://sourceforge.net/p/forge/documentation/How%20to%20Remove%20a%20Project/ 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Monthly ALL.TXT archives
Hi, Never used alltext.exe while wsjtx was running so I never ran into this
problem. I will look into changing that. Will be going on holiday but will see
if I can update the program before I leave. Will let you know if I did manage
to do that. 73, Sam W2JDB
-Original Message-
From: DG2YCB, Uwe
To: 'WSJT software development'
Sent: Tue, Jun 25, 2019 12:13 pm
Subject: Re: [wsjt-devel] Monthly ALL.TXT archives
#yiv6314331436 #yiv6314331436 -- _filtered #yiv6314331436
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv6314331436
{font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;} #yiv6314331436
#yiv6314331436 p.yiv6314331436MsoNormal, #yiv6314331436
li.yiv6314331436MsoNormal, #yiv6314331436 div.yiv6314331436MsoNormal
{margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;font-family:New;}
#yiv6314331436 a:link, #yiv6314331436 span.yiv6314331436MsoHyperlink
{color:blue;text-decoration:underline;} #yiv6314331436 a:visited,
#yiv6314331436 span.yiv6314331436MsoHyperlinkFollowed
{color:purple;text-decoration:underline;} #yiv6314331436
p.yiv6314331436MsoAcetate, #yiv6314331436 li.yiv6314331436MsoAcetate,
#yiv6314331436 div.yiv6314331436MsoAcetate
{margin:0cm;margin-bottom:.0001pt;font-size:8.0pt;} #yiv6314331436
span.yiv6314331436E-MailFormatvorlage17 {color:#1F497D;} #yiv6314331436
span.yiv6314331436SprechblasentextZchn {} #yiv6314331436
.yiv6314331436MsoChpDefault {} _filtered #yiv6314331436 {margin:70.85pt 70.85pt
2.0cm 70.85pt;} #yiv6314331436 div.yiv6314331436WordSection1 {} #yiv6314331436
Sam,alltext.exe works great, BUT there is one big disadvantage: Once the
ALL.txt file is opened with alltext.exe, the ALL.TXT file is locked by Windows.
And due to that WSJT-X is showing error messages “Cannot open …ALL.TXT” because
the file is in use (see screen shot). Is there a fix for this (or any
workaround)? I don’t know why, but the normal Windows editor does not lock the
ALL.txt. file like alltxt.exe does. 73 de Uwe, DG2YCB Von: Sam W2JDB via
wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Gesendet: Dienstag, 25. Juni 2019 16:07
An: wsjt-devel@lists.sourceforge.net
Cc: Sam W2JDB
Betreff: Re: [wsjt-devel] Monthly ALL.TXT archives Hi Rich, IN the QLOGBeta
file folder is a program called alltext.exe.I use it to search the all.txt
file. It has various filters and presents only the lines that meet the
criteria. I use that when I need to confirm what I think is an incomplete QSO.
Try it. Its pretty fast. 73, Sam W2JDB -Original Message-
From: Rich Zwirko - K1HTV
To: WSJT
Sent: Tue, Jun 25, 2019 10:00 am
Subject: [wsjt-devel] Monthly ALL.TXT archivesRecently, a WSJT-X users asked me
how to check if a QSO was actually completed. He had received a request to
confirm a QSO which was not in his log. I pointed him at the ALL.TXT file. He
got back to me later saying that the file size was enormous and too large for
any of his text editors to read. Monthly, I edit my ALL.TXT file and manually
archive the decoded data for future use. These files have been used a number of
times to confirm QSOs when a station that I work, usually a DXpedition, says
I'm not in the log and I know that it was a solid QSO. I excerpt the decodes,
showing responses to me and others, attaching the info to an email that is sent
to him. Unless it is kept to a reasonable size, the ALL.TXT will be useless to
most WSJT-X ops who want to check it. Why not archive the lines of decoded data
into a file with a file name reflecting the month that the data was decoded,
such as: 2019-06ALL.TXT I believe that this change should be seriously
considered in a future release of WSJT-X. 73,Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Monthly ALL.TXT archives
Hi Bill, Thanks. Will do that shortly. Sam W2JDB -Original Message- From: Bill Somerville To: wsjt-devel Sent: Tue, Jun 25, 2019 12:58 pm Subject: Re: [wsjt-devel] Monthly ALL.TXT archives On 25/06/2019 17:50, Sam W2JDB via wsjt-devel wrote: > I had to remove it from SourceForge as my program is not open source > And I could not figure out how to delete the project from there. Hi Sam, https://sourceforge.net/p/forge/documentation/How%20to%20Remove%20a%20Project/ 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Monthly ALL.TXT archives
On 25/06/2019 17:50, Sam W2JDB via wsjt-devel wrote: I had to remove it from SourceForge as my program is not open source And I could not figure out how to delete the project from there. Hi Sam, https://sourceforge.net/p/forge/documentation/How%20to%20Remove%20a%20Project/ 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Monthly ALL.TXT archives
Hi Bill, I had to remove it from SourceForge as my program is not open source And I could not figure out how to delete the project from there.Very sorry about that. 73, Sam W2JDB -Original Message- From: Bill Somerville To: wsjt-devel Sent: Tue, Jun 25, 2019 12:38 pm Subject: Re: [wsjt-devel] Monthly ALL.TXT archives Hi Mike, did you miss the ;-) Yes the Groups.io forum is probably the best place to go. 73 Bill G4WJS. On 25/06/2019 17:31, Black Michael via wsjt-devel wrote: Well without knowing Sam is the author And the top result has non-downloadable links. https://sourceforge.net/projects/w2jdb-quicklog/ Mike On Tuesday, June 25, 2019, 10:59:34 AM CDT, Bill Somerville wrote: On 25/06/2019 16:50, Black Michael via wsjt-devel wrote: > And where can one get that software? > > Lots of "qlog" programs out there it seems. > Hi Mike, https://lmgtfy.com/?q=w2jdb+qlog ;-) 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Monthly ALL.TXT archives
Hi Mike, did you miss the ;-) Yes the Groups.io forum is probably the best place to go. 73 Bill G4WJS. On 25/06/2019 17:31, Black Michael via wsjt-devel wrote: Well without knowing Sam is the author And the top result has non-downloadable links. https://sourceforge.net/projects/w2jdb-quicklog/ Mike On Tuesday, June 25, 2019, 10:59:34 AM CDT, Bill Somerville wrote: On 25/06/2019 16:50, Black Michael via wsjt-devel wrote: > And where can one get that software? > > Lots of "qlog" programs out there it seems. > Hi Mike, https://lmgtfy.com/?q=w2jdb+qlog ;-) 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Monthly ALL.TXT archives
Well without knowing Sam is the author And the top result has non-downloadable links. https://sourceforge.net/projects/w2jdb-quicklog/ Mike On Tuesday, June 25, 2019, 10:59:34 AM CDT, Bill Somerville wrote: On 25/06/2019 16:50, Black Michael via wsjt-devel wrote: > And where can one get that software? > > Lots of "qlog" programs out there it seems. > Hi Mike, https://lmgtfy.com/?q=w2jdb+qlog ;-) 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Monthly ALL.TXT archives
Sam, alltext.exe works great, BUT there is one big disadvantage: Once the ALL.txt file is opened with alltext.exe, the ALL.TXT file is locked by Windows. And due to that WSJT-X is showing error messages “Cannot open …ALL.TXT” because the file is in use (see screen shot). Is there a fix for this (or any workaround)? I don’t know why, but the normal Windows editor does not lock the ALL.txt. file like alltxt.exe does. 73 de Uwe, DG2YCB Von: Sam W2JDB via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Gesendet: Dienstag, 25. Juni 2019 16:07 An: wsjt-devel@lists.sourceforge.net Cc: Sam W2JDB Betreff: Re: [wsjt-devel] Monthly ALL.TXT archives Hi Rich, IN the QLOGBeta file folder is a program called alltext.exe. I use it to search the all.txt file. It has various filters and presents only the lines that meet the criteria. I use that when I need to confirm what I think is an incomplete QSO. Try it. Its pretty fast. 73, Sam W2JDB -Original Message- From: Rich Zwirko - K1HTV To: WSJT Sent: Tue, Jun 25, 2019 10:00 am Subject: [wsjt-devel] Monthly ALL.TXT archives Recently, a WSJT-X users asked me how to check if a QSO was actually completed. He had received a request to confirm a QSO which was not in his log. I pointed him at the ALL.TXT file. He got back to me later saying that the file size was enormous and too large for any of his text editors to read. Monthly, I edit my ALL.TXT file and manually archive the decoded data for future use. These files have been used a number of times to confirm QSOs when a station that I work, usually a DXpedition, says I'm not in the log and I know that it was a solid QSO. I excerpt the decodes, showing responses to me and others, attaching the info to an email that is sent to him. Unless it is kept to a reasonable size, the ALL.TXT will be useless to most WSJT-X ops who want to check it. Why not archive the lines of decoded data into a file with a file name reflecting the month that the data was decoded, such as: 2019-06ALL.TXT I believe that this change should be seriously considered in a future release of WSJT-X. 73, Rich - K1HTV ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Monthly ALL.TXT archives
On 25/06/2019 16:50, Black Michael via wsjt-devel wrote: And where can one get that software? Lots of "qlog" programs out there it seems. Hi Mike, https://lmgtfy.com/?q=w2jdb+qlog ;-) 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Monthly ALL.TXT archives
And where can one get that software? Lots of "qlog" programs out there it seems. de Mike W9MDB On Tuesday, June 25, 2019, 09:40:52 AM CDT, Sam W2JDB via wsjt-devel wrote: Hi Rich, IN the QLOGBeta file folder is a program called alltext.exe.I use it to search the all.txt file. It has various filters and presents only the lines that meet the criteria. I use that when I need to confirm what I think is an incomplete QSO. Try it. Its pretty fast. 73, Sam W2JDB ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Monthly ALL.TXT archives
Hi Rich, IN the QLOGBeta file folder is a program called alltext.exe.I use it to search the all.txt file. It has various filters and presents only the lines that meet the criteria. I use that when I need to confirm what I think is an incomplete QSO. Try it. Its pretty fast. 73, Sam W2JDB -Original Message- From: Rich Zwirko - K1HTV To: WSJT Sent: Tue, Jun 25, 2019 10:00 am Subject: [wsjt-devel] Monthly ALL.TXT archives Recently, a WSJT-X users asked me how to check if a QSO was actually completed. He had received a request to confirm a QSO which was not in his log. I pointed him at the ALL.TXT file. He got back to me later saying that the file size was enormous and too large for any of his text editors to read. Monthly, I edit my ALL.TXT file and manually archive the decoded data for future use. These files have been used a number of times to confirm QSOs when a station that I work, usually a DXpedition, says I'm not in the log and I know that it was a solid QSO. I excerpt the decodes, showing responses to me and others, attaching the info to an email that is sent to him. Unless it is kept to a reasonable size, the ALL.TXT will be useless to most WSJT-X ops who want to check it. Why not archive the lines of decoded data into a file with a file name reflecting the month that the data was decoded, such as: 2019-06ALL.TXT I believe that this change should be seriously considered in a future release of WSJT-X. 73,Rich - K1HTV ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Monthly ALL.TXT archives
On Windows: find "K1HTV" ALL.TXT | find "S92HP"190611_061900 14.074 Rx FT8 -17 0.1 2393 S92HP K1HTV -11190611_062030 14.074 Rx FT8 -15 0.1 1106 S92HP K1HTV -11190611_062100 14.074 Rx FT8 -17 0.4 1107 S92HP K1HTV -11190611_062145 14.074 Rx FT8 -17 0.4 1106 S92HP K1HTV -11190611_062200 14.074 Rx FT8 -15 0.4 1107 S92HP K1HTV RR73190611_062230 14.074 Rx FT8 -15 0.4 1107 S92HP K1HTV RR73 On Linuxgrep "K1HTV" ALL.TXT | grep "S92HP" de Mike W9MDB On Tuesday, June 25, 2019, 09:01:02 AM CDT, Rich Zwirko - K1HTV wrote: Recently, a WSJT-X users asked me how to check if a QSO was actually completed. He had received a request to confirm a QSO which was not in his log. I pointed him at the ALL.TXT file. He got back to me later saying that the file size was enormous and too large for any of his text editors to read. Monthly, I edit my ALL.TXT file and manually archive the decoded data for future use. These files have been used a number of times to confirm QSOs when a station that I work, usually a DXpedition, says I'm not in the log and I know that it was a solid QSO. I excerpt the decodes, showing responses to me and others, attaching the info to an email that is sent to him. Unless it is kept to a reasonable size, the ALL.TXT will be useless to most WSJT-X ops who want to check it. Why not archive the lines of decoded data into a file with a file name reflecting the month that the data was decoded, such as: 2019-06ALL.TXT I believe that this change should be seriously considered in a future release of WSJT-X. 73,Rich - K1HTV ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Monthly ALL.TXT archives
Recently, a WSJT-X users asked me how to check if a QSO was actually completed. He had received a request to confirm a QSO which was not in his log. I pointed him at the ALL.TXT file. He got back to me later saying that the file size was enormous and too large for any of his text editors to read. Monthly, I edit my ALL.TXT file and manually archive the decoded data for future use. These files have been used a number of times to confirm QSOs when a station that I work, usually a DXpedition, says I'm not in the log and I know that it was a solid QSO. I excerpt the decodes, showing responses to me and others, attaching the info to an email that is sent to him. Unless it is kept to a reasonable size, the ALL.TXT will be useless to most WSJT-X ops who want to check it. Why not archive the lines of decoded data into a file with a file name reflecting the month that the data was decoded, such as: 2019-06ALL.TXT I believe that this change should be seriously considered in a future release of WSJT-X. 73, Rich - K1HTV ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
