Date   

Re: DXView File Type Pop-Up

Dave AA6YQ
 

+ AA6YQ comments below

Every time I booted DXView, I got a pop-up that asked me how I want to open .kml files. It appears that this file type is associated with Google Earth. In the attempt to get rid of the pop-up (which could be cleared by hitting the Escape key), I tried several options in the drop down box in the pop-up. None worked, and each simply has yielded another error screen. How can I stop this from happening? Anyone else had the problem?

+ Has DXView always done this, or is this new behavior? If the latter, when did it start? What changes did you make to your hardware or software around that time?

+ On the "World Map" tab of DXView's Configuration window, is the "Google Earth" panel's Enable box checked?

73,

Dave, AA6YQ


DXView File Type Pop-Up

Jeff, K6JW
 

Every time I booted DXView, I got a pop-up that asked me how I want to open .kml files. It appears that this file type is associated with Google Earth. In the attempt to get rid of the pop-up (which could be cleared by hitting the Escape key), I tried several options in the drop down box in the pop-up. None worked, and each simply has yielded another error screen. How can I stop this from happening? Anyone else had the problem?
--Jeff, K6JW


Re: Odd Propview Behavior with WSJT-X

Hasan Schiers N0AN
 

Sent to wrong place, resent to you directly with attachments
Hasan


On Fri, Feb 28, 2020 at 1:10 PM Hasan Schiers N0AN via Groups.Io <hbasri.schiers6=gmail.com@groups.io> wrote:
I tried two different double-clicks and no change happened in DXView
73, N0AN
Hasan


On Fri, Feb 28, 2020 at 12:35 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

All following tests done on 17m which is not terribly busy
Win10 Pro, Core I5 3.2 GHz, 8GB Ram, Processor load is well below 20% even while decoding FT8. Idle it is about 5%

Now, no matter what I do, DXView does not populate a callsign from WSJT-X when I double click on it. >snip<

+ As a first step, I suggest that you configure WSJT-X and SpotCollector for direct interoperation by reviewing the step-by-step instructions in

<https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect.

+  In the WSJT-X panel on the "Spot Sources" tab of SpotCollector's Configuration window, the Enable and Lookup boxes should both be checked.

+ When properly configured, any change to the contents of the "DX Call" box in the lower-left corner of the WSJT-X Main window should be conveyed (via SpotCollector) to DXView.

+ If that's not the case, then please do the following:

1. on the General tab of Spotcollector's Configuration window, check the "log debugging info" box

2. take an action that changes the contents of the "DX Call" box in the lower-left corner of the WSJT-X Main window

3. if the action succeeds, write down the callsign in the "DX Call" box, and go back to step 2

4. if the action fails,

4a. on the General tab of Spotcollector's Configuration window, uncheck the "log debugging info" box

4b. attach the errorlog.txt file from your SpotCollector folder to an email message that contains the last callsign that was successfully conveyed to DXView, and send the message to me via

aa6yq (at) ambersoft.com

        73,

               Dave, AA6YQ













Re: Odd Propview Behavior with WSJT-X

Hasan Schiers N0AN
 

I tried two different double-clicks and no change happened in DXView
73, N0AN
Hasan


On Fri, Feb 28, 2020 at 12:35 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

All following tests done on 17m which is not terribly busy
Win10 Pro, Core I5 3.2 GHz, 8GB Ram, Processor load is well below 20% even while decoding FT8. Idle it is about 5%

Now, no matter what I do, DXView does not populate a callsign from WSJT-X when I double click on it. >snip<

+ As a first step, I suggest that you configure WSJT-X and SpotCollector for direct interoperation by reviewing the step-by-step instructions in

<https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect.

+  In the WSJT-X panel on the "Spot Sources" tab of SpotCollector's Configuration window, the Enable and Lookup boxes should both be checked.

+ When properly configured, any change to the contents of the "DX Call" box in the lower-left corner of the WSJT-X Main window should be conveyed (via SpotCollector) to DXView.

+ If that's not the case, then please do the following:

1. on the General tab of Spotcollector's Configuration window, check the "log debugging info" box

2. take an action that changes the contents of the "DX Call" box in the lower-left corner of the WSJT-X Main window

3. if the action succeeds, write down the callsign in the "DX Call" box, and go back to step 2

4. if the action fails,

4a. on the General tab of Spotcollector's Configuration window, uncheck the "log debugging info" box

4b. attach the errorlog.txt file from your SpotCollector folder to an email message that contains the last callsign that was successfully conveyed to DXView, and send the message to me via

aa6yq (at) ambersoft.com

        73,

               Dave, AA6YQ













Re: Odd Propview Behavior with WSJT-X

Hasan Schiers N0AN
 

Dave,.
 I will experiment. I sent you a reply with new info.
I found a way to make things work, but it requires JTAlert.
That works every time. Please read that message and let me know if you want me to *undo* my JTAlert setting, and retry the settings in your current message and create a dump file.

73, N0AN
Hasan


On Fri, Feb 28, 2020 at 12:35 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

All following tests done on 17m which is not terribly busy
Win10 Pro, Core I5 3.2 GHz, 8GB Ram, Processor load is well below 20% even while decoding FT8. Idle it is about 5%

Now, no matter what I do, DXView does not populate a callsign from WSJT-X when I double click on it. >snip<

+ As a first step, I suggest that you configure WSJT-X and SpotCollector for direct interoperation by reviewing the step-by-step instructions in

<https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect.

+  In the WSJT-X panel on the "Spot Sources" tab of SpotCollector's Configuration window, the Enable and Lookup boxes should both be checked.

+ When properly configured, any change to the contents of the "DX Call" box in the lower-left corner of the WSJT-X Main window should be conveyed (via SpotCollector) to DXView.

+ If that's not the case, then please do the following:

1. on the General tab of Spotcollector's Configuration window, check the "log debugging info" box

2. take an action that changes the contents of the "DX Call" box in the lower-left corner of the WSJT-X Main window

3. if the action succeeds, write down the callsign in the "DX Call" box, and go back to step 2

4. if the action fails,

4a. on the General tab of Spotcollector's Configuration window, uncheck the "log debugging info" box

4b. attach the errorlog.txt file from your SpotCollector folder to an email message that contains the last callsign that was successfully conveyed to DXView, and send the message to me via

aa6yq (at) ambersoft.com

        73,

               Dave, AA6YQ













Re: Odd Propview Behavior with WSJT-X

Dave AA6YQ
 

+ AA6YQ comments below

All following tests done on 17m which is not terribly busy
Win10 Pro, Core I5 3.2 GHz, 8GB Ram, Processor load is well below 20% even while decoding FT8. Idle it is about 5%

Now, no matter what I do, DXView does not populate a callsign from WSJT-X when I double click on it. >snip<

+ As a first step, I suggest that you configure WSJT-X and SpotCollector for direct interoperation by reviewing the step-by-step instructions in

<https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect.

+ In the WSJT-X panel on the "Spot Sources" tab of SpotCollector's Configuration window, the Enable and Lookup boxes should both be checked.

+ When properly configured, any change to the contents of the "DX Call" box in the lower-left corner of the WSJT-X Main window should be conveyed (via SpotCollector) to DXView.

+ If that's not the case, then please do the following:

1. on the General tab of Spotcollector's Configuration window, check the "log debugging info" box

2. take an action that changes the contents of the "DX Call" box in the lower-left corner of the WSJT-X Main window

3. if the action succeeds, write down the callsign in the "DX Call" box, and go back to step 2

4. if the action fails,

4a. on the General tab of Spotcollector's Configuration window, uncheck the "log debugging info" box

4b. attach the errorlog.txt file from your SpotCollector folder to an email message that contains the last callsign that was successfully conveyed to DXView, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ


Re: Odd Propview Behavior with WSJT-X

Hasan Schiers N0AN
 

All following tests done on 17m which is not terribly busy
Win10 Pro, Core I5 3.2 GHz, 8GB Ram, Processor load is well below 20% even while decoding FT8. Idle it is about 5%

Now, no matter what I do, DXView does not populate a callsign from WSJT-X when I double click on it. I have checked DXV config and "Generate Propagation Forecast" is checked. I have rebooted.

I was running the checks below because of the intermittent performance of DXView and now I'm quite stuck. If we get this working, then what follows is relevant.

BTW, Dave, it does not pick it up reliably. I frequently have to try multiple times of clicking (in X) on a station before Propview picks it up and then hit the SP button. There is often a substantial delay (up to 10  seconds) after double clicking on a call in WSJT-X , before it is picked up by DXView and ultimately fed to Propview, so I can hit the PropView SP button and get a prediction.

I do have all of DXLabs folder excluded from Virus Detection. No MalWare Bytes installed.

For testing: I have the following windows so I can see them:

WSJT-X (referred to as X); JTAlert is running but mimimized
DXView (no map)
Propview (parameter tab, so I can see if it has gotten new DX call from X

Now: double click on callsign:

X populates for calling EA5RT (in TX1 - TX5)
DXView did NOT accept the new call. Sitting on W1YRC where it was
Propview: Still shows United States in Parm Tab

Trying again:
ZB2IF :
X populates
4 sec later, DXView populates
Propview populates as soon as DXview populated
Propview executes proper Prediction upon hitting SP button.

Another try: (only watching DXV to see if it populates)

I6RGQ: 6 seconds to populate DXView
EB3RT: 6 sec
EA4DB: Failed to populate, stayed with EB3RT
CO7MLS: 6 sec
WO1X: Failed to populate
NP4BM: 5 sec
KC1LWH: Failed
...several successes...
K0IEA: Failed
CT1EHX: Failed
YO9HP: 6 sec

So, X always populates. DXView does not....and if DXView doesn't then Propview can't update. (at least that's how it looks to me)

It seems if I double click on a call, very late in the reply cycle, even though it populates X, it does not Populate DXView:

Just tested W0BLE at 10 sec into the seq where I should be tx'ing. it did not "take", but it did show in X TX1 - TX5

At 5 sec it 'took' (by that I mean the call was forwarded successfully to DXV)
At 7 sec it 'took'

Best info I can generate:

The earlier in the reply sequence (immediately after a decode), that I double-click on a call, the more likely it is to populate DXView. It always populates X, no matter how late in the reply sequence I choose to double-click.

Went to 20m (very busy) and now double clicking on X does nothing for DXView. ....and 20m has stopped decoding ...shutting down X, and DXLab, restarting, (not rebooting, that comes next)

Went back to 17m after restarting both programs.
X decodes, DXV doesn't populate. Rebooting.
Now DXView does not populate from WSJT-X double click callsign, no matter what I do. (Go back to top of this message)

73, N0AN
Hasan


On Fri, Feb 28, 2020 at 9:38 AM Dave AA6YQ <aa6yq@...> wrote:
* more AA6YQ comments below

Aha. It also populates the DXView and the PropView AFTER I log a qso (which seems a bit backwards, but now, at least I know how to make it work for me.

* As you point out below, selecting a new callsign in WSJT-X prepares PropView to generate a forecast; you must then click a PropView button to initiate either a short-path or a long-path forecast.

       73,

               Dave, AA6YQ
On Fri, Feb 28, 2020 at 9:07 AM Dave AA6YQ <aa6yq@...> wrote:


        + AA6YQ comments below

        When I double-click on a station in WSJT-X to begin calling them:

        Propview shows the new station info on it's Parameters Tab, but it does not show a new prediction on the Predication Tab UNTIL, I click on the Predict From SP button. Then the graph populates.

        Is this normal behavior?

        + Yes.

                73,

                        Dave, AA6YQ






Re: Odd Propview Behavior with WSJT-X

Dave AA6YQ
 

* more AA6YQ comments below

Aha. It also populates the DXView and the PropView AFTER I log a qso (which seems a bit backwards, but now, at least I know how to make it work for me.

* As you point out below, selecting a new callsign in WSJT-X prepares PropView to generate a forecast; you must then click a PropView button to initiate either a short-path or a long-path forecast.

73,

Dave, AA6YQ

On Fri, Feb 28, 2020 at 9:07 AM Dave AA6YQ <aa6yq@ambersoft.com> wrote:


+ AA6YQ comments below

When I double-click on a station in WSJT-X to begin calling them:

Propview shows the new station info on it's Parameters Tab, but it does not show a new prediction on the Predication Tab UNTIL, I click on the Predict From SP button. Then the graph populates.

Is this normal behavior?

+ Yes.

73,

Dave, AA6YQ


Re: Slow Startup of Apps in Windows 10

Bob Main
 

Dave, that was it.  I also use what Microsoft provides for antivirus and but couldn’t figure out how to exclude the files.  Your instructions told me what I needed.  Of course after entering the files I tried DXView again and it still took about 35 seconds.  Then I thought “Hey dummy reboot”.  After the reboot DXview started in less than 10 seconds.

 

As for the WinWarbler stuff it was the WSIT-X and its associated program that was needed that broke WinWarber.  I never did figure those problems but I did uninstall all three files.  I used to be a network administrator and also worked the Help Desk so not totally dumb about what to do to remove a program.

 

Have a good weekend and happy DXing.

 

73, Bob KB4CL

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of w6de
Sent: Thursday, February 27, 2020 7:01 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Slow Startup of Apps in Windows 10

 

Your slow start-up of the DXLabs aps is likely due to the anti-virus software you are running.  I did see this when I was running Windows-7.  With Win-10 I use the Microsoft supplied Virus protection and do the following:

Enter the virus software and mark each DXLab executable as excluded.  If you are using the virus protection security provided by Windows-10:

Windows-10 doesn’t make it easy to select find the Virus Exclusions.  Be patient and follow all the steps.

Click the windows flag in the lower left corner of the screen, select the gear symbol (Settings),  Select Virus & threat protection,  Select ‘Virus and threat protection settings’ scroll-down and under Exclusions select ‘Manage settings’, in manage scroll-down and under Exclusions select ‘add or remove exclusions’, click “Add an exclusion.  Then one-at-a-time navigate to each DXLab executable and select the appropriate executable.  While you are at it also select any other ham radio executable, e.g., WSJT-X.

I have found in previous versions of Microsoft Windows virus protection to work as expected by just selecting the DXLabs folder, probably has something to due to updating the executable within that folder. Without doing any more exclusion activity.

 

I have no guidance on your WinWarbler issues.

 

Dave, W6DE

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Bob Main
Sent: 27 February, 2020 22:18
To: DXLab@groups.io
Subject: [DXLab] Slow Startup of Apps in Windows 10

 

I finally got the nerve and moved to Windows 10 from Windows 7 back in January.  The changeover with more smoothly than I expected, but I had some issues, mostly between the ears, concerning how Windows 10 worked.  It took a couple days but all is working.  The only thing that I am finding are the programs are taking a while to start, at least longer than with Windows 7.  For example DXView is taking 35 seconds and I don’t think it took that long before.  I know this has been discussed before and there is also probably something in the DXLAb help file, but I am not getting any hits from my searches.  I know this has something to do with the search criteria that I am entering and discovered over the years that without proper terminology the search produces nothing.  I have already looked at the two articles that come up when I do a search for “Windows 10” and followed those directions right after the install.  Can anybody give me some clues how to do the search so that I can get on the right track?

 

For what it is worth I have been using DXLabs for the last 14 years, only big problem I have ever had was when I attempted to install the programs to use F8 with WinWarbler.  I followed the directions in the help file Never had any luck and found that those two programs “broke” what I actually had working in WinWarbler and finally deleted those programs and when I couldn’t figure out what was messed up in WinWarbler I deleted that too.  What was so bad was that I used to be able to do RTTY and PSK and using it and had finally gotten everything working again.  Then I installed the two programs and everything went south, but that is another problem.  Looking at the Windows 10 thing first.

 

Thanks in advance.

 

73, Bob KB4CL


Re: Odd Propview Behavior with WSJT-X

Hasan Schiers N0AN
 

Aha. It also populates the DXView and the PropView AFTER I log a qso (which seems a bit backwards, but now, at least I know how to make it work for me.
Tnx, 73
Hasan


On Fri, Feb 28, 2020 at 9:07 AM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

When I double-click on a station in WSJT-X to begin calling them:

Propview shows the new station info on it's Parameters Tab, but it does not show a new prediction on the Predication Tab UNTIL, I click on the Predict From SP button. Then the graph populates.

Is this normal behavior?

+ Yes.

        73,

                Dave, AA6YQ






Re: Odd Propview Behavior with WSJT-X

Dave AA6YQ
 

+ AA6YQ comments below

When I double-click on a station in WSJT-X to begin calling them:

Propview shows the new station info on it's Parameters Tab, but it does not show a new prediction on the Predication Tab UNTIL, I click on the Predict From SP button. Then the graph populates.

Is this normal behavior?

+ Yes.

73,

Dave, AA6YQ


Odd Propview Behavior with WSJT-X

Hasan Schiers N0AN
 

When I double-click on a station in WSJT-X to begin calling them:

Propview shows the new station info on it's Parameters Tab, but it does not show a new prediction on the Predication Tab UNTIL, I click on the Predict From SP button. Then the graph populates.

Is this normal behavior?
Hasan


Re: DXView's ""Populate override content from entity"

Björn SM7IUN
 

Thank you Dave. 

This was all I really wanted. My apologies for taking the discussion on a detour via the grid locator.

Björn

Den fre 28 feb. 2020 kl 03:25 skrev Dave AA6YQ <aa6yq@...>:

+ AA6YQ comments below

My point is that DXView is providing beam heading and distance for callsigns with an override but no grid specified. Obviously using an approximate location.

I don't see the harm in using the same exact mechanics also for sunset/sunrise information.

Currently the Sun information panel is blank if a grid is not explicitly specified.

+ Björn, I've sent you a new version of DXView that determines the location of a callsign whose override doesn't specify a grid square by using the DXCC entity specified in the override to query the USAP and DXCC databases. This change does not alter the way SpotCollector determines an active station's grid square.

+ Please let me know how it goes.

        73,

              Dave, AA6YQ






Re: Slow Startup of Apps in Windows 10

Buck
 

I found it helpful to prune the Spotcollector database

k4ia, Buck
K3s# 11497
Honor Roll 8B DXCC
EasyWayHamBooks.com

On 2/27/2020 5:42 PM, ND9G Mike wrote:
I would suggest you start here: https://www.dxlabsuite.com/dxlabwiki/ApplicationInteference
That gives you some common culprits to slow operation of the DX Labs applications. There are also some good steps to take to locate the issue.
73,
Mike ND9G
On Thu, Feb 27, 2020 at 4:18 PM Bob Main <bobmain1@windstream.net <mailto:bobmain1@windstream.net>> wrote:
I finally got the nerve and moved to Windows 10 from Windows 7 back
in January.  The changeover with more smoothly than I expected, but
I had some issues, mostly between the ears, concerning how Windows
10 worked.  It took a couple days but all is working.  The only
thing that I am finding are the programs are taking a while to
start, at least longer than with Windows 7.  For example DXView is
taking 35 seconds and I don’t think it took that long before.  I
know this has been discussed before and there is also probably
something in the DXLAb help file, but I am not getting any hits from
my searches.  I know this has something to do with the search
criteria that I am entering and discovered over the years that
without proper terminology the search produces nothing.  I have
already looked at the two articles that come up when I do a search
for “Windows 10” and followed those directions right after the
install.  Can anybody give me some clues how to do the search so
that I can get on the right track?____
__ __
For what it is worth I have been using DXLabs for the last 14 years,
only big problem I have ever had was when I attempted to install the
programs to use F8 with WinWarbler.  I followed the directions in
the help file Never had any luck and found that those two programs
“broke” what I actually had working in WinWarbler and finally
deleted those programs and when I couldn’t figure out what was
messed up in WinWarbler I deleted that too.  What was so bad was
that I used to be able to do RTTY and PSK and using it and had
finally gotten everything working again.  Then I installed the two
programs and everything went south, but that is another problem. Looking at the Windows 10 thing first.____
__ __
Thanks in advance.____
__ __
73, Bob KB4CL____


Re: Slow Startup of Apps in Windows 10

Bob Main
 

I did run the "uninstall a program" to remove the programs. Otherwise you
have all sort of junk left in the registry that could cause problems.

73, Bob KB4CL

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Thursday, February 27, 2020 7:22 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Slow Startup of Apps in Windows 10

+ AA6YQ comments below

I finally got the nerve and moved to Windows 10 from Windows 7 back in
January. The changeover with more smoothly than I expected,
but I had some issues, mostly between the ears, concerning how Windows 10
worked. It took a couple days but all is working. The
only thing that I am finding are the programs are taking a while to start,
at least longer than with Windows 7. For example DXView
is taking 35 seconds and I don't think it took that long before. I know
this has been discussed before and there is also probably
something in the DXLAb help file, but I am not getting any hits from my
searches. I know this has something to do with the search
criteria that I am entering and discovered over the years that without
proper terminology the search produces nothing. I have
already looked at the two articles that come up when I do a search for
"Windows 10" and followed those directions right after the
install. Can anybody give me some clues how to do the search so that I can
get on the right track?

+ I can remember no case of "slow application startup" over the past 19
years that wasn't the result of interference from another
application.

+ The culprit is almost always a misconfigured or incompetent anti-malware
application.

+ A few other applications have been found to interfere; they are listed
here:

<https://www.dxlabsuite.com/dxlabwiki/ApplicationInteference>

+ Reminder: never delete an installed Windows application before first
directing Windows to uninstall it. You can determine if an
application is installed by running the "Uninstall a program" applet
accessible via the Windows Control Panel; this applet displays
a list of installed programs.

73,

Dave, AA6YQ


Re: DXView's ""Populate override content from entity"

Dave AA6YQ
 

+ AA6YQ comments below

My point is that DXView is providing beam heading and distance for callsigns with an override but no grid specified. Obviously using an approximate location.

I don't see the harm in using the same exact mechanics also for sunset/sunrise information.

Currently the Sun information panel is blank if a grid is not explicitly specified.

+ Björn, I've sent you a new version of DXView that determines the location of a callsign whose override doesn't specify a grid square by using the DXCC entity specified in the override to query the USAP and DXCC databases. This change does not alter the way SpotCollector determines an active station's grid square.

+ Please let me know how it goes.

73,

Dave, AA6YQ


Re: Slow Startup of Apps in Windows 10

Dave AA6YQ
 

+ AA6YQ comments below

I finally got the nerve and moved to Windows 10 from Windows 7 back in January. The changeover with more smoothly than I expected,
but I had some issues, mostly between the ears, concerning how Windows 10 worked. It took a couple days but all is working. The
only thing that I am finding are the programs are taking a while to start, at least longer than with Windows 7. For example DXView
is taking 35 seconds and I don't think it took that long before. I know this has been discussed before and there is also probably
something in the DXLAb help file, but I am not getting any hits from my searches. I know this has something to do with the search
criteria that I am entering and discovered over the years that without proper terminology the search produces nothing. I have
already looked at the two articles that come up when I do a search for "Windows 10" and followed those directions right after the
install. Can anybody give me some clues how to do the search so that I can get on the right track?

+ I can remember no case of "slow application startup" over the past 19 years that wasn't the result of interference from another
application.

+ The culprit is almost always a misconfigured or incompetent anti-malware application.

+ A few other applications have been found to interfere; they are listed here:

<https://www.dxlabsuite.com/dxlabwiki/ApplicationInteference>

+ Reminder: never delete an installed Windows application before first directing Windows to uninstall it. You can determine if an
application is installed by running the "Uninstall a program" applet accessible via the Windows Control Panel; this applet displays
a list of installed programs.

73,

Dave, AA6YQ


Re: Slow Startup of Apps in Windows 10

w6de
 

Your slow start-up of the DXLabs aps is likely due to the anti-virus software you are running.  I did see this when I was running Windows-7.  With Win-10 I use the Microsoft supplied Virus protection and do the following:

Enter the virus software and mark each DXLab executable as excluded.  If you are using the virus protection security provided by Windows-10:

Windows-10 doesn’t make it easy to select find the Virus Exclusions.  Be patient and follow all the steps.

Click the windows flag in the lower left corner of the screen, select the gear symbol (Settings),  Select Virus & threat protection,  Select ‘Virus and threat protection settings’ scroll-down and under Exclusions select ‘Manage settings’, in manage scroll-down and under Exclusions select ‘add or remove exclusions’, click “Add an exclusion.  Then one-at-a-time navigate to each DXLab executable and select the appropriate executable.  While you are at it also select any other ham radio executable, e.g., WSJT-X.

I have found in previous versions of Microsoft Windows virus protection to work as expected by just selecting the DXLabs folder, probably has something to due to updating the executable within that folder. Without doing any more exclusion activity.

 

I have no guidance on your WinWarbler issues.

 

Dave, W6DE

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Bob Main
Sent: 27 February, 2020 22:18
To: DXLab@groups.io
Subject: [DXLab] Slow Startup of Apps in Windows 10

 

I finally got the nerve and moved to Windows 10 from Windows 7 back in January.  The changeover with more smoothly than I expected, but I had some issues, mostly between the ears, concerning how Windows 10 worked.  It took a couple days but all is working.  The only thing that I am finding are the programs are taking a while to start, at least longer than with Windows 7.  For example DXView is taking 35 seconds and I don’t think it took that long before.  I know this has been discussed before and there is also probably something in the DXLAb help file, but I am not getting any hits from my searches.  I know this has something to do with the search criteria that I am entering and discovered over the years that without proper terminology the search produces nothing.  I have already looked at the two articles that come up when I do a search for “Windows 10” and followed those directions right after the install.  Can anybody give me some clues how to do the search so that I can get on the right track?

 

For what it is worth I have been using DXLabs for the last 14 years, only big problem I have ever had was when I attempted to install the programs to use F8 with WinWarbler.  I followed the directions in the help file Never had any luck and found that those two programs “broke” what I actually had working in WinWarbler and finally deleted those programs and when I couldn’t figure out what was messed up in WinWarbler I deleted that too.  What was so bad was that I used to be able to do RTTY and PSK and using it and had finally gotten everything working again.  Then I installed the two programs and everything went south, but that is another problem.  Looking at the Windows 10 thing first.

 

Thanks in advance.

 

73, Bob KB4CL


Re: Slow Startup of Apps in Windows 10

Bob Main
 

Thanks Mike, I’ll take a look at it.

 

73, Bob KB4CL

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of ND9G Mike
Sent: Thursday, February 27, 2020 5:42 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Slow Startup of Apps in Windows 10

 

I would suggest you start here:  https://www.dxlabsuite.com/dxlabwiki/ApplicationInteference 

 

That gives you some common culprits to slow operation of the DX Labs applications. There are also some good steps to take to locate the issue.

 

73,

Mike ND9G

 

 

On Thu, Feb 27, 2020 at 4:18 PM Bob Main <bobmain1@...> wrote:

I finally got the nerve and moved to Windows 10 from Windows 7 back in January.  The changeover with more smoothly than I expected, but I had some issues, mostly between the ears, concerning how Windows 10 worked.  It took a couple days but all is working.  The only thing that I am finding are the programs are taking a while to start, at least longer than with Windows 7.  For example DXView is taking 35 seconds and I don’t think it took that long before.  I know this has been discussed before and there is also probably something in the DXLAb help file, but I am not getting any hits from my searches.  I know this has something to do with the search criteria that I am entering and discovered over the years that without proper terminology the search produces nothing.  I have already looked at the two articles that come up when I do a search for “Windows 10” and followed those directions right after the install.  Can anybody give me some clues how to do the search so that I can get on the right track?

 

For what it is worth I have been using DXLabs for the last 14 years, only big problem I have ever had was when I attempted to install the programs to use F8 with WinWarbler.  I followed the directions in the help file Never had any luck and found that those two programs “broke” what I actually had working in WinWarbler and finally deleted those programs and when I couldn’t figure out what was messed up in WinWarbler I deleted that too.  What was so bad was that I used to be able to do RTTY and PSK and using it and had finally gotten everything working again.  Then I installed the two programs and everything went south, but that is another problem.  Looking at the Windows 10 thing first.

 

Thanks in advance.

 

73, Bob KB4CL


Re: Slow Startup of Apps in Windows 10

Bob Main
 

Thanks Chuck.  I usually leave my computer on all the time, that way I don’t have to wait for it to boot up.  So maybe that might explain it except I left it on when I had Windows 7 too.

 

73, Bob KB4CL

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Chuck, WS1L
Sent: Thursday, February 27, 2020 5:36 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Slow Startup of Apps in Windows 10

 

I've seen that, it seems to get longer depending on how long my PC has been running since it was last rebooted.  I've looked at the error logging and really can't pin it down to anything in particular, I was suspecting DDE but that didn't seem to be a factor.  For now I've been unable to investigate further but I think this is the 3rd report so it is something...

 

73 de Chuck, WS1L

 

On Thu, Feb 27, 2020 at 4:18 PM Bob Main <bobmain1@...> wrote:

I finally got the nerve and moved to Windows 10 from Windows 7 back in January.  The changeover with more smoothly than I expected, but I had some issues, mostly between the ears, concerning how Windows 10 worked.  It took a couple days but all is working.  The only thing that I am finding are the programs are taking a while to start, at least longer than with Windows 7.  For example DXView is taking 35 seconds and I don’t think it took that long before.  I know this has been discussed before and there is also probably something in the DXLAb help file, but I am not getting any hits from my searches.  I know this has something to do with the search criteria that I am entering and discovered over the years that without proper terminology the search produces nothing.  I have already looked at the two articles that come up when I do a search for “Windows 10” and followed those directions right after the install.  Can anybody give me some clues how to do the search so that I can get on the right track?

 

For what it is worth I have been using DXLabs for the last 14 years, only big problem I have ever had was when I attempted to install the programs to use F8 with WinWarbler.  I followed the directions in the help file Never had any luck and found that those two programs “broke” what I actually had working in WinWarbler and finally deleted those programs and when I couldn’t figure out what was messed up in WinWarbler I deleted that too.  What was so bad was that I used to be able to do RTTY and PSK and using it and had finally gotten everything working again.  Then I installed the two programs and everything went south, but that is another problem.  Looking at the Windows 10 thing first.

 

Thanks in advance.

 

73, Bob KB4CL


 

--

 

 

===================

Chuck Chandler

===================

11241 - 11260 of 202756