Date   

Re: No FT8 checkbox for mode

JOHN BIRKBY
 

Sorry, Darl. I can’t find it there. That’s why I’m here.

73,
Scott

E se


On Mar 10, 2020, at 5:06 PM, Darl DEEDS <na8w@...> wrote:



You can add any mode you wish! Look in the Help file for all the information! It’s very simple!

 

Darl  NA8W

 

From: n2qlt via Groups.Io
Sent: Tuesday, March 10, 2020 15:25
To: hamlogger@groups.io
Subject: [hamlogger] No FT8 checkbox for mode

 

I noticed that there is no checkbox for FT8 mode. If I use mode according to bandplan, it comes up with PSK31. And there is no way to enter FT8 if I want to make a manual log entry (that I can find). No big deal, when logging automatically with WSJT-X it does end up logging as FT8. But there is not a way to calculate DXCC stats, since there is no checkbox there either. Couldn't find anything in the help menu or by searching here. Has anyone found a way to deal with this?

One more thing, off subject. When messing with this issue, I clicked the wrong button apparently and logger32 moved all of my recent FT8 entries in the logbook window back to 1993. It didn't change anything in the loggings, just moved all of it far away. So I'm scratching my head here.

Any suggestions would be welcome!

 


Re: No FT8 checkbox for mode

JOHN BIRKBY
 

Thanks, Guary. I certainly do appreciate a helping hand. Sorry to sound so stupid. I’m talking about the logging window, and when you click on “mode” a window pops up that says BandMode selection. In the right hand side of that window under “mode” there are many modes listed but not FT8.
The other place I cannot find FT8 is when I click on the top menu under awards and select DXCC. When the window pops up there is a pulldown menu in the bottom left-hand corner that lists all of the modes, but FT8 is not among them. Thank you for your help.

73,
Scott


On Mar 10, 2020, at 4:26 PM, Gary Hinson <Gary@...> wrote:



Hello n2qlt.

 

What kind of checkbox would you like?  Where would you like it?  What would you like it to do?

 

Your email doesn’t make much sense.  Please try harder to explain your issue/s and we’ll try harder to help you.

 

73

Garuy  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of n2qlt via Groups.Io
Sent: 11 March 2020 08:25
To: hamlogger@groups.io
Subject: [hamlogger] No FT8 checkbox for mode

 

I noticed that there is no checkbox for FT8 mode. If I use mode according to bandplan, it comes up with PSK31. And there is no way to enter FT8 if I want to make a manual log entry (that I can find). No big deal, when logging automatically with WSJT-X it does end up logging as FT8. But there is not a way to calculate DXCC stats, since there is no checkbox there either. Couldn't find anything in the help menu or by searching here. Has anyone found a way to deal with this?

One more thing, off subject. When messing with this issue, I clicked the wrong button apparently and logger32 moved all of my recent FT8 entries in the logbook window back to 1993. It didn't change anything in the loggings, just moved all of it far away. So I'm scratching my head here.

Any suggestions would be welcome!


Re: No FT8 checkbox for mode

Darl DEEDS
 

You can add any mode you wish! Look in the Help file for all the information! It’s very simple!

 

Darl  NA8W

 

From: n2qlt via Groups.Io
Sent: Tuesday, March 10, 2020 15:25
To: hamlogger@groups.io
Subject: [hamlogger] No FT8 checkbox for mode

 

I noticed that there is no checkbox for FT8 mode. If I use mode according to bandplan, it comes up with PSK31. And there is no way to enter FT8 if I want to make a manual log entry (that I can find). No big deal, when logging automatically with WSJT-X it does end up logging as FT8. But there is not a way to calculate DXCC stats, since there is no checkbox there either. Couldn't find anything in the help menu or by searching here. Has anyone found a way to deal with this?

One more thing, off subject. When messing with this issue, I clicked the wrong button apparently and logger32 moved all of my recent FT8 entries in the logbook window back to 1993. It didn't change anything in the loggings, just moved all of it far away. So I'm scratching my head here.

Any suggestions would be welcome!

 


Re: No FT8 checkbox for mode

Gary Hinson
 

Hello n2qlt.

 

What kind of checkbox would you like?  Where would you like it?  What would you like it to do?

 

Your email doesn’t make much sense.  Please try harder to explain your issue/s and we’ll try harder to help you.

 

73

Garuy  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of n2qlt via Groups.Io
Sent: 11 March 2020 08:25
To: hamlogger@groups.io
Subject: [hamlogger] No FT8 checkbox for mode

 

I noticed that there is no checkbox for FT8 mode. If I use mode according to bandplan, it comes up with PSK31. And there is no way to enter FT8 if I want to make a manual log entry (that I can find). No big deal, when logging automatically with WSJT-X it does end up logging as FT8. But there is not a way to calculate DXCC stats, since there is no checkbox there either. Couldn't find anything in the help menu or by searching here. Has anyone found a way to deal with this?

One more thing, off subject. When messing with this issue, I clicked the wrong button apparently and logger32 moved all of my recent FT8 entries in the logbook window back to 1993. It didn't change anything in the loggings, just moved all of it far away. So I'm scratching my head here.

Any suggestions would be welcome!


No FT8 checkbox for mode

JOHN BIRKBY
 

I noticed that there is no checkbox for FT8 mode. If I use mode according to bandplan, it comes up with PSK31. And there is no way to enter FT8 if I want to make a manual log entry (that I can find). No big deal, when logging automatically with WSJT-X it does end up logging as FT8. But there is not a way to calculate DXCC stats, since there is no checkbox there either. Couldn't find anything in the help menu or by searching here. Has anyone found a way to deal with this?

One more thing, off subject. When messing with this issue, I clicked the wrong button apparently and logger32 moved all of my recent FT8 entries in the logbook window back to 1993. It didn't change anything in the loggings, just moved all of it far away. So I'm scratching my head here.

Any suggestions would be welcome!


Re: Update L32Logsync v 2.0.15

daniel lavocat <F6FLU@...>
 

Many thanks Rick
I tested the new feature to upload to QRZ.com that works fine
Thanks again
73

--
Daniel

F6FLU
Daniel Lavocat
F6FLU@...
https://f6flu.crx.cloud

F6KOP Team #1277


UFT #1277
  
CDXC #1632   DXCC CW #13586 


keith hotchkiss a écrit le 10/03/2020 à 17:31 :

Rick,
Thank you and all the smart people who keep writing and sharing the add ons for Logger32.

Many thanks
Keith - G0FEA


Re: Update L32Logsync v 2.0.15

keith hotchkiss
 

Rick,
Thank you and all the smart people who keep writing and sharing the add ons for Logger32.

Many thanks
Keith - G0FEA


Update L32Logsync v 2.0.15

Rick Ellison
 

I have just posted a new update for my L32Logsync application. It is
available at the link below.

This update has 2 main changes to the program.
1. It corrects a bug in the eQSL downloading of qso's for users whose
password contained Shifted characters. The parse routine was not correctly
escaping those characters.

2. This adds to the program the ability to upload individual qso's and log
files to the QRZ Logbook. Please note in order for the QRZ Logbook to work
the user is required to have one of the QRZ Subscriptions. The least being
the XML Lookup subscription ($29.99). If you do not have a subscription QRZ
will notify the user of this after it tries to upload the qso. This only
works with uploads. It does not work for Deletions and Fetching.

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


73 Rick N2AMG


--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


Re: LOTW Files

Ian Morrison
 

Import the log into Excel.


Sent from my mobile phone


-------- Original Message --------
Subject: [hamlogger] LOTW Files
From: Joe Ivey
To: "'hamlogger@groups.io'"
CC:


Is there a file or software that  can just fill in the worked/confirmed in the Logger32 logbook?

Seems I remember a post a few years ago of a software that would do just that. I have over 1200 QSO's that I need to confirm. Entering each one by hand would be a long process.

W4JSI, Joe



LOTW Files

Joe Ivey
 

Is there a file or software that  can just fill in the worked/confirmed in the Logger32 logbook?

Seems I remember a post a few years ago of a software that would do just that. I have over 1200 QSO's that I need to confirm. Entering each one by hand would be a long process.

W4JSI, Joe



Re: New file uploaded to hamlogger@groups.io

Sante - IK0HBN
 

Thank you Constantin!
Poka
Sante


At 09:31 09/03/2020, you wrote:

Hello,

This email message is a notification to let you know that the following files have been uploaded to the Files area of the hamlogger@groups.io group.
Uploaded By: Constantin UA1AKE <ua1ake@...>

Description:
Secondary Admin database for Russia (2642 districts for RDA award - January 2020)

Cheers,
The Groups.io Team


New file uploaded to hamlogger@groups.io

hamlogger@groups.io Notification <hamlogger+notification@...>
 

Hello,

This email message is a notification to let you know that the following files have been uploaded to the Files area of the hamlogger@groups.io group.

Uploaded By: Constantin UA1AKE <ua1ake@...>

Description:
Secondary Admin database for Russia (2642 districts for RDA award - January 2020)

Cheers,
The Groups.io Team


Re: L32, HDSDR and COM1 ---- FT-1000MP

Chuck Miller
 

I have an if-output installed in the Ft1000mp mkv field and the rsp1a connected to that. Then connected SDR-console to the Yaesu using Omni-Rig and then I connect Logger32 to the sdr-console using the external radio interface. Have a look at this thread near the bottom of page 2
.
https://groups.io/g/hamlogger/message/78936

If you are using a splitter (so the SDR is connected to the antenna instead of the if output) then you can use the method Rick N2AMG used.
73, Chuck
N0NC


L32, HDSDR and COM1 ---- FT-1000MP

Markku OH2BLV
 

How config this or is it impossible ?
I  try use VPSE virtual COM port,   L32 slave or echo  and   HDRSD omni-rig setup.
Rig and L32   or   rig and HDSDR working alone perfect
Please help me. 

de Markku OH2BLV


Re: Logbook

DL7VOG
 

Click onto the grid "DATE" in the "Previous QSOs" window. This should solve your problem.

73 - Gerd / DL7VOG



Am 06.03.2020 um 16:28 schrieb Tjerk:

Is it possible to change the logbook order so that the youngest/latest QSO appears on top row and not on the bottom?
Tjerk ZS6P
zs6p@...


Logbook

Tjerk
 

Is it possible to change the logbook order so that the youngest/latest QSO appears on top row and not on the bottom?
Tjerk ZS6P
zs6p@...


Re: Helpfile

Anthony Buscaglia
 

Hi Sante,

Thanks for the info and the invite.
Will let you know if get over there again!
We will pray that this virus situation will calm down and be properly contained.

I recognized your call and see we have had 18 Qs since 1994. All  CW.
CU on the bands!
Caio!

73
Tony


On Mar 6, 2020, at 3:47 AM, Sante - IK0HBN via Groups.Io <ik0hbn@...> wrote:

Hi Tony,
surely your surname could not hide your Italian origins! I'm sorry for the forced return of your granddaughter, but here the government was the first in Europe to put in place measures to contain the contagion, a contagion that has not started, as some shameful and false slides show, from Italy, but by a German gentleman who had contracted the infection in Shanghai. In any case, as an Italian saying goes, "every world is a village", in the sense that we are all in the same pot and therefore blame a country because it was the first to create a big and serious problem, it does not lead to any way to a solution. In Italy we have many cases of infection because here the government went to look for them and counted them. Different thing in other European countries that are only now realizing the big danger. Italy is currently a safe country, because it is putting in place everything that is possible to stem the infection ... we hope that Heaven will help us in this too. I apologize if Coronavirus is an OFF-Topic here, but I think that if we all live on planet Earth, this problem, hopefully not, could affect many other people. See you soon Tony and enjoy Italy the next time you come, I live 100 km north of Rome, almost on the border of Tuscany: make yourself heard the next time you come!
Hello and see you soon
Sante


At 19:57 05/03/2020, you wrote:
Sante,

Right you are!

Father: Montemaggiore Belsito, Sicilia� (Busscaglia)
Mother: Sumona, Abruzzi� (Marinucci)

Our granddaughter just came home from Florence.
She was attending a semester but they sent her home due to the virus.
She is not happy about having to return.

We have been to Italy many times.

Our favorite place to visit!
Hope to CU in the ARRL DX test this weekend?

Caio!

Tony




On Mar 5, 2020, at 1:08 PM, Sante - IK0HBN via Groups.Io < ik0hbn@...> wrote:

You welcome...
Your surname sounds a little italian...))
Ciao


At 19:06 05/03/2020, you wrote:
Hi Sante!

I just figured that out.

Thank you!

Caio!

Tony


On Mar 5, 2020, at 1:03 PM, Sante - IK0HBN via Groups.Io < ik0hbn@...> wrote:

Tony,
you must delete the file .chi.
73's Sante


At 18:50 05/03/2020, you wrote:
When I put the file in the L32 directory, I get this error. Then L32 hangs and I have to launch Task Mgr and Shut L32 down.
73
Tony
K2NV


<7d05e4e.png>

On Mar 5, 2020, at 12:43 PM, Anthony Buscaglia via Groups.Io <tonybb@... > wrote:

I downloaded an updated help file. Logger32.chm

I tried copying it to the Logger32 directory, but I canテδ「テつ�テつ冲 get it to come up in Logger32.

Whatテδ「テつ�テつ冱 the procedure?

Also is it normal for Windows UAC to come up every time I launch L32 on Win10?

73
TOny
K2NV




Re: Unable to open L32 and more

kenfilmer@outlook.com
 

Villi

 

That’s very useful, thanks, I’m trying it now!

 

73

Ken

G3XPO

 

Sent from Mail for Windows 10

 


From: hamlogger@groups.io <hamlogger@groups.io> on behalf of Vilhjalmur Sigurjonsson <vilhj@...>
Sent: Friday, March 6, 2020 11:08:39 AM
To: hamlogger@groups.io <hamlogger@groups.io>
Subject: Re: [hamlogger] Unable to open L32 and more
 

Ken,

The usual place for the bad.adi file is in the Logger32 directory, C:\Logger32.

It is a text file, you can edit it with any text editor, the default being notepad. If you try to open it from the Notepad file open menu, please note that the editor is only looking for .txt files by default, you have to specify to look for any file.

Further, you have to rename the bad.adi file in order to be able to use it for import, I usually call my files something with a date, e.g. today it would be fixed200306.adi.

The bad adi export puts comments in each entry declaring why it is bad and what needs to be changed, there is no need to remove the comments, they are ignored in the import process.

 

GL es 73 de Villi, TF3VS

 

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: föstudagur, 6. mars 2020 10:24
To: hamlogger@groups.io
Subject: Re: [hamlogger] Unable to open L32 and more

 

Hi Gary

 

Nice to hear from you again. You helped me with FT8 some months ago.

 

Many thanks for the advice.

 

I shall persevere with L32. Its just so !!!***@@@ frustrating after using L32 happily for years and years and then for no apparent reason it all goes to pot!

 

I’m no computer expert which is probably most of my problem, but with L32 I didn’t do anything I haven’t done hundreds of times before.

 

Thanks again.

 

By the way, how do I access the ‘BAD ADI FILE?’

 

That message (or something like it) came up when some ADIF contacts failed to load into the new L32 programme.

 

Thanks again, best to all from sunny Hawkinge!

 

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 


From: hamlogger@groups.io <hamlogger@groups.io> on behalf of Gary Hinson <Gary@...>
Sent: Thursday, March 5, 2020 11:44:52 PM
To: hamlogger@groups.io <hamlogger@groups.io>
Subject: Re: [hamlogger] Unable to open L32 and more

 

Hi Ken.

 

If you’d have asked for help earlier, we might have been able to avoid you having to reconfigure L32!  There should be backups of your L32 files, including the .INI configuration file, stashed somewhere on your computer.

 

Anyway …

 

First, just in case, take a backup copy of your ADIF log and save it somewhere safe, offline (e.g. on a USB stick or CD).  That way, if something goes horribly wrong, at least you won’t have lost your whole log. 

 

Since importing your log lost 5,000 QSOs, that suggests a fault in the ADIF file.  Since it appears 28,000 QSOs loaded OK, the fault is likely to lie between the 28,000 and 5,000, so roughly 85% of the way through the ADIF.  I would open the ADIF with a plain text editor (such as Wordpad or TED), scroll down 85% of the way and look for any obvious/gross` issues such as junk in the file, corrupted lines, blanks or whatever. 

 

If you find gross errors, correct them manually if you can and save the corrected ADIF file with a new name, otherwise save just the uncorrupted QSO records after that point to a new ADIF file, then import that into L32.

 

If you don’t find gross errors, you might try opening and checking through the ADIF file using ADIFmaster.  It understands the ADIF field names, showing your log as a table/spreadsheet.  It might tell you about errors as it opens the file (more clues for you to fix manually), or you can scroll down to see if it has the whole log (in which case, export the file to a new ADIF and, again, try importing that into L32).

 

I’m not sure what’s going on with the QSO numbering: I don’t pay much attention to QSO numbers, normally, but I know there is a function to “reformat” (i.e. renumber) QSO numbers for your whole log sequentially if it matters to you.  Try that.  Look under Tools:

 

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of kenfilmer@...
Sent: 06 March 2020 06:01
To: hamlogger@groups.io
Subject: [hamlogger] Unable to open L32 and more

 

I’ve happily used L32 for years until the last auto update came along this week. Once I updated I was unable open Logger32. I tried everything, no success so I reloaded the programme, set up bands and modes etc!

Loading my saved log ADIF L32 wouldn’t load some 5000 contacts and L32 said recalculate statistics, which I did.. Now whenever I log a contact despite the last QSO being numbered 28000, the next QSO number is number 1.

Has anybody any ideas what went wrong?

Ken G3XPO

 

Sent from Mail for Windows 10

 


Re: Unable to open L32 and more

Vilhjalmur Sigurjonsson
 

Ken,

The usual place for the bad.adi file is in the Logger32 directory, C:\Logger32.

It is a text file, you can edit it with any text editor, the default being notepad. If you try to open it from the Notepad file open menu, please note that the editor is only looking for .txt files by default, you have to specify to look for any file.

Further, you have to rename the bad.adi file in order to be able to use it for import, I usually call my files something with a date, e.g. today it would be fixed200306.adi.

The bad adi export puts comments in each entry declaring why it is bad and what needs to be changed, there is no need to remove the comments, they are ignored in the import process.

 

GL es 73 de Villi, TF3VS

 

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: föstudagur, 6. mars 2020 10:24
To: hamlogger@groups.io
Subject: Re: [hamlogger] Unable to open L32 and more

 

Hi Gary

 

Nice to hear from you again. You helped me with FT8 some months ago.

 

Many thanks for the advice.

 

I shall persevere with L32. Its just so !!!***@@@ frustrating after using L32 happily for years and years and then for no apparent reason it all goes to pot!

 

I’m no computer expert which is probably most of my problem, but with L32 I didn’t do anything I haven’t done hundreds of times before.

 

Thanks again.

 

By the way, how do I access the ‘BAD ADI FILE?’

 

That message (or something like it) came up when some ADIF contacts failed to load into the new L32 programme.

 

Thanks again, best to all from sunny Hawkinge!

 

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 


From: hamlogger@groups.io <hamlogger@groups.io> on behalf of Gary Hinson <Gary@...>
Sent: Thursday, March 5, 2020 11:44:52 PM
To: hamlogger@groups.io <hamlogger@groups.io>
Subject: Re: [hamlogger] Unable to open L32 and more

 

Hi Ken.

 

If you’d have asked for help earlier, we might have been able to avoid you having to reconfigure L32!  There should be backups of your L32 files, including the .INI configuration file, stashed somewhere on your computer.

 

Anyway …

 

First, just in case, take a backup copy of your ADIF log and save it somewhere safe, offline (e.g. on a USB stick or CD).  That way, if something goes horribly wrong, at least you won’t have lost your whole log. 

 

Since importing your log lost 5,000 QSOs, that suggests a fault in the ADIF file.  Since it appears 28,000 QSOs loaded OK, the fault is likely to lie between the 28,000 and 5,000, so roughly 85% of the way through the ADIF.  I would open the ADIF with a plain text editor (such as Wordpad or TED), scroll down 85% of the way and look for any obvious/gross` issues such as junk in the file, corrupted lines, blanks or whatever. 

 

If you find gross errors, correct them manually if you can and save the corrected ADIF file with a new name, otherwise save just the uncorrupted QSO records after that point to a new ADIF file, then import that into L32.

 

If you don’t find gross errors, you might try opening and checking through the ADIF file using ADIFmaster.  It understands the ADIF field names, showing your log as a table/spreadsheet.  It might tell you about errors as it opens the file (more clues for you to fix manually), or you can scroll down to see if it has the whole log (in which case, export the file to a new ADIF and, again, try importing that into L32).

 

I’m not sure what’s going on with the QSO numbering: I don’t pay much attention to QSO numbers, normally, but I know there is a function to “reformat” (i.e. renumber) QSO numbers for your whole log sequentially if it matters to you.  Try that.  Look under Tools:

 

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of kenfilmer@...
Sent: 06 March 2020 06:01
To: hamlogger@groups.io
Subject: [hamlogger] Unable to open L32 and more

 

I’ve happily used L32 for years until the last auto update came along this week. Once I updated I was unable open Logger32. I tried everything, no success so I reloaded the programme, set up bands and modes etc!

Loading my saved log ADIF L32 wouldn’t load some 5000 contacts and L32 said recalculate statistics, which I did.. Now whenever I log a contact despite the last QSO being numbered 28000, the next QSO number is number 1.

Has anybody any ideas what went wrong?

Ken G3XPO

 

Sent from Mail for Windows 10

 


Re: Unable to open L32 and more

kenfilmer@outlook.com
 

Hi Gary

 

Nice to hear from you again. You helped me with FT8 some months ago.

 

Many thanks for the advice.

 

I shall persevere with L32. Its just so !!!***@@@ frustrating after using L32 happily for years and years and then for no apparent reason it all goes to pot!

 

I’m no computer expert which is probably most of my problem, but with L32 I didn’t do anything I haven’t done hundreds of times before.

 

Thanks again.

 

By the way, how do I access the ‘BAD ADI FILE?’

 

That message (or something like it) came up when some ADIF contacts failed to load into the new L32 programme.

 

Thanks again, best to all from sunny Hawkinge!

 

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 


From: hamlogger@groups.io <hamlogger@groups.io> on behalf of Gary Hinson <Gary@...>
Sent: Thursday, March 5, 2020 11:44:52 PM
To: hamlogger@groups.io <hamlogger@groups.io>
Subject: Re: [hamlogger] Unable to open L32 and more
 

Hi Ken.

 

If you’d have asked for help earlier, we might have been able to avoid you having to reconfigure L32!  There should be backups of your L32 files, including the .INI configuration file, stashed somewhere on your computer.

 

Anyway …

 

First, just in case, take a backup copy of your ADIF log and save it somewhere safe, offline (e.g. on a USB stick or CD).  That way, if something goes horribly wrong, at least you won’t have lost your whole log. 

 

Since importing your log lost 5,000 QSOs, that suggests a fault in the ADIF file.  Since it appears 28,000 QSOs loaded OK, the fault is likely to lie between the 28,000 and 5,000, so roughly 85% of the way through the ADIF.  I would open the ADIF with a plain text editor (such as Wordpad or TED), scroll down 85% of the way and look for any obvious/gross` issues such as junk in the file, corrupted lines, blanks or whatever. 

 

If you find gross errors, correct them manually if you can and save the corrected ADIF file with a new name, otherwise save just the uncorrupted QSO records after that point to a new ADIF file, then import that into L32.

 

If you don’t find gross errors, you might try opening and checking through the ADIF file using ADIFmaster.  It understands the ADIF field names, showing your log as a table/spreadsheet.  It might tell you about errors as it opens the file (more clues for you to fix manually), or you can scroll down to see if it has the whole log (in which case, export the file to a new ADIF and, again, try importing that into L32).

 

I’m not sure what’s going on with the QSO numbering: I don’t pay much attention to QSO numbers, normally, but I know there is a function to “reformat” (i.e. renumber) QSO numbers for your whole log sequentially if it matters to you.  Try that.  Look under Tools:

 

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of kenfilmer@...
Sent: 06 March 2020 06:01
To: hamlogger@groups.io
Subject: [hamlogger] Unable to open L32 and more

 

I’ve happily used L32 for years until the last auto update came along this week. Once I updated I was unable open Logger32. I tried everything, no success so I reloaded the programme, set up bands and modes etc!

Loading my saved log ADIF L32 wouldn’t load some 5000 contacts and L32 said recalculate statistics, which I did.. Now whenever I log a contact despite the last QSO being numbered 28000, the next QSO number is number 1.

Has anybody any ideas what went wrong?

Ken G3XPO

 

Sent from Mail for Windows 10

 

4501 - 4520 of 83581