¿ªÔÆÌåÓý

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

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


free off-site backup

 

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


Re: 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".

73 - Jim - K8SIA

-----Original Message-----
From: Dave AA6YQ [mailto:aa6yq@...]
Sent: Monday, September 07, 2009 2:31 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 2:12 PM
To: dxlab@...
Subject: [dxlab] New Feature or I Don't Click Enough Spots


Being a slow and damp day, I have been more active playing with the DXLab's
features than normal. I discovered something I don't recall happening before
and that is when I click on a spot it populates WW and creates an entry in
DXK. The problem is no matter what I do, I can't clear the entry in DXK and
end up logging the Q. After logging the Q in DXK, I go and delete the entry.
Kind of a pain but now I know where the odd contacts are coming from.

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". To
clear the Capture window without logging a QSO, click the Clear button in
its lower-right corner, or strike CTRL-W (for Wipe).

If I've misunderstood your question, please elaborate...
73,

Dave, AA6YQ



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

Yahoo! Groups Links


Re: WAC report

Phil Cooper
 

Hi again Dave,

Yes, I see your point, but I read that statement to mean that ANY DXCC
entities already CREDITED for the DXCC program can be utilised in the
application.

As far as I can make out (and this is where the ARRL statement could be
misconstrued!) the important part is:
"Applicants who have a current DXCC award in the DXCC computer system can
apply for WAC by completing the WAC application form ........"

By that I assume they mean that if I have (for example) AA6YQ verified as my
DXCC entity on each band in LoTW, then I can claim that call for use in the
WAC application, as it is verified as a DXCC entity, and also counts for NA
in WAC.
Now, as I do NOT have AA6YQ listed in my DXCC list for W, then I cannot use
it to claim WAC for NA, even if it were a good match in LoTW.

To get my SQL statement, I had to use QSL_Rec'd (LoTW and Paper) ='v' and
='s' (but not 'y')!!

I plan to submit my claim using all DXCC credits, including a few that are
verified via LoTW, but I may just send them an email first to query that
staement.
I'll let you know what happens.

73 all

Phil GU0SUP


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


Re: CW with WinWarbler, a 746Pro, and a Rigblaster Plug and Play interface

 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
john.w6hw
Sent: Monday, September 07, 2009 1:04 PM
To: dxlab@...
Subject: [dxlab] Re: CW with WinWarbler, a 746Pro, and a Rigblaster Plug
and Play interface


Dave, I'd like to bring up the question from WC5M again (Message 65183)
While there isn't a CI-V command to send CW via the transceiver Remote Jack,
the RIGblaster Plug & Play USB interface has a separate CW output that is
controlled by the serial port DTR line. (The P&P CW output is connected to
the IC-746 KEY jack.) Since Commander is already able to control the DTR
line, shouldn't CW be possible from WinWarbler without needing another
serial port?

Yes. The challenge is that only one application can open a serial port,
so Commmander must be extended to appropriately wiggle the DTR line. My
original plan was to replicate WinWarbler's CW generator in Commander (I
can't simultaneously remove the CW generator from WinWarbler, as some ops
use WinWarbler without Commander). Then I had the bright idea of making
WinWarbler convey the dots and dashes to Commander via DDE (the interprogram
communication mechanism used by DXLab applications). Unfortunately, this
experiment was a failure: DDE couldn't handle the command rate. Using
Windows Messages instead of DDE to convey the dots and dashes from
WinWarbler to Commander would definitely work, but this approach would make
both WinWarbler and Commander far more difficult to maintain (no
breakpoints). I'm planning to migrate interprogram communication from DDE to
TCP/IP; DXKeeper now accepts some commands via TCP/IP, for example. When
this TCP/IP capability reaches WinWarbler and Commander, I'll try conveying
dots and dashes from WinWarbler to Commander via TCP/IP to see if that
works. If not, then replicating the CW generator as originally planned would
be the only option.

While all of this has been happening, products like MicroHam's have
introduced virtual serial ports that make eliminating the need for a second
port for CW less urgent a requirement.

73,

Dave, AA6YQ


Re: CW with WinWarbler, a 746Pro, and a Rigblaster Plug and Play interface

 

John,

The answer is "no." Commander (which handles the CAT/CI-V
interface) and WinWarbler (which does the CW) are separate
programs. The Windows system architecture (as well as DOS
before it and CP/M before that, etc.) allows only one
program to access a serial port and by extension a USB to
serial converter at a time.

When WinWarbler gets frequency and mode information from the
radio, it is asking Commander for that information using DDE
(Dynamic Data Exchange) between programs. Unfortunately the
DDE process is not fast enough for Winwarbler to "flip the
DTR bit" with enough precision to generate CW by DDE. In
order to have WinWarbler generate CW through Commander,
Dave would need to build a CW generator into Commander and
then talk to it as if it were an external keyer ... a lot
of work (and time critical routines) for relatively little
functionality.

73,

... Joe, W4TV

-----Original Message-----
From: dxlab@... [mailto:dxlab@...] On
Behalf Of john.w6hw
Sent: Monday, September 07, 2009 1:04 PM
To: dxlab@...
Subject: [dxlab] Re: CW with WinWarbler, a 746Pro, and a
Rigblaster Plug and Play interface


Dave, I'd like to bring up the question from WC5M again
(Message 65183) While there isn't a CI-V command to send CW
via the transceiver Remote Jack, the RIGblaster Plug & Play
USB interface has a separate CW output that is controlled by
the serial port DTR line. (The P&P CW output is connected to
the IC-746 KEY jack.) Since Commander is already able to
control the DTR line, shouldn't CW be possible from
WinWarbler without needing another serial port?

Thanks & 73, John W6HW

--- In dxlab@..., "Dave Bernstein" <aa6yq@...> wrote:

With an Icom transceiver, CW generation from WinWarbler requires a
separate serial port; you can't use the serial port used for
transceiver control for CW generation.

73,

Dave, AA6YQ




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

Yahoo! Groups Links



Re: SC and WW Questions

 

+++More AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Jim
Besancon
Sent: Monday, September 07, 2009 2:16 PM
To: dxlab@...
Subject: RE: [dxlab] SC and WW Questions


Dave wrote:

No. I was concerned that carrying over a filter from the previous
operating session might cause a user to miss needed DX. - I guess that
would be my problem and not yours :).

+++The tradeoff is pretty clear: one mouse click at SpotCollector startup to
manually re-instate the desired filter vs. potentially missing an all-time
new one...

snip<
DXLab does not explicitly set the memories of any transceiver. - I guess
what I was asking is there a way to have WW open silently? That is just
open the RTTY window when RTTY is clicked and not direct CC to do anything ?

+++That would require the user to remember that WinWarbler hadn't directed
Commander to put the transceiver on the correct frequency in the correct
mode, and later manually direct WinWarbler to do this. I don't believe this
increase in user-perceived complexity is justified; as I pointed out in an
earlier post, Commander provides memories that you can use instead of your
transceiver's memories.

73,

Dave, AA6YQ


Re: 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 2:12 PM
To: dxlab@...
Subject: [dxlab] New Feature or I Don't Click Enough Spots


Being a slow and damp day, I have been more active playing with the DXLab's
features than normal. I discovered something I don't recall happening before
and that is when I click on a spot it populates WW and creates an entry in
DXK. The problem is no matter what I do, I can't clear the entry in DXK and
end up logging the Q. After logging the Q in DXK, I go and delete the entry.
Kind of a pain but now I know where the odd contacts are coming from.

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". To
clear the Capture window without logging a QSO, click the Clear button in
its lower-right corner, or strike CTRL-W (for Wipe).

If I've misunderstood your question, please elaborate...
73,

Dave, AA6YQ


Re: SC and WW Questions

 

Dave wrote:

No. I was concerned that carrying over a filter from the previous
operating session might cause a user to miss needed DX. - I guess that
would be my problem and not yours :).

Add B (with no slash) to the Special Callsign list with no tag. - Works
great, thanks.

DXLab does not explicitly set the memories of any transceiver. - I guess
what I was asking is there a way to have WW open silently? That is just
open the RTTY window when RTTY is clicked and not direct CC to do anything ?

73 - Jim - K8SIA

-----Original Message-----
From: Dave AA6YQ [mailto:aa6yq@...]
Sent: Sunday, September 06, 2009 2:45 PM
To: dxlab@...
Subject: RE: [dxlab] SC and WW Questions

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Jim
Besancon
Sent: Sunday, September 06, 2009 2:18 PM
To: dxlab@...
Subject: [dxlab] SC and WW Questions


Good Afternoon

Two SC Questions:

1-Can SC be configured to save the last filter I was using? I have
SC set so the filter buttons are off the screen, so at every startup I
need to move things around to activate 'my' filter.

No. I was concerned that carrying over a filter from the previous
operating session might cause a user to miss needed DX.

2-Eliminating Beacon '/B' stations. I know this has been covered and
I have set /B as an invalid call sign, but they just keep on coming.
Any information would be appreciated.

Add B (with no slash) to the Special Callsign list with no tag.

One WW Question:

1- My radio (FT1000D) has two memories per band for the main VFO. I
generally keep one memory in the CW portion and the other in the RTTY
portion of any given band. Now using 20M as an example, one memory is
14025 CW and the other is 14085 FSK RTTY. The question/problem is when I see
a RTTY spot, I switch to the RTTY memory and listen for the station. If
the station is heard, I set the mode on the radio to LSB (AFSK RTTY) and
then click the RTTY mode button in WW. At this point, WW sets both memories
to the RTTY LSB frequency, there by destroying my ability to quickly go back
to CW. Is there a set up or button pushing sequence that will just set
WW to RTTY, open up the RTTY screen and do nothing with the memories on the
radio?

DXLab does not explicitly set the memories of any transceiver; whatever
changes to your FT1000D's memories are occuring are the transceiver's
response to being instructed to QSY to a particular frequency an mode.

You can configure SpotCollector so that when you see CW, phone, PSK, or
RTTY spot database entry of interest, all you need do is double-click that
entry; WinWarbler's QSO Info window will be appropriately initialized with
information from the spot database entry, and WinWarbler will direct
Commander to QSY to the appropriate frequency and mode so that operation can
begin immediately (e.g. if the frequency of a RTTY or PSK spot database
entry is accurate, WinWarbler will immediately begin displaying decoded
characters.

To do this, open the General tab of SpotCollector's Config window and
- in the "Actions with Digital Mode Application connected" panel, check the
Service column's Digital, CW, and SSB boxes

- in the "Digital Mode Application" panel, ensure that the Name is set to
WinWarbler

73,

Dave, AA6YQ



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

Yahoo! Groups Links


New Feature or I Don't Click Enough Spots

 

Being a slow and damp day, I have been more active playing with the DXLab's
features than normal. I discovered something I don't recall happening before
and that is when I click on a spot it populates WW and creates an entry in
DXK. The problem is no matter what I do, I can't clear the entry in DXK and
end up logging the Q. After logging the Q in DXK, I go and delete the entry.
Kind of a pain but now I know where the odd contacts are coming from.

Any clues or advice?

73 - Jim - K8SIA


Re: A query about the WPX report

 

The WPX award program has some "interesting" rules for computing prefixes
from callsigns; see section 3 in

<>

In particular, note part C of that section: "Example: LX/WN5N would count as
LXO"

To determine what callsigns are responsible for your 1BO and 1KO prefixes,
run the "CQ WPX" panel's Submission report; it lists a callsign for each
prefix. If you think that one or more prefixes have been computing
incorrectly, please let me know and I'll take a look.

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Phil
Cooper
Sent: Monday, September 07, 2009 11:43 AM
To: dxlab@...
Subject: [dxlab] A query about the WPX report


Hi again!

After checking my WAC tally, I also decided to check my WPX progress.
After running the report, it produces a nice list of prefixes.

My query is that it shows I have worked prefixes that I cannot find in my
log!
For example, it shows I have worked 1B0 and 1K0, but no such calls exist.
I know I have the right SQL expression, as filtering for a known good call
works OK - I used CY9.
So, how come I end up with prefixes like 1B0 and 1K0 that are clearly not
valid, and do not appear to be in my log?

And one final thought...........
Would it be useful to have a call (or calls??) listed for these prefixes in
the WPX list?
The WPX application form has to show call, date, time, band, mode etc, but
the WPX report doesn't really provide this info.
As I have over 1000 WPX's, it does get a little tiresome having to filter
the log for each WPX, QSL received etc.

73 for now

Phil GU0SUP




---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 090906-1, 06/09/2009
Tested on: 07/09/2009 16:42:58
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: WAC report

 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Phil
Cooper
Sent: Monday, September 07, 2009 11:36 AM
To: dxlab@...
Subject: [dxlab] RE: WAC report


Hi all,

Larry W6NWS quoted the ARRL site................
"... At the present time credits in the ARRL LogBook of The World (LoTW)
system cannot be claimed for WAC credit. Applicants who have a current DXCC
award in the DXCC computer system can apply for WAC by completing the WAC
application form and sending it to the address noted above, listing credits
to be claimed on the application form. In this case QSL cards are not
required. ...."

I did find the above statement a little confusing at first, but it implies
that LoTW credits that are now part of your DXCC claim CAN indeed be used.

I'm dubious. There's been a ton of pressure on the ARRL to support more
awards with LotW. If WAC were now supported by LotW, we'd have seen a press
release. You can configure DXKeeper to "count" LotW confirmations when
generating a WAC progress report; I'm not going to "hardwire" this untill I
see a press release.


So, I thought I would do a search and see what I came up with. It took a
while to get the proper SQL function, but I got there in the end.
The confusing bit was having to remember to use both the LoTW QSL Received
and also the QSL Received functions for all of S and V.
But, after a few goes, I got it right, and found that I do indeed have
enough DXCC credits to claim 5BWAC - all on RTTY.

You can do this by checking the "include LotW confirmations in VUCC, WAC,
& Maidenhead progress" box at the top of the Config window's Awards tab
before initiating the WAC progress report.


Another point for those wishing to check whether they have 5BWAC, you must
also filter the log for each band as well as filtering for QSL's verified.
I just entered the SQL expression in the ADV boxes, and then changed the
band after each click of the WAC progress button. Save the resulting file as
something like WAC-80m and you are away!

You could create a script to generate a WAC progress report for each
band. The MultiWAS.txt file in DXKeeper's Scripts folder illustrates the
technique.

73,

Dave, AA6YQ


Re: 'lock DXV' during card checking

 

Thanks to all who responded to Bill's post below.

For those wondering why their DXView never updates automatically, Bill has
"Automatic DXView lookup" enabled on the General tab of SpotCollector's
Config window. This means that each time a new Spot Database Entry is
created, SpotCollector directs DXView to perform a lookup on the entry's
callsign so that he can see whether or not he needs it (Bill is chasing all
the entity-band-mode combinations).

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
FireBrick
Sent: Monday, September 07, 2009 10:31 AM
To: DXLabs List
Subject: [dxlab] 'lock DXV' during card checking


Reading the Daily DX, I saw a mention about some qsl manager change.
I entered the callsign in the filter box in DXK and selected DXCC so that
DXV would tell me if that band/mode qso was confirmed.

But before I could read all the W' C' V's a cluster spot came in and changed
DXV to a different entity.

Is there a way to click a 'Hold' button or stop DXV from changing it's
entity/callsign display?

Say a X minute timer that will return DXV to normal?


TOWER/WEBCAMS and Weather Page
@



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

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: Stopping Programs

 

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



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

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: Erratic function of Commander 5.8.7

 

+++More AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
ben frantzac
Sent: Monday, September 07, 2009 8:05 AM
To: dxlab@...
Subject: RE: [dxlab] Re: Erratic function of Commander 5.8.7



Are you saying thaI the Windows Control Panels' "Add/Remove
Programs"applet >>>>doesn't show Commander in its list of installed
programs? On the
Launcher's Main window, what color is the LED-like display above the CMD
button?

When I installed version 5.8.7 first, it accordingly made an entry to
Control Panels Add/Remove. When version 5.8.7 started creating problems I
removed it using the same
"Add/Remove Programs" and the program was removed correctly.

+++Removing a DXLab application with the intention of re-installing it is
almost always a bad idea. It very rarely solves the problem at hand, but can
destroy useful evidence and risks confusing Windows.


After that I installed just 792Update (Zip file755kt) as such. When I
unzipped that file, it created the same files as 5.8.7 without the actual
set up. In other words it was ready after unzipping. But it behaved
erratically.

+++As Rich W3ZJ pointed out, this is way out of bounds. You uninstalled
Commander, loaded a few files, and tried to run one of them.


So I cleaned the registry from everything found with names "Commander" and
"DXLab" After that unzipping 792Update I got a working Commander. But no
entry of it in "Add/remove".

+++There's no entry for Commander in Add/Remove because you haven't
installed Commander. I'm frankly surprised that Commander is working.


I did not install DXLab Launcher at all so I cannot say anything about its
main window. Maybe that was the reason to problems?

+++There is nothing wrong with installing DXLab applications manually,
although using the Launcher is a lot less work (one mouse click per
application). However, you do have to follow the instructions.

73,

Dave, AA6YQ


Re: Losing Contact With Commander

 

Your initial report stated that at some point, "Commander did not 'follow'
the radio". This is the time to enable "log debugging info" for a minute or
two, then disable it and send me the resulting errorlog.txt file. I just
need to see what commands are being sent to your K3, and how your K3 is
responding to those commands.

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
aburkefl
Sent: Monday, September 07, 2009 8:00 AM
To: dxlab@...
Subject: [dxlab] Re: Losing Contact With Commander


Not exactly certain how to engage this scenario. If I turn on "log
debugging" and don't lose control, you'll learn nothing. If I work for a
while and then discover I've lost contact with Commander, that won't help
either, will it?

How large can the file get before it will give you problems? I could turn
debugging on first thing and then run as normal as possible (at least as
normally as I've been running!), but the debugging file might get kind of
large.

Art - N4PJ

--- In dxlab@..., "aa6yq" <aa6yq@...> wrote:

AA6YQ comments below
--- In dxlab@..., "aburkefl" <aburkefl@> wrote:

At times, I've changed bands on my K3 and then discovered that Commander
did not "follow" the radio. Terminating and restarting Commander generally
"cures" the problem - for a while. I'm using a microHAM USB interface and
when Commander loses contact with the K3, I can see that the Router still
maintains contact with the K3 (patched).

At this point, I can only assume that some other program running in the
background is creating some kind of conflict.

Windows won't let more than one application open the same serial port.
The next time this happens, please enable "log debugging info" on the
Config window's General tab, wait a minute, disable "log debugging info",
and then attach the errorlog.txt file from your Commander folder to an email
message to me at aa6yq@... . The errorlog will include Commander's
directives to your K3 and the K3's responses, so I'll be able to see what's
going on.


I can't remember the name or source of one of those programs that will
stop all unnecessary applications and let only the minimum of programs.

Dave, right off the top of your head, is the OCX a potential problem?
Once I tried to start something running involving the MARAC Logger while
DXLabs was also running. Could there be a potential conflict if the two are
battling for the OCX?

There are many .ocx modules; to which one(s) are you referring?
73,

Dave, AA6YQ



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

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/06/09
05:51:00


Re: 'lock DXV' during card checking

FireBrick
 

Yes, I've been manually 'Verifying' some old cards from the boxes.
Pre DXLab days.
so I wasn't thinking 10 minute timer but maybe 3 or 5.
But a 'REsume' button...I'd probably forget to hit it and wonder why the DXV wasn't changing. LOL

On 9/7/2009 9:53:34 AM, Bob Main (bobmain1@...) wrote:
How about along with the timer a "Normal" button so in case you zone out
and
forget to change back to normal it will do it automatically? That way if
you are finished after a minute or two you
don't have to wait another 5
minutes before it switches back.



Bob

KB4Cl



_____

From: dxlab@... [mailto:dxlab@...] On Behalf Of
FireBrick
Sent: Monday, September 07, 2009 10:31 AM
To: DXLabs List
Subject: [dxlab] 'lock
DXV' during card checking





Reading the Daily DX, I saw a mention about some qsl manager change.
I entered the callsign in the filter box in DXK and selected DXCC so that
DXV would tell me if that band/mode qso was confirmed.

But before I could read all the W'
C' V's a cluster spot came in and changed

DXV to a different entity.

Is there a way to click a 'Hold' button or stop DXV from changing it's
entity/callsign display?

Say a X minute timer that will return DXV to normal?

TOWER/WEBCAMS and Weather Page
@ . <> webhop.org


Re: 'lock DXV' during card checking

FireBrick
 

Damn Dave is good, he installed my request before I requested it......

And that Flashing 'Locked' should work to remind me to 'unlock'.
So won't need the timer....LOL LOL

Damn he's good....

On 9/7/2009 10:21:21 AM, aburkefl (aburkefl@...) wrote:
In DXView, look down toward the lower right-hand corner of the window,
just above "DXCC" where it says "SC Lock." Click in the window to set
"focus" on the DXView window and hover your mouse cursor over the button
that says "SC Lock."

Just in case your "mouse cursor messages" are turned off, that button will
"lock" DXView and temporarily ignore any incoming spots from SpotCollector
- until you turn it off (actually, I guess
you'll be turning it back on!) when you so choose - then SC will again change as spots arrive.

Art - N4PJ

--- In dxlab@..., "FireBrick" <w9ol@...> wrote:

Reading the Daily DX, I saw a mention about some qsl manager change.
I entered the callsign in the filter box in DXK and selected DXCC so that
DXV would tell me if that band/mode qso was confirmed.

But before I could read all the W'
C' V's a cluster spot came in and changed
DXV to a different entity.

Is there a way to click a 'Hold' button or stop DXV from changing it's
entity/callsign display?

Say a X minute timer that will return DXV to normal?


T


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


Re: Stopping Programs

 

The second sentence in the 4th paragraph of my response below is erroneous;
it should begin

"You do not need to restart immediately..."

This information is now accessible via "Getting Started with DXLab" in the
"Windows Tricks" section:

<>

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Dave AA6YQ
Sent: Monday, September 07, 2009 12:42 PM
To: dxlab@...
Subject: RE: [dxlab] Stopping Programs


AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
aburkefl
Sent: Monday, September 07, 2009 7:58 AM
To: dxlab@...
Subject: [dxlab] Stopping Programs


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

I don't know of an application that will automatically determine what
programs and services shouldn't be running and terminate them.

Once a program is running, it should ideally be shut down in an orderly
fashion. For "interactive" programs, that means clicking the red X button in
the upper-right corner, finding and executing a "shutdown" menu entry (e.g.
File:Exit), or in the case of DXLab applications, by directing the Launcher
to send a message directing them to terminate. For a service that Windows is
running in the background, you can terminate it in an orderly fashion by
running the Services manager (Windows Control panel, Administrative Tools),
right-clicking the service of interest, and selecting the Stop menu item.

You can use the Windows Task Manager to immediately terminate any running
process by right clicking the process and selecting the "End Process" item,
but the shutdown will not be "orderly", and so can have negative
consequences. Its not always obvious what process name is associated with
the application you're trying to terminate; Google likely-looking process
names until you find the right one (measure twice, cut once!).

If you know what programs you've started, its generally easy to stop them
in an orderly manner. Somewhat more challenging is to discover what programs
and services Windows has started on its own. Directing Windows to run
MSCONFIG will start the "System Configuration Utility", whose Startup tab
displays a list of all programs that Windows is automatically starting. Each
entry includes a (possibly cryptic) "Startup Item", the command used to
start the program, and the "location" responsible for the startup; the
location will either be a pathname in the Windows Registry, or the words
"Common Startup". Unchecking the box to the left of the "Startup Item" will
prevent that item from being started the next time you boot Windows. The
System Configuration Utility's Services tab provides a similar list of
Services; unchecking the box to the left of a Service will prevent that
Service from being started the next time you boot Windows.

When you use the System Configuration Utility to disable the startup of
one or more programs or services and then terminate the System Configuration
Utility, it informs you that "you must restart your compute for some of the
changes made by System Configuration to take effect", and offers you the
opportunity to Restart. You need to restart immediately, though the programs
and services you disabled will continue to run until you reboot, or
terminate them individually as described above. Each time you reboot
Windows, you'll be informed that the System Configuration Utility is
preventing certain applications and services from running. The only way to
eliminate this nuisance is to re-enable the disabled entries in the System
Configuration Utility and then permanently disable them by deleting their
entries in the Windows Registry or Startup Folder; the former is not
recommended unless you are proficient with the Windows Registry Editor AND
have taken the precaution of directing Windows to create a Restore Point
beforehand. Once false move in the Windows Registry Editor can render your
system unbootable.

73,

Dave, AA6YQ





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

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