Date   

Re: WARNING about Windows 11

Peter Laws / N5UWY
 

On Mon, Nov 1, 2021 at 8:46 AM g4wjs <bill.8@...> wrote:
Gil,

that may be an over-reaction. BitLocker has been around since Windows 8 and is a good thing if you want to protect your personal data. I believe MS announced some time ago that it would be enabled by default for Windows 11. What matters is where the decryption and recovery keys are stored. If I understand correctly, if you use a microsoft
An over-reaction? That *never* happens! :-D

My company required disk encryption on my company-supplied MacBook Pro
several years ago. Turned it on, OS X did it's thing, and that was
that. Never noticed it since. No performance impact that I can
detect. This discussion did cause me to realize that I really don't
know where the keys are!! :-D I suspect they are tied to my Apple ID
(same as having a M$ account) but I will google here in a bit to see.
I should also check to see if it also encrypts my TimeMachine backup
disk and images. USB keys are becoming an issue in real IT
environments and I guess I need to educate myself on that as well - I
do know that none of the USB drive encryption services that are
included in MacOS or Windows are cross-platform.

Hopefully, Bitlocker works as smoothly/silently as Apples unbranded
disk encryption. Good luck! :-D

--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!


Re: DXKeeper Filter and Batch Modify ?

W9MR Mike
 

Yes, that is correct. It will only update the QSOs displayed on the filtered log.

It is highly recommended that you make a backup of your log database before doing en masse updates.

73,
Mike ND9G


On Mon, Nov 1, 2021 at 9:53 AM w2eck <eckerpw@...> wrote:
Read some older postings on subject, but want to be sure.
If I do a UTC filter of my log and generate a log page of QSO's in  the desired time range, then use the Modify QSOs in Log Page Display- to add a comment to each, these comments will only be added to the "filtered" page ?

73 Paul w2eck


Re: DXKeeper Filter and Batch Modify ?

Dave AA6YQ
 

+ AA6YQ comments below
Read some older postings on subject, but want to be sure.
If I do a UTC filter of my log and generate a log page of QSO's in  the desired time range, then use the Modify QSOs in Log Page Display- to add a comment to each, these comments will only be added to the "filtered" page ?

+ On the lower section of its Main window's "Log QSOs" tab, DXKeeper provides the "Log Page Display", which can display all of your logged QSOs, or a subset of your logged QSOs. The process of determining which subset of your logged QSOs is present in the "Log Page Display" is referred to as "filtering". 

+ Action taken in the "Modify QSOs" panel on the "Advanced Sorts, Filters, and Modifiers" window is only applied to the subset of QSOs present in the "Log Page Display". See

https://www.dxlabsuite.com/dxlabwiki/QSOModifying

+ Don't skip step 1 !

      73,

             Dave, AA6YQ        

 


Re: Skimmer-to-Commander with Commander - strange behaviour

Dave AA6YQ
 

+ AA6YQ comments below
unfortunately I did not identify, which version of Commander I was using when I reported the problem in interoperation of my FT5000 with CW Skimmer/Skimmer--to-Commander and Commander last year. It probably was Commander 14.7.1.

So I have done some (hopefully exhaustive) testing with Commander 12.1.8 (used by W3OA when testing his program), Commander 14.5.8 (oldest version still on my PC), Commander 14.6.2 and Commander 14.6.5.
Modes of relevance are CW-Split (find a listening frequency in a CW pile-up) and RTTY-Split (find a free spots in an RTTY pile-up).
I have put the details of the test into an EXCEL file, which I will send to AA6YQ(at)ambersoft.com and also to Dick, W3OA.

Summary:
Commander 12.1.8 / 14.5.8 and 14.6.2 and Skimmer-to-Commander show identical behaviour:

Whichever mode the FT5000 was set to before switching to CW-Split or RTTY-Split
Clicking the Skimmer waterfall QSYs VFO-B to the click-frequency without changing VFO-B mode - FINE

When the FT-5000 is in PKT-Split  (e.g for WSJT or PSK) regardless of the previously used mode
Clicking the Skimmer waterfall QSYs VFO-B to the click-frequency and changes VFO-A and VFO-B mode to USB.
As it makes no sense to use CW Skimmer/Skimmer-to-Commander in PSK or WSJT  this misbehaviour is irrelevant..

The problem comes up when Skimmer-to-Commander is used with Commander 14.6.5:

When the FT5000 is commanded from SSB to CW-Split and PKT-Split or RTTY-Split have NOT been used before
Clicking the Skimmer waterfall QSYs VFO-B to the click-frequency without changing VFO-B mode

When the FT5000 is commanded from SSB or CW to RTTY-Split and PKT-Split has NOT been used before
Clicking the Skimmer waterfall QSYs VFO-B to the click-frequency without changing VFO-B mode

When the FT5000 is commanded from RTTY-Split  to CW-Split and PKT-Split has NOT been used before
Clicking the Skimmer waterfall QSYs VFO-B to the click-frequency and VFO-B mode is changed from CW to RTTY

When the FT5000 is commanded to CW-Split or RTTY-Split and PKT-Split has been used before at any time
Clicking the Skimmer waterfall QSYs VFO-B to the click-frequency and VFO-B mode is changed CW/RTTY to USB

So reverting to Commander 14.6.2, which more than satifies my needs, will solve my problem.

Hope this helps.

+ Wolf, I investigated this issue when you first raised it two years ago. My recommendation then was

"It's clear from your description above that incorrect commands are being sent to the radio while "CW Skimmer to Commander" is running. I do not have the source code to this application. Thus I suggest that you report the above behavior to its author Dick W3OA; I will be happy to assist Dick if he needs help."

https://groups.io/g/DXLab/message/196970

+ Your recitation above does not change this recommendation.

      73,

              Dave, AA6YQ

 


Re: Spotcollector 8.9.2 and Telnet Clusters

Dave AA6YQ
 

+ AA6YQ comments below

here is some additional info:

1. In between I have seen that the prefilter was enabled. After disabling it 2m-spots are displayed as well.

But:

2. After having rbn.dr4.w.de activated in WinTelnet-X no spot of rbn.dr4w.de which is still shown in SC's telnet cluster window is displayed in SC's database display window. If I disable rbn.dr4w.de in WinTelnet-X then all the spots displayed in the telnet cluster window are shown in the database display window as well.

3. If I configure the telnet cluster connection using WinTelnet-X  then the connection is ok and all spots of my local FT8 skimmer are displayed in SC's telnet cluster window but - as before - not any spot in SC's database display window.

+ Juergen, I don't know anything about SparkSDR2DXC or WinTelnet-X.If a source of spots conforms to the telnet DXCluster protocol, then SpotCollector will interact with it. Note that

1. SpotCollector will ignore incoming spots that are older than the age you've specified in the "Maximum age of valid incoming spots" on SpotCollector's Configuration window's "Spot Database" tab

2. Incoming spots from skimmers will be ignored if you have the "Discard spots from spotting station callsigns ending in -#" or "Discard spots from spotting station callsigns ending in -@" box checked on the Configuration window's Special Callsigns tab.

      73,

            Dave, AA6YQ


DXKeeper Filter and Batch Modify ?

w2eck
 

Read some older postings on subject, but want to be sure.
If I do a UTC filter of my log and generate a log page of QSO's in  the desired time range, then use the Modify QSOs in Log Page Display- to add a comment to each, these comments will only be added to the "filtered" page ?

73 Paul w2eck


Re: WARNING about Windows 11

g4wjs
 

On 01/11/2021 12:45, Gilbert Baron W0MN wrote:

Microsoft has decided to automatically turn on data encryption in Windows! 11. Not sure if on home but I read an article by the  reporter on Minneapolis paper that it did on his home edition. THEY DO NOT TELL YOU WHERE THE KEY IS OR WHAT IT IS. If your system fails you have just lost your data. Go to settings and TURN IT OFF

.

Outlook LT Gil W0MN

Gil,

that may be an over-reaction. BitLocker has been around since Windows 8 and is a good thing if you want to protect your personal data. I believe MS announced some time ago that it would be enabled by default for Windows 11. What matters is where the decryption and recovery keys are stored. If I understand correctly, if you use a microsoft account (MSA) to log in to your PC then the keys are stored there, but if you PC has an enabled TPM chip then they are stored there thus allowing you to operate without being tied to a MSA. I have not researched this in depth so may be slight off on the details.

Is there a Windows 11 Home edition? Home editions of 8, 8.1, and 10 did not have BitLocker available by default.


--
73

Bill

G4WJS.


Re: WARNING about Windows 11

BILL KENNAMER
 

Where under settings do you find this?

Hard to stay ahead of what Microsoft is doing to you that you don't know about.

K5FUV

On Monday, November 1, 2021, 07:45:34 AM CDT, Gilbert Baron W0MN <w0mn00@...> wrote:


Microsoft has decided to automatically turn on data encryption in Windows! 11. Not sure if on home but I read an article by the  reporter on Minneapolis paper that it did on his home edition. THEY DO NOT TELL YOU WHERE THE KEY IS OR WHAT IT IS. If your system fails you have just lost your data. Go to settings and TURN IT OFF

.

Outlook LT Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

 

 


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


WARNING about Windows 11

Gilbert Baron W0MN
 

Microsoft has decided to automatically turn on data encryption in Windows! 11. Not sure if on home but I read an article by the  reporter on Minneapolis paper that it did on his home edition. THEY DO NOT TELL YOU WHERE THE KEY IS OR WHAT IT IS. If your system fails you have just lost your data. Go to settings and TURN IT OFF

.

Outlook LT Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

 

 


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


Re: Spotcollector 8.9.2 and Telnet Clusters

dl8le
 

Hello,

here is some additional info:

1. In between I have seen that the prefilter was enabled. After disabling it 2m-spots are displayed as well.

But:

2. After having rbn.dr4.w.de activated in WinTelnet-X no spot of rbn.dr4w.de which is still shown in SC's telnet cluster window is displayed in SC's database display window. If I disable rbn.dr4w.de in WinTelnet-X then all the spots displayed in the telnet cluster window are shown in the database display window as well.

3. If I configure the telnet cluster connection using WinTelnet-X  then the connection is ok and all spots of my local FT8 skimmer are displayed in SC's telnet cluster window but - as before - not any spot in SC's database display window.

73

Juergen, DL8LE


Skimmer-to-Commander with Commander - strange behaviour

Wolf, DK1FW
 

Dave,

unfortunately I did not identify, which version of Commander I was using when I reported the problem in interoperation of my FT5000 with CW Skimmer/Skimmer--to-Commander and Commander last year. It probably was Commander 14.7.1.

So I have done some (hopefully exhaustive) testing with Commander 12.1.8 (used by W3OA when testing his program), Commander 14.5.8 (oldest version still on my PC), Commander 14.6.2 and Commander 14.6.5.
Modes of relevance are CW-Split (find a listening frequency in a CW pile-up) and RTTY-Split (find a free spots in an RTTY pile-up).
I have put the details of the test into an EXCEL file, which I will send to AA6YQ(at)ambersoft.com and also to Dick, W3OA.

Summary:
Commander 12.1.8 / 14.5.8 and 14.6.2 and Skimmer-to-Commander show identical behaviour:

Whichever mode the FT5000 was set to before switching to CW-Split or RTTY-Split
Clicking the Skimmer waterfall QSYs VFO-B to the click-frequency without changing VFO-B mode - FINE

When the FT-5000 is in PKT-Split  (e.g for WSJT or PSK) regardless of the previously used mode
Clicking the Skimmer waterfall QSYs VFO-B to the click-frequency and changes VFO-A and VFO-B mode to USB.
As it makes no sense to use CW Skimmer/Skimmer-to-Commander in PSK or WSJT  this misbehaviour is irrelevant..

The problem comes up when Skimmer-to-Commander is used with Commander 14.6.5:

When the FT5000 is commanded from SSB to CW-Split and PKT-Split or RTTY-Split have NOT been used before
Clicking the Skimmer waterfall QSYs VFO-B to the click-frequency without changing VFO-B mode

When the FT5000 is commanded from SSB or CW to RTTY-Split and PKT-Split has NOT been used before
Clicking the Skimmer waterfall QSYs VFO-B to the click-frequency without changing VFO-B mode

When the FT5000 is commanded from RTTY-Split  to CW-Split and PKT-Split has NOT been used before
Clicking the Skimmer waterfall QSYs VFO-B to the click-frequency and VFO-B mode is changed from CW to RTTY

When the FT5000 is commanded to CW-Split or RTTY-Split and PKT-Split has been used before at any time
Clicking the Skimmer waterfall QSYs VFO-B to the click-frequency and VFO-B mode is changed CW/RTTY to USB

So reverting to Commander 14.6.2, which more than satifies my needs, will solve my problem.

Hope this helps.

73 de Wolf, DK1FW


Spotcollector 8.9.2 and Telnet Clusters

dl8le
 

Hello,

I have following problems with my present SC setup (modes and bands, origin etc set to ALL):

1. My telnet cluster rbn.dr4w.de (port 7300) shows all the FT8 spots in SC's telnet cluster window but only those from 160 to 10 m are displayed in SC's database display window, the spot on 144.174 Mhz doesn't show up even though it is shown in the telnet cluster window.

2.My FT8 skimmer using SparkSDR2DXC together with Wintelnet-X (192.168.2.133, port 7373) shows all the spots in SC's telnet cluster window, i.e. there is no problem with the connection, but none is shown in SC's database display window (remark: I have used the same set up together with N1MM+'s bandmaps and there is no problem).

Question: What settings are necessary because there is not any restriction in modes, bands, origin etc.? There shouldn't be any problem with computer resources either because even when I enable the local FT8 skimmer only nothing is displayed in the database display window, when I filter the spots on rbn.dr4w.de to show 2m only (all other telnet clusters disabled) the spots are still displayed in the telnet cluster window but not in the database display window

Some advice would be very nice.

73

Juergen, DL8LE


Re: Question about SpotCollector performance [8.9.2]

Rick
 

Thanks, Dave, to you and Joe W4TV. I'll review the references once again.

Your comment re Chrome is interesting; I use Firefox and have noticed the same thing. "Obnoxious RAM greed." ;<) However, I run only "ham apps" on this computer. I should also have noted that I encounter these issues during non-contest periods -- daily actually.

I'll work on it. Thanks again!

R

On Sunday, October 31, 2021, 09:04:14 PM EDT, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ comments below

See <http://www.dxlabsuite.com/dxlabwiki/GettingStarted> for information on optimizing SC Performance by limiting database size, etc.

+ The article to which Joe W4TV refers is here:

https://www.dxlabsuite.com/dxlabwiki/OptimizeSCPerformance

+ To replicate a "high-spot rate environment" before the next major contest, you can temporarily use the Remote Beacon Network as a spot source:

http://www.reversebeacon.net/

+ Telnet host addresses and ports are given here:

http://www.reversebeacon.net/pages/Telnet+servers+30

+ Performance will suffer if SpotCollector is constantly competing with apps that consume a lot of RAM. Google's Chrome seems to have gotten rather RAM-greedy over the past year; I recently caught one Chrome process using a gigabyte of RAM! Consider baselining SpotCollector's performance after rebooting Windows with no applications but SpotCollector running; then compare this performance with that in your normal operating environment.

    73,

                Dave, AA6YQ







Re: Using IP for K4 CAT control

Dave AA6YQ
 

+ AA6YQ comments below
Is there a way to have DX commander use a K4's IP address for CAT control instead of a serial port.

+ No, that won't be implemented until Elecraft can loan me a K4.

 

 In testing Hamlib's support for this, I see a significant decrease in response time.  

+ Response time as measured between which events, exactly?

     73,

              Dave, AA6YQ


Using IP for K4 CAT control

Joe, KO8V
 

Is there a way to have DX commander use a K4's IP address for CAT control instead of a serial port.  In testing Hamlib's support for this, I see a significant decrease in response time.  In hamlib, I just have to set the serial port to the IP of the radio followed by :9200.  Plus it gets us closer to being able to dump the USB connections in favor of Ethernet.
 
--
73
Joe, KO8V


Re: Question about SpotCollector performance [8.9.2]

Dave AA6YQ
 

+ AA6YQ comments below

See <http://www.dxlabsuite.com/dxlabwiki/GettingStarted> for information on optimizing SC Performance by limiting database size, etc.

+ The article to which Joe W4TV refers is here:

https://www.dxlabsuite.com/dxlabwiki/OptimizeSCPerformance

+ To replicate a "high-spot rate environment" before the next major contest, you can temporarily use the Remote Beacon Network as a spot source:

http://www.reversebeacon.net/

+ Telnet host addresses and ports are given here:

http://www.reversebeacon.net/pages/Telnet+servers+30

+ Performance will suffer if SpotCollector is constantly competing with apps that consume a lot of RAM. Google's Chrome seems to have gotten rather RAM-greedy over the past year; I recently caught one Chrome process using a gigabyte of RAM! Consider baselining SpotCollector's performance after rebooting Windows with no applications but SpotCollector running; then compare this performance with that in your normal operating environment.

73,

Dave, AA6YQ


Re: Question about SpotCollector performance [8.9.2]

Joe Subich, W4TV
 

On 2021-10-31 8:02 PM, Rick via groups.io wrote:
I'm finding SC is not working well for me -- I'm guessing I have a
setting or two screwed up. Here's what I see:
- The "Q" often exceeds 400, sometimes 500.
You have identified your own problem .... Q > 400 or 500 indicates a
backlog of 400 - 500 spots. I saw the same thing regularly this
weekend with all the SSB spots for CQWW. As soon as the clock hit
00:00, the backlog of spots dropped to a more normal 15-30.

The computer is an i7 with a good SSD and 16GB of RAM. Not extraordinary but at one time it was more than sufficient.
Same here - except 32 GB of RAM. Still, using Resource Monitor
one "CPU" (thread) is maxed out at 100% when SC has unprocessed
spots in the queue. SpotCollector uses an average of 13-15% of
CPU resources on a 60 second basis.

See <http://www.dxlabsuite.com/dxlabwiki/GettingStarted> for information
on optimizing SC Performance by limiting database size, etc.

73,

... Joe, W4TV


On 2021-10-31 8:02 PM, Rick via groups.io wrote:
I'm finding SC is not working well for me -- I'm guessing I have a setting or two screwed up.  Here's what I see:
- The "Q" often exceeds 400, sometimes 500.  The "Q" often turns red.  The "Q" always counts down slowly.
- This is true with a single source in operation (e.g., VE7CC or AE5E -- both of which include FT4/8 spots.)  It gets worse with multiple sources in use.
- When I hear a voice announcement of a needed band slot or mode the spoken characters are sometimes separated by long spaces of silence.
- In order to shut SC down a ctrl/alt/del is often required -- rarely can one "x" out of it.
- Changes made to SC while running, e.g., deleting a nuisance/bad spot, often do not work as the software does not respond.
Essentially it's pretty much unusable.
The computer is an i7 with a good SSD and 16GB of RAM.  Not extraordinary but at one time it was more than sufficient.
What I've done to work with this:
- Disabled virus checking after finding setting the software as "safe" did not help.
- Checked the help at http://www.dxlabsuite.com/spotcollector/Help/index.htm and elsewhere.
- Checked task manager to see what resources SC is using (about 7-11% CPU; 29.5MB RAM, about 3-5 MB/sec disk I/O, and negligible network).
- Reviewed settings at Config -> Spot Database (2 days max age; 20 min max separation in time; 2KHz max freq sep; process priority set to high; maintain DXCC entity-band-mode fields not checked.
- Enabled and disabled pre-filtering (normally in use with several bands ignored, several modes ignored and all spots originating from outside NA ignored [something I would rather not do.])
- Considered "What changed" -- nothing I can identify.
The other DXLab products seem to be working fine.
I'll appreciate any suggestions!  :<)
Rick


Question about SpotCollector performance [8.9.2]

Rick
 

I'm finding SC is not working well for me -- I'm guessing I have a setting or two screwed up.  Here's what I see:
- The "Q" often exceeds 400, sometimes 500.  The "Q" often turns red.  The "Q" always counts down slowly.
- This is true with a single source in operation (e.g., VE7CC or AE5E -- both of which include FT4/8 spots.)  It gets worse with multiple sources in use.
- When I hear a voice announcement of a needed band slot or mode the spoken characters are sometimes separated by long spaces of silence.
- In order to shut SC down a ctrl/alt/del is often required -- rarely can one "x" out of it.
- Changes made to SC while running, e.g., deleting a nuisance/bad spot, often do not work as the software does not respond.
Essentially it's pretty much unusable.

The computer is an i7 with a good SSD and 16GB of RAM.  Not extraordinary but at one time it was more than sufficient.

What I've done to work with this:
- Disabled virus checking after finding setting the software as "safe" did not help.
- Checked the help at http://www.dxlabsuite.com/spotcollector/Help/index.htm and elsewhere.
- Checked task manager to see what resources SC is using (about 7-11% CPU; 29.5MB RAM, about 3-5 MB/sec disk I/O, and negligible network).
- Reviewed settings at Config -> Spot Database (2 days max age; 20 min max separation in time; 2KHz max freq sep; process priority set to high; maintain DXCC entity-band-mode fields not checked.
- Enabled and disabled pre-filtering (normally in use with several bands ignored, several modes ignored and all spots originating from outside NA ignored [something I would rather not do.])
- Considered "What changed" -- nothing I can identify.

The other DXLab products seem to be working fine

I'll appreciate any suggestions!  :<)

Rick


updated eQSL AG and LoTW databases are available...

Dave AA6YQ
 

...via the Databases tab of DXView's Configuration window.

73,

Dave, AA6YQ


Re: Spot Collector Hiccup ... ??

Dave AA6YQ
 

+ AA6YQ comments below

Tnx and I've been putzing with those as well. I'll get a combination that makes sense for me.

Reason for my approach is that I have very detailed filters set in CC User and am using discreet SSIDs for the two clusters I've always used.

+ The only reason to connect SpotCollector to CC User is to make your PC run slower by unnecessarily consuming CPU cycles and RAM; if you're running SpotCollector, CC User provides no incremental value.

Ergo ... all the band, mode Cont, etc.. are pre-selected before being ported into Spot Collector.

+ If you're a DXer, pre-filtering spots -- with CC User or SpotCollector -- is generally a bad idea. The whole point of SpotCollector is to capture the activity of all active stations, and use this information to deduce the operating patterns of needed DX stations, and to identify band openings between your QTH and those needed DX stations. The information in spots discarded by pre-filtering is lost forever, whereas the information in your Spot Database is only discarded when its pruned - presumably after it's no longer of value.

+ Suppose you don't enjoy SSB QSOs, or perhaps you're already at the top of the DXCC Phone Honor Roll. Wouldn't it make sense to configure the pre-filter to ignore incoming spots of stations operating in SSB? Absolutely not! For example, when I was chasing ZC4GR in my effort to confirm every DXCC entity in FT8, I wanted to know when stations located within 500 miles of my QTH were spotting stations in ZC4, 5B4, TA, OD, 4X, and SU -- a question easily answered by this SQL filter:

(DXCCPrefix in ('ZC4','5B4','TA','OD','4X','SU')) and (ODX<500)

+ Had I configured SpotCollector to pre-filter SSB spots, I'd have been missing information critical to my query! Here was the "propagation view" of SpotCollector's Spot Database after applying the filter above:

https://www.dxlabsuite.com/spotcollector/nrMe-nrZC4.jpg

+ Combined with an understanding of ZC4GR's operating pattern revealed by the Callsign filter, I focused on 20m from 20Z to 23Z - and worked ZC4GR around 2030Z a few days later.

Seems like I'm doing a 'double' filtering, but mainly it is about me better understanding how SC works.

+ For DXers, SpotCollector is by far the most useful component of the DXLab Suite. It's also the most unique, as (to my knowledge) no other amateur radio application provides the equivalent of a Spot Database, and the ability to filter and view it in different ways. If you want to effectively use SpotCollector, take the time to understand it by reviewing

https://www.dxlabsuite.com/dxlabwiki/CollectingSpots

+ This video of my May 2021 presentation to the International DX Convention includes a review of SpotCollector's data architecture, and the above ZC4GR example of its use:

https://www.youtube.com/watch?v=scnHv5aGYhM&t=63s

73,

Dave, AA6YQ

4701 - 4720 of 208811