ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
esc to dismiss
Re: AT&T ending email to text on June18
<>
shows Android, iPhone & iPad, Desktop (Browser based).
Looks like the one-time license fee is now $4.99 per
platform (Android, iPhone/iPad, Desktop) for up to 10
devices. They have a 30 day trial.
73,
... Joe, W4TV
toggle quoted message
Show quoted text
On 2025-04-02 9:49 AM, Dean W8ZF wrote: Hi Jim,
I had similar unreliable email to sms service from Tmobile, and then Gmail. I found an Android app called Pushover. It costed like, $2.99 for lifetime use. I got an address to send my emails, and it sends me an SMS. It is nearly instantaneous and works very well. Don't know if there's an iPhone version.
73
Dean W8ZF
|
Re: AT&T ending email to text on June18
Hi Jim,
I had similar unreliable email to sms service from Tmobile, and then Gmail. I found an Android app called Pushover. It costed like, $2.99 for lifetime use. I got an address to send my emails, and it sends me an SMS. It is nearly instantaneous and works very well. Don't know if there's an iPhone version.
73?
Dean W8ZF?
|
You can't simply copy an installation from one computer to
another. However, if you follow the instructions here:
<>
you can reinstall on the new computer with all of your
settings and intact.
73,
... Joe, W4TV
toggle quoted message
Show quoted text
On 2025-04-02 7:55 AM, scot via groups.io wrote: Hello,
I wanted to know if there is a way to copy a profile from 1 computer to another ? I had a crash and lost the laptop. I have a good working install on a desktop.
Scott
N2SAB
|
|
| |
toggle quoted message
Show quoted text
On Apr 2, 2025, at 06:55, scot via groups.io <n2sab@...> wrote:
Hello,
?
I wanted to know if there is a way to copy a profile from 1 computer to another ? I had a crash and lost the laptop. I have a good working install on a desktop.
?
Scott
N2SAB
Hello,
?
I wanted to know if there is a way to copy a profile from 1 computer to another ? I had a crash and lost the laptop. I have a good working install on a desktop.
?
Scott
N2SAB
|
Re: FW: [CC-User] Bogus DX Spot Attacks on Clusters
+ AA6YQ comments below
Well, I (just now) took a look at it, and it has enough entries that I am not sure I want to pursue it further! <G>
+ You can reduce your "search" to the time the behavior occurred, and the 5-10 minutes before that.? ? ? ? ? ?Dave
|
Re: FW: [CC-User] Bogus DX Spot Attacks on Clusters
On Tuesday, April 1st, 2025 at 4:50 PM, Dave AA6YQ <aa6yq@...> wrote: + AA6YQ comments below <SNIP> Spot Database Entries was somewhere around 30K-40K entries.
+ That'd a big Spot Database during a popular contest with your own Skimmer running. Yes, I agree. I just didn't think of the contest, I was just trying to contact a particular DX area, using every spot source / input I could get. There is/wasn't error log.
+ I suggest checking the Windows Error Log:
Well, I (just now) took a look at it, and it has enough entries that I am not sure I want to pursue it further! <G> Thanks, Dave. Watch for next email. 7 3 Earl Sent with Proton Mail secure email.
|
Re: Unable to upload to LotW
Dave, OK, Thanks.? I can wait for the next general release.??
+ "Report unmatched QSOs and QSLs as error" box checked on the "QSL Configuation" window's LoTW tab? ? *? Now unchecked. +???invoke "Sync LoTW QSOs" again.
? *? Done
Rich, NU6T
# more AA6YQ comments below
?
? * Two QSOs show in the Log QSOs tab.??
?
? *? I also see an Error File notice and in the notice I see a long list of errors for 2025-04-01.? Examples below:
- 2025-04-01 21:01:40.892 > program error 52 in module Common.PrintField, theFile = 3: Bad file name or number
- 2025-04-01 21:01:40.895 > program error 52 in module ADIF.LotWImportError: Bad file name or number
? *? The errors are in about 82 sets of 7 of the first followed by 1 of the second.
?
# That's the result of a defect in the current version of DXKeeper when "Sync LoTW QSOs" reports an error - typically a QSO that LoTW is reporting as accepted but is not present in your log. This defect is corrected in the next version of DXKeeper, which i can send you, but before I do that, is the "Report unmatched QSOs and QSLs as error" box checked on the "QSL Configuation" window's LoTW tab? If so, uncheck it, and then invoke "Sync LoTW QSOs" again. ? ? ?73,
? ? ? ? ? ? Dave, AA6YQ
|
Re: FW: [CC-User] Bogus DX Spot Attacks on Clusters
+ AA6YQ comments below
I had noticed "something " going on. For the first time in many months, I turned SKIMMER on, on my spot sources.
It took a few hours, but I found all my spot sources indicators were yellow, and when I opened config, Prune, Compact, Clear and (I think) Recompute were all flashing. Spot Collector was locked up and I had to use Task Manager to kill it.
+ Spot Source status displayed as "yellow" means "disconnected, trying to reconnect".
Spot Database Entries was somewhere around 30K-40K entries.
+ That'd a big Spot Database during a popular contest with your own Skimmer running.
There is/wasn't error log.
+ I suggest checking the Windows Error Log:
73,
Dave, AA6YQ
\
|
Re: FW: [CC-User] Bogus DX Spot Attacks on Clusters
I had noticed "something " going on. For the first time in many months, I turned SKIMMER on, on my spot sources.
It took a few hours, but I found all my spot sources indicators were yellow, and when I opened config, Prune, Compact, Clear and (I think) Recompute were all flashing. Spot Collector was locked up and I had to use Task Manager to kill it.
Spot Database Entries was somewhere around 30K-40K entries.
There is/wasn't error log.
Turning Skimmer off and limiting the database size to 7K entries seems to have fixed whatever it was.
Just another data point, I guess.
7 3
Earl / KD5XB
Sent from Proton Mail Android
toggle quoted message
Show quoted text
-------- Original Message -------- On 4/1/25 10:47 AM, Dave AA6YQ <aa6yq@...> wrote: FYI:
From: [email protected] [mailto:[email protected]] On Behalf Of Lee Sawkins via groups.io
Sent: Tuesday, April 01, 2025 10:25 AM
To: [email protected]
Subject: Re: [CC-User] Bogus DX Spot Attacks on Clusters
What happened this weekend was that tens of thousands of bogus spots were entered into the cluster system. These spots were all for SSB. Since there are no SSB skimmers available yet, all of these spots appeared to be manually entered, but in fact they were generated by a computer.
Normally the human entered spots never are more than 60 per minute. During the weekend spots that were bogus were entered at many thousands per minute. These spots were targeting specific active calls. These spots were giving different frequencies on all contest bands for each bogus spot. These spots had same DX call and a different spotter call and different originating cluster call. This caused many nodes to get bogged down trying to process all this data. Some crashed. Others got hopelessly behind and continued sending data to my cluster which dropped the spots because they were too old. Millions of spots were being dropped.
My cluster limits the number of spots to 60 per minute. This limited bogus spots but also good spots in each minute. When bogus spots stopped, then all the new good ones got through.
Lee VE7CC
|
Re: AT&T ending email to text on June18
+ AA6YQ comments below
From Your favorite email folders and groups now in Outlook for iOS | Microsoft Community Hub <>
Q: How do I add a contact to my favorites?
A: Favorite contacts are not currently supported on Outlook for iOS , but should be coming soon!
In any event, I could not find a place to add a favorite in my Outlook for iOS app.
+ This is the URL that Perplexity cited as the basis for its claim that you could specify favorites in Outlook on an iPhone:
+ Did you watch the video cited in the response there?
73,
Dave, AA6YQ
|
Re: Unable to upload to LotW
# more AA6YQ comments below
?
? * Two QSOs show in the Log QSOs tab.??
?
? *? I also see an Error File notice and in the notice I see a long list of errors for 2025-04-01.? Examples below:
- 2025-04-01 21:01:40.892 > program error 52 in module Common.PrintField, theFile = 3: Bad file name or number
- 2025-04-01 21:01:40.895 > program error 52 in module ADIF.LotWImportError: Bad file name or number
? *? The errors are in about 82 sets of 7 of the first followed by 1 of the second.
?
# That's the result of a defect in the current version of DXKeeper when "Sync LoTW QSOs" reports an error - typically a QSO that LoTW is reporting as accepted but is not present in your log. This defect is corrected in the next version of DXKeeper, which i can send you, but before I do that, is the "Report unmatched QSOs and QSLs as error" box checked on the "QSL Configuation" window's LoTW tab? If so, uncheck it, and then invoke "Sync LoTW QSOs" again. ? ? ?73,
? ? ? ? ? ? Dave, AA6YQ
|
Re: AT&T ending email to text on June18
From
?
Q: How do I add a contact to my favorites? ? ? ??
A: Favorite contacts are not currently supported on Outlook for iOS , but should be coming soon!
?
In any event, I could not find a place to add a favorite in my Outlook for iOS app.
?
Tim K9WX
|
Re: Unable to upload to LotW
* NU6T comment below
6. in an hour or so, click the "Sync LoTW QSOs" button
? * Two QSOs show in the Log QSOs tab.??
? *? I also see an Error File notice and in the notice I see a long list of errors for 2025-04-01.? Examples below: - 2025-04-01 21:01:40.892 > program error 52 in module Common.PrintField, theFile = 3: Bad file name or number
- 2025-04-01 21:01:40.895 > program error 52 in module ADIF.LotWImportError: Bad file name or number
? *? The errors are in about 82 sets of 7 of the first followed by 1 of the second.
+ Normally, interoperation with LoTW does not require all of these manual steps. You can configure DXKeeper to automatically upload QSOs to LoTW as you log them. WinWarbler and all of the digital mode applications that interoperate with DXKeeper can be configured to direct DXKeeper to automatically upload QSOs to LoTW as you log them. Then periodically invoking DXKeeper's "Sync All" command is all that's required.?
? * I thought I had the system set up to log each QSO to LotW and ClubLog, and checked in Lotw every so often and thought they were showing up there.? I'll double check.
+ Note: if you're a contester and concerned with optimizing rate, importing your contest log into DXKeeper at the end of each contest and directing DXKeeper to upload your QSOs is the better approach.
? *? I use N1MM+ and upload files to my log after each contest and then to LotW, and ClubLog.? I've only recently begun to use ClubLog. ? *? Rate optimization?is just a vertical dream....
+ Unless you enjoy manual operations, avoid uploading QSOs to LoTW without first importing them into DXKeeper and uploading them to DXKeeper from there.
? *Grin, no I don't.? I'm looking forward to having enough knowledge to successfully keep up the automation of this amazing software.
+ See?
? *? Thank You
+ Similar automation is provided for Club Log, eQSL, and QRZ.
? *? Thank you.
Rich, NU6T + AA6YQ comments below
Dave, I proceeded through the instructions to:? 3. click the "Upload to LoTW" button
?
At that point I received a message that, in part, there were no QSLs to upload:
?
"TQSL Version 2.7.5 [v2.7.5]
Signing using Callsign NU6T, DXCC Entity UNITED STATES OF AMERICA
Already Uploaded QSO detected on line 5
CALL: 4E1DX
TIME_ON: 174200
QSO_DATE: 20250401
MODE: FT8
BAND: 20M
FREQ: 14.074996
?
Duplicate QSO detected
No QSOs to upload
Final Status: No QSOs to upload(8)"
?
I
?
+ That means at least 1 of those 95 QSOs - 4E1DX - had already been uploaded to LoTW from your current computer, even though the QSO doesn't so indicate.? + Please do the following: 1. Filter the Log Page Display with the SQL expressionapp_dxkeeper_lotw_qsl_sent <> 'Y'2. On the Main window's QSL tab, 2a. set the "QSL Via" panel to LoTW 2b. click the Clear button beneath the "QSL Queue" 2c. click the "Update from LoTW" button; this will direct LoTW to report the status of the QSOs in the Log Page Display as a result of step 1 3. When step 2b finished, again f ilter the Log Page Display with the SQL expressionapp_dxkeeper_lotw_qsl_sent <> 'Y'
Do any QSOs appear in the Log Page Display? If so, on the Main window's QSL tab, 4, click the "Add All" button 5. click the "Upload to LoTW" button; this time, we're only seeking to upload QSOs that we are certain have not already been updated 6. in an hour or so, click the "Sync LoTW QSOs" button + Normally, interoperation with LoTW does not require all of these manual steps. You can configure DXKeeper to automatically upload QSOs to LoTW as you log them. WinWarbler and all of the digital mode applications that interoperate with DXKeeper can be configured to direct DXKeeper to automatically upload QSOs to LoTW as you log them. Then periodically invoking DXKeeper's "Sync All" command is all that's required.? + Note: if you're a contester and concerned with optimizing rate, importing your contest log into DXKeeper at the end of each contest and directing DXKeeper to upload your QSOs is the better approach. + Unless you enjoy manual operations, avoid uploading QSOs to LoTW without first importing them into DXKeeper and uploading them to DXKeeper from there. + See? + Similar automation is provided for Club Log, eQSL, and QRZ. ? ? ? 73, ? ? ? ? ? Dave, AA6YQ
?
?
--
|
Re: FW: [CC-User] Bogus DX Spot Attacks on Clusters
This is not the first time it happened.
I informed Dave, but no action was needed in DXLab.
Eddy ON5JK
Op 1/04/2025 om 18:47 schreef Dave AA6YQ:
toggle quoted message
Show quoted text
FYI:
From: [email protected] [mailto:[email protected]] On Behalf Of Lee Sawkins via groups.io
Sent: Tuesday, April 01, 2025 10:25 AM
To: [email protected]
Subject: Re: [CC-User] Bogus DX Spot Attacks on Clusters
What happened this weekend was that tens of thousands of bogus spots were entered into the cluster system. These spots were all for SSB. Since there are no SSB skimmers available yet, all of these spots appeared to be manually entered, but in fact they were generated by a computer.
Normally the human entered spots never are more than 60 per minute. During the weekend spots that were bogus were entered at many thousands per minute. These spots were targeting specific active calls. These spots were giving different frequencies on all contest bands for each bogus spot. These spots had same DX call and a different spotter call and different originating cluster call. This caused many nodes to get bogged down trying to process all this data. Some crashed. Others got hopelessly behind and continued sending data to my cluster which dropped the spots because they were too old. Millions of spots were being dropped.
My cluster limits the number of spots to 60 per minute. This limited bogus spots but also good spots in each minute. When bogus spots stopped, then all the new good ones got through.
Lee VE7CC
|
Re: AT&T ending email to text on June18
+ AA6YQ comments below
AT&T was getting really bad in delivering the mailed texts sometimes nearly 12hrs late.
+ Are they delivering SMS messages late, or email messages late? ? ? ? 73, ? ? ? ? ? ? Dave, AA6YQ
|
Re: Unable to upload to LotW
+ AA6YQ comments below
Dave, I proceeded through the instructions to:? 3. click the "Upload to LoTW" button
?
At that point I received a message that, in part, there were no QSLs to upload:
?
"TQSL Version 2.7.5 [v2.7.5]
Signing using Callsign NU6T, DXCC Entity UNITED STATES OF AMERICA
Already Uploaded QSO detected on line 5
CALL: 4E1DX
TIME_ON: 174200
QSO_DATE: 20250401
MODE: FT8
BAND: 20M
FREQ: 14.074996
?
Duplicate QSO detected
No QSOs to upload
Final Status: No QSOs to upload(8)"
?
I
?
+ That means at least 1 of those 95 QSOs - 4E1DX - had already been uploaded to LoTW from your current computer, even though the QSO doesn't so indicate.? + Please do the following: 1. Filter the Log Page Display with the SQL expressionapp_dxkeeper_lotw_qsl_sent <> 'Y'2. On the Main window's QSL tab, 2a. set the "QSL Via" panel to LoTW 2b. click the Clear button beneath the "QSL Queue" 2c. click the "Update from LoTW" button; this will direct LoTW to report the status of the QSOs in the Log Page Display as a result of step 1 3. When step 2b finished, again f ilter the Log Page Display with the SQL expressionapp_dxkeeper_lotw_qsl_sent <> 'Y'
Do any QSOs appear in the Log Page Display? If so, on the Main window's QSL tab, 4, click the "Add All" button 5. click the "Upload to LoTW" button; this time, we're only seeking to upload QSOs that we are certain have not already been updated 6. in an hour or so, click the "Sync LoTW QSOs" button + Normally, interoperation with LoTW does not require all of these manual steps. You can configure DXKeeper to automatically upload QSOs to LoTW as you log them. WinWarbler and all of the digital mode applications that interoperate with DXKeeper can be configured to direct DXKeeper to automatically upload QSOs to LoTW as you log them. Then periodically invoking DXKeeper's "Sync All" command is all that's required.? + Note: if you're a contester and concerned with optimizing rate, importing your contest log into DXKeeper at the end of each contest and directing DXKeeper to upload your QSOs is the better approach. + Unless you enjoy manual operations, avoid uploading QSOs to LoTW without first importing them into DXKeeper and uploading them to DXKeeper from there. + See? + Similar automation is provided for Club Log, eQSL, and QRZ. ? ? ? 73, ? ? ? ? ? Dave, AA6YQ
?
?
|
Re: AT&T ending email to text on June18
Dave
?
Thanks for the ideas. I'll give them a try. AT&T was getting really bad in delivering the mailed texts sometimes nearly 12hrs late.
?
Thanks
?
JIm ab3cv
|
Re: Unable to upload to LotW
Dave, I proceeded through the instructions to:?
3. click the "Upload to LoTW" button
At that point I received a message that, in part, there were no QSLs to upload:
"TQSL Version 2.7.5 [v2.7.5] Signing using Callsign NU6T, DXCC Entity UNITED STATES OF AMERICA Already Uploaded QSO detected on line 5 CALL: 4E1DX TIME_ON: 174200 QSO_DATE: 20250401 MODE: FT8 BAND: 20M FREQ: 14.074996
Duplicate QSO detected No QSOs to upload Final Status: No QSOs to upload(8)"
It is not clear to me whether the "no QSOs to upload" relates only to the 4E1DX QSO or to the set of 95 QSOs.
I will continue with instruction #4 in an hour or so.
Rich, NU6T
+ AA6YQ comments below
Dave, thank you.? Yes, I show 95 QSLs as a result of the query:? app_dxkeeper_lotw_qsl_sent <> 'Y'
+ With those 95 QSOs present in the Log Page Display, select the Main window's QSL tab, and 1. set the "QSL VIa" panel to LoTW 2. click the "Add All" button; this will populate the QSL Queue with those 95 QSOs 3. click the "Upload to LoTW" button 4. wait an hour (the LoTW Queue duration was recently 18 minutes), and then 4a. click the "Sync LoTW QSOs" button 4b. on the Main window's "Log QSOs" tab, click the Filter panel's LoTW button; do any QSOs appear in the "Log Page Display"? ? ? ? 73, ? ? ? ? ? ? Dave, AA6YQ
|
Re: Unable to upload to LotW
+ AA6YQ comments below
Dave, thank you.? Yes, I show 95 QSLs as a result of the query:? app_dxkeeper_lotw_qsl_sent <> 'Y'
+ With those 95 QSOs present in the Log Page Display, select the Main window's QSL tab, and 1. set the "QSL VIa" panel to LoTW 2. click the "Add All" button; this will populate the QSL Queue with those 95 QSOs 3. click the "Upload to LoTW" button 4. wait an hour (the LoTW Queue duration was recently 18 minutes), and then 4a. click the "Sync LoTW QSOs" button 4b. on the Main window's "Log QSOs" tab, click the Filter panel's LoTW button; do any QSOs appear in the "Log Page Display"? ? ? ? 73, ? ? ? ? ? ? Dave, AA6YQ
|
