开云体育

I don't know but given the increasing number of questions concerning the matter I would suggest it is no longer a trivial fraction. In addition, given the number of users that are known to use

Fiji Islands has not changed to Conway Reef. Apparently you have a recent QSO with a 3D2 station ClubLog lists as being on Conway (perhaps 3D2CCC). Find the QSO in question and edit the DXCC box to

The slow startup could be waiting for TQSL to contact the mothership if he didn’t stop that as you recommended previously. Bruce - K5WBM

Thanks Dave!! I was being an idiot ... not adding the /spots to the URL!! Working perfectly now!!! Thanks for pointing me in the right direction!!! 73 de BARRY MURRELL ZS2EZ KF26ta - Port Elizabeth,

+ AA6YQ comments below I have no data on the fraction of the current and prospective user community that has or will have a physical layout that makes such capability useful. So, in the absence of

+ AA6YQ comments below I have just got my DX Cluster (ZS2EZ-3) back up and running after a couple of weeks down - now have a Fixed IP on my Fibre Line (was using No-IP service) and have a parked

+ AA6YQ comments below I was trying to upload my ADIF file to Clublog and I received an error message that Fiji Islands is now Conway Reef. How do I change designation in DX Keeper to Conway Reef? +

With the Launcher configured to automatically start your DXLab applications, the recommended diagnostic test for "slow startup" is 1. reboot Windows into "Safe mode with networking" 2. note the time

I was trying to upload my ADIF file to Clublog and I received an error message that Fiji Islands is now Conway Reef.? How do I change designation in DX Keeper to Conway Reef?

Hi Dave I have just got my DX Cluster (ZS2EZ-3) back up and running after a couple of weeks down - now have a Fixed IP on my Fibre Line (was using No-IP service) and have a parked domain pointing to

No worries, Curt - I just wanted to understand because mine doesn't take nearly as long to start. I'm also not starting everything at once. My auto-start list when Launcher kicks off is SpotCollector

Yes... I noticed LoTW was down ... I said "I notice right away"..... again I will be more careful with my word smithing on this site! I guess I should have said;? I noticed LOTW was down right

Brian N8wrl... My words but by bootup .. I mean launching DXLab complete suite of apps, including all the "Apps started After DXLab Apps" using? DX LA launcher. I'll try to be more careful with my

I have no data on the fraction of the current and prospective user community that has or will have a physical layout that makes such capability useful. So, in the absence of data, I'll tell a

+ AA6YQ comments below + For what fraction of the current and prospective user community? + Note that the DXLab's direct interoperation with WSJT-X supports multiple instances of WSJT-X running on

This assumes that each of the transceivers are physically adjacent to the computer (can be reached by the operator from the computer) and that only one transceiver is in use at a time. Both

That did it Dave. Thanks! 73, Dick - W6TK [email protected]> wrote:

+ AA6YQ comments below + The errorlog indicates that your Spot Database has been corrupted. To recover from this, 1. terminate SpotCollector 2. delete the file

+ AA6YQ comments below + Commander can be connected to up to 4 primary transceivers, and can switch from one to another with a single mouse click. Thus logging with multiple transceivers can be

Hello Dave and all, I have encountered an issue with Spot Collector in the last two days - it doesn't open or connect to the network and allow spots to come through. I have a note on the Spot