Date   

Re: Spotcollector VE7CC connect

iain macdonnell - N6ML
 

Art,

It appears that for this to work properly, the callsign suffix used in
the SpotCollector source must be the same as the one used in CCUser. I
suspect the SpotCollector is looking at the prompt text for a matching
callsign. It appears that you have one configured as "K6XT-10" and the
other as "K6XT-2"

~iain / N6ML

On Fri, Jan 28, 2011 at 5:34 PM, Art K6XT <k6xt@...> wrote:
I'm (trying to) use VE7CC as a spot source using VE7CC program telnet
server so I have also the handy by-band view in VE7CC.

In this discussion I'm renaming Spotcollector's VE7CC window to xyl's
call W0MOE to avoid confusion. VE7CC means the actual VE7CC program.
W0MOE means Spotcollector's VE7CC window.

VE7CC telnet is ON, port 7300.

SC is set to 127.0.0.1 as instructed, also port 7300. I can see various
spots in W0MOE window. However they're not showing in SC's main display
window.

A secondary, perhaps connected, issue is SC's Spot Sources Hide button
is uniquely (other windows work 'right') partially inoperative. It will
expand SC's W0MOE window but not contract it as the others do. And its
LED is permanently yellow although the spots are showing up just as they
do in VE7CC program window.

Tertiarily, if thats a word, every few minutes W0MOE reconnects itself
to VE7CC, having suffered a "K6XT command error". Typical text shown below.

W0MOE outgoing spots are correctly routed to the VE7CC program and sent
out to the world.

Skimmer server is connected to port 7300 as well. Skimmer spots are
correctly displayed. I changed VE7CC and W0MOE to 7302, this made no
difference in the situation. And I think the number of connections is
unlimited.

Any hints what is happening to the invisible W0MOE spots?

[K6XT Command error. Note, these spots in W0MOE window do not appear in
Spotcollector's main window but they should.]
Hello >
DX de WA2AOG: 24892.0 VP8ORK wkd up 1 1723Z
DX de N3DG: 14013.0 FM/AI5P 1723Z
DX de K1CP: 24892.0 VP8ORK up 1 Tnx 1726Z
K6XT command error
K6XT-10 de VE7CC-1 28-Jan-2011 1725Z CCC >
*** Connected to: CC User
K6XT-10 de VE7CC-1 28-Jan-2011 1725Z CCC >
Welcome to CC User
Please enter your call:
login:
K6XT-2
K6XT-2 de VE7CC-1 >
Hello >
DX de EA1EYG: 21024.0 VP8ORK 1st call 2 up low but clear TU 1728Z
--

73 Art
Allison, Colorado
    A glass is good, and a lass is good,
  And a pipe to smoke in cold weather;
The world is good, and the people are good,
  And we ’re all good fellows together.
          John O’Keefe
Happy New Year!




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

Yahoo! Groups Links




Spotcollector VE7CC connect

Art K6XT <k6xt@...>
 

I'm (trying to) use VE7CC as a spot source using VE7CC program telnet
server so I have also the handy by-band view in VE7CC.

In this discussion I'm renaming Spotcollector's VE7CC window to xyl's
call W0MOE to avoid confusion. VE7CC means the actual VE7CC program.
W0MOE means Spotcollector's VE7CC window.

VE7CC telnet is ON, port 7300.

SC is set to 127.0.0.1 as instructed, also port 7300. I can see various
spots in W0MOE window. However they're not showing in SC's main display
window.

A secondary, perhaps connected, issue is SC's Spot Sources Hide button
is uniquely (other windows work 'right') partially inoperative. It will
expand SC's W0MOE window but not contract it as the others do. And its
LED is permanently yellow although the spots are showing up just as they
do in VE7CC program window.

Tertiarily, if thats a word, every few minutes W0MOE reconnects itself
to VE7CC, having suffered a "K6XT command error". Typical text shown below.

W0MOE outgoing spots are correctly routed to the VE7CC program and sent
out to the world.

Skimmer server is connected to port 7300 as well. Skimmer spots are
correctly displayed. I changed VE7CC and W0MOE to 7302, this made no
difference in the situation. And I think the number of connections is
unlimited.

Any hints what is happening to the invisible W0MOE spots?

[K6XT Command error. Note, these spots in W0MOE window do not appear in
Spotcollector's main window but they should.]
Hello >
DX de WA2AOG: 24892.0 VP8ORK wkd up 1 1723Z
DX de N3DG: 14013.0 FM/AI5P 1723Z
DX de K1CP: 24892.0 VP8ORK up 1 Tnx 1726Z
K6XT command error
K6XT-10 de VE7CC-1 28-Jan-2011 1725Z CCC >
*** Connected to: CC User
K6XT-10 de VE7CC-1 28-Jan-2011 1725Z CCC >
Welcome to CC User
Please enter your call:
login:
K6XT-2
K6XT-2 de VE7CC-1 >
Hello >
DX de EA1EYG: 21024.0 VP8ORK 1st call 2 up low but clear TU 1728Z
--

73 Art
Allison, Colorado
A glass is good, and a lass is good,
And a pipe to smoke in cold weather;
The world is good, and the people are good,
And we ’re all good fellows together.
John O’Keefe
Happy New Year!


O.T. DM780 question

Tom Provost <ag2a@...>
 

I am using dm780 bridged to the dxlab suite (for everything except digital). I needed to load a new copy of version 4.1 after a hard drive problem. Everything is working okay but for one thing. I use to hover the cursor over a call sign in the received window and a text bubble would appear with log data on that station,if worked before and if so what bands. If I have worked the station before,it shows the check mark after the call but no text. If I haven't worked the call before it should show DXCC entity and whether we worked before and what bands. I can't find any option that will add this text bubble. Any ideas out there?
tOm AG2A


LOTW question

wb5aaa <wb5aaa@...>
 

What to with QSO's that has been uploaded to LOTW
by DXkeeper but after several days it still has
a "U" in the sent box?


Thought

Paul M Dunphy
 

Dave,

With SpotCollector, clicking on the call QSYs the rig to the right QRG and mode and pre-loads DXK, etc.

How about ctrl+click or alt+click launching your browser with the QRZ.COM lookup? VE7CC's CC User program does this, and sometimes it can be useful to just look at their QRZ write up -- for many reasons -- without actually going to their frequency and loading DXKeeper with everything.

I picked QRZ.COM as that seems to be where most people are putting stuff these days. Maybe another call book server would be just as good, or ctrl takes you to one and alt to another. Even could expand this to the spotter -- that is useful because if the W1 is really in Florida, it can explain apparent oddities in propagation.

Maybe all of this is available in PathFinder. I don't use it because I have an XML subscription to QRZ. Is this worth considering?

73, Paul VE1DX


Newbie in digital modes (RTTY)

ik2rpe@...
 

I'm a newbie on digital modes and I would like to have an help on how to configure ports on Commander and WinWarbler.
Ports has to be different or same in the two programs Commander (Ports)and WinWarbler(PTT for RTTY)?
The problem is that I cannot go through in RTTY tx, but I do receive RTTY and Commander properly switches me in the different frequencies/bands. Ports have to be "linked" in a way?
What am I doing wrong?
Thanks in advance for any help.

Carlo IK2RPE


Re: LOTW questions

Ken - K4XL
 

On Fri, Jan 28, 2011 at 12:25 AM, Dave AA6YQ <aa6yq@...> wrote:

+++ More AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Kenneth Grimm
Sent: Thursday, January 27, 2011 12:18 AM
To: dxlab@...
Subject: Re: [dxlab] LOTW questions


On Wed, Jan 26, 2011 at 11:20 PM, Dave AA6YQ <aa6yq@...> wrote:

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Kenneth Grimm
Sent: Wednesday, January 26, 2011 10:38 PM
To: dxlab
Subject: [dxlab] LOTW questions


I was lucky enough to work ST2AR the other night on 160. I logged the
QSO
in DXKeeper and it showed previous QSOs with ST2AR with a yellow
background,
indicating LOTW. However, the 160 contact does not have the yellow
background. I looked up ST2AR on QRZ.com and it shows "direct only to
S53R." When I looked up S53R on QRZ.com, it says that ST2AR QSOs have
been
uploaded to LOTW. So that is one puzzle. The question I am most
interested
in though is why the background isn't yellow for the 160 contact? Is the
LOTW database now being corrected for stations who no longer indicate
that
they are using LOTW?

A lookup of ST2AR in DXView shows that this station is a known LotW
participant, and last uploaded on 2010-12-25.

With your 160m QSO selected, is the "LotW Member" box checked in the
"Online QSL" panel on the Main window's "Log QSOs" tab?
No, the box has nothing in it. Earlier QSOs with the yellow background do
have a Y in the box. However, this must have automagically been added as I
certainly have never never manually entered anything in this box.

When you're logging QSOs via the Capture window, whether or not that
QSO's "LotW Member" item is set to 'Y' depends on the state of the Capture
window's "LotW member" checkbox when you click the Capture window's Log
button; if it's checked, then the QSO's "LotW Member" item is set to 'Y',
otherwise, it isn't.

There are several ways that the Capture window's "LotW member" box can
be
checked:

1. by clicking it with your mouse (clicking it when checked will un-check
it)

2. by typing in a callsign and initiating a Lookup operation, or by
double-clicking a callsign in SpotCollector's Spot Database Display
Aha! I can't say for sure, but I would guess that I typed ST2AR in the
Capture window, initiated a QRZ.com lookup while QRZ.com was touring the
galaxy.



2a. if DXKeeper's "Display previous QSOs on Lookup" option is enabled, then
the Lookup operation will inspect each previous QSO with the callsign; if
the "LotW Member" item in any previously-logged QSO is set to 'Y', then the
Capture window's "LotW member" box will be checked
Now it gets mysterious. I do have "Display previous QSOs on Lookup"
checked.



2b. if DXView is running, DXKeeper will direct DXView to query the LotW
Database; if the callsign is listed in the LotW Database, then the Capture
window's "LotW member" box will be checked

Note that if 2a or 2b above results in the Capture window's "LotW
member"
box being checked but you click the "LotW member" box, this will uncheck
the
"LotW member" box; if you then click the Capture window's Log button, the
QSO will be recorded with it's "LotW Member" item not set to 'Y'.

If you discover a case where step 1 above is not correctly checking the
Capture window's "LotW member" box (or is incorrectly checking this box),
please

1. clear the Capture window

2. on the Configuration window's General tab, check the "Log Debugging
Info"
box

3. repeat the steps that resulted in the Capture window's "Lotw member" box
not being properly set

4. on the Configuration window's General tab, uncheck the "Log Debugging
Info" box

5. attach the errorlog.txt file from your DXKeeper folder to an email
message and send it to me at aa6yq (at) ambersoft.com
I haven't seen a recurrence of the problem, but if I do, I'll follow your
instructions. Thanks.

73,

Ken



Thanks!
73,

Dave, AA6YQ



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

Yahoo! Groups Links




--
Ken - K4XL
BoatAnchor Manual Archive
BAMA - http://bama.edebris.com


Re: Collecting/Displaying eQSL cards

Richard B Drake
 

All eQSL's are either .gif or .jpg files, those are the only two graphic
formats that work with the image processor that Dave Morris is using.
Occasionally we have a problem when a user submits a custom image that
is either in the a wrong format or is way too big and in that case eQSL
may return an error message instead of an image. We can usually fix that
but would need to know specific callsigns to find the accounts with
corrupt card images. I checked the 9W2RZL card in Charles' Archive, it
is a stock image and displays fine. I am forwarding a copy of this to
Dave Morris for his comments.

73, Rich - W3ZJ

Dave AA6YQ wrote:

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Charles Brasell
Sent: Thursday, January 27, 2011 7:55 PM
To: dxlab@...
Subject: [dxlab] Collecting/Displaying eQSL cards


Hi Dave,

While checking some confirmed eQSLs in DXK the other day I clicked to
display the card from 9w2rzl (which has been confirmed) and it came up not
found. Going to the eQSL folder I found I have a bunch of confirmations
stored as MHTML documents, all the others are jpeg's. I am wondering how
this bunch got there. (they will display the card by double clicking the
file) Is it something I have done/not done?? I usually initially display the
cards by clicking display on the eQSL website.


I wasn't aware that eQSL was responding to requests for QSL images using
MHTML instead of JPEG. Rich W3ZJ, can you shed light on this?


While talking eQSL, I am still confused with the double negative statement,
"Don't upload QSO's whose station callsign isn't the specified Username"
My eQSL Username is ZL4DX, under which I have 4 accounts, 2 of which have
the callsign ZL2DZ, all in the same DXK log. While using ZL4DX I am still
occasionally entering up old logs.


The grammatically-challenged "Don't upload QSO's whose station callsign
isn't the specified Username" may no longer be correct given the the
subsequently added support for eQSL Nicknames. Rich, can you confirm this?

Should the DXK QTHID be changed when uploading?
Where should I look to find QTH Nickname? (I can't remember if I entered one
or not)


If you have defined Nicknames in eQSL, then each QSO you upload to eQSL
should be uploaded with the appropriate Nickname specified. You can do this
by

1. specifying a "QTH Nickname" on the "QSL Configuration" window's eQSL tab

or

2. checking the "Use each QSO's myQTHID as its QTH Nickname when uploading
or exporting" box on the the "QSL Configuration" window's eQSL tab (assuming
you've defined and assigned myQTHIDs that match the Nicknames you've defined
in eQSL)

73,

Dave, AA6YQ



DXView Ctrl-enterturns rotor on low bands

Chuck, WS1L
 

My usualy method of checking calls for need has been to enter them in the
capture window and then see what DXView has to say. I recently decided to
try entering the call in DXView and control-entering. This should give me a
propagation lookup as well as a callbook lookup and populate the capture
window. It does all that, but it also turns my rotor to the proper heading.


All well and good, but the rig was on 160, and the beam is not that big!

So, I checked DXView config, made sure rotor control was set to only accept
directives for 20-10 meters. It was.

I guess DXView doesn't know what band I'm on, so it turns the rotor. I like
the ability to get everything ready for a station, but turning the rotor
this way and that might be a bit much. I see shift-enter does a qrz lookup.

Is there a way to get the benefits of qrz, propagation, and capture pre-fill
without the rotor needlessly hunting? Priority for me would be:

Capture pre-fill
rotor if 20-10 meters
Propagation
qrz lookup

Not a big deal, and others may use the features differently so may have
different needs.

73 de Chuck, WS1L

--


===================
Chuck Chandler
chandlerusm@...
===================


DxKeeper and CTRL+C

it9fga <it9fga@...>
 

Hi to all,

CTRL+C not working into DXKeeper fields...wht not enabling this feature?

73's de

Giuseppe, IT9FGA


DxKeeper 9.2.7

it9fga <it9fga@...>
 

Hi to all,

after log a qso, I can modify all fields except ADDRESS..sam on your side ?

73's de

Giuseppe, IT9FGA


Re: SC

eddy on5jk
 

Dave,
Depressing CTRL key togheter with the X button in the SC-Filter Panel transfers ALL of the Spots into the SC-window.
INCLUDING CW-Spots and others. Whitch i don't need.
Earlier i used to stay in SC with the ""Band and Mode"" filter on (only clicking X in the SC-Filter Panel).
And then the << SH/DX F >>button (macro) shows all the Spots from <F> in the Source-window.
Then the Spots from the Source-window , that corresponds with my setting > Band and Mode< in the SC-MainWindow,where automaticly transferred into the SC-Main Window.Thus giving me all of the wanted Spots from France,in SSB and Band as defined in my Band &Mode settings.
Thanks for your quick answering.

ON5JK

----- Original Message -----
From: Dave AA6YQ
To: dxlab@...
Sent: Friday, January 28, 2011 1:12 AM
Subject: RE: [dxlab] SC



>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
eddy on5jk
Sent: Thursday, January 27, 2011 7:36 AM
To: YahooGroup DXLabs
Subject: [dxlab] SC

Dave,
Once again i've got a problem.
When opening the window from EA7URC,i ask via a Macro or direct commando
f.i. SH/DX F
Then the spots from "F" populate that window.
But the spots are not transferred to the Spotcollector main-window.Although
it used to go that way in better times.
I did propose you the same problem a long time ago.
Any suggestion?

>>>On SpotCollector's Main window, depress the CTRL key while clicking the
the Filter panel's X button. Then try typing SH/DX F in a spot source
window; do the results now appear in SpotCollector's Main window?

73,

Dave, AA6YQ


Updated eQSL AG and LotW Databases are available...

Dave AA6YQ
 

...via the Databases tab of DXView's Configuration window.

73,

Dave, AA6YQ


Re: Collecting/Displaying eQSL cards

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Charles Brasell
Sent: Thursday, January 27, 2011 7:55 PM
To: dxlab@...
Subject: [dxlab] Collecting/Displaying eQSL cards


Hi Dave,

While checking some confirmed eQSLs in DXK the other day I clicked to
display the card from 9w2rzl (which has been confirmed) and it came up not
found. Going to the eQSL folder I found I have a bunch of confirmations
stored as MHTML documents, all the others are jpeg's. I am wondering how
this bunch got there. (they will display the card by double clicking the
file) Is it something I have done/not done?? I usually initially display the
cards by clicking display on the eQSL website.

I wasn't aware that eQSL was responding to requests for QSL images using
MHTML instead of JPEG. Rich W3ZJ, can you shed light on this?


While talking eQSL, I am still confused with the double negative statement,
"Don't upload QSO's whose station callsign isn't the specified Username"
My eQSL Username is ZL4DX, under which I have 4 accounts, 2 of which have
the callsign ZL2DZ, all in the same DXK log. While using ZL4DX I am still
occasionally entering up old logs.

The grammatically-challenged "Don't upload QSO's whose station callsign
isn't the specified Username" may no longer be correct given the the
subsequently added support for eQSL Nicknames. Rich, can you confirm this?

Should the DXK QTHID be changed when uploading?
Where should I look to find QTH Nickname? (I can't remember if I entered one
or not)

If you have defined Nicknames in eQSL, then each QSO you upload to eQSL
should be uploaded with the appropriate Nickname specified. You can do this
by

1. specifying a "QTH Nickname" on the "QSL Configuration" window's eQSL tab

or

2. checking the "Use each QSO's myQTHID as its QTH Nickname when uploading
or exporting" box on the the "QSL Configuration" window's eQSL tab (assuming
you've defined and assigned myQTHIDs that match the Nicknames you've defined
in eQSL)

73,

Dave, AA6YQ


Re: Spot collector missing spots

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
wb2nvr
Sent: Thursday, January 27, 2011 11:12 AM
To: dxlab@...
Subject: [dxlab] Re: Spot collector missing spots


I did have the AH filter active, and it hid one spot - with ???? in the
notes. I unchecked both boxes in the AH filter, with no change. LOTW was
not checked, and eQSL is not check (or activated).

Control X this morning shows FR5ZL. Searching for the call FR5ZL yields
nothing; clicking X also does not show FR5ZL. FR5ZL was spotted on 7,012 CW
and is DMN in my SpotCollector panel as an unworked Band/Mode.

Any other clues?

Please do the following
1. on the General tab of SpotCollector's Configuration window, check the
"Log Debugging Info" box

2. in the Main window's Filter panel, type FR5ZL into the textbox and click
the Call button

3. on the General tab of SpotCollector's Configuration window, uncheck the
"Log Debugging Info" box

4. terminate SpotCollector

5. place the Spots.mdb file from SpotCollector's Databases folder and the
Errorlog.txt file from your SpotCollector folder into a zip archive, attach
this zip archive to an email message, and send it to me at aa6yq (at)
ambersoft.com so I can see what's going on.

Thanks...

73,

Dave, AA6YQ


Re: LOTW questions

Dave AA6YQ
 

+++ More AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Kenneth Grimm
Sent: Thursday, January 27, 2011 12:18 AM
To: dxlab@...
Subject: Re: [dxlab] LOTW questions


On Wed, Jan 26, 2011 at 11:20 PM, Dave AA6YQ <aa6yq@...> wrote:

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Kenneth Grimm
Sent: Wednesday, January 26, 2011 10:38 PM
To: dxlab
Subject: [dxlab] LOTW questions


I was lucky enough to work ST2AR the other night on 160. I logged the QSO
in DXKeeper and it showed previous QSOs with ST2AR with a yellow
background,
indicating LOTW. However, the 160 contact does not have the yellow
background. I looked up ST2AR on QRZ.com and it shows "direct only to
S53R." When I looked up S53R on QRZ.com, it says that ST2AR QSOs have
been
uploaded to LOTW. So that is one puzzle. The question I am most
interested
in though is why the background isn't yellow for the 160 contact? Is the
LOTW database now being corrected for stations who no longer indicate that
they are using LOTW?

A lookup of ST2AR in DXView shows that this station is a known LotW
participant, and last uploaded on 2010-12-25.

With your 160m QSO selected, is the "LotW Member" box checked in the
"Online QSL" panel on the Main window's "Log QSOs" tab?
No, the box has nothing in it. Earlier QSOs with the yellow background do
have a Y in the box. However, this must have automagically been added as I
certainly have never never manually entered anything in this box.

When you're logging QSOs via the Capture window, whether or not that
QSO's "LotW Member" item is set to 'Y' depends on the state of the Capture
window's "LotW member" checkbox when you click the Capture window's Log
button; if it's checked, then the QSO's "LotW Member" item is set to 'Y',
otherwise, it isn't.

There are several ways that the Capture window's "LotW member" box can be
checked:

1. by clicking it with your mouse (clicking it when checked will un-check
it)

2. by typing in a callsign and initiating a Lookup operation, or by
double-clicking a callsign in SpotCollector's Spot Database Display

2a. if DXKeeper's "Display previous QSOs on Lookup" option is enabled, then
the Lookup operation will inspect each previous QSO with the callsign; if
the "LotW Member" item in any previously-logged QSO is set to 'Y', then the
Capture window's "LotW member" box will be checked

2b. if DXView is running, DXKeeper will direct DXView to query the LotW
Database; if the callsign is listed in the LotW Database, then the Capture
window's "LotW member" box will be checked

Note that if 2a or 2b above results in the Capture window's "LotW member"
box being checked but you click the "LotW member" box, this will uncheck the
"LotW member" box; if you then click the Capture window's Log button, the
QSO will be recorded with it's "LotW Member" item not set to 'Y'.

If you discover a case where step 1 above is not correctly checking the
Capture window's "LotW member" box (or is incorrectly checking this box),
please

1. clear the Capture window

2. on the Configuration window's General tab, check the "Log Debugging Info"
box

3. repeat the steps that resulted in the Capture window's "Lotw member" box
not being properly set

4. on the Configuration window's General tab, uncheck the "Log Debugging
Info" box

5. attach the errorlog.txt file from your DXKeeper folder to an email
message and send it to me at aa6yq (at) ambersoft.com

Thanks!
73,

Dave, AA6YQ


Re: Cannot get SpotCollector to Work on New Computer

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
John Bastin
Sent: Thursday, January 27, 2011 11:10 PM
To: dxlab@...
Subject: Re: [dxlab] Re: Cannot get SpotCollector to Work on New
Computer



On Jan 27, 2011, at 21:33:08, Jim wrote:

I received an email from Danny Douglas suggesting that I had perhas set my
computer clock wrong. I checked and I had adjusted the time to local but
had the time zone wrong. What superior help!

One of the members of our local DX group was having similar problems with
Spot Collector that he told me about at our monthly meeting this week. I
gave him all the possible causes and told him, "be sure to check your
computer clock to make sure it's right." He replied, "I'm sure it's correct,
but I'll check it again."

I got an e-mail from him this evening, his clock had the right numbers but
it was set for AM instead of PM, he was 12 hours off. Needless to say, he
wasn't seeing much in Spot Collector.

Never rule out the simple things; check your clock when Spot Collector is
blank...:-)

A full list of things that can prevent SpotCollector's Spot Database
Display from being populated can be found in

<http://www.dxlabsuite.com/dxlabwiki/EmptyDatabase>

73,

Dave, AA6YQ


Re: Cannot get SpotCollector to Work on New Computer

John Bastin <jbastin@...>
 

On Jan 27, 2011, at 21:33:08, Jim wrote:

I received an email from Danny Douglas suggesting that I had perhas set my computer clock wrong. I checked and I had adjusted the time to local but had the time zone wrong. What superior help!
One of the members of our local DX group was having similar problems with Spot Collector that he told me about at our monthly meeting this week. I gave him all the possible causes and told him, "be sure to check your computer clock to make sure it's right." He replied, "I'm sure it's correct, but I'll check it again."

I got an e-mail from him this evening, his clock had the right numbers but it was set for AM instead of PM, he was 12 hours off. Needless to say, he wasn't seeing much in Spot Collector.

Never rule out the simple things; check your clock when Spot Collector is blank...:-)

73,

John K8AJS
jbastin@...


Re: Cannot get SpotCollector to Work on New Computer

Jim <jimstuder@...>
 

I received an email from Danny Douglas suggesting that I had perhas set my computer clock wrong. I checked and I had adjusted the time to local but had the time zone wrong. What superior help!

73,

Jim S

--- In dxlab@..., "Jim" <jimstuder@...> wrote:

I just built a new Intel I7 machine running Windows 7 64-bit. I've installed other programs such as N1MM logger with no trouble. However, when I installed DXLab suites on the new computer everything runs well with one exception. Spot Collector is giving me trouble. It can contact the DX spotting services and spots scroll by as you watch. When I click on any of the green dots that show you're connected to a spot source, I see tons of spots. I've tried Control X and the display says "No Filters", I've tried ininstalling the program, deleting the subdirectory that it was in, and reinstalling the software, ahd still nothing shows up. I've spent two days massing with this and it's got me stumped. It's worked fine on my XP machine for almost a year with no trouble. Can anyone think of any reason that the spots would show up in the individual spot windows but none of them make to the main screen? I really need help with this.

73,

Jim S


Cannot get SpotCollector to Work on New Computer

Jim <jimstuder@...>
 

I just built a new Intel I7 machine running Windows 7 64-bit. I've installed other programs such as N1MM logger with no trouble. However, when I installed DXLab suites on the new computer everything runs well with one exception. Spot Collector is giving me trouble. It can contact the DX spotting services and spots scroll by as you watch. When I click on any of the green dots that show you're connected to a spot source, I see tons of spots. I've tried Control X and the display says "No Filters", I've tried ininstalling the program, deleting the subdirectory that it was in, and reinstalling the software, ahd still nothing shows up. I've spent two days massing with this and it's got me stumped. It's worked fine on my XP machine for almost a year with no trouble. Can anyone think of any reason that the spots would show up in the individual spot windows but none of them make to the main screen? I really need help with this.

73,

Jim S

120201 - 120220 of 208946