Date   

Re: USA prefixes...

Larry Fravel
 

Been having this problem for over a week now on various prefixes.  All seem to be near the end of the alphabet.  Asked about it last week but got no response.  thought maybe I was the only one having it.
 
Larry K8YYY
 
"Never interrupt some one doing something you said couldn't be done"
Amelia Earhart



AVG logo

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



Re: New Update for L32LogSync

Rick Ellison
 

All depends on how you are uploading them. If you are uploading them in real-time you should not get any except if the file contains more than 1 qso in it then it will use the WebUpload routine where you will get an email from ClubLog. Turn on debug and the next time you upload to Clublog after doing so send the debug.txt file to me so I can look at how it is doing the upload..

 

73 Rick n2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Filipe Lopes
Sent: Friday, April 6, 2018 1:09 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] New Update for L32LogSync

 

Hi Rick

 

I keep getting emails from CLUBLOG for every single QSO that I made with this v2.0.2 version, is this normal?


 

73's Filipe Lopes 

CT1ILT - CR6K

F4VPX - TM3M 

 

2018-04-06 3:22 GMT+02:00 Rick Ellison <rellison@...>:

I have uploaded a new version to my website. This is an update only for the
.exe file. Open the zip after downloading it and unzip the file contents
into the install directory where you have installed L32LogSync.

http://www.n2amg.com/software/l32-logsync/

This version has fixes for a bunch of bugs including eQSL and ClubLog. Also
for the TQSL path error.

73 Rick N2AMG



 


USA prefixes...

Steph Collas <f5nzy@...>
 

Hello,

I use the very last update of Logger32.

If I hit, for exemple, AA4AK, which is an OM from USA, the Logger32's data base does not recognize it as USA (see print screen: Unknown prefix).

I recalculate statistics... same issue.

Any idea?

73 de Steph, F5NZY




Re: Distance Recording as 0

Gerald Boutin
 

Dan,

Good try, but not the issue here. These were directly logged in L32. When I import logs from my contest logger, the Distance field is left blank.

Actually, I wish L32 did compute the distance when I import logs. I would be happy if it just used the default DXCC distance from the prefix.

-- 
Gerald, VE1DT


On Fri, Apr 6, 2018 at 10:53 am, Dan Atchison wrote:
Had you by chance imported those Q's from a different program that doesn't compute distance?  If so, L32 will not compute it for you unless you did a manual, direct entry into L32.  IOW, if you imported an adif from N1MM into Logger 32 there would be no distance calculated and associated with that QSO.

73,
Dan


On 4/6/2018 1:02 PM, Gerald Boutin wrote:
Jim,

Double checking shows that they are, of course, correct. Logging other stations was and currently still is working correctly. Distances and bearings in the entry window also continue to be correct. So far, just this one callsign. Even LY29A  and LY280A work properly.

Here is what an exported ADIF shows. It is not exactly zero, but .04. While looking there, I also found one other QSO in my log that had this problem. Logging a test qso for that call also still shows the problem.

<DISTANCE:3>.04 <BAND:3>20M <CALL:5>LY28A
<DISTANCE:3>.04 <BAND:3>40M <CALL:9>TI5/N4YDU

I have also tried recalculating statistics and restarting the program, but the issue persists. I am out of ideas as to where else to look.
 
-- 
Gerald, VE1DT



On Fri, Apr 6, 2018 at 09:21 am, Jim Hargrave wrote:

Gerald,

 

Check your Log Entry | Setup | My QTH settings. Make sure they a correct.

It logs Distance  properly here.

 

Jim – w5ifp@...

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Gerald Boutin
Sent: Friday, April 6, 2018 10:42 AM
To: hamlogger@groups.io
Subject: [hamlogger] Distance Recording as 0

 

Logging a QSO for LY28A logs 0 km for the distance. From VE1, it should be logging 5753 km.

Typing the callsign in the entry window shows proper DXCC, bearing and distance, yet the distance is logged as 0 km. Distance logging has been working all along for other callsigns including other LY calls. I was using version 3.50.347 when I initially logged the QSO.  The same problem also happens with version 3.50.351.

The LY28A callsign also shows up properly in qrz.com. Any other ideas as to why this is happening and how to get it working?

--
Gerald, VE1DT

 


Re: Distance Recording as 0

Gerald Boutin
 

Apparently this problem has a mind of it's own. The LY28A callsign now works to store the distance.  I tried different bands and different modes. I also tried logging a qso with the internet disconnected. However, nothing was conclusive. But I just tried it again now and it is working.

I also tried similar things that I did with the LY28A call with the TI5/N4YDU call, but it still resists storing the correct distance. So, I still don't know whether or not it was something I did or not.

-- 
Gerald, VE1DT


On Fri, Apr 6, 2018 at 10:02 am, Gerald Boutin wrote:
Jim,

Double checking shows that they are, of course, correct. Logging other stations was and currently still is working correctly. Distances and bearings in the entry window also continue to be correct. So far, just this one callsign. Even LY29A  and LY280A work properly.

Here is what an exported ADIF shows. It is not exactly zero, but .04. While looking there, I also found one other QSO in my log that had this problem. Logging a test qso for that call also still shows the problem.

<DISTANCE:3>.04 <BAND:3>20M <CALL:5>LY28A
<DISTANCE:3>.04 <BAND:3>40M <CALL:9>TI5/N4YDU

I have also tried recalculating statistics and restarting the program, but the issue persists. I am out of ideas as to where else to look.
 
-- 
Gerald, VE1DT



On Fri, Apr 6, 2018 at 09:21 am, Jim Hargrave wrote:

Gerald,

 

Check your Log Entry | Setup | My QTH settings. Make sure they a correct.

It logs Distance  properly here.

 

Jim – w5ifp@...

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Gerald Boutin
Sent: Friday, April 6, 2018 10:42 AM
To: hamlogger@groups.io
Subject: [hamlogger] Distance Recording as 0

 

Logging a QSO for LY28A logs 0 km for the distance. From VE1, it should be logging 5753 km.

Typing the callsign in the entry window shows proper DXCC, bearing and distance, yet the distance is logged as 0 km. Distance logging has been working all along for other callsigns including other LY calls. I was using version 3.50.347 when I initially logged the QSO.  The same problem also happens with version 3.50.351.

The LY28A callsign also shows up properly in qrz.com. Any other ideas as to why this is happening and how to get it working?

--
Gerald, VE1DT

 


Re: Distance Recording as 0

Dan Atchison
 

Had you by chance imported those Q's from a different program that doesn't compute distance?  If so, L32 will not compute it for you unless you did a manual, direct entry into L32.  IOW, if you imported an adif from N1MM into Logger 32 there would be no distance calculated and associated with that QSO.

73,
Dan


On 4/6/2018 1:02 PM, Gerald Boutin wrote:
Jim,

Double checking shows that they are, of course, correct. Logging other stations was and currently still is working correctly. Distances and bearings in the entry window also continue to be correct. So far, just this one callsign. Even LY29A  and LY280A work properly.

Here is what an exported ADIF shows. It is not exactly zero, but .04. While looking there, I also found one other QSO in my log that had this problem. Logging a test qso for that call also still shows the problem.

<DISTANCE:3>.04 <BAND:3>20M <CALL:5>LY28A
<DISTANCE:3>.04 <BAND:3>40M <CALL:9>TI5/N4YDU

I have also tried recalculating statistics and restarting the program, but the issue persists. I am out of ideas as to where else to look.
 
-- 
Gerald, VE1DT



On Fri, Apr 6, 2018 at 09:21 am, Jim Hargrave wrote:

Gerald,

 

Check your Log Entry | Setup | My QTH settings. Make sure they a correct.

It logs Distance  properly here.

 

Jim – w5ifp@...

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Gerald Boutin
Sent: Friday, April 6, 2018 10:42 AM
To: hamlogger@groups.io
Subject: [hamlogger] Distance Recording as 0

 

Logging a QSO for LY28A logs 0 km for the distance. From VE1, it should be logging 5753 km.

Typing the callsign in the entry window shows proper DXCC, bearing and distance, yet the distance is logged as 0 km. Distance logging has been working all along for other callsigns including other LY calls. I was using version 3.50.347 when I initially logged the QSO.  The same problem also happens with version 3.50.351.

The LY28A callsign also shows up properly in qrz.com. Any other ideas as to why this is happening and how to get it working?

--
Gerald, VE1DT

 


Re: New Update for L32LogSync

Filipe Lopes
 

Hi Rick

I keep getting emails from CLUBLOG for every single QSO that I made with this v2.0.2 version, is this normal?


73's Filipe Lopes 
CT1ILT - CR6K
F4VPX - TM3M 

2018-04-06 3:22 GMT+02:00 Rick Ellison <rellison@...>:

I have uploaded a new version to my website. This is an update only for the
.exe file. Open the zip after downloading it and unzip the file contents
into the install directory where you have installed L32LogSync.

http://www.n2amg.com/software/l32-logsync/

This version has fixes for a bunch of bugs including eQSL and ClubLog. Also
for the TQSL path error.

73 Rick N2AMG






Re: Distance Recording as 0

Dave Colliau
 

I get 4577 miles here

Dave N8DC

On April 6, 2018 at 1:02 PM Gerald Boutin <groupsio@...> wrote:

Jim,

Double checking shows that they are, of course, correct. Logging other stations was and currently still is working correctly. Distances and bearings in the entry window also continue to be correct. So far, just this one callsign. Even LY29A  and LY280A work properly.

Here is what an exported ADIF shows. It is not exactly zero, but .04. While looking there, I also found one other QSO in my log that had this problem. Logging a test qso for that call also still shows the problem.

<DISTANCE:3>.04 <BAND:3>20M <CALL:5>LY28A
<DISTANCE:3>.04 <BAND:3>40M <CALL:9>TI5/N4YDU

I have also tried recalculating statistics and restarting the program, but the issue persists. I am out of ideas as to where else to look.
 
-- 
Gerald, VE1DT



On Fri, Apr 6, 2018 at 09:21 am, Jim Hargrave wrote:

Gerald,

 

Check your Log Entry | Setup | My QTH settings. Make sure they a correct.

It logs Distance  properly here.

 

Jim – w5ifp@...

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Gerald Boutin
Sent: Friday, April 6, 2018 10:42 AM
To: hamlogger@groups.io
Subject: [hamlogger] Distance Recording as 0

 

Logging a QSO for LY28A logs 0 km for the distance. From VE1, it should be logging 5753 km.

Typing the callsign in the entry window shows proper DXCC, bearing and distance, yet the distance is logged as 0 km. Distance logging has been working all along for other callsigns including other LY calls. I was using version 3.50.347 when I initially logged the QSO.  The same problem also happens with version 3.50.351.

The LY28A callsign also shows up properly in qrz.com. Any other ideas as to why this is happening and how to get it working?

--
Gerald, VE1DT

 


Re: Distance Recording as 0

Gerald Boutin
 

Jim,

Double checking shows that they are, of course, correct. Logging other stations was and currently still is working correctly. Distances and bearings in the entry window also continue to be correct. So far, just this one callsign. Even LY29A  and LY280A work properly.

Here is what an exported ADIF shows. It is not exactly zero, but .04. While looking there, I also found one other QSO in my log that had this problem. Logging a test qso for that call also still shows the problem.

<DISTANCE:3>.04 <BAND:3>20M <CALL:5>LY28A
<DISTANCE:3>.04 <BAND:3>40M <CALL:9>TI5/N4YDU

I have also tried recalculating statistics and restarting the program, but the issue persists. I am out of ideas as to where else to look.
 
-- 
Gerald, VE1DT



On Fri, Apr 6, 2018 at 09:21 am, Jim Hargrave wrote:

Gerald,

 

Check your Log Entry | Setup | My QTH settings. Make sure they a correct.

It logs Distance  properly here.

 

Jim – w5ifp@...

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Gerald Boutin
Sent: Friday, April 6, 2018 10:42 AM
To: hamlogger@groups.io
Subject: [hamlogger] Distance Recording as 0

 

Logging a QSO for LY28A logs 0 km for the distance. From VE1, it should be logging 5753 km.

Typing the callsign in the entry window shows proper DXCC, bearing and distance, yet the distance is logged as 0 km. Distance logging has been working all along for other callsigns including other LY calls. I was using version 3.50.347 when I initially logged the QSO.  The same problem also happens with version 3.50.351.

The LY28A callsign also shows up properly in qrz.com. Any other ideas as to why this is happening and how to get it working?

--
Gerald, VE1DT

 


Re: Distance Recording as 0

Jim Hargrave
 

Gerald,

 

Check your Log Entry | Setup | My QTH settings. Make sure they a correct.

It logs Distance  properly here.

 

Jim – w5ifp@...

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Gerald Boutin
Sent: Friday, April 6, 2018 10:42 AM
To: hamlogger@groups.io
Subject: [hamlogger] Distance Recording as 0

 

Logging a QSO for LY28A logs 0 km for the distance. From VE1, it should be logging 5753 km.

Typing the callsign in the entry window shows proper DXCC, bearing and distance, yet the distance is logged as 0 km. Distance logging has been working all along for other callsigns including other LY calls. I was using version 3.50.347 when I initially logged the QSO.  The same problem also happens with version 3.50.351.

The LY28A callsign also shows up properly in qrz.com. Any other ideas as to why this is happening and how to get it working?

--
Gerald, VE1DT


Distance Recording as 0

Gerald Boutin
 

Logging a QSO for LY28A logs 0 km for the distance. From VE1, it should be logging 5753 km.

Typing the callsign in the entry window shows proper DXCC, bearing and distance, yet the distance is logged as 0 km. Distance logging has been working all along for other callsigns including other LY calls. I was using version 3.50.347 when I initially logged the QSO.  The same problem also happens with version 3.50.351.

The LY28A callsign also shows up properly in qrz.com. Any other ideas as to why this is happening and how to get it working?

--
Gerald, VE1DT


L32LogSync OK !!!

Carlo, I4HRH
 

All ok Rick!
You are great!
73 Carlo I4HRH


Logger32 v3.50.351 and Awards Tables display issues

IK6AWY
 

Dear Logger32 Programmers, I have WindowsXP SP3 in my Samsung 22" with
1920x1080 resolution screen from my Nvidia Geforce 210 videocard, with
Logger32 v3.50.351 give me an issue of display of the AWARDS TABLES
visualization.

If I Click on DIPLOME>DXCC (but is the same for the other AWARDS
TABLES) the window of DXCC_MIXED - All Op, All confirmations, All
credits - is open, BUT NOT VISUALIZE NONE.

The screen of the window is in grey color and not is anyone data.

This incredible situation is for all Awards windows and for all
Diplome.

For what?

What is my error of configuration?

I read and re-read the Help of Logger32, but not have any just
reasons.

Please is possible help me?

Many Thanks for your interest to my problem.

Bye for now.





--
I migliori 73, Scrivi a:
IK6AWY ik6awy@hotmail.com


L32 LogSync and LOTW Problem - Solved

gw8szl
 

Hi All,

Just an update on my problem with LOTW crashing Windows 7 Professional
for you.

I downloaded L32LogSync ver 2.0.0.2 and tried enabling LOTW from the
Program Setup menu as before and it crashed once again.

I then had a look at the L32Lotw_eQSL_Utility.ini file from the
previous version and noticed the line:

TQSLPath=C:\Program Files\TrustedQSL\tqsl.exe

I added this manually to the new L32LogSync.ini file along with LOTW=
True and now i can access the LOTW Setup menu. I have just got to
enter all my details now.

Just thought i would let you know how i have managed to get it working
as it could help others with the same problem.

73

Dave GW8SZL


Notice to all members - Transition to groups.io

Jim Hargrave
 

The Logger32 group transition to hamlogger@groups.io has been completed.

Please bookmark your Logger32 e-mail to the new group.

 

NOTE: I have received  over 200 notices where members were automatically unsubscribed from the new group. Most were a result of messages rejected as Spam by the ISP.

 

=================== Sample ========

This is to notify you that  (XXXXX @  XXXX )  has been unsubscribed from your group hamlogger@groups.io because a message to them was marked as spam. Note that this may have been done by their email service provider, not by the individual member personally.

==================================

 

If you fall in this category, please review your spam/white list settings to insure group messages are not bounced. Once you have the problem corrected, please re-subscribe.

 

All future postings should be to: hamlogger@groups.io.

 

Thanks to all for your patience during the transition!

 

Jim – w5ifp@...

 


Subscription

weinerpr@...
 

Kindly remove my husband's email from your records as my dearest husband David Weiner passed away in December, 2017.


Re: New Update for L32LogSync

Dave Colliau
 

All good. Up and running here.

Dave N8DC

On April 6, 2018 at 8:56 AM Rick Ellison <rellison@...> wrote:

I have not uploaded a full build yet. If someone installed the full version the update would correct the name used. I will be uploading a full build today but if you have already installed the program just the update is needed..

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of daniel lavocat
Sent: Friday, April 6, 2018 2:29 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] New Update for L32LogSync

 

Hello

WARNING : with the 2.0.1 version the name is L32 LogSync.exe

The 2.0.2 Version is : L32LogSync.exe (without the space character)

On the site Web the Title is " Current version : 2.0.1" but the current version is : 2.0.2

73


--
Daniel


F6FLU
Daniel Lavocat

F6FLU@...
http://F6FLU.fr

 


F6KOP Team #1277

 


UFT #1277
  

CDXC #1632  

DXCC CW #13586 




6 avril 2018 à 03:22

I have uploaded a new version to my website. This is an update only for the
.exe file. Open the zip after downloading it and unzip the file contents
into the install directory where you have installed L32LogSync.

http://www.n2amg.com/software/l32-logsync/

This version has fixes for a bunch of bugs including eQSL and ClubLog. Also
for the TQSL path error.

73 Rick N2AMG



 

 


 


Re: New Update for L32LogSync

Rick Ellison
 

I will upload a full installer later this morning that corrects everything..

73 Rick N2AMG

-----Original Message-----
From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Kp365
Oliver
Sent: Friday, April 6, 2018 6:17 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] New Update for L32LogSync

Yes ok Rick i come back without space.
But i have installed several days ago the prog with complete installer and
there is a space in the name of the .EXE. I've not touched anything.
Thats why i told you to correct it but if the complete installation now
write the EXE without space so it's ok

Thanks
73s
Olivier
F4FQH


-----Message d'origine-----
From: Rick Ellison
Sent: Friday, April 6, 2018 8:20 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] New Update for L32LogSync

No do not add a space to the name. I have removed the space as on some OS's
it causes the new update routines to not work correctly. Change your entries
in the L32 Utility menu that you have created. The name of the app is
L32LogSync.exe

When I make changes and post the file to the website the program will detect
the update is on the site and let you know there is an update available.
When you tell it to download it will download the updates and install them
for you. When testing this and switching languages some of the Russian based
and Chinese languages would not find the file to replace if it contained a
space. Thus I made the change.

73 Rick N2AMG

-----Original Message-----
From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Kp365
Oliver
Sent: Friday, April 6, 2018 2:09 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] New Update for L32LogSync

Hi Rick
Warning, there is no space on the name of the file between l32 and logsync.
Change it in the zip please.

If some people use the update before Rick correct it, add a space of it will
stay in .1.

73s
Olivier
F4FQH


-----Message d'origine-----
From: Rick Ellison
Sent: Friday, April 6, 2018 3:22 AM
To: hamlogger@groups.io
Subject: [hamlogger] New Update for L32LogSync

I have uploaded a new version to my website. This is an update only for the
.exe file. Open the zip after downloading it and unzip the file contents
into the install directory where you have installed L32LogSync.

http://www.n2amg.com/software/l32-logsync/

This version has fixes for a bunch of bugs including eQSL and ClubLog. Also
for the TQSL path error.

73 Rick N2AMG


Re: New Update for L32LogSync

Rick Ellison
 

Thanks for the report.. Will look at this this morning..

73 Rick N2AMG

-----Original Message-----
From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Vytas LY3BG
Sent: Friday, April 6, 2018 4:55 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] New Update for L32LogSync

2018.04.06 11:50:26 - Error- Main.WebUpload
=Error Report=
Conversion from string "DebugLog.txt" to type 'Double' is not valid.
at
Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String
Value, NumberFormatInfo NumberFormat)
at
Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value)
at L32LogSync.Main.UploadToClubLog()
=Error Report End=


73 Vytas LY3BG
www.qrz.lt/ly3bg


Re: New Update for L32LogSync

Rick Ellison
 

I will have to look at HamQTH and see what it takes but it shouldn’t be a problem…

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Fabian/EB1TR
Sent: Friday, April 6, 2018 2:30 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] New Update for L32LogSync

 

Hi Rick, thnaks for your work!

 

¿What do you think about add HamQTH upload and realtime features?

 

 

06.04.2018, 08:21, "Rick Ellison" <rellison@...>:

No do not add a space to the name. I have removed the space as on some OS's
it causes the new update routines to not work correctly. Change your entries
in the L32 Utility menu that you have created. The name of the app is
L32LogSync.exe

When I make changes and post the file to the website the program will detect
the update is on the site and let you know there is an update available.
When you tell it to download it will download the updates and install them
for you. When testing this and switching languages some of the Russian based
and Chinese languages would not find the file to replace if it contained a
space. Thus I made the change.

73 Rick N2AMG

-----Original Message-----
From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Kp365
Oliver
Sent: Friday, April 6, 2018 2:09 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] New Update for L32LogSync

Hi Rick
Warning, there is no space on the name of the file between l32 and logsync.
Change it in the zip please.

If some people use the update before Rick correct it, add a space of it will
stay in .1.

73s
Olivier
F4FQH


-----Message d'origine-----
From: Rick Ellison
Sent: Friday, April 6, 2018 3:22 AM
To: hamlogger@groups.io
Subject: [hamlogger] New Update for L32LogSync

I have uploaded a new version to my website. This is an update only for the
.exe file. Open the zip after downloading it and unzip the file contents
into the install directory where you have installed L32LogSync.

http://www.n2amg.com/software/l32-logsync/

This version has fixes for a bunch of bugs including eQSL and ClubLog. Also
for the TQSL path error.

73 Rick N2AMG










 

 

 

-- 

Fabian/EB1TR

 

8841 - 8860 of 82841