开云体育

+ 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%

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,

* 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

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

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

+ 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

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

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@...>:

I found it helpful to prune the Spotcollector database k4ia, Buck K3s# 11497 Honor Roll 8B DXCC EasyWayHamBooks.com

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

+ 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

+ 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

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

Thanks Mike, I’ll take a look at it. 73, Bob KB4CL Sent: Thursday, February 27, 2020 5:42 PM To: [email protected] Subject: Re: [DXLab] Slow Startup of Apps in Windows 10 I would suggest you start

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

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

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 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

Makes sense. Thanks, Dave. 73, Mike, W4UM

Joe, I'll try to be even more clear. 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