¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Re: Pathfinder - not working..

 

If you type my callsign into Pathfinder's callsign box and click the QRZ
button, what happens?

If you type my callsign into Pathfinder's callsign box and click the Buck
button, what happens?

If you open Pathfinder's Config window, to what is the QRZ.com URL set?

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Tom Roberts
Sent: Monday, September 07, 2009 8:50 PM
To: dxlab@...
Subject: [dxlab] Pathfinder - not working..


Dear Dave and the group..
???

I have not been able to access QRZ for several days. I have made the
necessary
adjustments to Pathfinder, with not success.
???
I hope there is a fix.. regards.. Tom
???
???








------------------------------------

Yahoo! Groups Links



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.74/2339 - Release Date: 09/07/09
06:40:00


Re: Complete DX Lab Uninstall for clean re-install?

Bill, W6WRT
 

ORIGINAL MESSAGE:

On Mon, 07 Sep 2009 16:50:30 -0000, "themmd2003" <rickwilliams@...>
wrote:

I used the Windows remove program which only removed some of the program files
REPLY:

It's too late now, but for the future, there is a program called Total Uninstall
which will take care of that kind of problem. It takes a snapshot of your hard
drive before and after installing any program and allows you to totally reverse
any changes that are made during installation. I have used it for years and it
works great.



It is not free - under $30 - but for the price, well worth it, IMO.

The usual disclaimers.

73, Bill W6WRT


Pathfinder - not working..

Tom Roberts
 

Dear Dave and the group..
?

I have not been able to access QRZ for several days. I have made the necessary
adjustments to Pathfinder, with not success.
?
I hope there is a fix.. regards.. Tom
?
?




[Non-text portions of this message have been removed]


Re: WPX report

 

The QSO responsible for the 1B0 WPX prefix is not confirmed, which is why it
doesn't appear in the Submission report. You can find it with the SQL query

PFX='1B0'

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Phil Cooper
Sent: Monday, September 07, 2009 5:23 PM
To: dxlab@...
Subject: [dxlab] RE: WPX report


Dave and the group,

I hadn't thought to do a Submission report, but I have now run that, and I
can see where the 2K0 comes from, but the 1B0 is a mystery still.
The 2K0 is from a G call I worked back in 2000, as we were then allowed to
use (eg) G1ABC/2K for the Millenium. I guess the WPX in DXK sees the /2K as
an alternative, just like AA6YQ/C6.

I am including a snippet from both reports here:
(Please note that I have included the log filter, merely as info, as that
1B0 showed up as a 40m DG contact)
WPX Progress:
GU0SUP Worked All Prefixes Progress Report 07-Sep-2009
Log Filter: ((mode='rtty') or (mode='psk') or (mode='digi')) and band='40m'
Index Prefix Status
1 1A0 worked (40m, DG)
2 1B0 worked (40m, DG)
3 2E0 worked (40m, DG)
4 2I0 worked (40m, DG)
5 3A2 worked (40m, DG)
6 3B7 confirmed (40m, DG)
7 3V8 worked (40m, DG)
8 3Z0 worked (40m, DG)
9 3Z1 confirmed (40m, DG)
10 3Z10 worked (40m, DG)
Total WPX Prefixes 928
Confirmed WPX Prefixes 326
Worked WPX Prefixes 602

Now the Submission report:
GU0SUP Worked All Prefixes Submission Report 07-Sep-2009
Log Filter: ((mode='rtty') or (mode='psk') or (mode='digi')) and band='40m'
Index Call Prefix Cards eQSL-AG
1 3B7SP 3B7 Y
2 3Z1V 3Z1 Y
3 4K6DI 4K6 Y
4 4L1BR 4L1 Y
5 4U1ITU 4U1 Y
6 4X6UU 4X6 Y
7 4Z5AV 4Z5 Y
8 5A7A 5A7 Y
9 5C5W 5C5 Y
10 7S4RY 7S4 Y
.
.
.
.
326 ZX2B ZX2 Y

So, both agree that I have 326 confirmed WPX's on 40m digi modes, and I
assume the difference between the top 10 in each case is that the Progress
is reporting those calls worked, whereas the Progress is showing those
confirmed.
However, I cannot find that 1B0 (zero, not letter O) whatever I do to filter
the log, or even leave it unfiltered.
I've also tried various SQL expressions to see if there is a call like /1B
in the log, but I don't recall any such call, and nothing comes of using
CALL LIKE '*/1*' or any other combination I can think of.
Any idea what I might use to try and find that 1B0 ??

73 de Phil GU0SUP



---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 090906-1, 06/09/2009
Tested on: 07/09/2009 22:23:17
avast! - copyright (c) 1988-2009 ALWIL Software.






------------------------------------

Yahoo! Groups Links



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.74/2339 - Release Date: 09/07/09
06:40:00


Re: BEGIN MACRO Request or Did I Miss This Also?

 

When a QSO's start time is set, it appears in red font to the right of the
words "QSO Info" on DXKeeper's Main window. Click the Begin button so you'll
see what I mean.

Now click the X button to clear the QSO Info panel, and then slowly repeat
the procedure you've been using. At what point is the QSO start time set?

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Jim
Besancon
Sent: Monday, September 07, 2009 4:54 PM
To: dxlab@...
Subject: RE: [dxlab] BEGIN MACRO Request or Did I Miss This Also?



Answers/Comments

If you want your RST items initialized to but don't want the QSO's start
time set when you capture a callsign, disable "set QSO start when RST
Rcvd". -

This is my setup. I have "set QSO start when RST Rcvd" unchecked and
"initialize RST items to
default" checked.

Note that if you log a QSO without having clicked the Begin button,
WinWarbler will record the QSO's start and end times as the time at which
you clicked the Log button (or executed the Log macro command).

I just clicked 3A2MD at 2045 and walked away from computer. I came back hit
my log macro F key and then looked in the DXK log file. The Q start time was
2045 and the Q end time was 2050.

73 - Jim - K8SIA



-----Original Message-----
From: Dave AA6YQ [mailto:aa6yq@...]
Sent: Monday, September 07, 2009 4:31 PM
To: dxlab@...
Subject: RE: [dxlab] BEGIN MACRO Request or Did I Miss This Also?

AA6YQ comments below


-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Jim
Besancon
Sent: Monday, September 07, 2009 4:16 PM
To: dxlab@...
Subject: [dxlab] BEGIN MACRO Request or Did I Miss This Also?


Situation: Click on spot or find station in pile up and start entry (enter
call sign) in WW. I then use TAB to see if I should proceed with chasing the
station. The QSO Started At Date/Time appears in red above call sign in WW.

Problem: I don't always get the station for several minutes and when I do,
it is a mad click to hit the BEGIN button and then the F Key to send my
report.

Is there or can there be a <begin> macro that can be placed in a F Key
function to reset the start time of the QSO? I can't find one in the list of
macros.

By default, a QSO's start time is set when you click the Main window's
"QSO Info" panel's Begin button.

On the Config window's Log tab, enabling the "set QSO start when RST
Rcvd" option means that a QSO's start time will be set when you specify its
"RST Rcvd" item, either by typing a report into the Main windows' "Log QSOs"
tab, or by double-clicking a received signal report.

On the Config window's Log tab, there is also an "initialize RST items to
default" option. If you enable this option and have also enabled "set QSO
start when RST Rcvd", then when you type a callsign into the "QSO Info"
window or double-click a decoded callsign

1. the "RST Rcvd" item is initialized to the default

2. the QSO's start time is set (because the "RST Rcvd" was recorded and you
have "set QSO start when RST Rcvd" enabled

If you want your RST items initialized to but don't want the QSO's start
time set when you capture a callsign, disable "set QSO start when RST
Rcvd".

Note that if you log a QSO without having clicked the Begin button,
WinWarbler will record the QSO's start and end times as the time at which
you clicked the Log button (or executed the Log macro command).


I will bet that the group will be glad when today is over :)

Not at all, Jim. Providing answers to questions is one of the fundamental
purposes of this group. .

73,

Dave, AA6YQ



------------------------------------

Yahoo! Groups Links





------------------------------------

Yahoo! Groups Links



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.74/2339 - Release Date: 09/07/09
06:40:00


Re: SC Outgoing Spot Control

 

Rich and All



Yes, it is double click¡­¡­.



I guess I find it annoying or misleading to have it sit there. My eye keeps catching it and it just bothers me.



I yield, it isn¡¯t a problem J



Thanks



73 ¨C Jim ¨C K8SIA



From: Rich - W3ZJ [mailto:rich@...]
Sent: Monday, September 07, 2009 5:12 PM
To: dxlab@...
Subject: Re: [dxlab] SC Outgoing Spot Control







Jim Besancon wrote:
When I click on a spot it populates WW and also populates the call sign in
the outgoing spot box in SC.
Mine doesn't do that unless I "double click" on a spot but perhaps
that's what you meant to say.
If I clear WW, after deciding that I can't work
the spot or don't want to work the spot, the call sign in the outgoing spot
in SC remains populated.

How can the spot call sign be cleared automatically? Now I just highlight
the call sign and hit the space bar, kind of old fashioned.
Why clear it? It's not hurting anything and will be replaced when you
double click the next spot. Min sits there with some callsign in it
almost all the time.

Also the spot frequency is not locked to the spot. If I move the dial the
spot frequency changes but the call sign remains. Is this normal?
Yes, if you had to tune your radio to bring the station in, then the
original spot frequency wasn't quite correct. If you re-spot the
station, you want to do so with what your believe to be the correct
frequency.

73, Rich - W3ZJ
Thanks

73 - Jim - K8SIA





[Non-text portions of this message have been removed]


Re: WPX report

Phil Cooper
 

Dave and the group,

I hadn't thought to do a Submission report, but I have now run that, and I
can see where the 2K0 comes from, but the 1B0 is a mystery still.
The 2K0 is from a G call I worked back in 2000, as we were then allowed to
use (eg) G1ABC/2K for the Millenium. I guess the WPX in DXK sees the /2K as
an alternative, just like AA6YQ/C6.

I am including a snippet from both reports here:
(Please note that I have included the log filter, merely as info, as that
1B0 showed up as a 40m DG contact)
WPX Progress:
GU0SUP Worked All Prefixes Progress Report 07-Sep-2009
Log Filter: ((mode='rtty') or (mode='psk') or (mode='digi')) and band='40m'
Index Prefix Status
1 1A0 worked (40m, DG)
2 1B0 worked (40m, DG)
3 2E0 worked (40m, DG)
4 2I0 worked (40m, DG)
5 3A2 worked (40m, DG)
6 3B7 confirmed (40m, DG)
7 3V8 worked (40m, DG)
8 3Z0 worked (40m, DG)
9 3Z1 confirmed (40m, DG)
10 3Z10 worked (40m, DG)
Total WPX Prefixes 928
Confirmed WPX Prefixes 326
Worked WPX Prefixes 602

Now the Submission report:
GU0SUP Worked All Prefixes Submission Report 07-Sep-2009
Log Filter: ((mode='rtty') or (mode='psk') or (mode='digi')) and band='40m'
Index Call Prefix Cards eQSL-AG
1 3B7SP 3B7 Y
2 3Z1V 3Z1 Y
3 4K6DI 4K6 Y
4 4L1BR 4L1 Y
5 4U1ITU 4U1 Y
6 4X6UU 4X6 Y
7 4Z5AV 4Z5 Y
8 5A7A 5A7 Y
9 5C5W 5C5 Y
10 7S4RY 7S4 Y
.
.
.
.
326 ZX2B ZX2 Y

So, both agree that I have 326 confirmed WPX's on 40m digi modes, and I
assume the difference between the top 10 in each case is that the Progress
is reporting those calls worked, whereas the Progress is showing those
confirmed.
However, I cannot find that 1B0 (zero, not letter O) whatever I do to filter
the log, or even leave it unfiltered.
I've also tried various SQL expressions to see if there is a call like /1B
in the log, but I don't recall any such call, and nothing comes of using
CALL LIKE '*/1*' or any other combination I can think of.
Any idea what I might use to try and find that 1B0 ??

73 de Phil GU0SUP



---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 090906-1, 06/09/2009
Tested on: 07/09/2009 22:23:17
avast! - copyright (c) 1988-2009 ALWIL Software.


excuse me

FireBrick
 

I meant to reply to Jim directly, hit the wrong button.

I said I was old and senile....now do you believe me?


----------------------------------------------------------
History repeats itself because nobody reads. ----------------------------------------------------------
TOWER/WEBCAMS and Weather Page
@


Re: SC Outgoing Spot Control

 

Jim Besancon wrote:
When I click on a spot it populates WW and also populates the call sign in
the outgoing spot box in SC.
Mine doesn't do that unless I "double click" on a spot but perhaps that's what you meant to say.
If I clear WW, after deciding that I can't work
the spot or don't want to work the spot, the call sign in the outgoing spot
in SC remains populated.

How can the spot call sign be cleared automatically? Now I just highlight
the call sign and hit the space bar, kind of old fashioned.
Why clear it? It's not hurting anything and will be replaced when you double click the next spot. Min sits there with some callsign in it almost all the time.

Also the spot frequency is not locked to the spot. If I move the dial the
spot frequency changes but the call sign remains. Is this normal?
Yes, if you had to tune your radio to bring the station in, then the original spot frequency wasn't quite correct. If you re-spot the station, you want to do so with what your believe to be the correct frequency.

73, Rich - W3ZJ
Thanks

73 - Jim - K8SIA


Re: Q & A's - W9OL

FireBrick
 




Thanks for the W9OL Q's
but somehow none in 2009.



73 - Jim - K8SIA
Wife is working me to death. LOL

Kidding aside, a few minor health problems, and 18 grandkids makes weekends a tough go for contesting.

But slowing down a bit now, grandkids don't want those old smelly grandparents around so much. LOL

The other issue is I've been converted to SDR, Flex Radio is a fantastic DX machine.
But not so much a contesting machine.

So have been working with software writers of the Flex to make contesting easier.


Re: Q & A's - W9OL

 

Bill



Thanks Bill for the kind words. I have been using DXL for 16 months but
seldom get a chance to play with it and start asking questions.



I keep a separate folder in my email for DXL advice that I might find useful
and check that often before typing away.



I do support you in the request for a change to SC , that if it isn't
confirmed on band/mode it is needed J



Thanks for the W9OL Q's but somehow none in 2009.



73 - Jim - K8SIA



From: FireBrick [mailto:w9ol@...]
Sent: Monday, September 07, 2009 4:46 PM
To: DXLabs List
Subject: [dxlab] Q & A's





I will bet that the group will be glad when today is over :)

Not at all, Jim. Providing answers to questions is one of the fundamental
purposes of this group. .

Which is why I read almost all of the Q&A's here.
I may have forgotten how a feature works.
I may not have known how it worked in the first place.
I see other ways to do things that could improve my techniques.

DXL is way to much for me to remember....so this Group is a way for me to
get my brain refreshed.

Plus...this is one of the most congenial, friendly, groups.
Some of the groups....get a bit testy at times.
Never in DXL

----------------------------------------------------------
"The attention span of a computer is only as long as its power cord.
----------------------------------------------------------
TOWER/WEBCAMS and Weather Page
@


Re: BEGIN MACRO Request or Did I Miss This Also?

 

Answers/Comments

If you want your RST items initialized to but don't want the QSO's start
time set when you capture a callsign, disable "set QSO start when RST
Rcvd". -

This is my setup. I have "set QSO start when RST Rcvd" unchecked and
"initialize RST items to
default" checked.

Note that if you log a QSO without having clicked the Begin button,
WinWarbler will record the QSO's start and end times as the time at which
you clicked the Log button (or executed the Log macro command).

I just clicked 3A2MD at 2045 and walked away from computer. I came back hit
my log macro F key and then looked in the DXK log file. The Q start time was
2045 and the Q end time was 2050.

73 - Jim - K8SIA



-----Original Message-----
From: Dave AA6YQ [mailto:aa6yq@...]
Sent: Monday, September 07, 2009 4:31 PM
To: dxlab@...
Subject: RE: [dxlab] BEGIN MACRO Request or Did I Miss This Also?

AA6YQ comments below


-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Jim
Besancon
Sent: Monday, September 07, 2009 4:16 PM
To: dxlab@...
Subject: [dxlab] BEGIN MACRO Request or Did I Miss This Also?


Situation: Click on spot or find station in pile up and start entry (enter
call sign) in WW. I then use TAB to see if I should proceed with chasing the
station. The QSO Started At Date/Time appears in red above call sign in WW.

Problem: I don't always get the station for several minutes and when I do,
it is a mad click to hit the BEGIN button and then the F Key to send my
report.

Is there or can there be a <begin> macro that can be placed in a F Key
function to reset the start time of the QSO? I can't find one in the list of
macros.

By default, a QSO's start time is set when you click the Main window's
"QSO Info" panel's Begin button.

On the Config window's Log tab, enabling the "set QSO start when RST
Rcvd" option means that a QSO's start time will be set when you specify its
"RST Rcvd" item, either by typing a report into the Main windows' "Log QSOs"
tab, or by double-clicking a received signal report.

On the Config window's Log tab, there is also an "initialize RST items to
default" option. If you enable this option and have also enabled "set QSO
start when RST Rcvd", then when you type a callsign into the "QSO Info"
window or double-click a decoded callsign

1. the "RST Rcvd" item is initialized to the default

2. the QSO's start time is set (because the "RST Rcvd" was recorded and you
have "set QSO start when RST Rcvd" enabled

If you want your RST items initialized to but don't want the QSO's start
time set when you capture a callsign, disable "set QSO start when RST
Rcvd".

Note that if you log a QSO without having clicked the Begin button,
WinWarbler will record the QSO's start and end times as the time at which
you clicked the Log button (or executed the Log macro command).


I will bet that the group will be glad when today is over :)

Not at all, Jim. Providing answers to questions is one of the fundamental
purposes of this group. .

73,

Dave, AA6YQ



------------------------------------

Yahoo! Groups Links


Re: Stopping Programs

 

Hi Dave,

Thanks for the reminder to try "Advanced SystemCare." Wow! It found
lots of stuff that the other programs that I was using to keep the
computer clean had just passed over. I ran it and found that my
computer was noticeably faster in loading programs! Thanks for the
tip! I've added it to all my computers. It's nice to have all of these
functions in one program.

73,

Ken - K4XL

Dave AA6YQ wrote:

I forgot about GameBooster, Ken. I don't use it, but I tried it once and it
seemed to work well. Thanks for pointing this out!

My experience with IObit tools has been uniformly positive. I have the free
version of "Advanced SystemCare" running on every one of my PCs:

<>

I have no relationship with IObit.

73,

Dave, AA6YQ


-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Kenneth D. Grimm, K4XL
Sent: Monday, September 07, 2009 1:18 PM
To: dxlab@...
Subject: Re: [dxlab] Stopping Programs


aburkefl wrote:

What are the names of some of the popular (and successful!) programs that
will disable anything running in the background that doesn't need to be
running when running amateur applications (like DXKeeper or other parts of
the DXLab suite)?

Thanks.

Art - N4PJ




I use Game Booster. While this little program was designed for serious
game players, it will do what you are asking. Freeware. Works for me,
but there may be other, better programs that I don't know about.

73,

--
Ken K4XL
k4xl@...

*** BoatAnchor Manual Archive ***
On the web at and
FTP site info: bama.sbc.edu login: anonymous p/w: youremailadr




--
Ken K4XL
k4xl@...

*** BoatAnchor Manual Archive ***
On the web at and
FTP site info: bama.sbc.edu login: anonymous p/w: youremailadr


Re: SC Outgoing Spot Control

 

AA6YQ comments below
--- In dxlab@..., "Jim Besancon" <k8sia@...> wrote:

Last question of the day.

When I click on a spot it populates WW and also populates the call sign in the outgoing spot box in SC. If I clear WW, after deciding that I can't work the spot or don't want to work the spot, the call sign in the outgoing spot in SC remains populated.

How can the spot call sign be cleared automatically? Now I just highlight the call sign and hit the space bar, kind of old fashioned.

I didn't provide automation for this because its not necessary. If you double-click another spot database entry or double-click a decoded callsign in WinWarbler, the outgoing spot callsign will be updated. If you want to manually type in a new outgoing spot callsign, click on the existing outgoing spot callsign, strike CTRL-A to select it, and then type the new outgoing spot callsign.
Also the spot frequency is not locked to the spot. If I move the dial the spot frequency changes but the call sign remains. Is this normal?

Yes. You might find that the station's actual frequency is different than what was originally spotted, or the station may QSY after being spotted. Either way, your outgoing spot should include an accurate frequency.
73,

Dave, AA6YQ


Q & A's

FireBrick
 

I will bet that the group will be glad when today is over :)

Not at all, Jim. Providing answers to questions is one of the fundamental
purposes of this group. .



Which is why I read almost all of the Q&A's here.
I may have forgotten how a feature works.
I may not have known how it worked in the first place.
I see other ways to do things that could improve my techniques.

DXL is way to much for me to remember....so this Group is a way for me to get my brain refreshed.

Plus...this is one of the most congenial, friendly, groups.
Some of the groups....get a bit testy at times.
Never in DXL




----------------------------------------------------------
"The attention span of a computer is only as long as its power cord.
----------------------------------------------------------
TOWER/WEBCAMS and Weather Page
@


SC Outgoing Spot Control

 

Last question of the day.

When I click on a spot it populates WW and also populates the call sign in
the outgoing spot box in SC. If I clear WW, after deciding that I can't work
the spot or don't want to work the spot, the call sign in the outgoing spot
in SC remains populated.

How can the spot call sign be cleared automatically? Now I just highlight
the call sign and hit the space bar, kind of old fashioned.

Also the spot frequency is not locked to the spot. If I move the dial the
spot frequency changes but the call sign remains. Is this normal?

Thanks

73 - Jim - K8SIA


Re: BEGIN MACRO Request or Did I Miss This Also?

 

AA6YQ comments below


-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Jim
Besancon
Sent: Monday, September 07, 2009 4:16 PM
To: dxlab@...
Subject: [dxlab] BEGIN MACRO Request or Did I Miss This Also?


Situation: Click on spot or find station in pile up and start entry (enter
call sign) in WW. I then use TAB to see if I should proceed with chasing the
station. The QSO Started At Date/Time appears in red above call sign in WW.

Problem: I don't always get the station for several minutes and when I do,
it is a mad click to hit the BEGIN button and then the F Key to send my
report.

Is there or can there be a <begin> macro that can be placed in a F Key
function to reset the start time of the QSO? I can't find one in the list of
macros.

By default, a QSO's start time is set when you click the Main window's
"QSO Info" panel's Begin button.

On the Config window's Log tab, enabling the "set QSO start when RST
Rcvd" option means that a QSO's start time will be set when you specify its
"RST Rcvd" item, either by typing a report into the Main windows' "Log QSOs"
tab, or by double-clicking a received signal report.

On the Config window's Log tab, there is also an "initialize RST items to
default" option. If you enable this option and have also enabled "set QSO
start when RST Rcvd", then when you type a callsign into the "QSO Info"
window or double-click a decoded callsign

1. the "RST Rcvd" item is initialized to the default

2. the QSO's start time is set (because the "RST Rcvd" was recorded and you
have "set QSO start when RST Rcvd" enabled

If you want your RST items initialized to but don't want the QSO's start
time set when you capture a callsign, disable "set QSO start when RST
Rcvd".

Note that if you log a QSO without having clicked the Begin button,
WinWarbler will record the QSO's start and end times as the time at which
you clicked the Log button (or executed the Log macro command).


I will bet that the group will be glad when today is over :)

Not at all, Jim. Providing answers to questions is one of the fundamental
purposes of this group. .

73,

Dave, AA6YQ


BEGIN MACRO Request or Did I Miss This Also?

 

Situation: Click on spot or find station in pile up and start entry (enter
call sign) in WW. I then use TAB to see if I should proceed with chasing the
station. The QSO Started At Date/Time appears in red above call sign in WW.

Problem: I don't always get the station for several minutes and when I do,
it is a mad click to hit the BEGIN button and then the F Key to send my
report.

Is there or can there be a <begin> macro that can be placed in a F Key
function to reset the start time of the QSO? I can't find one in the list of
macros.

This scenario happens in state QSO parties when I am chasing mobiles, etc.

I will bet that the group will be glad when today is over :)

73 - Jim - K8SIA


Re: New Feature or I Don't Click Enough Spots

 

Dave

Thanks, that cleared up my problem.

73 - Jim - K8SIA

-----Original Message-----
From: Dave AA6YQ [mailto:aa6yq@...]
Sent: Monday, September 07, 2009 3:51 PM
To: dxlab@...
Subject: RE: [dxlab] New Feature or I Don't Click Enough Spots

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Jim
Besancon
Sent: Monday, September 07, 2009 3:41 PM
To: dxlab@...
Subject: RE: [dxlab] New Feature or I Don't Click Enough Spots


Dave and All


Answering: By " it populates WW and creates an entry in DXK", I assume you
mean "It
populates WinWarbler's 'QSO Info' panel and DXKeeper's Capture window".

No, I don't use the Capture Window. I had it active until yesterday but
found I never used it so I closed it. It populates DXK "Log QSO/Entry"
Window. If I have had a previous Q with the station it shows the previous Q
and places a red entry line in the log window. If no previous Q, then only a
red entry line in the DXK "Log Entry Window".

On the General tab of DXKeeper's Config window, uncheck the Options
panel's "New QSO on DX Spot activation" box.

73,

Dave, AA6YQ



------------------------------------

Yahoo! Groups Links


Re: free off-site backup

 

For what it's worth . . . I've used the free 2GB Mozy service for several months. Seems to me that it works as advertised.

Like Dave, I have no affiliation with Mozy other than being (so far) a satisfied user.

Steve K8JQ

Dave AA6YQ wrote:

Awhile back, I mentioned that I'd begun using "SOS Online Backup", an
off-site backup application that charges $20 annually for 2 GB of offline
storage and $30 annualy for 5 GB of offline storage. I set this up to
perform daily backups on my DXLab Development, Digital Photography, and XYL
PCs. While all of these systems are backed up nightly to a server, my data
was still vulnerable to a single catastrophe.

Unfortunately, "SOS Online Backup" has problems. The "client" application
that runs on each PC has resource leaks, takes forever to start up (around 2
minutes on my DXLab PC), and doesn't accurately report the amount of storage
in use. When I reported these problems to the company, they eventually sent
me a new version of the client that while improved in some dimensions is far
less reliable; it's great if you're a collector of stack traces.

I have begun evaluating Mozy (www.mozy.com) and find it to be both reliable
and useable. Initially, I was put off by the fact that files within

c:&#92;program files

could not be selected for backup, but there's a configuration option that
overrides this. The free version of Mozy gives you 2 GB -- likely more than
enough for your email, personal documents (not images), and log files. In

<>

and look for the "MozyHome Free" box along the left margin.

For those needing more than 2 GB, unlimited storage will cost you $5/month
for one PC.

I have no affiliation with Mozy beyond being a satisfied (so far) user.

73,

Dave, AA6YQ



------------------------------------

Yahoo! Groups Links




--
Read The Patriot Post
hppt://PatriotPost.US/Subscribe/ Vetitas vos Liberabit