Date   

Re: Cannot export Files to LoTW and eQSL

Rick Williams - VE7TK
 

Tony before throwing in the towel try a computer shut down and reboot.

73, Rick

On Tue, Jul 4, 2017 at 14:47, cr7wp2f3ps4pyumxzlkdktztoxvftpuzudhxwb7f@... [hamlogger]
wrote:
 

Jim,

Thanks for the time and trouble suggesting possible solutions.  I have tried everything, including entering sample qso's using another operator with the Send LoTW QSL checked.  The operator still does not show up in the selection box.  I'm the only operator in the logbook and the LoTW file upload process has been working flawlessly up until very recently.  I've been using Logger32 for more than 3 years now.  At this point, I'm afraid I may have to uninstall/reinstall.  As you mentioned, it may be a broken index.

Once I get this resolved, I'll post my findings.  Let's hope I can!!

Best 73
Tony KU4NY
 


Re: Cannot export Files to LoTW and eQSL

Gary Hinson
 

I agree: it’s not normally necessary to uninstall and reinstall the program itself.  

 

A full export to ADIF is well worth doing at least once a month anyway, as a log backup (save it safely offline e.g. on USB stick or CD reserved for that purpose).  Having done that anyway, opening a new logbook and importing the ADIF is no big deal provided you’re not in too much of a hurry (it takes a while to populate its internal database and calculate the statistics).

 

Hinson tip: if you do go down the reinstall route, I recommend saving offline copies of your .INI (and .ini) files first: they store your configuration – the screen and logbook layout, colours, port settings, macros, spot filters, alarms etc.  They are plain text files, editable with Notepad or TED.  Rarely, Logger32 issues can be caused by corruption or conflict in the .INI files (usually Logger32.INI for me), in which case individual sections from the saved .INI copies can be cut-n-pasted into the fresh default .INI files that Logger32 creates if they are missing, systematically testing at each stage until you find the broken section.  Alternatively, if your setup is fairly basic with most settings still at the defaults, it’s quicker and easier to forget your .INIs and just reconfigure a fresh Logger32 install manually from scratch.

 

73  GL!

Gary  ZL2iFB

 

From: hamlogger@... [mailto:hamlogger@...]
Sent: Wednesday, 5 July 2017 10:13 a.m.
To: hamlogger@...
Subject: RE: [hamlogger] Cannot export Files to LoTW and eQSL

 

 

Tony,

 

Exporting my entire log as an ADIF file and importing it to a new, clean logbook worked here. It's easy enough to try.

 

> Gerald, VE1DT

 

 

---In hamlogger@..., <cr7wp2f3ps4pyumxzlkdktztoxvftpuzudhxwb7f@...> wrote :

Jim,

 

Thanks for the time and trouble suggesting possible solutions.  I have tried everything, including entering sample qso's using another operator with the Send LoTW QSL checked.  The operator still does not show up in the selection box.  I'm the only operator in the logbook and the LoTW file upload process has been working flawlessly up until very recently.  I've been using Logger32 for more than 3 years now.  At this point, I'm afraid I may have to uninstall/reinstall.  As you mentioned, it may be a broken index.

 

Once I get this resolved, I'll post my findings.  Let's hope I can!!

 

Best 73

Tony KU4NY

 


Re: Cannot export Files to LoTW and eQSL

gboutin@...
 

Tony,

Exporting my entire log as an ADIF file and importing it to a new, clean logbook worked here. It's easy enough to try.

> Gerald, VE1DT


---In hamlogger@..., <cr7wp2f3ps4pyumxzlkdktztoxvftpuzudhxwb7f@...> wrote :

Jim,

Thanks for the time and trouble suggesting possible solutions.  I have tried everything, including entering sample qso's using another operator with the Send LoTW QSL checked.  The operator still does not show up in the selection box.  I'm the only operator in the logbook and the LoTW file upload process has been working flawlessly up until very recently.  I've been using Logger32 for more than 3 years now.  At this point, I'm afraid I may have to uninstall/reinstall.  As you mentioned, it may be a broken index.

Once I get this resolved, I'll post my findings.  Let's hope I can!!

Best 73
Tony KU4NY
 


Re: Cannot export Files to LoTW and eQSL

cr7wp2f3ps4pyumxzlkdktztoxvftpuzudhxwb7f@...
 

Jim,

Thanks for the time and trouble suggesting possible solutions.  I have tried everything, including entering sample qso's using another operator with the Send LoTW QSL checked.  The operator still does not show up in the selection box.  I'm the only operator in the logbook and the LoTW file upload process has been working flawlessly up until very recently.  I've been using Logger32 for more than 3 years now.  At this point, I'm afraid I may have to uninstall/reinstall.  As you mentioned, it may be a broken index.

Once I get this resolved, I'll post my findings.  Let's hope I can!!

Best 73
Tony KU4NY
 


Re: Interface IC-7600

Larry Fravel
 

Here is how I have mine set up:
 
COM3  (yours may be different)
 
Baud 9600
 
Data 8
 
Stop Bits 1
 
Parity None
 
Poling 500 MS
 
HEX  Address 7A
 
Boxes Ticked
 
Set DTR High
 
SET RTS High
 
Use Narrow CW Filter
 
ICOM Has Data ON/Off Control
 
Show VFO Split
 
Identity IC-7600
Larry K8YYY
 
It's easier to fool people than convince them that they've been fooled.
Mark Twain



AVG logo

This email has been checked for viruses by AVG antivirus software.
www.avg.com



Interface IC-7600

Ron Smith <n7rd@...>
 

Just wondering if anyone has had a problem interfacing the IC-7600 to the program.
I've been running a IC-756 Pro2 with it for years with no problems, but the IC-7600
seems to not like the connection or could be it don't like me.  Any help would be greatly
appreciated.

Tnx,
Ron N7RD


Cannot export ADIF file

nvjims@...
 

When I try to export my ADIF file, I get a popup starting Windows Installer that hangs and i have to exit the program using Task Manager.


I am also trying to get my data out using the LoTW in export files. I check the 'All Operators' in the popup and it then tells me 'There are no QSOs with All Operators flagged to be put in the LoTW file'...  It does not show my callsign in the popup, just the All Operators.  How do I flag the QSOs?


This is a new install with update since July 1, and I entered about 20 QSOs and changed the dates/times to correspond with the paper log.... I just want to get this data out so I do not need to retype everything.....


Jim, W6US


False positive

Jan
 

I just got this mail:




Greetings,

Thank you for contacting F-Secure.

We are writing with regards to the white-listing of logger32.exe

After monitoring it for some time now it has stayed white-listed.

If there is anything else we can help you with, please do not hesitate to contact us again.

Thank you.

Best regards,
Shem
Malware Analyst
F-Secure Security Labs
-- 
____________________________________________________
my dxspider clusters running on a raspberry pi:  
pa4jj-2 83.162.186.242 port 7300
pa4jj-3 83.162.186.242 port 7388


Re: Need to open port each time I get on

Gary Hinson
 

It could be that the relevant USB port is going to sleep: check the advanced port settings in Windoze (under device manager in control panel).

 

By default, many peripherals nod-off if they are neglected for too long.  As indeed do many L32 users.

 

73

Gary  ZL2iFB

 

PS  You can also open the radio port directly from the main screen without going though the setup menu – right click the “Radio 1” box on the lower status bar then “Open port – [radio name here]”.  The text in the box is red when no radio port is open, otherwise it’s blue.

 

From: hamlogger@... [mailto:hamlogger@...]
Sent: Tuesday, 4 July 2017 12:44 p.m.
To: hamlogger@...
Subject: [hamlogger] Re: Need to open port each time I get on

 

 

Doc

What is your radio ?
What is  your radio interface ?

73 de aki  ja1nlx



---In hamlogger@..., <weinerpr@...> wrote :

Whenever I open Logger 32, I need to do to setup/radio and open the port to allow me to see the frequency on my logbook entry. Any idea why this is happening? "Doc" VE3BZ


Re: Need to open port each time I get on

ayoshida@...
 

Doc

What is your radio ?
What is  your radio interface ?

73 de aki  ja1nlx


---In hamlogger@..., <weinerpr@...> wrote :

Whenever I open Logger 32, I need to do to setup/radio and open the port to allow me to see the frequency on my logbook entry. Any idea why this is happening? "Doc" VE3BZ


Need to open port each time I get on

weinerpr@...
 

Whenever I open Logger 32, I need to do to setup/radio and open the port to allow me to see the frequency on my logbook entry. Any idea why this is happening? "Doc" VE3BZ


Re: Cannot export Files to LoTW and eQSL - RESOLVED

Jim Hargrave
 

Gerald,

I’m glad you got it resolved



73, Jim – w5ifp@gvtc.com



From: hamlogger@yahoogroups.com [mailto:hamlogger@yahoogroups.com]
Sent: Monday, July 3, 2017 2:09 PM
To: hamlogger@yahoogroups.com
Subject: RE: [hamlogger] Cannot export Files to LoTW and eQSL - RESOLVED





Jim,



As usual, Bob is on top of the situation. The issue is resolved for me.



I had already followed all of the necessary steps and, as per Bob's evaluation, my logbook would appear to have a broken index.



I had also already tried "Recalculate Statistics" and "Reformat QSO numbers" and that did not fix the issue. However, a full export to ADI and import back into a new Logbook has resolved the issue.



Gerald, VE1DT




---In hamlogger@yahoogroups.com, <w5ifp@...> wrote :

Some further comments from K4CY:

"For me it works as expected. Double (and triple) check that the Operator callsign is what you think it should be for the QSOs you want to send to LoTW. Double (and triple) check the SEND LOTW QSOs flags are set for these callsigns.

Is the Logbook database broken? Export in ADIF Format. Change the Logbook to a new name (something like TESTLOG). Import the ADIF File into TESTLOG.

... but WAIT ... I just read this last paragraph again ... I also tried adding a new callsign as a test and entered a test QSO. The new callsign also does not show up in the "Only QSOs by" filter

It is NOT the callsign of the station you QSOd with that is added to the selection list. The selection list is a list of Operators who have QSOs in the Logbook with QSOs flagged for QSOs to be sent to LoTW.

Simply adding a new operator (VE150DT for example) then adding a dummy QSO with VE1DT will not add VE150DT to the export selection list. First the VE150DT QSO with VE1DT must be flagged as SEND LoTW QSL. Now VE150DT will show up on the export selection list ... If not, your Logbook probably has a broken index"

73, Jim – w5ifp@... <mailto:w5ifp@...>

-----Original Message-----
From: hamlogger@yahoogroups.com <mailto:hamlogger@yahoogroups.com>
[mailto:hamlogger@yahoogroups.com <mailto:hamlogger@yahoogroups.com> ]
Sent: Monday, July 3, 2017 8:03 AM
To: hamlogger@yahoogroups.com <mailto:hamlogger@yahoogroups.com>
Subject: RE: [hamlogger] Cannot export Files to LoTW and eQSL

Jerald & Tony,

I cannot see this problem.

Logger32 will only display the operator callsign IF there are QSO’s
logged by the current operator & flagged for LOTW export.

To test this,

1) I entered several dummy QSO’s under different operator
callsigns. All flagged for send LOTW export

2) Initiated Export file – LOTW

3) ALL operator callsigns were listed, including current operator.

4) I selected the current operator and made the export telling it
to mark the QSO as having been sent.

5) I then initiated Export file – LOTW. This time the current
operator callsign does not appear because no QSO’s are flagged to
be sent to LOTW.

IF you see something different please tell me the steps you took
and please verify you actually have QSO’s flagged.



73, Jim – w5ifp@... <mailto:w5ifp@...>



From: hamlogger@yahoogroups.com <mailto:hamlogger@yahoogroups.com>
[mailto:hamlogger@yahoogroups.com <mailto:hamlogger@yahoogroups.com> ]
Sent: Sunday, July 2, 2017 7:23 PM
To: hamlogger@yahoogroups.com <mailto:hamlogger@yahoogroups.com>
Subject: RE: [hamlogger] Cannot export Files to LoTW and eQSL





Jim,



The exports may be working, but the problem is with the "Only
QSOs by" filter. The current callsign is not offered as a choice.



The steps are easy to repro:

File > Export Files > Export to LoTW

The presented menu does not allow using the active callsign.



Perhaps it works if there is only one callsign. I have several in my
logbook. The old ones show up as choices, but not the active
callsign. QSOs are flagged as "Send LOTW QSL".





I also tried adding a new callsign as a test and entered a test QSO.
The new callsign also does not show up in the "Only QSOs by" filter.





I don't use eQSL, so can't add anything there.



Gerald, VE1DT




---In hamlogger@yahoogroups.com <mailto:hamlogger@yahoogroups.com> , <w5ifp@...> wrote :

Tony,

The LOTW & eQSL export files are working.

Please remind us of what you are trying to do that is not working for
you.

Tell us the exact procedure that you used.

73, Jim – w5ifp@... <mailto:w5ifp@...>



From: hamlogger@yahoogroups.com <mailto:hamlogger@yahoogroups.com>
<mailto:hamlogger@yahoogroups.com <mailto:hamlogger@yahoogroups.com> >
[mailto:hamlogger@yahoogroups.com <mailto:hamlogger@yahoogroups.com>
<mailto:hamlogger@yahoogroups.com <mailto:hamlogger@yahoogroups.com> > ]
Sent: Thursday, June 29, 2017 3:45 PM
To: hamlogger@yahoogroups.com <mailto:hamlogger@yahoogroups.com>
<mailto:hamlogger@yahoogroups.com <mailto:hamlogger@yahoogroups.com> >
Subject: RE: [hamlogger] Cannot export Files to LoTW and eQSL








I just upgraded to version 3.50.323 (latest release), but the problem
remains. Any further suggestions? I could possibly be missing
something.



Thanks

Tony KU4NY










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










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



------------------------------------
Posted by: "Jim Hargrave" <w5ifp@... <mailto:w5ifp@...> >
------------------------------------

Visit these sites for Logger and other downloads:
http://www.logger32.net/

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

Yahoo Groups Links











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


Re: Cannot export Files to LoTW and eQSL - RESOLVED

gboutin@...
 

Jim,

As usual, Bob is on top of the situation. The issue is resolved for me.

I had already followed all of the necessary steps and, as per Bob's evaluation, my logbook would appear to have a broken index.

I had also already tried "Recalculate Statistics" and "Reformat QSO numbers" and that did not fix the issue. However, a full export to ADI and import back into a new Logbook has resolved the issue.

> Gerald, VE1DT


---In hamlogger@..., <w5ifp@...> wrote :

Some further comments from K4CY:

"For me it works as expected. Double (and triple) check that the Operator callsign is what you think it should be for the QSOs you want to send to LoTW. Double (and triple) check the SEND LOTW QSOs flags are set for these callsigns.

Is the Logbook database broken? Export in ADIF Format. Change the Logbook to a new name (something like TESTLOG). Import the ADIF File into TESTLOG.

... but WAIT ... I just read this last paragraph again ... I also tried adding a new callsign as a test and entered a test QSO. The new callsign also does not show up in the "Only QSOs by" filter

It is NOT the callsign of the station you QSOd with that is added to the selection list. The selection list is a list of Operators who have QSOs in the Logbook with QSOs flagged for QSOs to be sent to LoTW.

Simply adding a new operator (VE150DT for example) then adding a dummy QSO with VE1DT will not add VE150DT to the export selection list. First the VE150DT QSO with VE1DT must be flagged as SEND LoTW QSL. Now VE150DT will show up on the export selection list ... If not, your Logbook probably has a broken index"

73, Jim – w5ifp@...

>> -----Original Message-----
>> From: hamlogger@...
>> [mailto:hamlogger@...]
>> Sent: Monday, July 3, 2017 8:03 AM
>> To: hamlogger@...
>> Subject: RE: [hamlogger] Cannot export Files to LoTW and eQSL
>>
>> Jerald & Tony,
>>
>> I cannot see this problem.
>>
>> Logger32 will only display the operator callsign IF there are QSO’s
>> logged by the current operator & flagged for LOTW export.
>>
>> To test this,
>>
>> 1) I entered several dummy QSO’s under different operator
>> callsigns. All flagged for send LOTW export
>>
>> 2) Initiated Export file – LOTW
>>
>> 3) ALL operator callsigns were listed, including current operator.
>>
>> 4) I selected the current operator and made the export telling it
>> to mark the QSO as having been sent.
>>
>> 5) I then initiated Export file – LOTW. This time the current
>> operator callsign does not appear because no QSO’s are flagged to
>> be sent to LOTW.
>>
>> IF you see something different please tell me the steps you took
>> and please verify you actually have QSO’s flagged.
>>
>>
>>
>> 73, Jim – w5ifp@...
>>
>>
>>
>> From: hamlogger@...
>> [mailto:hamlogger@...]
>> Sent: Sunday, July 2, 2017 7:23 PM
>> To: hamlogger@...
>> Subject: RE: [hamlogger] Cannot export Files to LoTW and eQSL
>>
>>
>>
>>
>>
>> Jim,
>>
>>
>>
>> The exports may be working, but the problem is with the "Only
>> QSOs by" filter. The current callsign is not offered as a choice.
>>
>>
>>
>> The steps are easy to repro:
>>
>> File > Export Files > Export to LoTW
>>
>> The presented menu does not allow using the active callsign.
>>
>>
>>
>> Perhaps it works if there is only one callsign. I have several in my
>> logbook. The old ones show up as choices, but not the active
>> callsign. QSOs are flagged as "Send LOTW QSL".
>>
>>
>>
>>
>>
>> I also tried adding a new callsign as a test and entered a test QSO.
>> The new callsign also does not show up in the "Only QSOs by" filter.
>>
>>
>>
>>
>>
>> I don't use eQSL, so can't add anything there.
>>
>>
>>
>> > Gerald, VE1DT
>>
>>
>>
>>
>>
>> ---In hamlogger@..., <w5ifp@...> wrote :
>>
>> Tony,
>>
>> The LOTW & eQSL export files are working.
>>
>> Please remind us of what you are trying to do that is not working for
>> you.
>>
>> Tell us the exact procedure that you used.
>>
>> 73, Jim – w5ifp@... <mailto:w5ifp@...>
>>
>>
>>
>> From: hamlogger@...
>> <mailto:hamlogger@...>
>> [mailto:hamlogger@...
>> <mailto:hamlogger@...> ]
>> Sent: Thursday, June 29, 2017 3:45 PM
>> To: hamlogger@...
>> <mailto:hamlogger@...>
>> Subject: RE: [hamlogger] Cannot export Files to LoTW and eQSL
>>
>>
>>
>>
>>
>>
>>
>>
>> I just upgraded to version 3.50.323 (latest release), but the problem
>> remains. Any further suggestions? I could possibly be missing
>> something.
>>
>>
>>
>> Thanks
>>
>> Tony KU4NY
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> [Non-text portions of this message have been removed]
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> [Non-text portions of this message have been removed]
>>
>>
>>
>> ------------------------------------
>> Posted by: "Jim Hargrave" <w5ifp@...>
>> ------------------------------------
>>
>> Visit these sites for Logger and other downloads:
>> http://www.logger32.net/
>>
>> ------------------------------------
>>
>> Yahoo Groups Links
>>
>>
>>


Re : New windows solved floating windows

BTX
 

Hi dan 
in "glass form"   you are right the right click can work but in a completely random way only by right click on the call sign. You had to know! it was necessary to be aware!

Mailto: f6itd@...



-----E-mail d'origine-----
De : Dan Atchison N3ND@... [hamlogger]
A: hamlogger
Envoyé le : Lu, 3 Jul 2017 17:43
Sujet : Re: [hamlogger] New windows solved floating windows

 
??    Try again.  Right click on the one of the callsign characters.  You'll get the right click menu from which you can exit.  Yes in glass form mode, too.

On 7/3/2017 10:40 AM, 'Berthoumieux Jean-pierre (F6ITD)' F6ITD@... [hamlogger] wrote:
 
Tks Alex and Jim  floating windows was in "glass form"   no right click possible  in  this configuration .
 Only 1 possibility to leave : Ctrl F only in menu Operator window > callsign > Ctrl/F
73
Jean-Pierre

Mailto: f6itd@...



-----E-mail d'origine-----
De : OK1VOF Alex ok1vof@... [hamlogger]
A: hamlogger
Envoyé le : Lu, 3 Jul 2017 14:53
Sujet : Re: [hamlogger] New windows

 
Jean-Pierre,
the same as if You write callsign in opreator window?

If yes it is foating callsign field (started in menu Operator window > callsign > Ctrl/F). But I also don't know how to cancel this feature.

73 de
Alex OK1VOF / OK4AS

2017-07-03 14:08 GMT+02:00 'Berthoumieux Jean-pierre (F6ITD)' F6ITD@... [hamlogger] <hamlogger@...>:
 
Hello everybody
When I click on a DX spot (cluster windows) the call sign is transferred to the window operator (normal ..) but at the same time, a new large window appears where the same Call sign  appears with a large font red color .. No menu on this window. I can move this window, that's all.
 Can someone illuminate my lantern? 
73
Jean-Pierre

Thanks in advance.
Mailto: f6itd@...



Bez virů. www.avast.com


Re: New windows solved floating windows

Gerry VE6LB
 

 
In the Glass window, you need to right click on some portion of the displayed call (not a blank space).
 
73 Gerry VE6LB
 

From: Dan Atchison N3ND@... [hamlogger]
Sent: Monday, July 03, 2017 09:43
To: hamlogger@...
Subject: Re: [hamlogger] New windows solved floating windows
 
 

??    Try again.  Right click on the one of the callsign characters.  You'll get the right click menu from which you can exit.  Yes in glass form mode, too.

On 7/3/2017 10:40 AM, 'Berthoumieux Jean-pierre (F6ITD)' F6ITD@... [hamlogger] wrote:
 

Tks Alex and Jim  floating windows was in "glass form"   no right click possible  in  this configuration .
Only 1 possibility to leave : Ctrl F only in menu Operator window > callsign > Ctrl/F
73
Jean-Pierre

Mailto: f6itd@...
 


-----E-mail d'origine-----
De : OK1VOF Alex ok1vof@... [hamlogger] mailto:hamlogger@...
A: hamlogger mailto:hamlogger@...
Envoyé le : Lu, 3 Jul 2017 14:53
Sujet : Re: [hamlogger] New windows

 
Jean-Pierre,
the same as if You write callsign in opreator window?

If yes it is foating callsign field (started in menu Operator window > callsign > Ctrl/F). But I also don't know how to cancel this feature.

73 de
Alex OK1VOF / OK4AS
 
2017-07-03 14:08 GMT+02:00 'Berthoumieux Jean-pierre (F6ITD)' F6ITD@... [hamlogger] <hamlogger@...>:
 
Hello everybody
When I click on a DX spot (cluster windows) the call sign is transferred to the window operator (normal ..) but at the same time, a new large window appears where the same Call sign  appears with a large font red color .. No menu on this window. I can move this window, that's all.
Can someone illuminate my lantern?
73
Jean-Pierre
 
Thanks in advance.
Mailto: f6itd@...
 
 

Bez virů. www.avast.com


Re: New windows solved floating windows

Dan Atchison
 

??    Try again.  Right click on the one of the callsign characters.  You'll get the right click menu from which you can exit.  Yes in glass form mode, too.

On 7/3/2017 10:40 AM, 'Berthoumieux Jean-pierre (F6ITD)' F6ITD@... [hamlogger] wrote:
 

Tks Alex and Jim  floating windows was in "glass form"   no right click possible  in  this configuration .
 Only 1 possibility to leave : Ctrl F only in menu Operator window > callsign > Ctrl/F
73
Jean-Pierre

Mailto: f6itd@...



-----E-mail d'origine-----
De : OK1VOF Alex ok1vof@... [hamlogger]
A: hamlogger
Envoyé le : Lu, 3 Jul 2017 14:53
Sujet : Re: [hamlogger] New windows

 
Jean-Pierre,
the same as if You write callsign in opreator window?

If yes it is foating callsign field (started in menu Operator window > callsign > Ctrl/F). But I also don't know how to cancel this feature.

73 de
Alex OK1VOF / OK4AS

2017-07-03 14:08 GMT+02:00 'Berthoumieux Jean-pierre (F6ITD)' F6ITD@... [hamlogger] <hamlogger@...>:
 
Hello everybody
When I click on a DX spot (cluster windows) the call sign is transferred to the window operator (normal ..) but at the same time, a new large window appears where the same Call sign  appears with a large font red color .. No menu on this window. I can move this window, that's all.
 Can someone illuminate my lantern? 
73
Jean-Pierre

Thanks in advance.
Mailto: f6itd@...



Bez virů. www.avast.com


New windows solved floating windows

BTX
 

Tks Alex and Jim  floating windows was in "glass form"   no right click possible  in  this configuration .
 Only 1 possibility to leave : Ctrl F only in menu Operator window > callsign > Ctrl/F
73
Jean-Pierre

Mailto: f6itd@...



-----E-mail d'origine-----
De : OK1VOF Alex ok1vof@... [hamlogger]
A: hamlogger
Envoyé le : Lu, 3 Jul 2017 14:53
Sujet : Re: [hamlogger] New windows

 
Jean-Pierre,
the same as if You write callsign in opreator window?

If yes it is foating callsign field (started in menu Operator window > callsign > Ctrl/F). But I also don't know how to cancel this feature.

73 de
Alex OK1VOF / OK4AS

2017-07-03 14:08 GMT+02:00 'Berthoumieux Jean-pierre (F6ITD)' F6ITD@... [hamlogger] <hamlogger@...>:
 
Hello everybody
When I click on a DX spot (cluster windows) the call sign is transferred to the window operator (normal ..) but at the same time, a new large window appears where the same Call sign  appears with a large font red color .. No menu on this window. I can move this window, that's all.
 Can someone illuminate my lantern? 
73
Jean-Pierre

Thanks in advance.
Mailto: f6itd@...



Bez virů. www.avast.com


Re: Cannot export Files to LoTW and eQSL

Jim Hargrave
 

Some further comments from K4CY:

"For me it works as expected. Double (and triple) check that the Operator callsign is what you think it should be for the QSOs you want to send to LoTW. Double (and triple) check the SEND LOTW QSOs flags are set for these callsigns.

Is the Logbook database broken? Export in ADIF Format. Change the Logbook to a new name (something like TESTLOG). Import the ADIF File into TESTLOG.

... but WAIT ... I just read this last paragraph again ... I also tried adding a new callsign as a test and entered a test QSO. The new callsign also does not show up in the "Only QSOs by" filter

It is NOT the callsign of the station you QSOd with that is added to the selection list. The selection list is a list of Operators who have QSOs in the Logbook with QSOs flagged for QSOs to be sent to LoTW.

Simply adding a new operator (VE150DT for example) then adding a dummy QSO with VE1DT will not add VE150DT to the export selection list. First the VE150DT QSO with VE1DT must be flagged as SEND LoTW QSL. Now VE150DT will show up on the export selection list ... If not, your Logbook probably has a broken index"

73, Jim – w5ifp@gvtc.com

-----Original Message-----
From: hamlogger@yahoogroups.com
[mailto:hamlogger@yahoogroups.com]
Sent: Monday, July 3, 2017 8:03 AM
To: hamlogger@yahoogroups.com
Subject: RE: [hamlogger] Cannot export Files to LoTW and eQSL

Jerald & Tony,

I cannot see this problem.

Logger32 will only display the operator callsign IF there are QSO’s
logged by the current operator & flagged for LOTW export.

To test this,

1) I entered several dummy QSO’s under different operator
callsigns. All flagged for send LOTW export

2) Initiated Export file – LOTW

3) ALL operator callsigns were listed, including current operator.

4) I selected the current operator and made the export telling it
to mark the QSO as having been sent.

5) I then initiated Export file – LOTW. This time the current
operator callsign does not appear because no QSO’s are flagged to
be sent to LOTW.

IF you see something different please tell me the steps you took
and please verify you actually have QSO’s flagged.



73, Jim – w5ifp@gvtc.com



From: hamlogger@yahoogroups.com
[mailto:hamlogger@yahoogroups.com]
Sent: Sunday, July 2, 2017 7:23 PM
To: hamlogger@yahoogroups.com
Subject: RE: [hamlogger] Cannot export Files to LoTW and eQSL





Jim,



The exports may be working, but the problem is with the "Only
QSOs by" filter. The current callsign is not offered as a choice.



The steps are easy to repro:

File > Export Files > Export to LoTW

The presented menu does not allow using the active callsign.



Perhaps it works if there is only one callsign. I have several in my
logbook. The old ones show up as choices, but not the active
callsign. QSOs are flagged as "Send LOTW QSL".





I also tried adding a new callsign as a test and entered a test QSO.
The new callsign also does not show up in the "Only QSOs by" filter.





I don't use eQSL, so can't add anything there.



Gerald, VE1DT




---In hamlogger@yahoogroups.com, <w5ifp@...> wrote :

Tony,

The LOTW & eQSL export files are working.

Please remind us of what you are trying to do that is not working for
you.

Tell us the exact procedure that you used.

73, Jim – w5ifp@... <mailto:w5ifp@...>



From: hamlogger@yahoogroups.com
<mailto:hamlogger@yahoogroups.com>
[mailto:hamlogger@yahoogroups.com
<mailto:hamlogger@yahoogroups.com> ]
Sent: Thursday, June 29, 2017 3:45 PM
To: hamlogger@yahoogroups.com
<mailto:hamlogger@yahoogroups.com>
Subject: RE: [hamlogger] Cannot export Files to LoTW and eQSL








I just upgraded to version 3.50.323 (latest release), but the problem
remains. Any further suggestions? I could possibly be missing
something.



Thanks

Tony KU4NY










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










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



------------------------------------
Posted by: "Jim Hargrave" <w5ifp@gvtc.com>
------------------------------------

Visit these sites for Logger and other downloads:
http://www.logger32.net/

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

Yahoo Groups Links



Re: New windows

Jim Hargrave
 

To close the floating callsign window, Right click on the window and select “Exit”



73, Jim – w5ifp@gvtc.com



From: hamlogger@yahoogroups.com [mailto:hamlogger@yahoogroups.com]
Sent: Monday, July 3, 2017 7:53 AM
To: hamlogger@yahoogroups.com
Subject: Re: [hamlogger] New windows








Jean-Pierre,

the same as if You write callsign in opreator window?

If yes it is foating callsign field (started in menu Operator window > callsign > Ctrl/F). But I also don't know how to cancel this feature.

73 de
Alex OK1VOF / OK4AS



2017-07-03 14:08 GMT+02:00 'Berthoumieux Jean-pierre (F6ITD)' F6ITD@aol.com <mailto:F6ITD@aol.com> [hamlogger] <hamlogger@yahoogroups.com <mailto:hamlogger@yahoogroups.com> >:



Hello everybody

When I click on a DX spot (cluster windows) the call sign is transferred to the window operator (normal ..) but at the same time, a new large window appears where the same Call sign appears with a large font red color .. No menu on this window. I can move this window, that's all.

Can someone illuminate my lantern?

73

Jean-Pierre



Thanks in advance.

Mailto: f6itd@aol.com <mailto:f6itd@aol.com>








<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>

Bez virů. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> www.avast.com










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


Re: Cannot export Files to LoTW and eQSL

Jim Hargrave
 

Jerald & Tony,

I cannot see this problem.

Logger32 will only display the operator callsign IF there are QSO’s logged by the current operator & flagged for LOTW export.

To test this,

1) I entered several dummy QSO’s under different operator callsigns. All flagged for send LOTW export

2) Initiated Export file – LOTW

3) ALL operator callsigns were listed, including current operator.

4) I selected the current operator and made the export telling it to mark the QSO as having been sent.

5) I then initiated Export file – LOTW. This time the current operator callsign does not appear because no QSO’s are flagged to be sent to LOTW.

IF you see something different please tell me the steps you took and please verify you actually have QSO’s flagged.



73, Jim – w5ifp@gvtc.com



From: hamlogger@yahoogroups.com [mailto:hamlogger@yahoogroups.com]
Sent: Sunday, July 2, 2017 7:23 PM
To: hamlogger@yahoogroups.com
Subject: RE: [hamlogger] Cannot export Files to LoTW and eQSL





Jim,



The exports may be working, but the problem is with the "Only QSOs by" filter. The current callsign is not offered as a choice.



The steps are easy to repro:

File > Export Files > Export to LoTW

The presented menu does not allow using the active callsign.



Perhaps it works if there is only one callsign. I have several in my logbook. The old ones show up as choices, but not the active callsign. QSOs are flagged as "Send LOTW QSL".





I also tried adding a new callsign as a test and entered a test QSO. The new callsign also does not show up in the "Only QSOs by" filter.





I don't use eQSL, so can't add anything there.



Gerald, VE1DT




---In hamlogger@yahoogroups.com, <w5ifp@...> wrote :

Tony,

The LOTW & eQSL export files are working.

Please remind us of what you are trying to do that is not working for you.

Tell us the exact procedure that you used.

73, Jim – w5ifp@... <mailto:w5ifp@...>



From: hamlogger@yahoogroups.com <mailto:hamlogger@yahoogroups.com> [mailto:hamlogger@yahoogroups.com <mailto:hamlogger@yahoogroups.com> ]
Sent: Thursday, June 29, 2017 3:45 PM
To: hamlogger@yahoogroups.com <mailto:hamlogger@yahoogroups.com>
Subject: RE: [hamlogger] Cannot export Files to LoTW and eQSL








I just upgraded to version 3.50.323 (latest release), but the problem remains. Any further suggestions? I could possibly be missing something.



Thanks

Tony KU4NY










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










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

13461 - 13480 of 85220