Date   

Re: Distance

Rob
 
Edited

opps that was a typo on my behalf.... I just exported some QSOs with no distance calculaTED.

Opened a new logbook, imported them.......and still no distance.

Regards

Rob


On Tue, Feb 9, 2021 at 10:15 AM, Bob wrote:
<!doctype html>
Rob, you said (in your original post) that distance is calculated on log import. Does that give you any clues as to how you might go about respectively populating the distance fields? And, before you go buggering around, please make an ADIF backup and hide it under the mattress. SeventyThree(s).
On 02/09/2021 2:57 AM Rob <rob.harrison@...> wrote:
 
 
Thanks Bob, I have that ticked...is there anyway to retrospectively calculate distance when it hasn't been populated?

73

Rob

On Mon, Feb 8, 2021 at 07:12 PM, Bob wrote:
<!doctype html>
On the logbook entry window right click on any entry field. Click SETUP. Check the option to AUTOLOG DISTANCE, etc. 73.
On 02/08/2021 1:23 PM Rob <rob.harrison@...> wrote:
 
 
Is there anyway of forcing L32 to calculate the distance if it is not populated.

I notice distance is calculated on log imports and manually entered qso's

73 de Rob G4UJS


Re: JTDX/WSJTX via Logger32

Bob
 

If, on the second computer, you can't see the checkbox for "on top" and "high priority", can you see the APPLY and CANCEL buttons? 73.
 

On 02/09/2021 3:00 AM Vilhjalmur Sigurjonsson < vilhj@...> wrote:
 
 
DR Peter,
I would try to increase the delay after starting the JTDX a little on
the 2nd computer.
(UDP band map, Start, Delay ... at the bottom of the menu).
73 Villi
TF3VS
 
On 2021-02-09 07:42, Peter Eckersberger wrote:
Hello,
 
I'm using JTDX/WSJTX on 2 computers together with Logger32. Fantastic
combination! Especially the "cherry picking" is really something
special. But one thing I'm witnessing now for a few days is a bit
irritating. Although on both computers all the different settings are
exactly the same (including the checks for "Start WSJTX/JTDX as "on
Top" Window" and "Start WSJTX/JTDX to run at high priority" in the
Setup starts menu).
 
On comp #1 everything is fine but on the 2nd comp the expected text
"On-top, high priority" is missing though this was working before.
 
Well, this missing text means that both commands "On-top" and "high
priority" are not executed. In other words when ever I'm clicking on a
callsign both program windows JTDX/WSJTX and Wide Graph are
disappearing and have to be recalled by the operator every single
time! Quite boring. What for gods sake am I doing wrong? As I said ...
on the second comp everything works fine although all the settings are
the same. At least AFAIK 😭. I didn't find any difference.
 
Additional info: OS on both computers is Windows 10 HOME with all the
very latest updates, Logger32 v 4.0.242, JTDX v 2.2.0 rc155 and WSJTX
v 2.3.0.
 
Any reasonable advise would be highly appreciated. TIA!
 
73 de Peter, OE3EPW
 
 
 
Links:
------
 
 


Re: Distance

Bob
 

Rob, you said (in your original post) that distance is calculated on log import. Does that give you any clues as to how you might go about respectively populating the distance fields? And, before you go buggering around, please make an ADIF backup and hide it under the mattress. SeventyThree(s).

On 02/09/2021 2:57 AM Rob <rob.harrison@...> wrote:
 
 
Thanks Bob, I have that ticked...is there anyway to retrospectively calculate distance when it hasn't been populated?

73

Rob

On Mon, Feb 8, 2021 at 07:12 PM, Bob wrote:
<!doctype html>
On the logbook entry window right click on any entry field. Click SETUP. Check the option to AUTOLOG DISTANCE, etc. 73.
On 02/08/2021 1:23 PM Rob <rob.harrison@...> wrote:
 
 
Is there anyway of forcing L32 to calculate the distance if it is not populated.

I notice distance is calculated on log imports and manually entered qso's

73 de Rob G4UJS


Re: Distance

Giuseppe Giunta
 

Ciao Guys,
I am equally interested in a retrospective calculation of the Km, of my + 118k Qso. Thank you, Giu IT9VDQ
(one of IB9T)


Il giorno mar 9 feb 2021 alle ore 08:57 Rob <rob.harrison@...> ha scritto:
Thanks Bob, I have that ticked...is there anyway to retrospectively calculate distance when it hasn't been populated?

73

Rob

On Mon, Feb 8, 2021 at 07:12 PM, Bob wrote:
<!doctype html>
On the logbook entry window right click on any entry field. Click SETUP. Check the option to AUTOLOG DISTANCE, etc. 73.
On 02/08/2021 1:23 PM Rob <rob.harrison@...> wrote:
 
 
Is there anyway of forcing L32 to calculate the distance if it is not populated.

I notice distance is calculated on log imports and manually entered qso's

73 de Rob G4UJS


Re: JTDX/WSJTX via Logger32

Vilhjalmur Sigurjonsson
 

DR Peter,
I would try to increase the delay after starting the JTDX a little on the 2nd computer.
(UDP band map, Start, Delay ... at the bottom of the menu).
73 Villi
TF3VS

On 2021-02-09 07:42, Peter Eckersberger wrote:
Hello,
I'm using JTDX/WSJTX on 2 computers together with Logger32. Fantastic
combination! Especially the "cherry picking" is really something
special. But one thing I'm witnessing now for a few days is a bit
irritating. Although on both computers all the different settings are
exactly the same (including the checks for "Start WSJTX/JTDX as "on
Top" Window" and "Start WSJTX/JTDX to run at high priority" in the
Setup starts menu).
On comp #1 everything is fine but on the 2nd comp the expected text
"On-top, high priority" is missing though this was working before.
Well, this missing text means that both commands "On-top" and "high
priority" are not executed. In other words when ever I'm clicking on a
callsign both program windows JTDX/WSJTX and Wide Graph are
disappearing and have to be recalled by the operator every single
time! Quite boring. What for gods sake am I doing wrong? As I said ...
on the second comp everything works fine although all the settings are
the same. At least AFAIK 😭. I didn't find any difference.
Additional info: OS on both computers is Windows 10 HOME with all the
very latest updates, Logger32 v 4.0.242, JTDX v 2.2.0 rc155 and WSJTX
v 2.3.0.
Any reasonable advise would be highly appreciated. TIA!
73 de Peter, OE3EPW
Links:
------
[1] https://groups.io/g/hamlogger/message/82587
[2] https://groups.io/mt/80499485/385597
[3] https://groups.io/g/hamlogger/post
[4] https://groups.io/g/hamlogger/editsub/385597
[5] https://groups.io/g/hamlogger/leave/defanged


Re: Distance

Rob
 

Thanks Bob, I have that ticked...is there anyway to retrospectively calculate distance when it hasn't been populated?

73

Rob


On Mon, Feb 8, 2021 at 07:12 PM, Bob wrote:
<!doctype html>
On the logbook entry window right click on any entry field. Click SETUP. Check the option to AUTOLOG DISTANCE, etc. 73.
On 02/08/2021 1:23 PM Rob <rob.harrison@...> wrote:
 
 
Is there anyway of forcing L32 to calculate the distance if it is not populated.

I notice distance is calculated on log imports and manually entered qso's

73 de Rob G4UJS


JTDX/WSJTX via Logger32

Peter Eckersberger
 

Hello,

I'm using JTDX/WSJTX on 2 computers together with Logger32. Fantastic combination! Especially the "cherry picking" is really something special. But one thing I'm witnessing now for a few days is a bit irritating. Although on both computers all the different settings are exactly the same (including the checks for "Start WSJTX/JTDX as "on Top"  Window" and "
Start WSJTX/JTDX to run at high priority" in the Setup starts menu).

On comp #1 everything is fine but on the 2nd comp the expected text "On-top, high priority" is missing though this was working before.

Well, this missing text means that both commands
"On-top" and "high priority" are not executed. In other words when ever I'm clicking on a callsign both program windows JTDX/WSJTX and Wide Graph are disappearing and have to be recalled by the operator every single time! Quite boring. What for gods sake am I doing wrong? As I said ... on the second comp everything works fine although all the settings are the same. At least AFAIK 😭. I didn't find any difference.

Additional info: OS on both computers is Windows 10 HOME with all the very latest updates, Logger32 v 4.0.242, JTDX v 2.2.0 rc155 and WSJTX v 2.3.0.

Any reasonable advise would be highly appreciated. TIA!


73 de Peter, OE3EPW



Re: Tracking DX Marathon

Michael Herron
 

Yes it is just for the current year. I saw you can do that but it can be a lot of scrolling around. As a Simple Award, it is a much smaller database window with just small check boxes which can be much more quick and handy. 
In searching about it in this group, I only saw where one other person had asked about the same thing but got no answers. I did see on the logger32 webpage that the DX Marathon is supported but did not see where it was specifically discussed or to what extent it was supported. 
Since the grid or database that would be great to use showed up in the simple awards,
It just seems to need to be populated.
Mike K7MH.

On Feb 8, 2021, at 8:18 PM, n5kd <n5kd@...> wrote:



Hi Mike,

 

I’m thinking what you need are the DXCC stats for the current year, or is it more involved?
If I’m right, then select AWARDS | DXCC – But at the bottom row select 2021 instead of complete logbook.
Same thing in the Worked/Confirmed window.

 

73’ Pete, N5KD.

<7BF7944E94F94507922E11A93B04325C[28373396].png>

 

From: Michael Herron
Sent: Tuesday, February 9, 2021 12:35 AM
To: hamlogger@groups.io
Subject: [hamlogger] Tracking DX Marathon

 

I would like to track DX Marathon stats in Logger32. I entered it in the

simple awards and the tracking database does show up, so far so good!

I am however not sure how to get my log entries to show up in that

database. I suspect there is a checkbox somewhere to enable that but I

have not found the way as yet.

Any hints would be much appreciated!

Mike K7MH

 

--

This email has been checked for viruses by Avast antivirus software.

https://www.avast.com/antivirus

 

 

 

 

 

 


Virus-free. www.avg.com
<7BF7944E94F94507922E11A93B04325C[28373396].png>


Re: Tracking DX Marathon

n5kd
 

Hi Mike,

 

I’m thinking what you need are the DXCC stats for the current year, or is it more involved?
If I’m right, then select AWARDS | DXCC – But at the bottom row select 2021 instead of complete logbook.
Same thing in the Worked/Confirmed window.

 

73’ Pete, N5KD.

 

From: Michael Herron
Sent: Tuesday, February 9, 2021 12:35 AM
To: hamlogger@groups.io
Subject: [hamlogger] Tracking DX Marathon

 

I would like to track DX Marathon stats in Logger32. I entered it in the

simple awards and the tracking database does show up, so far so good!

I am however not sure how to get my log entries to show up in that

database. I suspect there is a checkbox somewhere to enable that but I

have not found the way as yet.

Any hints would be much appreciated!

Mike K7MH

 

--

This email has been checked for viruses by Avast antivirus software.

https://www.avast.com/antivirus

 

 

 

 

 

 


Virus-free. www.avg.com


Tracking DX Marathon

Michael Herron
 

I would like to track DX Marathon stats in Logger32. I entered it in the simple awards and the tracking database does show up, so far so good!
I am however not sure how to get my log entries to show up in that database. I suspect there is a checkbox somewhere to enable that but I have not found the way as yet.
Any hints would be much appreciated!
Mike K7MH

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


Re: Distance

Bob
 

On the logbook entry window right click on any entry field. Click SETUP. Check the option to AUTOLOG DISTANCE, etc. 73.

On 02/08/2021 1:23 PM Rob <rob.harrison@...> wrote:
 
 
Is there anyway of forcing L32 to calculate the distance if it is not populated.

I notice distance is calculated on log imports and manually entered qso's

73 de Rob G4UJS


Distance

Rob
 

Is there anyway of forcing L32 to calculate the distance if it is not populated.

I notice distance is calculated on log imports and manually entered qso's

73 de Rob G4UJS


Logger32: v.4.0.242

Steph, F5NZY
 

Hi all,

I have been using Logger32 for over 20 years. I remember version 7.09b, in 16 bits.

Spontaneously, I would have liked to send Bob a good bottle, but when he says :

"It is 100% free. No donations solicited or accepted. SeventyThreeThree(s)."

I respectfully bow.

I am always quite amazed at the subtleties that Logger32 offers.

I migrated from v3.50.421 to v4.0.242 without the slightest problem.

I RTFM and followed the procedure.

An attaboy for you, Bob ! 😉

73 de Steph, F5NZY.

-- 
Everything looks impossible to the people who never tried, anything.
Dr J-L Etienne.


logger32 v4

splat1956
 

Thank you Bob and team !
I upgraded to v4 and then to the current version of v4 this weekend.
I waited until people had more experience with the upgrade in case I had problems. I had an issue with the autoupdate but the v4 manual addressed my issue and it is working great. Thank you for all of the effort on the program and the documentation.
Your work is appreciated.
David W9PH


Thanks to all for V4

kenfilmer@outlook.com
 

Bob et al,

 

Just wanted to say thanks for the issue of V4. My L32 log goes back 20 years now and I can’t envisage playing radio without it.

 

With some trepidation (because I know nothing about PCs and was sure something would go wrong!) I updated last night and everything was fine. No problems.

 

I shall now spend time trying to get to know all the enhancements in V4.

 

So Bob and all the developers, that’s a huge amount of work you have put in, my thanks.

 

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 


Re: Resolved ..... : [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

Rick Ellison
 

Oh geeesss.. You’re going to make his head swell..:)

 

73 Rick

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Alex Del Chicca
Sent: Sunday, February 7, 2021 4:38 PM
To: hamlogger@groups.io
Subject: Re: Resolved ..... : [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

Look Bob that I am not a habit of giving compliments ... you are great (but you already knew that .. hi),

as well as those who collaborate with you.     73

 

 

Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di Bob
Inviato: domenica 7 febbraio 2021 21:48
A: hamlogger@groups.io
Oggetto: Re: Resolved ..... : [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

It is 100% free. No donations solicited or accepted. SeventyThree(s).

On 02/07/2021 3:41 PM Alex Del Chicca <ik5pwj@...> wrote:

 

 

Hello everyone,

after trying various solutions to the problem that I had inherent in the random crash of the Loggger32, going into conflict with some .dll libraries,

I was able to eliminate this problem by deleting the old logger32.ini file.

So after the new installation, I reconfigured the logger32 v.4 from scratch and made the updates to the latest version,

it works without crashing, after a day of continuous operation.

Sure, but I don't know what, the problem was in the configuration .ini wires which had problems.

 

Bob I'm sorry to have caused you trouble ..... but as already written the logger32 is, in my humble opinion, the best log for OM,

and I could not give up its use (as you also Bob wrote in your msg. given the strange problem I had).

 

Moreover, the LOGGER32 is free and honestly I have also looked for in the past how to contribute in some way to help

with the expenses incurred, but I have not found any indication about it.

 

I would therefore like to have, if possible, the info to be able to send a small contribution in support of the Logger32 group.

 

Thanks again Bob for the great work you have done and are doing.

 

73 Alex ik5pwj

 

Da: ik5pwj@... <ik5pwj@...>
Inviato: lunedì 1 febbraio 2021 00:57
A: 'hamlogger@groups.io' <hamlogger@groups.io>
Oggetto: R: [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

Hi Rich, no I don't have a VPN connection ... it's disabled in my router.

 

However, the connection of the router and the private network active on my PCs at home has always worked

and it works even now with Logger32 vers. 3.50.424 without any crashes.    Only with vers. 4.0 ... I have these problems.

 

For Pete N5KD .... I tried to connect with other clusters also with VE7CC but the problem remains ... and logger32 vers. 4

 

crashes and gives the error I indicated in my msg. previous one.

 

Alex ik5pwj

 

Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di n5kd
Inviato: lunedì 1 febbraio 2021 00:25
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

Some Logger32 users are using VE7CC to connect to the cluster, then L32 connects to the VE7CC program.

 

73’ Pete, N5KD.

 

From: Rick EA4M via groups.io
Sent: Sunday, January 31, 2021 10:57 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

Do you have an active VPN connection?

 

 

 

 

El dom., 31 ene. 2021 23:42, Alex Del Chicca <ik5pwj@...> escribió:

Yes sure ... W10Pro 64Bit  regular activetion and new installation.

All other programs work without any problems.

Only Logger32 goes shutdown when the connection via telnet to any cluster is active (I tried to change the source cluster but it is the same).

Without any connection via telnet or via Local Host the Logger32 works.

 

By chance, if the telnet connection is active, it goes shutdown giving these errors in the Windows 10 Registry which I report below:

 

Name of the application that generated the error: Logger32.exe, version 4.0.0.239. timestamp: 0x6016cb77

Name of the module that generated the error: ucrtbase.dll, version 10.0.19041.546, timestamp: 0x73123758

Exception code: 0x0000409

Error offset 0x0009edbb

Process ID that generated the error: 0x01d6f813bf37a4d2

Path of the application that generated the error: C: \ Logger32 \ logger32.exe

Path to the module that generated the error: C: \ Windows \ System32 \ ucrtbase.dll

Reporting ID 414728f1-fa55-4025-a0f6-943ededab69e

 

That's all.....

Thanks anyway

73 Alex ik5pwj

 

Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di Rick EA4M via groups.io
Inviato: domenica 31 gennaio 2021 23:23
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

Are you sure that W10 is fully up to date????

 

El dom., 31 ene. 2021 23:16, Alex Del Chicca <ik5pwj@...> escribió:

Bob, thanks ..... I still sent a screen shot showing the error.

 Anyway, thanks and ..... he followed your advice ......

73

 

Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di Bob
Inviato: domenica 31 gennaio 2021 22:59
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

Alex, I have no idea. Maybe you need a different logging program? 73.

On 01/31/2021 4:55 PM Alex Del Chicca <ik5pwj@...> wrote:

 

 

Hi all,

Hi Bob, unfortunately I have to write this msg. because as you will read the logger32 ver.4 crash problem has come back

and now in another way.

After having reinstalled the operating system Windows 10 PRO 64B and some basic programs ex new, I also reinstalled

the logger32 and updated with the whole database to the latest version 4.0 ...

 

I left the loggger32 connected to the local cluster and everything seemed ok as after several hours of operation the logger32 was UP and working.

 

I installed other programs including SmartSDR v.2.6.2 and other programs with which the logger32 v.3.5 worked perfectly

without ever interrupting with the connection to the cluster active.

 

Now with the 4.0.238 version but also with 239 the logger32 crashes it closes sending these msg.

in the "Administrative Events" file and in the "Windows \ Applications Registry  and that I insert as a screen shot in this mail.

 

They are in Italian and in any case, as you can verify with a translator, the two crashes, for example of 31 / jan / 2021 at 21 : 47: 32 and at 21:57:38

they are derived from program C: \ LOGGER32 \ lOGGER32.EXE

 

and the path of the module that generated the error is in: C: \ Windows \ System32 \ ucrtbase.dll

 

As you can see from the images that I report below to my msg.

Unfortunately I have absolutely no knowledge to be able to understand and remedy this problem.

 

f you need more info about the complete error described in the Windows Logs, let me know ....... now I have

not written it completely as the copy and paste does not work and I should write it completely, but if you are necessary I will send it .

 

What do you think Bob?

 

I await your reply Bob ....

Thank you

73 Alex ik5pwj

 

 

Virus-free. www.avg.com

 


Re: Resolved ..... : [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

Alex Del Chicca
 

Look Bob that I am not a habit of giving compliments ... you are great (but you already knew that .. hi),

as well as those who collaborate with you.     73

 

 

Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di Bob
Inviato: domenica 7 febbraio 2021 21:48
A: hamlogger@groups.io
Oggetto: Re: Resolved ..... : [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

It is 100% free. No donations solicited or accepted. SeventyThree(s).

On 02/07/2021 3:41 PM Alex Del Chicca <ik5pwj@...> wrote:

 

 

Hello everyone,

after trying various solutions to the problem that I had inherent in the random crash of the Loggger32, going into conflict with some .dll libraries,

I was able to eliminate this problem by deleting the old logger32.ini file.

So after the new installation, I reconfigured the logger32 v.4 from scratch and made the updates to the latest version,

it works without crashing, after a day of continuous operation.

Sure, but I don't know what, the problem was in the configuration .ini wires which had problems.

 

Bob I'm sorry to have caused you trouble ..... but as already written the logger32 is, in my humble opinion, the best log for OM,

and I could not give up its use (as you also Bob wrote in your msg. given the strange problem I had).

 

Moreover, the LOGGER32 is free and honestly I have also looked for in the past how to contribute in some way to help

with the expenses incurred, but I have not found any indication about it.

 

I would therefore like to have, if possible, the info to be able to send a small contribution in support of the Logger32 group.

 

Thanks again Bob for the great work you have done and are doing.

 

73 Alex ik5pwj

 

Da: ik5pwj@... <ik5pwj@...>
Inviato: lunedì 1 febbraio 2021 00:57
A: 'hamlogger@groups.io' <hamlogger@groups.io>
Oggetto: R: [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

Hi Rich, no I don't have a VPN connection ... it's disabled in my router.

 

However, the connection of the router and the private network active on my PCs at home has always worked

and it works even now with Logger32 vers. 3.50.424 without any crashes.    Only with vers. 4.0 ... I have these problems.

 

For Pete N5KD .... I tried to connect with other clusters also with VE7CC but the problem remains ... and logger32 vers. 4

 

crashes and gives the error I indicated in my msg. previous one.

 

Alex ik5pwj

 

Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di n5kd
Inviato: lunedì 1 febbraio 2021 00:25
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

Some Logger32 users are using VE7CC to connect to the cluster, then L32 connects to the VE7CC program.

 

73’ Pete, N5KD.

 

From: Rick EA4M via groups.io
Sent: Sunday, January 31, 2021 10:57 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

Do you have an active VPN connection?

 

 

 

 

El dom., 31 ene. 2021 23:42, Alex Del Chicca <ik5pwj@...> escribió:

Yes sure ... W10Pro 64Bit  regular activetion and new installation.

All other programs work without any problems.

Only Logger32 goes shutdown when the connection via telnet to any cluster is active (I tried to change the source cluster but it is the same).

Without any connection via telnet or via Local Host the Logger32 works.

 

By chance, if the telnet connection is active, it goes shutdown giving these errors in the Windows 10 Registry which I report below:

 

Name of the application that generated the error: Logger32.exe, version 4.0.0.239. timestamp: 0x6016cb77

Name of the module that generated the error: ucrtbase.dll, version 10.0.19041.546, timestamp: 0x73123758

Exception code: 0x0000409

Error offset 0x0009edbb

Process ID that generated the error: 0x01d6f813bf37a4d2

Path of the application that generated the error: C: \ Logger32 \ logger32.exe

Path to the module that generated the error: C: \ Windows \ System32 \ ucrtbase.dll

Reporting ID 414728f1-fa55-4025-a0f6-943ededab69e

 

That's all.....

Thanks anyway

73 Alex ik5pwj

 

Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di Rick EA4M via groups.io
Inviato: domenica 31 gennaio 2021 23:23
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

Are you sure that W10 is fully up to date????

 

El dom., 31 ene. 2021 23:16, Alex Del Chicca <ik5pwj@...> escribió:

Bob, thanks ..... I still sent a screen shot showing the error.

 Anyway, thanks and ..... he followed your advice ......

73

 

Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di Bob
Inviato: domenica 31 gennaio 2021 22:59
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

Alex, I have no idea. Maybe you need a different logging program? 73.

On 01/31/2021 4:55 PM Alex Del Chicca <ik5pwj@...> wrote:

 

 

Hi all,

Hi Bob, unfortunately I have to write this msg. because as you will read the logger32 ver.4 crash problem has come back

and now in another way.

After having reinstalled the operating system Windows 10 PRO 64B and some basic programs ex new, I also reinstalled

the logger32 and updated with the whole database to the latest version 4.0 ...

 

I left the loggger32 connected to the local cluster and everything seemed ok as after several hours of operation the logger32 was UP and working.

 

I installed other programs including SmartSDR v.2.6.2 and other programs with which the logger32 v.3.5 worked perfectly

without ever interrupting with the connection to the cluster active.

 

Now with the 4.0.238 version but also with 239 the logger32 crashes it closes sending these msg.

in the "Administrative Events" file and in the "Windows \ Applications Registry  and that I insert as a screen shot in this mail.

 

They are in Italian and in any case, as you can verify with a translator, the two crashes, for example of 31 / jan / 2021 at 21 : 47: 32 and at 21:57:38

they are derived from program C: \ LOGGER32 \ lOGGER32.EXE

 

and the path of the module that generated the error is in: C: \ Windows \ System32 \ ucrtbase.dll

 

As you can see from the images that I report below to my msg.

Unfortunately I have absolutely no knowledge to be able to understand and remedy this problem.

 

f you need more info about the complete error described in the Windows Logs, let me know ....... now I have

not written it completely as the copy and paste does not work and I should write it completely, but if you are necessary I will send it .

 

What do you think Bob?

 

I await your reply Bob ....

Thank you

73 Alex ik5pwj

 

 

Virus-free. www.avg.com

 


Re: Resolved ..... : [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

Bob
 

It is 100% free. No donations solicited or accepted. SeventyThree(s).

On 02/07/2021 3:41 PM Alex Del Chicca <ik5pwj@...> wrote:
 
 

Hello everyone,

after trying various solutions to the problem that I had inherent in the random crash of the Loggger32, going into conflict with some .dll libraries,

I was able to eliminate this problem by deleting the old logger32.ini file.

So after the new installation, I reconfigured the logger32 v.4 from scratch and made the updates to the latest version,

it works without crashing, after a day of continuous operation.

Sure, but I don't know what, the problem was in the configuration .ini wires which had problems.

 

Bob I'm sorry to have caused you trouble ..... but as already written the logger32 is, in my humble opinion, the best log for OM,

and I could not give up its use (as you also Bob wrote in your msg. given the strange problem I had).

 

Moreover, the LOGGER32 is free and honestly I have also looked for in the past how to contribute in some way to help

with the expenses incurred, but I have not found any indication about it.

 

I would therefore like to have, if possible, the info to be able to send a small contribution in support of the Logger32 group.

 

Thanks again Bob for the great work you have done and are doing.

 

73 Alex ik5pwj

 

Da: ik5pwj@... <ik5pwj@...>
Inviato: lunedì 1 febbraio 2021 00:57
A: 'hamlogger@groups.io' <hamlogger@groups.io>
Oggetto: R: [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

Hi Rich, no I don't have a VPN connection ... it's disabled in my router.

 

However, the connection of the router and the private network active on my PCs at home has always worked

and it works even now with Logger32 vers. 3.50.424 without any crashes.    Only with vers. 4.0 ... I have these problems.

 

For Pete N5KD .... I tried to connect with other clusters also with VE7CC but the problem remains ... and logger32 vers. 4

 

crashes and gives the error I indicated in my msg. previous one.

 

Alex ik5pwj

 

Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di n5kd
Inviato: lunedì 1 febbraio 2021 00:25
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

Some Logger32 users are using VE7CC to connect to the cluster, then L32 connects to the VE7CC program.

 

73’ Pete, N5KD.

 

From: Rick EA4M via groups.io
Sent: Sunday, January 31, 2021 10:57 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

Do you have an active VPN connection?

 

 

 

 

El dom., 31 ene. 2021 23:42, Alex Del Chicca <ik5pwj@...> escribió:

Yes sure ... W10Pro 64Bit  regular activetion and new installation.

All other programs work without any problems.

Only Logger32 goes shutdown when the connection via telnet to any cluster is active (I tried to change the source cluster but it is the same).

Without any connection via telnet or via Local Host the Logger32 works.

 

By chance, if the telnet connection is active, it goes shutdown giving these errors in the Windows 10 Registry which I report below:

 

Name of the application that generated the error: Logger32.exe, version 4.0.0.239. timestamp: 0x6016cb77

Name of the module that generated the error: ucrtbase.dll, version 10.0.19041.546, timestamp: 0x73123758

Exception code: 0x0000409

Error offset 0x0009edbb

Process ID that generated the error: 0x01d6f813bf37a4d2

Path of the application that generated the error: C: \ Logger32 \ logger32.exe

Path to the module that generated the error: C: \ Windows \ System32 \ ucrtbase.dll

Reporting ID 414728f1-fa55-4025-a0f6-943ededab69e

 

That's all.....

Thanks anyway

73 Alex ik5pwj

 

Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di Rick EA4M via groups.io
Inviato: domenica 31 gennaio 2021 23:23
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

Are you sure that W10 is fully up to date????

 

El dom., 31 ene. 2021 23:16, Alex Del Chicca <ik5pwj@...> escribió:

Bob, thanks ..... I still sent a screen shot showing the error.

 Anyway, thanks and ..... he followed your advice ......

73

 

Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di Bob
Inviato: domenica 31 gennaio 2021 22:59
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

Alex, I have no idea. Maybe you need a different logging program? 73.

On 01/31/2021 4:55 PM Alex Del Chicca <ik5pwj@...> wrote:

 

 

Hi all,

Hi Bob, unfortunately I have to write this msg. because as you will read the logger32 ver.4 crash problem has come back

and now in another way.

After having reinstalled the operating system Windows 10 PRO 64B and some basic programs ex new, I also reinstalled

the logger32 and updated with the whole database to the latest version 4.0 ...

 

I left the loggger32 connected to the local cluster and everything seemed ok as after several hours of operation the logger32 was UP and working.

 

I installed other programs including SmartSDR v.2.6.2 and other programs with which the logger32 v.3.5 worked perfectly

without ever interrupting with the connection to the cluster active.

 

Now with the 4.0.238 version but also with 239 the logger32 crashes it closes sending these msg.

in the "Administrative Events" file and in the "Windows \ Applications Registry  and that I insert as a screen shot in this mail.

 

They are in Italian and in any case, as you can verify with a translator, the two crashes, for example of 31 / jan / 2021 at 21 : 47: 32 and at 21:57:38

they are derived from program C: \ LOGGER32 \ lOGGER32.EXE

 

and the path of the module that generated the error is in: C: \ Windows \ System32 \ ucrtbase.dll

 

As you can see from the images that I report below to my msg.

Unfortunately I have absolutely no knowledge to be able to understand and remedy this problem.

 

f you need more info about the complete error described in the Windows Logs, let me know ....... now I have

not written it completely as the copy and paste does not work and I should write it completely, but if you are necessary I will send it .

 

What do you think Bob?

 

I await your reply Bob ....

Thank you

73 Alex ik5pwj

 

 

Virus-free. www.avg.com

 


Resolved ..... : [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

Alex Del Chicca
 

Hello everyone,

after trying various solutions to the problem that I had inherent in the random crash of the Loggger32, going into conflict with some .dll libraries,

I was able to eliminate this problem by deleting the old logger32.ini file.

So after the new installation, I reconfigured the logger32 v.4 from scratch and made the updates to the latest version,

it works without crashing, after a day of continuous operation.

Sure, but I don't know what, the problem was in the configuration .ini wires which had problems.

 

Bob I'm sorry to have caused you trouble ..... but as already written the logger32 is, in my humble opinion, the best log for OM,

and I could not give up its use (as you also Bob wrote in your msg. given the strange problem I had).

 

Moreover, the LOGGER32 is free and honestly I have also looked for in the past how to contribute in some way to help

with the expenses incurred, but I have not found any indication about it.

 

I would therefore like to have, if possible, the info to be able to send a small contribution in support of the Logger32 group.

 

Thanks again Bob for the great work you have done and are doing.

 

73 Alex ik5pwj

 

Da: ik5pwj@... <ik5pwj@...>
Inviato: lunedì 1 febbraio 2021 00:57
A: 'hamlogger@groups.io' <hamlogger@groups.io>
Oggetto: R: [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

Hi Rich, no I don't have a VPN connection ... it's disabled in my router.

 

However, the connection of the router and the private network active on my PCs at home has always worked

and it works even now with Logger32 vers. 3.50.424 without any crashes.    Only with vers. 4.0 ... I have these problems.

 

For Pete N5KD .... I tried to connect with other clusters also with VE7CC but the problem remains ... and logger32 vers. 4

 

crashes and gives the error I indicated in my msg. previous one.

 

Alex ik5pwj

 

Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di n5kd
Inviato: lunedì 1 febbraio 2021 00:25
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

Some Logger32 users are using VE7CC to connect to the cluster, then L32 connects to the VE7CC program.

 

73’ Pete, N5KD.

 

From: Rick EA4M via groups.io
Sent: Sunday, January 31, 2021 10:57 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

Do you have an active VPN connection?

 

 

 

 

El dom., 31 ene. 2021 23:42, Alex Del Chicca <ik5pwj@...> escribió:

Yes sure ... W10Pro 64Bit  regular activetion and new installation.

All other programs work without any problems.

Only Logger32 goes shutdown when the connection via telnet to any cluster is active (I tried to change the source cluster but it is the same).

Without any connection via telnet or via Local Host the Logger32 works.

 

By chance, if the telnet connection is active, it goes shutdown giving these errors in the Windows 10 Registry which I report below:

 

Name of the application that generated the error: Logger32.exe, version 4.0.0.239. timestamp: 0x6016cb77

Name of the module that generated the error: ucrtbase.dll, version 10.0.19041.546, timestamp: 0x73123758

Exception code: 0x0000409

Error offset 0x0009edbb

Process ID that generated the error: 0x01d6f813bf37a4d2

Path of the application that generated the error: C: \ Logger32 \ logger32.exe

Path to the module that generated the error: C: \ Windows \ System32 \ ucrtbase.dll

Reporting ID 414728f1-fa55-4025-a0f6-943ededab69e

 

That's all.....

Thanks anyway

73 Alex ik5pwj

 

Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di Rick EA4M via groups.io
Inviato: domenica 31 gennaio 2021 23:23
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

Are you sure that W10 is fully up to date????

 

El dom., 31 ene. 2021 23:16, Alex Del Chicca <ik5pwj@...> escribió:

Bob, thanks ..... I still sent a screen shot showing the error.

 Anyway, thanks and ..... he followed your advice ......

73

 

Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di Bob
Inviato: domenica 31 gennaio 2021 22:59
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Again Logger32 crash again with this error on Register Windows " error is in: C: \ Windows \ System32 \ ucrtbase.dll " etc.

 

Alex, I have no idea. Maybe you need a different logging program? 73.

On 01/31/2021 4:55 PM Alex Del Chicca <ik5pwj@...> wrote:

 

 

Hi all,

Hi Bob, unfortunately I have to write this msg. because as you will read the logger32 ver.4 crash problem has come back

and now in another way.

After having reinstalled the operating system Windows 10 PRO 64B and some basic programs ex new, I also reinstalled

the logger32 and updated with the whole database to the latest version 4.0 ...

 

I left the loggger32 connected to the local cluster and everything seemed ok as after several hours of operation the logger32 was UP and working.

 

I installed other programs including SmartSDR v.2.6.2 and other programs with which the logger32 v.3.5 worked perfectly

without ever interrupting with the connection to the cluster active.

 

Now with the 4.0.238 version but also with 239 the logger32 crashes it closes sending these msg.

in the "Administrative Events" file and in the "Windows \ Applications Registry  and that I insert as a screen shot in this mail.

 

They are in Italian and in any case, as you can verify with a translator, the two crashes, for example of 31 / jan / 2021 at 21 : 47: 32 and at 21:57:38

they are derived from program C: \ LOGGER32 \ lOGGER32.EXE

 

and the path of the module that generated the error is in: C: \ Windows \ System32 \ ucrtbase.dll

 

As you can see from the images that I report below to my msg.

Unfortunately I have absolutely no knowledge to be able to understand and remedy this problem.

 

f you need more info about the complete error described in the Windows Logs, let me know ....... now I have

not written it completely as the copy and paste does not work and I should write it completely, but if you are necessary I will send it .

 

What do you think Bob?

 

I await your reply Bob ....

Thank you

73 Alex ik5pwj

 

 

Virus-free. www.avg.com


Re: v4.0.242 is on-line ...

Alf. IT9MUO
 

YES, it's checked !
73

Il giorno dom 7 feb 2021 alle ore 18:45 Bob <k4cy@...> ha scritto:
Click VIEW. There is a menu ENABLE ERROR TRAPPING. Is it checked? 73.
On 02/06/2021 8:48 AM Alf. IT9MUO <it9muo@...> wrote:
 
 
Same problem for me.
Logger32 goes into shutdown even when it is in st.by for a few hours.
73

Il giorno sab 6 feb 2021 alle ore 12:05 Barry GM4GIF < gm4gif@...> ha scritto:
Bob, thanks for the Scratchpad size change, works fine.
Unfortunately the Tab problem has come back, if I right click on a field to amend it, then Tab to get to the next field, the program closes. If I R click on a field, amend its contents then R click on the next field to amend, the contents of the previous field amended disappears.
Tried pressing Enter instead of Tab in the above example, same result - the program closes.
Ah, the joys of programming, it’s all coming back to me hi.
73
Barry
 

 

 

2081 - 2100 of 84644