Perfectly explained, I know just what to do now, thanks and to you and all
responders. The thought was running through my mind that it may not matter,
and you confirmed it. Sorry for using so much time and BW, I think we can
close this one now,

73
----- Original Message ----- 
From: "K2DBK - David" <[EMAIL PROTECTED]>
To: "Donald Eriksen" <[EMAIL PROTECTED]>
Cc: "Rick Murphy" <[EMAIL PROTECTED]>; <dx4win@mailman.qth.net>
Sent: Monday, October 06, 2003 8:50 PM
Subject: Re: [Dx4win] LoTW exports


> Here's what's confusing you: On most Windows systems (Windows 95, 98, ME,
> 2000, XP), there is usually an application "associated" with a file type.
> For example, files that end in .XLS are normally Microsoft Excel
> spreadsheets. Double-clicking on an .XLS file will load that file into a
> copy of Excel and start running it. As a side effect of this, often the
> application's icon will get associated with the file type. Closer to home,
> the .DXL filetype is associated with DX4WIN so it has the DX4WIN logo
> associated with .DXL icons, and double-clicking on a .DXL file will start
> up a copy of DX4WIN using that logfile.
>
> What's apparently happened on your system is that Writelog is the
> application "associated" with ADIF files (those that end in .ADI), so
> double-clicking the exported file starts a copy of Writelog, and loads in
> that file. That's obviously not what you want to do.
>
> Fortunately, the associated file type is only what amounts to a
> "suggestion", so you can load an ADIF file into anything that will accept
it.
>
> What you want to do here (and as someone else already suggested) is not to
> double-click on the exported ADIF file, but to start your copy of TQSL,
and
> tell it to sign the already-existing ADIF file. That will result in a .TQ8
> file, which is what gets sent to the LoTW for processing. You can't just
> upload a plain ADIF file, it needs to be signed and compressed first.
>
> If that previous paragraph didn't make sense to you (especially the part
> about running TQSL), you should go to www.arrl.org/lotw and check out the
> "Getting Started" link, which will hopefully get you on the right track.
>
> (If you're really stuck, email me off the list and I'll try to walk you
> through the steps.)
>
> At 11:30 PM 10/6/2003, Donald Eriksen wrote:
> >I did export from dx4win into a file (not WriteLog)using the ADIF
exchange
> >format, the first export option. However the Writelog logs were imported
> >originally INTO dx4win using the WriteLog ADIF export, apparently there's
> >something I don't understand about that process. I think dx4win is doing
the
> >right thing.
> >Perhaps I'll have to query the WriteLog reflector and see if anyone is
> >getting the same results, I know a lot of them are using dx4win.
> >
> >------ Original Message -----
> >From: "Rick Murphy" <[EMAIL PROTECTED]>
> >To: "Donald Eriksen" <[EMAIL PROTECTED]>; "K2DBK - David"
> ><[EMAIL PROTECTED]>
> >Cc: <dx4win@mailman.qth.net>
> >Sent: Monday, October 06, 2003 8:02 PM
> >Subject: Re: [Dx4win] LoTW exports
> >
> >
> > > At 10:52 PM 10/6/2003, Donald Eriksen wrote:
> > > >I think I wasn't too clear as to what my problem was. I did exactly
the
> > > >steps outlined below, David (and others), I just saved it to a
location
> >to
> > > >try out the process before going on with the LoTW upload process.
> > > >What confuses me is that the file saved as a WriteLog ADI file (has
the
> >WL
> > > >symbol) and when I open the file, it opens WriteLog and I get a
message
> > > >"Invalid File Format".
> > >
> > > OK, why WriteLog? Maybe this is a stupid question, but I don't
> > > understand why you're using that format. LOTW accepts ADIF and
Cabrillo
> > > and the default DX4WIN export format is ADIF. Export your log in ADIF
> > > format and it'll work. In my DX4WIN installation, it's the first
export
> > > format, labelled "ADIF exchange format".
> > >          -Rick
> > >
> >
> >_______________________________________________
> >Dx4win mailing list
> >Dx4win@mailman.qth.net
> >http://mailman.qth.net/mailman/listinfo/dx4win
>
>
> 73,
> David - K2DBK
>

Reply via email to