¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. DXLab
  2. Messages
Expanded Topics Messages Polls
Date
Re: upgrading launcher

 

Whatever you do, "DON'T" just delete files from the launcher installation folder without first uninstalling it via add/remove programs in the control panel. To do so would remove the uninstall information and leave you with a much more difficult problem to correct. That's true of any installed program.

Assuming that the path name you gave is correct in accordance with the location where you initially installed Lanucher 1.5.2, there should be a file named "launcheragent.exe" there. If it's not there, apparently something didn't go right with the initial installation. Dave should be on-line a little later so let's wait for him to suggest the appropriate action. I just wanted to get this out quickly to hopefully avoid the above far more serious mistake. The good news is that If you have successfully installed other DXLab applications, they should not be affected by this problem.

73, Rich - W3ZJ

At 03:49 PM 8/30/2007, you wrote:

tried to upgrade launcher 1.5.2. clicked config, clicked upgrade to
upgrade to 1.5.5, downloaded data then window said "launcher agent is
missing from c:\program files\dxlab suite\launcher\launcheragent.exe".
should I delete dxlab launcher and reinstal it? If I do will I keep
everything I already have?
upgrading launcher

 

tried to upgrade launcher 1.5.2. clicked config, clicked upgrade to
upgrade to 1.5.5, downloaded data then window said "launcher agent is
missing from c:\program files\dxlab suite\launcher\launcheragent.exe".
should I delete dxlab launcher and reinstal it? If I do will I keep
everything I already have?
Re: alarm on Pathfinder 4.4.6

 

Errors in scripts can only come from the web page that Pathfinder is
attempting to display.

From the URL, Pathfinder is searching QRZ.com. The correct URL is

{TargetCallsign}

which is a bit different than what you show below.

Are you able to search sites other than QRZ.com without seeing script
errors?

73,

Dave, AA6YQ


--- In dxlab@..., "Danny Douglas" <n7dc@...> wrote:

I keep getting a pop up alarm when using Pathfinder: :
An error has occured in the script on this page
line 249
char 1
error object expected code 0
url ;database?callsign=(((callsign I have
requested))))

No matter if I say to continue or not to continue to use the script-
the web
site comes up with the proper response information.

When I go direct to qrz, I dont get the alarm.
This has been happening since I downloaded 4.4.6
Re: For those needing more serial ports

Earl Needham
 

--- In dxlab@..., "Bill Allen" <wallenpb@...> wrote:

Dan,

I use the F5U409 USB to Serial adapter by Belkin. It is available from
Staples and other dealers for about $20. I use it for both the serial
connectivity to my K2 and my Rigblaster Pro. It works very well and
supports ALL the RS232 serial lines. I know other hams using this
adapter
as well, nothing but glowing reports.

73,
Bill - WA5PB
OK -- I need to know if this is the Belkin F5U409-CU or the
F5U409V1. I'm going to try to order one if I can verify which one is
the right one.

Thanks,
Earl

KD5XB -- Earl Needham
Clovis, New Mexico DM84jk

Quoting from the Coast Guard: ZUT
Re: alarm on Pathfinder 4.4.6

 

I have a similar problem with AWS Weatherbug. Whenever I go to the radar display and ask to enlarge or animate the display I get that script error. It's very strange because it doesn't matter whether I say continue or don't continue, it continues anyway and nothing seems to be wrong. It seems to be a Windows thing and thus far I haven't been able to track it down. If anyone has the solution I'lI be eternally grateful. However, I have not had any problem with QRZ.com and Pathfinder 4.4.6.

73, Rich - W3ZJ

At 09:12 AM 8/30/2007, you wrote:

I keep getting a pop up alarm when using Pathfinder: :
An error has occured in the script on this page
line 249
char 1
error object expected code 0
url ;database?callsign=(((callsign I have requested))))

No matter if I say to continue or not to continue to use the script- the web
site comes up with the proper response information.

When I go direct to qrz, I dont get the alarm.
This has been happening since I downloaded 4.4.6
alarm on Pathfinder 4.4.6

Danny Douglas
 

I keep getting a pop up alarm when using Pathfinder: :
An error has occured in the script on this page
line 249
char 1
error object expected code 0
url ;database?callsign=(((callsign I have requested))))

No matter if I say to continue or not to continue to use the script- the web
site comes up with the proper response information.

When I go direct to qrz, I dont get the alarm.
This has been happening since I downloaded 4.4.6
Re: Dxlab and Multipsk?

Ken Bandy
 

Graeme, I see Dave has answered the technical questions relating to Multipsk
and DXLab integration. I'll add my personal preference to the mix.
WinWarbler is my "default" PSK and RTTY application. I am much more used to
the operation of WinWarbler, with the macros, seamless operation with other
DXLab apps and GUI layout. I use MultiPSK for the more "exotic" modes that
WinWarbler doesn't do. MultiPSK is a great piece of software, and I
appreciate the work Patrick has put in to it. It can be a bit overwhelming,
though. So many modes to choose from, hi.

73,
Ken
KC9GLQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...] On Behalf Of
zl1gbb
Sent: Wednesday, August 29, 2007 10:37 PM
To: dxlab@...
Subject: [dxlab] Dxlab and Multipsk?


Hi
I have the full suite of Dxlab set up. I have seen some references to
using Multipsk with it. Just what is involved with using Multipsk and
Dxlab? Do you use it in place of Winwarbler or along side it? Is the
log feature useable between both programs? I know Commander can be used
by Multipsk. Is data (e.g. log contacts etc.) transferred between
programs?

Graeme zl1gbb
Re: Dxlab and Multipsk?

zl1gbb
 

Thanks Dave
Strangely enough there is another fella with your name and callsign
over on the Multipsk group who answered this question with the same
answer. :)
Off hand, I don't think Spot Collector is going to be much use to me
but time may prove me wrong. Maybe I may find a DX spotter over in VK
which I can use it for.
The rest looks very usefull.

Graeme zl1gbb

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

1. if Commander is running, MultiPSK uses it to track your and to
change your transceiver's frequency and mode

2. if DXKeeper is running and you log a QSO in MultiPSK, the QSO
will
be recorded in DXKeeper

3. if SpotCollector is configured to use MultiPSK as its digital
mode
application (Config window, General tab, Interoperation panel),
then
if you double-click a digital mode Spot Database Entry,
SpotCollector
will convey the frequency and digital mode to MultiPSK, which will
configure itself to decode that mode and direct Commander to QSY
your
transceiver to the correct frequency and transceiver mode -- which
if
the spotted frequency is accurate results in decoded text from the
spotted station appearing in MultiPSK.

73,

Dave, AA6YQ


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

Hi
I have the full suite of Dxlab set up. I have seen some
references to
using Multipsk with it. Just what is involved with using Multipsk
and
Dxlab? Do you use it in place of Winwarbler or along side it? Is
the
log feature useable between both programs? I know Commander can
be
used
by Multipsk. Is data (e.g. log contacts etc.) transferred between
programs?

Graeme zl1gbb
Re: New laptop

Art K6XT
 

Rich
Turns out most of the units I see on Ebay use XP. Also new from Dell XP can be selected on any Latitude. I don't care much. PartitionMagic 8.0 takes care of Vista, will unhide the restore hidden partition as well so Vista would be truly gone. All necessary drivers are downloadable from Dell. So what op system comes with the PC isn't much of an issue. That ole Fdisk still works.

My 17" screens are likewise set to 1280x1024. It's about all the eyes are up for. So I've struck WUXGA from the must have list. OK if I get it because it can be throttled back to WSXGA+ but not desired. Also struck the shiny screens from the list (TrueLife at Dell). Reading the reviews what I see is a lot of comments about glare plus we do no video processing here and our only gaming has to do with radio. Outside of a hand at Doom 2 every 6 months for the target practice.

Thanks for your info.

73 Art

Richard B. Drake wrote:
Hi Art,
I am writing to you from a Dell Inspiron 8200 that's 4-5 years old. It too has a single serial port and also a line in jack to the sound chip. Two primary reasons for selecting this particular model. It is equipped with an Nvidia GetForce 2 Go that supports an external monitor as a second monitor in a dual monitor configuration. I use a Dell 19" flat panel as the second monitor and run both at 1280 X 1024. I didn't have to pay extra for that, it was standard in this model but It works great. So I have no hesitation in saying that should work out fine for you as it has for you. Bye the way get yourself a wireless notebook mouse which travels easily and disable the built in touch pad so that you don't accidently hit it while typing. It's nothing but a nuisance :-)

Can you get the D830 with WinXP or will you be stuck with Vista?

73, Rich - W3ZJ

At 01:55 PM 8/28/2007, you wrote:
[snip]
Re: New laptop

Art K6XT
 

Dave, thanks, good info.
My outgoing Latitude C610 does SXGA 1280x1024. That's about as small as I want it with my reading glasses on. If I can score a WUXGA at good price with the other goodies, fine, but I decided not to pay for more than WSXGA+.

Dell's had its hits lately on service as well. I don't have to spend much time on the service line unless some electronic part lets all the smoke out so am OK there. Last years model D820 is readily available on ebay and also from the Dell refurb site, first D8xx to use the 2 processor chip, I decided on that. The reviews say the two processor chip runs ordinary stuff about 1.5x faster than the equivalent cost P4M in the predecessor D810.

Huh...D810 to D820 to D830 encompasses about 1.75 years. Obsolete before sold. No future in buying new.

Tnx again
Art

Dave Bernstein wrote:

I haven't used a Dell Latitude in 5 years; they were fine then, but I found IBM Thinkpads a definite improvement. After my recent experience with Lenovo Thinkpads, however, I'll be looking at alternatives when the next upgrade cycle rolls around.

WUXGA is 1920 x 1200; I have run 1600 x 1200 on a 15" laptop (T42P), but found myself squinting a lot. It might be worth a trip to a well-
stocked computer store to try out some resolutions and screen sizes before making your decision.

73,

Dave, AA6YQ
Re: Dxlab and Multipsk?

 

1. if Commander is running, MultiPSK uses it to track your and to
change your transceiver's frequency and mode

2. if DXKeeper is running and you log a QSO in MultiPSK, the QSO will
be recorded in DXKeeper

3. if SpotCollector is configured to use MultiPSK as its digital mode
application (Config window, General tab, Interoperation panel), then
if you double-click a digital mode Spot Database Entry, SpotCollector
will convey the frequency and digital mode to MultiPSK, which will
configure itself to decode that mode and direct Commander to QSY your
transceiver to the correct frequency and transceiver mode -- which if
the spotted frequency is accurate results in decoded text from the
spotted station appearing in MultiPSK.

73,

Dave, AA6YQ


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

Hi
I have the full suite of Dxlab set up. I have seen some
references to
using Multipsk with it. Just what is involved with using Multipsk
and
Dxlab? Do you use it in place of Winwarbler or along side it? Is
the
log feature useable between both programs? I know Commander can be
used
by Multipsk. Is data (e.g. log contacts etc.) transferred between
programs?

Graeme zl1gbb
Re: New laptop

 

Hi Art,
I am writing to you from a Dell Inspiron 8200 that's 4-5 years old. It too has a single serial port and also a line in jack to the sound chip. Two primary reasons for selecting this particular model. It is equipped with an Nvidia GetForce 2 Go that supports an external monitor as a second monitor in a dual monitor configuration. I use a Dell 19" flat panel as the second monitor and run both at 1280 X 1024. I didn't have to pay extra for that, it was standard in this model but It works great. So I have no hesitation in saying that should work out fine for you as it has for you. Bye the way get yourself a wireless notebook mouse which travels easily and disable the built in touch pad so that you don't accidently hit it while typing. It's nothing but a nuisance :-)

Can you get the D830 with WinXP or will you be stuck with Vista?

73, Rich - W3ZJ

At 01:55 PM 8/28/2007, you wrote:

I'm getting a new laptop. Under consideration is a Dell Latitude, the
D830 (it has a serial port!). This thing would probably get integrated
into the station, displacing my desktop, if I can figure out a suitable
video display to replace the two 17" SXGA 1280x1024 screens I use now.
Would be great to get rid of the desktop fan noise.

One thought is to pay the $150 premium for WUXGA on the D830 and use one
of the present 17's on the external VGA port.

Any advice y'all can give (except 'get an apple') is welcome on any part
of this plan. I'm not married to the D830 idea, just been happy with the
previous Latitudes.

73 Art
Dxlab and Multipsk?

zl1gbb
 

Hi
I have the full suite of Dxlab set up. I have seen some references to
using Multipsk with it. Just what is involved with using Multipsk and
Dxlab? Do you use it in place of Winwarbler or along side it? Is the
log feature useable between both programs? I know Commander can be used
by Multipsk. Is data (e.g. log contacts etc.) transferred between
programs?

Graeme zl1gbb
Re: Winsock Error 10060 When Connecting Spotcollector?

 

Winsock error 10060 means "Connection timed out" -- A connection
attempt failed because the connected party did not properly respond
after a period of time, or established connection failed because
connected host has failed to respond.

If one of these appears in a spot source window while you're
attempting to connect to that spot source for the first time, you
probably have the host address or port specified incorrectly.

If you see these errors in all of your spot source windows, there's
an internet connectivity problem somewhere between your PC and your
ISP.

If you see this error in a single spot source window for a source
that's previously been connected with the current host address and
port -- as has been the case with DX Central today (for me, at
least) -- that spot source is either down or inaccessible.

73,

Dave, AA6YQ


--- In dxlab@..., Charles Schubert <chuckstalkie@...>
wrote:

I am getting Winsock Error 10060 when connecting
spotcollector?

What do you suggest?

Thanks in advance.

73 Chuck KI4HJH




______________________________________________________________________
______________
Be a better Heartthrob. Get better relationship answers from
someone who knows. Yahoo! Answers - Check it out.
Re: Pathfinder and DXKeeper

Rem Roberti
 

Ah-Ha! Thanks, Rich.

Rem
W6REM

Yes but be sure you are running PathFinder version 4.4.6. Recent
changes at QRZ.com required an update to PathFinder.

73, Rich - W3ZJ
Re: Winsock Error 10060 When Connecting Spotcollector?

Danny Douglas
 

Which spot sosurce are you getting that on? There can be several up at any
given time?

----- Original Message -----
From: "Charles Schubert" <chuckstalkie@...>
To: "DXLab DXLab" <dxlab@...>
Sent: Wednesday, August 29, 2007 9:24 PM
Subject: [dxlab] Winsock Error 10060 When Connecting Spotcollector?


I am getting Winsock Error 10060 when connecting
spotcollector?

What do you suggest?

Thanks in advance.

73 Chuck KI4HJH




____________________________________________________________________________
________
Be a better Heartthrob. Get better relationship answers from someone who
knows. Yahoo! Answers - Check it out.




Yahoo! Groups Links





--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.484 / Virus Database: 269.12.10/977 - Release Date: 8/28/2007
4:29 PM
Re: FYI LOTW

Ken Bandy
 

Yeah, I have to hand it to Kathy. We traded about a dozen or so emails over
the past week getting a club station on LoTW after I mucked up the original
application and some other stuff. She was very helpful. If this
"dissappearing QSL" snafu is something she can take care of, she will.

73,
Ken
KC9GLQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...] On Behalf Of JT
Croteau
Sent: Wednesday, August 29, 2007 8:14 PM
To: dxlab@...
Subject: Re: [dxlab] FYI LOTW


On 8/29/07, Art Searle W2NRA <w2nra@...> wrote:
BTW the last email I have gotten from Kathy Allison, KA1RWY, LotW
Specialist, was June 21st. I got no reply at all from my 2 subsequent
emails and a phone call.
Sorry to hear this. Kathy is usually VERY good at responding to
emails. However, I guess no one is immune to letting some emails slip
through the crack. I know I've been guilty of it and I used to live
and breath email as a Lotus Notes, cc:Mail, and Exchange administrator
for a few years.

--
JT Croteau, N1ESE - Manchester, NH
Re: 746 Pro and Commander

kg0ft1
 

I probably shouldn't say this -- I might be struck by lightning -- but
I think I'm beginning to get it. It works! Thanks for your patience.
And just so you know -- I DID read the manual. But I obviously missed
something somewhere.

Fred

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

Clicking one of Commander's "Sel" buttons activates a memory, which
sends its stored frequency and mode to your transceiver; the latter
operation disables data mode.

WinWarbler lets you specify 12 preset frequencies on the Config
window's General tab; you can then select a transceiver frequency
using the TX selector in the "Xcvr Freq" panel in the upper right
corner of WinWarbler's Main window -- without disabling data mode.
You can also use WinWarbler's macro buttons as memories that specify
a frequency, transceiver mode, and enable or disable data mode as
desired. By configuring the PSK, RTTY, CW, and Phone startup macros
to each load a mode-specific set of macros, you can have 32 macros
available in each operating mode -- a total of 128 macros.

73,

Dave, AA6YQ

--- In dxlab@..., "kg0ft1" <ffurland@> wrote:

I'm clicking one of the "select" buttons to transfer to the
frequency
assigned to that button.

I also set up a User Defined Command Sequence to turn on the data
mode. I get another error message -- Command: Tranceiver Command
rejected/Raw/29 August 200711:52:40

Fred


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

If you enable data mode, it remains enabled until you disable it.
Unless you also have <xcvrcommand: FEFE66E01A0601FD> in your PSK
startup macro, I assume that's why data mode remains enabled when
you
switch from RTTY to PSK.

When you say "when I change freq in Commander, data mode drops
out",
how are you changing frequency in Commander when this happens?

73,

Dave, AA6YQ





--- In dxlab@..., "kg0ft1" <ffurland@> wrote:

I have rtty set to AFSK, USB, and the xcvr mode is USB also.
And I
have the command <xcvrcommand: FEFE66E01A0601FD> as the RTTY
startup
macro. What I find interesting is that when I first go to RTTY
from
PSK31 in WW, the xcvr goes to data mode in USB. But when I
change
freq
in Commander, data mode drops out and I'm left in USB only.

And I just discovered that going to PSK from RTTY it does the
same
exact thing.

Fred


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

Well, that's progress -- at least you know the RTTY startup
macro
is
being executed.

What transceiver mode do you have WinWarbler configured to
use
when
you are operating RTTY? (On the Config window's RTTY tab, in
the "Modulation and transceiver mode" panel, which
combination of
AFSK/FSK and sideband have you selected, and to what is this
combination's "Xcvr Mode" selector set?)

73,

Dave, AA6YQ


--- In dxlab@..., "kg0ft1" <ffurland@> wrote:

For the first time, I got an error message box:

Commander: Transceiver command rejected
Set mode
29-Aug-2007 8:33:35

This happened when I put the data mode command you gave me
<xcvrcommand:FEFE66E01A0601FD> in the RTTY startup macro,
changed WW
to RTTY, and then changed freq in Commander.

By the way, I assume the 0 in the macro is a zero and not
the
letter o?

Fred


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

The correct command for placing your 746pro in Data mode
is

<xcvrcommand: FEFE66E01A0601FD>

I added this to my PSK startup macro (suitably modified
for
my
7800's
CI-V address) and it works correctly -- whenever I switch
to
PSK,
Data mode is enabled.

To disable data mode, use

<xcvrcommand: FEFE66E01A0600FD>

If this doesn't get you going, Fred, please let me know...

73,

Dave, AA6YQ

--- In dxlab@..., "kg0ft1" <ffurland@> wrote:

Still doesn't work. I've put a message on the 746Pro
group
to
see if
they can solve this.

Fred

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

There should not be spaces between the hex digits:

<xcvrcommand: FEFE66E01A16FD>

(I don't have a transceiver with me and so haven't
tested
this
specific command)

73,

Dave, AA6YQ

--- In dxlab@..., "kg0ft1" <ffurland@>
wrote:

I got WW to put the 746Pro into USB using
<xcvrmode:
usb>.

I can't get it into data mode, however. The manual
says
the
format
for
CI-V commands is -- FE FE 66 E0 Cn Sc FD.
FE FE is the preamble; 66 is the xcvr's default
address; E0
is
the
controller's default address; Cn is the command
number;
Sc
is
the
subcommand number; and FD is the ending.

The command number for send/read DATA mode is 1A.
The
subcommand
number is 06 -- 0=off; and 1=on.

I set it up to read -- <xcvrcommand: FE FE 66 E0 1A
16
FD>

Questions:

Did I write the xcvrcommand correctly?

Do I state the macro as <xcvrmode: usb>
<xcvrcommand:
FE FE
66
E0 1A
16 FD> all on one line?

Fred

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

Yes. Assuming you are using WinWarbler with
Commander,
you
can
establish a startup macro for PSK and/or RTTY
that
automatically
switches your transceiver when direct WinWarbler
to
begin
operating in
those modes. WinWarbler's <xcvrmode: usb> macro
command
will
place your
transceiver into USB mode. If the <xcvrmode>
command
doesn't
support
the mode you have in mind, you can use the
<xcvrcommand:
hexcmd>
macro
command to send any valid CI-V command.

If you need more details, let me know...

73,

Dave, AA6YQ

--- In dxlab@..., "kg0ft1"
<ffurland@>
wrote:

Is there anyway to get Commander to
automatically
put
this
rig
into
SSB
- digital mode? Instead of doing it manually?
(And
forgetting
to do so
most of the time and wondering why I'm not
heard?
Age-
related
problem
I'm afraid.)

Fred
Re: FYI LOTW

Art Searle W2NRA
 

Your example is even more serious than the changing QSLs. Who is Osten?

73 Art W2NRA
"Keep to the Code!"
w2nra.com

----- Original Message -----
From: "Danny Douglas" <n7dc@...>



Not a case of a QSL changing, but never showing a match:

Just last night, I did a Synch LOTW QSLs report, knowing I should
immediately get back 2 matches because tht 9Q1EK had just been uploaded to
them. Those two matches did not appear, although I had previously uploaded
my contacts. I simply changed the LOTW Send Y back to an R and again
uploaded them to LOTW, then did a Synch LOTW QSOs and QSLs and got an
immediate match. It made me wonder how many others I had uploaded, and for
which I never got a match back from them. Osten suggested I re-upload the
whole shebang, but at 24,044 QSOs I dont want to do that.

----- Original Message -----
From: "Dave Bernstein" <aa6yq@...>
To: <dxlab@...>
Sent: Wednesday, August 29, 2007 8:17 PM
Subject: [dxlab] Re: FYI LOTW


If the LotW development team doesn't get on top of this, I'll extend
the "Sync All LotW QSLs" operation to report any QSOs whose
LOTW_QSL_RCVD item is set to 'Y', 'S', or 'V" but is not reported as
confirmed in the information downloaded from LotW. This would be an
expensive option, but must faster than manual techniques.

73,

Dave, AA6YQ

--- In dxlab@..., Art Searle W2NRA <w2nra@...> wrote:

Hi Frank,

I have lost a total of 3 LotW QSLs over the last several months.
The only
answer I have gotten from my emails, phone calls and a personal
visit to
ARRL HQ was "We're working on it." Fortunately when you do a sync
in
DXKeeper it will NOT un-QSL any of your LotW QSL. So all you have
to do is
match your total number of LotW QSLs in DXKeeper to the total
number of LotW
QSLs on the LotW website to find out if you have any missing LotW
QSLs.

I can tell you that re-uploading the first 2 un-QSL'd LotW QSOs did
fix the
problem. I have been waiting for them to fix the last missing
QSL. BTW it
can be pretty difficult to figure out which one is missing. I did
it by
downloaded the full LotW QSL file from the LotW site and comparing
that
against my record of LotW QSLs in an EXCEL spreadsheet.

BTW the last email I have gotten from Kathy Allison, KA1RWY, LotW
Specialist, was June 21st. I got no reply at all from my 2
subsequent
emails and a phone call.

73 Art W2NRA
"Keep to the Code!"
w2nra.com
----- Original Message -----
From: "k8eew" <k8eew@...>


I seen an E-Mail on another reflector and this ham was wondering
why
his contact with E30NA changed from QSL to QSO, this is part of
the E-
Mail.





I apologize for the long delay in responding to your messge.

I checked the LoTW records and see that there should be a QSL
match
for your
10M QSO with E30NA.

LoTW has been experiencing issues with "changing" QSLs. From
what we
can
tell, it appears that if either party uploads the same QSL data,
sometimes
the QSL changes back to a QSO. The programmer is aware of this
and is
trying to fix it. The counter in the upper right corner may
also be
off.

You might want to try and sign & upload the one QSO for E30NA that
changed.
You can create a single QSO file by opening TQSL program and use
create an
ADIF file. Please follow the instructions and then sign the one
QSO. This
may reset the QSO back to a QSL.

We are sending the follow message to the LoTW users who have
experienced
some problems with their DXCC and WAS totals.

Due to some hardware communications issues, some LoTW users have
experienced
discrepancies in their QSL data as related to LoTW and paper QSLs.
Please be
assured that the QSOs are still in LoTW and all the data is
secure and
intact. The programmer is aware of these problems and is trying to
correct
them.

We will have it resolved soon. LoTW numbers may not jive with
recorded
data until the communications issues are resolved.

When the programmer gets these issues fixed, there will be a
reset of
the
entire LoTW system to correct the tallies. We apologize for the
inconvenience.

Again, I apologize for the delay in answering you.

Thank you for your participation.

73,

Kathy Allison KA1RWY
LoTW Specialist


ARRL - The national association for Amateur Radio
225 Main St
Newington CT 06111
Telephone: 860-594-0295



73, Frank, K8EEW
Winsock Error 10060 When Connecting Spotcollector?

 

I am getting Winsock Error 10060 when connecting
spotcollector?

What do you suggest?

Thanks in advance.

73 Chuck KI4HJH




____________________________________________________________________________________
Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out.

185861 - 185880 of 229185