Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- DXLab
- Messages
Search
|
Re: Windows 7 Resend with Spell Check auto on now :-)
That's going to have to change as more and more people are buying 64 bit capable processors with 4+ Gig of memory and the only way to access it all is with a 64 bit OS. The Windows 7 release is going to include disks for both the 32 and 64 bit versions.
toggle quoted message
Show quoted text
As W7 release day is now only a little over a month away I suspect that many manufacturers (at least those who want to stay in business) will be releasing new drivers. So, it probably warrants an almost daily check for updates. 73, Rich - W3ZJ rojomn wrote: After looking around the NET it seems that the biggest problem with the |
|
Re: broke freq
k9ct
Once the tx freq is deleted the tx band is deleted. I don't want the tx band to be deleted as that is the reference for the award.
toggle quoted message
Show quoted text
--- In dxlab@..., "Dave AA6YQ" <aa6yq@...> wrote:
-----Original Message-----AA6YQ comments below |
|
Re: Windows 7 Resend with Spell Check auto on now :-)
rojomn
After looking around the NET it seems that the biggest problem with the
toggle quoted message
Show quoted text
USB-Serial is that manufactures are not producing good or any 64 bit drivers. I am going to install the 32 bit version of the W7 and see what happens. I suspect it might work but I REALLY REALLY want to run the 64 bit. It may take a few day s to get the 32 bit X86 test run :-) Gil, W0MN N 44.082147 W 92.513085 1050' EN34rb Hierro Candente, Batir de repente -----Original Message----- |
|
Re: Problems with eQSL-database downloads
Is this happening on the same PC where DXKeeper generated an errorlog
toggle quoted message
Show quoted text
showing unexpected database failures when synchronizing with LotW or eQSL? 73, Dave, AA6YQ -----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of dk1ip Sent: Wednesday, September 16, 2009 3:24 AM To: dxlab@... Subject: [dxlab] Problems with eQSL-database downloads gm all, since migrating dxlab to a new (old) PC (macmini running XP3 via bootcamp) I'm stuck with loading new eQSL-databases. It's only a minor glitch as I don't use eQSLing so far ... but it's annoying to find different pop-ups while I refresh my DXLab-Suite with the latest databases telling me 'unknown data-format in eQSL.mdb'. That gives me an increasing errorlog in DXKeeper and DXView as well. I picked up the latest of both (any from previous date have the same content): DXKeeper_ErrorLog: 16-Sep-2009 06:38:40 > DXKeeper version 8.1.6 16-Sep-2009 06:38:40 > App.Path : C:\Program Files\DXLab Suite\DXKeeper 16-Sep-2009 06:38:40 > App.exe : DXKeeper 16-Sep-2009 06:38:40 > Operating System: Windows XP build 2600 16-Sep-2009 06:38:40 > Locale ID : 1031 (0x407) 16-Sep-2009 06:38:40 > ANSI CodePage : 1252 16-Sep-2009 06:38:40 > OEM CodePage : 850 16-Sep-2009 06:38:40 > Country : Germany 16-Sep-2009 06:38:40 > Language : German 16-Sep-2009 06:38:40 > DXLab Apps : 16-Sep-2009 06:38:44 > program error 3343 in module DXLogModule.OpeneQSLDatabase: Nicht erkennbares Datenbankformat 'C:\Program Files\DXLab Suite\DXView\Databases\eQSLAG.mdb'. 16-Sep-2009 06:47:36 > DXKeeper shutdown SpotCollector_ErrorLog: 01-Aug-2009 07:50:53 > SpotCollector version 4.9.8 01-Aug-2009 07:50:53 > App.Path : C:\Program Files\DXLab Suite\SpotCollector 01-Aug-2009 07:50:53 > App.exe : SpotCollector 01-Aug-2009 07:50:53 > Operating System: Windows XP build 2600 01-Aug-2009 07:50:53 > Country : Germany 01-Aug-2009 07:50:53 > Language : Deutsch (Deutschland) 01-Aug-2009 07:50:53 > DXLab Apps : 01-Aug-2009 07:50:55 > program error 3343 in module SpotDatabaseModule.OpeneQSLDatabase: Nicht erkennbares Datenbankformat 'C:\Program Files\DXLab Suite\DXView\Databases\eQSLAG.mdb'. 01-Aug-2009 07:54:06 > SpotCollector shutdown I tried everything I thought it could be useful: deleting the eQSL.mdb file and starting with a new download .. but no joy ;-(( As written above, this is only a minor glitch (for me), but anyhow I'd really like to get rid of it. A helping hand is very much appreciated! 73 Wolf, DK1IP ------------------------------------ Yahoo! Groups Links No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.339 / Virus Database: 270.13.99/2372 - Release Date: 09/15/09 05:59:00 |
|
Problems with eQSL-database downloads
dk1ip
gm all,
since migrating dxlab to a new (old) PC (macmini running XP3 via bootcamp) I'm stuck with loading new eQSL-databases. It's only a minor glitch as I don't use eQSLing so far ... but it's annoying to find different pop-ups while I refresh my DXLab-Suite with the latest databases telling me 'unknown data-format in eQSL.mdb'. That gives me an increasing errorlog in DXKeeper and DXView as well. I picked up the latest of both (any from previous date have the same content): DXKeeper_ErrorLog: 16-Sep-2009 06:38:40 > DXKeeper version 8.1.6 16-Sep-2009 06:38:40 > App.Path : C:\Program Files\DXLab Suite\DXKeeper 16-Sep-2009 06:38:40 > App.exe : DXKeeper 16-Sep-2009 06:38:40 > Operating System: Windows XP build 2600 16-Sep-2009 06:38:40 > Locale ID : 1031 (0x407) 16-Sep-2009 06:38:40 > ANSI CodePage : 1252 16-Sep-2009 06:38:40 > OEM CodePage : 850 16-Sep-2009 06:38:40 > Country : Germany 16-Sep-2009 06:38:40 > Language : German 16-Sep-2009 06:38:40 > DXLab Apps : 16-Sep-2009 06:38:44 > program error 3343 in module DXLogModule.OpeneQSLDatabase: Nicht erkennbares Datenbankformat 'C:\Program Files\DXLab Suite\DXView\Databases\eQSLAG.mdb'. 16-Sep-2009 06:47:36 > DXKeeper shutdown SpotCollector_ErrorLog: 01-Aug-2009 07:50:53 > SpotCollector version 4.9.8 01-Aug-2009 07:50:53 > App.Path : C:\Program Files\DXLab Suite\SpotCollector 01-Aug-2009 07:50:53 > App.exe : SpotCollector 01-Aug-2009 07:50:53 > Operating System: Windows XP build 2600 01-Aug-2009 07:50:53 > Country : Germany 01-Aug-2009 07:50:53 > Language : Deutsch (Deutschland) 01-Aug-2009 07:50:53 > DXLab Apps : 01-Aug-2009 07:50:55 > program error 3343 in module SpotDatabaseModule.OpeneQSLDatabase: Nicht erkennbares Datenbankformat 'C:\Program Files\DXLab Suite\DXView\Databases\eQSLAG.mdb'. 01-Aug-2009 07:54:06 > SpotCollector shutdown I tried everything I thought it could be useful: deleting the eQSL.mdb file and starting with a new download .. but no joy ;-(( As written above, this is only a minor glitch (for me), but anyhow I'd really like to get rid of it. A helping hand is very much appreciated! 73 Wolf, DK1IP |
|
Re: Ukrainian Poltavska Oblast DXCC Database error
DXKeeper refers to the DXCC database, so if you have DXCC database 2.2.7 installed and logged QSOs with Poltavska Oblast in Ukraine, then yes the wrong primary subdivision code would be logged. You can easily check to see if this is the case: click the Broke button in the Filter panel at the bottom of the Main window's "Log QSOs" tab.
toggle quoted message
Show quoted text
73, Dave, AA6YQ --- In dxlab@..., "joe voelkelt" <pitbull9@...> wrote:
|
|
Re: Ukrainian Poltavska Oblast DXCC Database error
joe voelkelt
i just use dx keeper dave, any problem with this error in dx keeper? have not logged any oblasts yet from the ukraine so do not know how to fix if indeed a problem in dxkeeper. thanks joe kl7lf
toggle quoted message
Show quoted text
----- Original Message -----
From: aa6yq To: dxlab@... Sent: Tuesday, September 15, 2009 9:16 PM Subject: [dxlab] Ukrainian Poltavska Oblast DXCC Database error The two Ukrainian entries in the DXCC database for Poltavska Oblast specify an incorrect primary administrative subdivision code. They currently specify Poltavska Oblast <Pri:HO> but should specify Poltavska Oblast <Pri:PO> This error (mine, not Joe W4TV's) will be corrected in the next version of the DXCC database, but those chasing Ukrainian Oblasts can immediately correct their DXCC database with the following procedure: 1. terminate DXKeeper and SpotCollector, if running 2. click the DXCC button on DXView's Main window; the "DXView DXCC Database" window will appear 3. in the "DXView DXCC Database" window's "Master Table" tab, 3a. in the spreadsheet-like display at the bottom of the tab, scroll down to the first entry whose Entity Name is "Ukraine" and whose Location is Poltavska Oblast <Pri:HO> and then click on this entry with your left mouse button 3b. in the Location textbox near the top of the tab, change Poltavska Oblast <Pri:HO> to Poltavska Oblast <Pri:PO> 3c. click on the next entry with your left mouse button, and repeat the correction described in step 3b 3d. click the Save button 3e. click the ReTable button 4. close the "DXView DXCC Database" window To determine whether you have logged QSOs with stations in Poltavska Oblast that recorded the incorrect primary subdivision code, click the Broke button in the Filter panel at the bottom of the "Log QSOs" tab of DXKeeper's Main window; any such QSOs will be displayed in your Log Page Display (assuming you have the Subdivision box checked in the Other panel on the Config window's Awards tab). 73, Dave, AA6YQ |
|
Ukrainian Poltavska Oblast DXCC Database error
The two Ukrainian entries in the DXCC database for Poltavska Oblast specify an incorrect primary administrative subdivision code. They currently specify
Poltavska Oblast <Pri:HO> but should specify Poltavska Oblast <Pri:PO> This error (mine, not Joe W4TV's) will be corrected in the next version of the DXCC database, but those chasing Ukrainian Oblasts can immediately correct their DXCC database with the following procedure: 1. terminate DXKeeper and SpotCollector, if running 2. click the DXCC button on DXView's Main window; the "DXView DXCC Database" window will appear 3. in the "DXView DXCC Database" window's "Master Table" tab, 3a. in the spreadsheet-like display at the bottom of the tab, scroll down to the first entry whose Entity Name is "Ukraine" and whose Location is Poltavska Oblast <Pri:HO> and then click on this entry with your left mouse button 3b. in the Location textbox near the top of the tab, change Poltavska Oblast <Pri:HO> to Poltavska Oblast <Pri:PO> 3c. click on the next entry with your left mouse button, and repeat the correction described in step 3b 3d. click the Save button 3e. click the ReTable button 4. close the "DXView DXCC Database" window To determine whether you have logged QSOs with stations in Poltavska Oblast that recorded the incorrect primary subdivision code, click the Broke button in the Filter panel at the bottom of the "Log QSOs" tab of DXKeeper's Main window; any such QSOs will be displayed in your Log Page Display (assuming you have the Subdivision box checked in the Other panel on the Config window's Awards tab). 73, Dave, AA6YQ |
|
: KS4Q cluster
Richard J. Fiero II W5TFW
I missed it also.
toggle quoted message
Show quoted text
Thank You. ----- Original Message -----
From: Larry To: dxlab@... Sent: Tuesday, September 15, 2009 7:58 PM Subject: Re: [dxlab] OT: KS4Q cluster I have been somewhat out of touch of late and missed that. Thanks 73, Larry W6NWS ----- Original Message ----- From: Jim N7US To: dxlab@... Sent: Tuesday, September 15, 2009 8:48 PM Subject: RE: [dxlab] OT: KS4Q cluster Ernie, KS4Q, died in early July. Jim N7US -----Original Message----- I have not been able to connect to KS4Q cluster via telnet. I was wondering if anyone else was having a problem. A few months ago there was problem and for a short while changed to port 7373 but moved back to 23. It used to work. 73, Larry W6NWS |
|
Re: OT: KS4Q cluster
FireBrick
Oh dear me, I missed that news, sad...
toggle quoted message
Show quoted text
On 9/15/2009 7:48:20 PM, Jim N7US (n7us@...) wrote:
Ernie, KS4Q, died in early July. |
|
Re: OT: KS4Q cluster
I have been somewhat out of touch of late and missed that.
toggle quoted message
Show quoted text
Thanks 73, Larry W6NWS ----- Original Message -----
From: Jim N7US To: dxlab@... Sent: Tuesday, September 15, 2009 8:48 PM Subject: RE: [dxlab] OT: KS4Q cluster Ernie, KS4Q, died in early July. Jim N7US -----Original Message----- I have not been able to connect to KS4Q cluster via telnet. I was wondering if anyone else was having a problem. A few months ago there was problem and for a short while changed to port 7373 but moved back to 23. It used to work. 73, Larry W6NWS |
|
Re: OT: KS4Q cluster
Ernie, KS4Q, died in early July.
toggle quoted message
Show quoted text
Jim N7US -----Original Message-----
I have not been able to connect to KS4Q cluster via telnet. I was wondering if anyone else was having a problem. A few months ago there was problem and for a short while changed to port 7373 but moved back to 23. It used to work. 73, Larry W6NWS |
|
Re: Solar Flux data
The resolution of this is that George was only using the "DX Summit via IRC"
toggle quoted message
Show quoted text
spot source, from which SpotCollector does not currently capture WWV spots. He's adding a telnet cluster as a spot source so SpotCollector can capture WWV spots and keep its Solar History display up-to-date. 73, Dave, AA6YQ -----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of George Steube Sent: Monday, September 14, 2009 8:59 PM To: dxlab@... Subject: RE: [dxlab]Solar Flux data Hi Dave, I noticed for about the last month that the solar flux data has not been updating. The last update I have is 8/31. I have gone to the spot sources and downloaded solar data, but the solar flux data in SC doesn't add it. I checked the help files and there doesn't seem to be a way of turning it off so what else could be set wrong? Thanks. George W2GS -----Original Message----- From: dxlab@... [mailto:dxlab@...]On Behalf Of Dave AA6YQ Sent: Sunday, September 13, 2009 12:45 PM To: dxlab@... Subject: RE: [dxlab] VISTA When you say that the Solar Flux window is not operating, do you mean that this window does not appear, or that the window appears but contains no data? What happens if you type a SH/WWV/100 command to one of your spot sources? 73, Dave, AA6YQ -----Original Message----- From: dxlab@... [mailto:dxlab@...]On Behalf Of leuven0 Sent: Sunday, September 13, 2009 7:33 AM To: dxlab@... Subject: [dxlab] VISTA Long time DxLab user. Just downloaded DxLab to a new computer with Vista OS and everything seems to be operating except the Solar Flux window in Spotcollector and consequently Propview. Any suggestions? Fred WA3JJM ------------------------------------ Yahoo! Groups Links No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.339 / Virus Database: 270.13.83/2353 - Release Date: 09/12/09 06:37:00 ------------------------------------ Yahoo! Groups Links No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.339 / Virus Database: 270.13.94/2367 - Release Date: 09/14/09 11:36:00 |
|
No Last QSO Information on WW
Richard J. Fiero II W5TFW
Dave,
toggle quoted message
Show quoted text
U are simply INCREDIBLE ! Joey ----- Original Message -----
From: Dave AA6YQ To: dxlab@... Sent: Tuesday, September 15, 2009 7:03 PM Subject: RE: [dxlab] Re: No Last QSO Information on WW Please place your DXKeeper log file in a zip archive, and attach this archive to an email message. In the email message, please indicate the starting and ending dates of the contest, and then send the email message to me at aa6yq@... so I can see what's going on. 73, Dave, AA6YQ -----Original Message----- From: dxlab@... [mailto:dxlab@...]On Behalf Of Mario Aviles Sent: Tuesday, September 15, 2009 7:44 PM To: dxlab@... Subject: Re: [dxlab] Re: No Last QSO Information on WW Dave: I checked in DX Keeper and it is not registering most of the information you pointed out. The only fields being registered are CALL DXCC, Starting UTC BAND MODE, SENT, REceived. It is not registering all the other information, not even the exchanged reports. THis is a contest which is not in the drop down box, so I entered it manualy. WW shows the fields and the counter does increment by one each time I looged a station but this info is not on DXK Thanks for your help Mario ----- Original Message ----- From: aa6yq To: dxlab@... Sent: Tuesday, September 15, 2009 5:31 PM Subject: [dxlab] Re: No Last QSO Information on WW In the previous QSO that wasn't reported, what was logged as the Contest ID, band, mode, and QSO Date? 73, Dave, AA6YQ --- In dxlab@..., "Mario Aviles" <mario.aviles@...> wrote: > > Thanks for response, however this is not the case in my setup. I found this problem when I called a station that I had already worked but did not show as previously worked. When the station responded he said that we had already worked and indeed, I checked DXKeeper and he was logged. When I unselected the contest mode, then it gave the adecuate indication > > 73?s > > Mario > ----- Original Message ----- > From: aa6yq > To: dxlab@... > Sent: Tuesday, September 15, 2009 5:16 PM > Subject: [dxlab] Re: No Last QSO Information on WW > > > With contest mode enabled, only previous contacts made in the current contest are displayed; this means QSOs logged in the current year with the current Contest ID. > > 73, > > Dave, AA6YQ > > --- In dxlab@..., "Mario Aviles" <mario.aviles@> wrote: > > > > Hi Group: > > > > Just found a problem with the LAST QSO info on WW ver 6.4.8. I am running a local contest and noticed that I worked a station previously worked and did not get the message that I had already worked him eventhough that was the case. Unselected the TEST check and it worked fine. Does this mean that the program is set not to indicate dupes when in contest mode, or maybe I need to set it up in one of the Config Menus. > > > > Any ideas? > > > > 73?s > > > > Mario/YS1MAE > > > > [Non-text portions of this message have been removed] > > > > > > > > [Non-text portions of this message have been removed] > [Non-text portions of this message have been removed] ------------------------------------ Yahoo! Groups Links No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.339 / Virus Database: 270.13.94/2367 - Release Date: 09/15/09 05:59:00 |
|
Re: No Last QSO Information on WW
Please place your DXKeeper log file in a zip archive, and attach this
toggle quoted message
Show quoted text
archive to an email message. In the email message, please indicate the starting and ending dates of the contest, and then send the email message to me at aa6yq@... so I can see what's going on. 73, Dave, AA6YQ -----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Mario Aviles Sent: Tuesday, September 15, 2009 7:44 PM To: dxlab@... Subject: Re: [dxlab] Re: No Last QSO Information on WW Dave: I checked in DX Keeper and it is not registering most of the information you pointed out. The only fields being registered are CALL DXCC, Starting UTC BAND MODE, SENT, REceived. It is not registering all the other information, not even the exchanged reports. THis is a contest which is not in the drop down box, so I entered it manualy. WW shows the fields and the counter does increment by one each time I looged a station but this info is not on DXK Thanks for your help Mario ----- Original Message ----- From: aa6yq To: dxlab@... Sent: Tuesday, September 15, 2009 5:31 PM Subject: [dxlab] Re: No Last QSO Information on WW In the previous QSO that wasn't reported, what was logged as the Contest ID, band, mode, and QSO Date? 73, Dave, AA6YQ --- In dxlab@..., "Mario Aviles" <mario.aviles@...> wrote: > > Thanks for response, however this is not the case in my setup. I found this problem when I called a station that I had already worked but did not show as previously worked. When the station responded he said that we had already worked and indeed, I checked DXKeeper and he was logged. When I unselected the contest mode, then it gave the adecuate indication > > 73???s > > Mario > ----- Original Message ----- > From: aa6yq > To: dxlab@... > Sent: Tuesday, September 15, 2009 5:16 PM > Subject: [dxlab] Re: No Last QSO Information on WW > > > With contest mode enabled, only previous contacts made in the current contest are displayed; this means QSOs logged in the current year with the current Contest ID. > > 73, > > Dave, AA6YQ > > --- In dxlab@..., "Mario Aviles" <mario.aviles@> wrote: > > > > Hi Group: > > > > Just found a problem with the LAST QSO info on WW ver 6.4.8. I am running a local contest and noticed that I worked a station previously worked and did not get the message that I had already worked him eventhough that was the case. Unselected the TEST check and it worked fine. Does this mean that the program is set not to indicate dupes when in contest mode, or maybe I need to set it up in one of the Config Menus. > > > > Any ideas? > > > > 73???s > > > > Mario/YS1MAE > > > > > > > > > > > > > ------------------------------------ Yahoo! Groups Links No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.339 / Virus Database: 270.13.94/2367 - Release Date: 09/15/09 05:59:00 |
|
Re: No Last QSO Information on WW
Mario Aviles
Dave:
toggle quoted message
Show quoted text
I checked in DX Keeper and it is not registering most of the information you pointed out. The only fields being registered are CALL DXCC, Starting UTC BAND MODE, SENT, REceived. It is not registering all the other information, not even the exchanged reports. THis is a contest which is not in the drop down box, so I entered it manualy. WW shows the fields and the counter does increment by one each time I looged a station but this info is not on DXK Thanks for your help Mario ----- Original Message -----
From: aa6yq To: dxlab@... Sent: Tuesday, September 15, 2009 5:31 PM Subject: [dxlab] Re: No Last QSO Information on WW In the previous QSO that wasn't reported, what was logged as the Contest ID, band, mode, and QSO Date? 73, Dave, AA6YQ --- In dxlab@..., "Mario Aviles" <mario.aviles@...> wrote: > > Thanks for response, however this is not the case in my setup. I found this problem when I called a station that I had already worked but did not show as previously worked. When the station responded he said that we had already worked and indeed, I checked DXKeeper and he was logged. When I unselected the contest mode, then it gave the adecuate indication > > 73?s > > Mario > ----- Original Message ----- > From: aa6yq > To: dxlab@... > Sent: Tuesday, September 15, 2009 5:16 PM > Subject: [dxlab] Re: No Last QSO Information on WW > > > With contest mode enabled, only previous contacts made in the current contest are displayed; this means QSOs logged in the current year with the current Contest ID. > > 73, > > Dave, AA6YQ > > --- In dxlab@..., "Mario Aviles" <mario.aviles@> wrote: > > > > Hi Group: > > > > Just found a problem with the LAST QSO info on WW ver 6.4.8. I am running a local contest and noticed that I worked a station previously worked and did not get the message that I had already worked him eventhough that was the case. Unselected the TEST check and it worked fine. Does this mean that the program is set not to indicate dupes when in contest mode, or maybe I need to set it up in one of the Config Menus. > > > > Any ideas? > > > > 73?s > > > > Mario/YS1MAE > > > > [Non-text portions of this message have been removed] > > > > > > > > [Non-text portions of this message have been removed] > [Non-text portions of this message have been removed] |
|
Re: No Last QSO Information on WW
In the previous QSO that wasn't reported, what was logged as the Contest ID, band, mode, and QSO Date?
toggle quoted message
Show quoted text
73, Dave, AA6YQ --- In dxlab@..., "Mario Aviles" <mario.aviles@...> wrote:
|
|
Re: No Last QSO Information on WW
Mario Aviles
Thanks for response, however this is not the case in my setup. I found this problem when I called a station that I had already worked but did not show as previously worked. When the station responded he said that we had already worked and indeed, I checked DXKeeper and he was logged. When I unselected the contest mode, then it gave the adecuate indication
toggle quoted message
Show quoted text
73?s Mario ----- Original Message -----
From: aa6yq To: dxlab@... Sent: Tuesday, September 15, 2009 5:16 PM Subject: [dxlab] Re: No Last QSO Information on WW With contest mode enabled, only previous contacts made in the current contest are displayed; this means QSOs logged in the current year with the current Contest ID. 73, Dave, AA6YQ --- In dxlab@..., "Mario Aviles" <mario.aviles@...> wrote: > > Hi Group: > > Just found a problem with the LAST QSO info on WW ver 6.4.8. I am running a local contest and noticed that I worked a station previously worked and did not get the message that I had already worked him eventhough that was the case. Unselected the TEST check and it worked fine. Does this mean that the program is set not to indicate dupes when in contest mode, or maybe I need to set it up in one of the Config Menus. > > Any ideas? > > 73?s > > Mario/YS1MAE > > [Non-text portions of this message have been removed] > [Non-text portions of this message have been removed] |
|
Re: No Last QSO Information on WW
With contest mode enabled, only previous contacts made in the current contest are displayed; this means QSOs logged in the current year with the current Contest ID.
toggle quoted message
Show quoted text
73, Dave, AA6YQ --- In dxlab@..., "Mario Aviles" <mario.aviles@...> wrote:
|
Jim N7US
to navigate to use esc to dismiss