|
DXView QTH coordinates not kept
running DXView only showed the correct coordinates that I had set. So I closed DXView and I run the whole suite. Coordinates were reverted again to center of grid. The cause was DXKeeper because the d
running DXView only showed the correct coordinates that I had set. So I closed DXView and I run the whole suite. Coordinates were reverted again to center of grid. The cause was DXKeeper because the d
|
By
Salvatore Besso
· #207343
·
|
|
DXView QTH coordinates not kept
ok that it could be sufficient for aiming the antenna, but I don't like that something is not saved when it is supposed to do so. 73 de Salvatore (I4FYV)
ok that it could be sufficient for aiming the antenna, but I don't like that something is not saved when it is supposed to do so. 73 de Salvatore (I4FYV)
|
By
Salvatore Besso
· #207342
·
|
|
DXView QTH coordinates not kept
hello Joe, yeah, maybe you are right. Of course I use a workspace and maybe this fact depends from it not being saved. I will try in a moment. 73 de Salvatore (I4FYV)
hello Joe, yeah, maybe you are right. Of course I use a workspace and maybe this fact depends from it not being saved. I will try in a moment. 73 de Salvatore (I4FYV)
|
By
Salvatore Besso
· #207341
·
|
|
DXView QTH coordinates not kept
Dave, as I have written in my original message, I have "saved" the change clicking on the Save button. Now I have just started DXlab and I'm checking... Coordinates are not saved and were reverted bac
Dave, as I have written in my original message, I have "saved" the change clicking on the Save button. Now I have just started DXlab and I'm checking... Coordinates are not saved and were reverted bac
|
By
Salvatore Besso
· #207331
·
|
|
DXView QTH coordinates not kept
hello, why my latitude and longitude are not kept between sessions? I have set my exact latitude to 44° 41 42 and my exact longitude to 10° 38 55. I have also saved clicking the homonymous button on t
hello, why my latitude and longitude are not kept between sessions? I have set my exact latitude to 44° 41 42 and my exact longitude to 10° 38 55. I have also saved clicking the homonymous button on t
|
By
Salvatore Besso
· #207304
·
|
|
File not found
in the download page, SpotCollector auxiliary files: Sub-band Definition file as of 2020-04-11 404 - File not found 73 de Salvatore (I4FYV)
in the download page, SpotCollector auxiliary files: Sub-band Definition file as of 2020-04-11 404 - File not found 73 de Salvatore (I4FYV)
|
By
Salvatore Besso
· #207216
·
|
|
DXKeeper Not Longer Adds QSOs To QSL Que
ok, but does at least one of those QSOs have an "R" in the QSL sent dropbox (open the QSL panel to look at this)? This sounds a bit strange, since it means that you have never requested a QSL, that's
ok, but does at least one of those QSOs have an "R" in the QSL sent dropbox (open the QSL panel to look at this)? This sounds a bit strange, since it means that you have never requested a QSL, that's
|
By
Salvatore Besso
· #206687
·
|
|
DXKeeper Not Longer Adds QSOs To QSL Que
sorry for the typo, I meant to write: it could mean "all QSOs between 2022-03-05 00:00:00 and the last logged QSO". 73 de Salvatore (I4FYV)
sorry for the typo, I meant to write: it could mean "all QSOs between 2022-03-05 00:00:00 and the last logged QSO". 73 de Salvatore (I4FYV)
|
By
Salvatore Besso
· #206685
·
|
|
DXKeeper Not Longer Adds QSOs To QSL Que
maybe because there are no requested QSOs to add to the queue when your log is filtered. Remove the filter and try again to see if some QSOs are added. it could mean "all QSOs between 2022-03-05 00:00
maybe because there are no requested QSOs to add to the queue when your log is filtered. Remove the filter and try again to see if some QSOs are added. it could mean "all QSOs between 2022-03-05 00:00
|
By
Salvatore Besso
· #206684
·
|
|
Stopping the update of a QSO with wrong data
Dave, thank you. In fact it is strange. Yesterday I got the wrong information for that QSO and I manually edited the QSO to restore the correct primary subdivision. Today, after another QSL Sync, I go
Dave, thank you. In fact it is strange. Yesterday I got the wrong information for that QSO and I manually edited the QSO to restore the correct primary subdivision. Today, after another QSL Sync, I go
|
By
Salvatore Besso
· #204701
·
|
|
Stopping the update of a QSO with wrong data
hello Dave, yes, in fact I have evidenced the "non existency" of this Oblast. well, I'll do, but this doesn't prevent LoTW to present the same wrong information at every QSL Sync and DXKeeper to pop-u
hello Dave, yes, in fact I have evidenced the "non existency" of this Oblast. well, I'll do, but this doesn't prevent LoTW to present the same wrong information at every QSL Sync and DXKeeper to pop-u
|
By
Salvatore Besso
· #204698
·
|
|
Stopping the update of a QSO with wrong data
hello, I had a QSO with RK0UT, whose primary administrative subdivision is ZK (Zabaykalsky Kraj). Every time I do a LoTW Sync QSLs I constantly get an update of this subdivision with an apparently non
hello, I had a QSO with RK0UT, whose primary administrative subdivision is ZK (Zabaykalsky Kraj). Every time I do a LoTW Sync QSLs I constantly get an update of this subdivision with an apparently non
|
By
Salvatore Besso
· #204694
·
|
|
updating DXLab's DXCC Database
Dave, yes, I forgot o mention in my yesterday's reply, that I have made also a ReTable operation. Thank you. 73 de Salvatore (I4FYV)
Dave, yes, I forgot o mention in my yesterday's reply, that I have made also a ReTable operation. Thank you. 73 de Salvatore (I4FYV)
|
By
Salvatore Besso
· #203785
·
|
|
DXCC data base
yes, Joe already said the same thing. Thank you. 73 de Salvatore (I4FYV)
yes, Joe already said the same thing. Thank you. 73 de Salvatore (I4FYV)
|
By
Salvatore Besso
· #203768
·
|
|
DXCC data base
in that in DXView\Databases, but it's possible that I could have made some mess with the file copy. Anyway, I have verified again, using DXView, that the change was correct, than I have closed and res
in that in DXView\Databases, but it's possible that I could have made some mess with the file copy. Anyway, I have verified again, using DXView, that the change was correct, than I have closed and res
|
By
Salvatore Besso
· #203767
·
|
|
DXCC data base
ok, I will check again. 73 de Salvatore (I4FYV)
ok, I will check again. 73 de Salvatore (I4FYV)
|
By
Salvatore Besso
· #203757
·
|
|
DXCC data base
hello Joe, ok, but sometimes it happens that I run only SpotCollector to see if there is something interesting on the bands, so I think that it's better to have the same database aligned everywhere. W
hello Joe, ok, but sometimes it happens that I run only SpotCollector to see if there is something interesting on the bands, so I think that it's better to have the same database aligned everywhere. W
|
By
Salvatore Besso
· #203754
·
|
|
DXCC data base
I enter this thread saying that I've always operated in this way to change the name of an entity; moreover, one should then exit DXLab and manually copy the modified DXCC.mdb that resides in the Datab
I enter this thread saying that I've always operated in this way to change the name of an entity; moreover, one should then exit DXLab and manually copy the modified DXCC.mdb that resides in the Datab
|
By
Salvatore Besso
· #203745
·
|
|
DXView not displaying current heading of rotor
ok, thank you. 73 de Salvatore (I4FYV)
ok, thank you. 73 de Salvatore (I4FYV)
|
By
Salvatore Besso
· #203589
·
|
|
DXView not displaying current heading of rotor
Dave, just for curiosity, isn't the Yaesu protocol the same for the 2800 and the 800? It seems not. Is it something that has to to do with the Yaesu protocol 232-A or 232-B? 73 de Salvatore (I4FYV)
Dave, just for curiosity, isn't the Yaesu protocol the same for the 2800 and the 800? It seems not. Is it something that has to to do with the Yaesu protocol 232-A or 232-B? 73 de Salvatore (I4FYV)
|
By
Salvatore Besso
· #203568
·
|