Logger32 vers. 4.0.... crash. It closes without indicating the problem ( no problem on vers. 3.5...)


Alex Del Chicca
 

Hi, already in the past the Logger32 program first versions 4.0... sometimes closed without understanding why.

Only the minimized window of the L32LogSync program application remained.

At that time I was using Windows 10 64Bit and now that I am using Windows 11 64Bit with 64gb of ram the problem occurs randomly and the

program closes while the L32LogSync application remains minimized.

 

Going to see in the control panel/maintenance,  and in problem details I see that almost every day the Logger32 randomly closes without giving indications

of the problem ... it closes and that's it.

Going into the specifics of the problem, in some crashes nothing is described, it only says: Logger32 It has stopped working and indicates the date and time.

 

In other cases, always looking in Problem details, the following is indicated: Logger32.exe Has stopped working date and time and in Action/view technical details,  is indicated:

 

Description:

Faulting Application Name: Logger32.exe, Version: 4.0.0.298, Timestamp: 0x63692f07

Faulting module name: OLEAUT32.dll, version: 10.0.22000.1, timestamp: 0x821a6441

Exception code: 0xc0000005

Error offset 0x00075c4c

Process ID that generated the error: 0x3380

Start time of the application that generated the error: 0x01d8fb219e69297b

Faulting application path: C:\Logger32\Logger32.exe

Path to the module that generated the error: C:\WINDOWS\System32\OLEAUT32.dll

Report ID: 04cb198f-777c-462f-9b8a-b2f214ea2a03

Full package name that generated the error:

Application ID of the package that generated the error:

 

Sorry for the length of the msg. but I would like to understand why now using version 4.0.... of Logger32 this program block often occurs,

while with Logger32 version 3.5.... these sudden blocks did not occur.

However, this does not happen to me but to several other Italian and European radio amateurs that I know and that we often discuss for info, program data, etc.

 

I would like to know how to solve this problem or minimize it as much as possible.

The program cannot close without a specific reason. Hoping for some help from someone, hoping there is a solution.

73 Alex ik5pwj


ja1nlx
 

Alex

One suggestion to find the cause.
Stop ALL applications (like L32LogSync etc) except Logger32.
See whether it happens for a while, a week, a month...

73 de aki
JA1NLX

On 2022/11/23 16:42:58, Alex Del Chicca <ik5pwj@...> wrote:

Hi, already in the past the Logger32 program first versions 4.0... sometimes closed without understanding why.

Only the minimized window of the L32LogSync program application remained.

At that time I was using Windows 10 64Bit and now that I am using Windows 11 64Bit with 64gb of ram the problem occurs randomly and the

program closes while the L32LogSync application remains minimized.

 

Going to see in the control panel/maintenance,  and in problem details I see that almost every day the Logger32 randomly closes without giving indications

of the problem ... it closes and that's it.

Going into the specifics of the problem, in some crashes nothing is described, it only says: Logger32 It has stopped working and indicates the date and time.

 

In other cases, always looking in Problem details, the following is indicated: Logger32.exe Has stopped working date and time and in Action/view technical details,  is indicated:

 

Description:

Faulting Application Name: Logger32.exe, Version: 4.0.0.298, Timestamp: 0x63692f07

Faulting module name: OLEAUT32.dll, version: 10.0.22000.1, timestamp: 0x821a6441

Exception code: 0xc0000005

Error offset 0x00075c4c

Process ID that generated the error: 0x3380

Start time of the application that generated the error: 0x01d8fb219e69297b

Faulting application path: C:\Logger32\Logger32.exe

Path to the module that generated the error: C:\WINDOWS\System32\OLEAUT32.dll

Report ID: 04cb198f-777c-462f-9b8a-b2f214ea2a03

Full package name that generated the error:

Application ID of the package that generated the error:

 

Sorry for the length of the msg. but I would like to understand why now using version 4.0.... of Logger32 this program block often occurs,

while with Logger32 version 3.5.... these sudden blocks did not occur.

However, this does not happen to me but to several other Italian and European radio amateurs that I know and that we often discuss for info, program data, etc.

 

I would like to know how to solve this problem or minimize it as much as possible.

The program cannot close without a specific reason. Hoping for some help from someone, hoping there is a solution.

73 Alex ik5pwj


ik4dry Stefano Zoli - Alice mail -
 

I have definitively solved every problem of anomalous closures, starting from shortcut in WIN7 compatibility.

 

73’s Steve

 

Inviato da Posta per Windows

 

Da: ja1nlx
Inviato: mercoledì 23 novembre 2022 09:04
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Logger32 vers. 4.0.... crash. It closes without indicating the problem ( no problem on vers. 3.5...)

 

Alex

 

One suggestion to find the cause.

Stop ALL applications (like L32LogSync etc) except Logger32.

See whether it happens for a while, a week, a month...

 

73 de aki

JA1NLX

On 2022/11/23 16:42:58, Alex Del Chicca <ik5pwj@...> wrote:

Hi, already in the past the Logger32 program first versions 4.0... sometimes closed without understanding why.

Only the minimized window of the L32LogSync program application remained.

At that time I was using Windows 10 64Bit and now that I am using Windows 11 64Bit with 64gb of ram the problem occurs randomly and the

program closes while the L32LogSync application remains minimized.

 

Going to see in the control panel/maintenance,  and in problem details I see that almost every day the Logger32 randomly closes without giving indications

of the problem ... it closes and that's it.

Going into the specifics of the problem, in some crashes nothing is described, it only says: Logger32 It has stopped working and indicates the date and time.

 

In other cases, always looking in Problem details, the following is indicated: Logger32.exe Has stopped working date and time and in Action/view technical details,  is indicated:

 

Description:

Faulting Application Name: Logger32.exe, Version: 4.0.0.298, Timestamp: 0x63692f07

Faulting module name: OLEAUT32.dll, version: 10.0.22000.1, timestamp: 0x821a6441

Exception code: 0xc0000005

Error offset 0x00075c4c

Process ID that generated the error: 0x3380

Start time of the application that generated the error: 0x01d8fb219e69297b

Faulting application path: C:\Logger32\Logger32.exe

Path to the module that generated the error: C:\WINDOWS\System32\OLEAUT32.dll

Report ID: 04cb198f-777c-462f-9b8a-b2f214ea2a03

Full package name that generated the error:

Application ID of the package that generated the error:

 

Sorry for the length of the msg. but I would like to understand why now using version 4.0.... of Logger32 this program block often occurs,

while with Logger32 version 3.5.... these sudden blocks did not occur.

However, this does not happen to me but to several other Italian and European radio amateurs that I know and that we often discuss for info, program data, etc.

 

I would like to know how to solve this problem or minimize it as much as possible.

The program cannot close without a specific reason. Hoping for some help from someone, hoping there is a solution.

73 Alex ik5pwj

 


F4FQH Olivier
 

Ciao Alex,
 
As Bob mentioned, change the compatibility mode to another one. Use windows 7. Seem to work here.
I prefer programs working in native mode but we make how we can.
 
I will experiment some other later but for now windows 7 seem to work. XP is too old............
 
73s
Olivier
F4FQH
 
From: Alex Del Chicca
Sent: Wednesday, November 23, 2022 8:42 AM
To: hamlogger@groups.io
Subject: *** SPAM *** [hamlogger] Logger32 vers. 4.0.... crash. It closes without indicating the problem ( no problem on vers. 3.5...)
 

Hi, already in the past the Logger32 program first versions 4.0... sometimes closed without understanding why.

Only the minimized window of the L32LogSync program application remained.

At that time I was using Windows 10 64Bit and now that I am using Windows 11 64Bit with 64gb of ram the problem occurs randomly and the

program closes while the L32LogSync application remains minimized.

 

Going to see in the control panel/maintenance,  and in problem details I see that almost every day the Logger32 randomly closes without giving indications

of the problem ... it closes and that's it.

Going into the specifics of the problem, in some crashes nothing is described, it only says: Logger32 It has stopped working and indicates the date and time.

 

In other cases, always looking in Problem details, the following is indicated: Logger32.exe Has stopped working date and time and in Action/view technical details,  is indicated:

 

Description:

Faulting Application Name: Logger32.exe, Version: 4.0.0.298, Timestamp: 0x63692f07

Faulting module name: OLEAUT32.dll, version: 10.0.22000.1, timestamp: 0x821a6441

Exception code: 0xc0000005

Error offset 0x00075c4c

Process ID that generated the error: 0x3380

Start time of the application that generated the error: 0x01d8fb219e69297b

Faulting application path: C:\Logger32\Logger32.exe

Path to the module that generated the error: C:\WINDOWS\System32\OLEAUT32.dll

Report ID: 04cb198f-777c-462f-9b8a-b2f214ea2a03

Full package name that generated the error:

Application ID of the package that generated the error:

 

Sorry for the length of the msg. but I would like to understand why now using version 4.0.... of Logger32 this program block often occurs,

while with Logger32 version 3.5.... these sudden blocks did not occur.

However, this does not happen to me but to several other Italian and European radio amateurs that I know and that we often discuss for info, program data, etc.

 

I would like to know how to solve this problem or minimize it as much as possible.

The program cannot close without a specific reason. Hoping for some help from someone, hoping there is a solution.

73 Alex ik5pwj


Alex Del Chicca
 

Hi Steve, thanks for the info and now it's in WIN7 mode......

Since this morning until now the program hasn't closed, let's see.

However I don't understand why a program that runs on 32Bit or 64Bit systems should be, let's say gagged by running it in WIN7 mode.

 

I hope the programmers can fix this. Thanks anyway for the excellent work you are doing.

 

Thanks again 73 Alex ik5pwj.

 

Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di ik4dry Stefano Zoli - Alice mail -
Inviato: mercoledì 23 novembre 2022 09:29
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Logger32 vers. 4.0.... crash. It closes without indicating the problem ( no problem on vers. 3.5...)

 

I have definitively solved every problem of anomalous closures, starting from shortcut in WIN7 compatibility.

 

73’s Steve

 

Inviato da Posta per Windows

 

Da: ja1nlx
Inviato: mercoledì 23 novembre 2022 09:04
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Logger32 vers. 4.0.... crash. It closes without indicating the problem ( no problem on vers. 3.5...)

 

Alex

 

One suggestion to find the cause.

Stop ALL applications (like L32LogSync etc) except Logger32.

See whether it happens for a while, a week, a month...

 

73 de aki

JA1NLX

On 2022/11/23 16:42:58, Alex Del Chicca <ik5pwj@...> wrote:

Hi, already in the past the Logger32 program first versions 4.0... sometimes closed without understanding why.

Only the minimized window of the L32LogSync program application remained.

At that time I was using Windows 10 64Bit and now that I am using Windows 11 64Bit with 64gb of ram the problem occurs randomly and the

program closes while the L32LogSync application remains minimized.

 

Going to see in the control panel/maintenance,  and in problem details I see that almost every day the Logger32 randomly closes without giving indications

of the problem ... it closes and that's it.

Going into the specifics of the problem, in some crashes nothing is described, it only says: Logger32 It has stopped working and indicates the date and time.

 

In other cases, always looking in Problem details, the following is indicated: Logger32.exe Has stopped working date and time and in Action/view technical details,  is indicated:

 

Description:

Faulting Application Name: Logger32.exe, Version: 4.0.0.298, Timestamp: 0x63692f07

Faulting module name: OLEAUT32.dll, version: 10.0.22000.1, timestamp: 0x821a6441

Exception code: 0xc0000005

Error offset 0x00075c4c

Process ID that generated the error: 0x3380

Start time of the application that generated the error: 0x01d8fb219e69297b

Faulting application path: C:\Logger32\Logger32.exe

Path to the module that generated the error: C:\WINDOWS\System32\OLEAUT32.dll

Report ID: 04cb198f-777c-462f-9b8a-b2f214ea2a03

Full package name that generated the error:

Application ID of the package that generated the error:

 

Sorry for the length of the msg. but I would like to understand why now using version 4.0.... of Logger32 this program block often occurs,

while with Logger32 version 3.5.... these sudden blocks did not occur.

However, this does not happen to me but to several other Italian and European radio amateurs that I know and that we often discuss for info, program data, etc.

 

I would like to know how to solve this problem or minimize it as much as possible.

The program cannot close without a specific reason. Hoping for some help from someone, hoping there is a solution.

73 Alex ik5pwj

 


Bob
 

Exception code: 0xc0000005

If you Google Exception code: 0xc0000005 you will find many sites offering tools that fix this error and cure everything for Erectile Dysfunction to toe nail fungus. These articles will list several common causes - Bad disk sectors, registry corruption, malware, etc. They also suggest that DEP (Data Execution Prevention) may be the cause.

It is not my suggestion/recommendation that you turn off DEP on your PC. On my PCs DEP is turned off. I didn't turn it off, they are old and tired, and came that way.

FWIW, I have never experienced any unexpected crashes of Logger32 where it simply disappears from the screen. And, I can assure you, while testing this code on a daily basis, I do some nasty things.

SeventyThree(s).

On 11/23/2022 2:42 AM Alex Del Chicca <ik5pwj@...> wrote:


Hi, already in the past the Logger32 program first versions 4.0... sometimes closed without understanding why.

Only the minimized window of the L32LogSync program application remained.

At that time I was using Windows 10 64Bit and now that I am using Windows 11 64Bit with 64gb of ram the problem occurs randomly and the

program closes while the L32LogSync application remains minimized.


Going to see in the control panel/maintenance,  and in problem details I see that almost every day the Logger32 randomly closes without giving indications

of the problem ... it closes and that's it.

Going into the specifics of the problem, in some crashes nothing is described, it only says: Logger32 It has stopped working and indicates the date and time.


In other cases, always looking in Problem details, the following is indicated: Logger32.exe Has stopped working date and time and in Action/view technical details,  is indicated:


Description:

Faulting Application Name: Logger32.exe, Version: 4.0.0.298, Timestamp: 0x63692f07

Faulting module name: OLEAUT32.dll, version: 10.0.22000.1, timestamp: 0x821a6441

Exception code: 0xc0000005

Error offset 0x00075c4c

Process ID that generated the error: 0x3380

Start time of the application that generated the error: 0x01d8fb219e69297b

Faulting application path: C:\Logger32\Logger32.exe

Path to the module that generated the error: C:\WINDOWS\System32\OLEAUT32.dll

Report ID: 04cb198f-777c-462f-9b8a-b2f214ea2a03

Full package name that generated the error:

Application ID of the package that generated the error:


Sorry for the length of the msg. but I would like to understand why now using version 4.0.... of Logger32 this program block often occurs,

while with Logger32 version 3.5.... these sudden blocks did not occur.

However, this does not happen to me but to several other Italian and European radio amateurs that I know and that we often discuss for info, program data, etc.


I would like to know how to solve this problem or minimize it as much as possible.

The program cannot close without a specific reason. Hoping for some help from someone, hoping there is a solution.

73 Alex ik5pwj


Alex Del Chicca
 

Hi Bob, thanks for your information but it seems that the problem of Logger32 closing unexpectedly has been solved.

 

I only started Logger32 in WIN7 compatible mode and for the moment no closing of the program.

I'll see in the next few days.

73 Alex ik5pwj

 

Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di Bob
Inviato: mercoledì 23 novembre 2022 19:22
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Logger32 vers. 4.0.... crash. It closes without indicating the problem ( no problem on vers. 3.5...)

 

Exception code: 0xc0000005

 

If you Google Exception code: 0xc0000005 you will find many sites offering tools that fix this error and cure everything for Erectile Dysfunction to toe nail fungus. These articles will list several common causes - Bad disk sectors, registry corruption, malware, etc. They also suggest that DEP (Data Execution Prevention) may be the cause.

 

It is not my suggestion/recommendation that you turn off DEP on your PC. On my PCs DEP is turned off. I didn't turn it off, they are old and tired, and came that way.

 

FWIW, I have never experienced any unexpected crashes of Logger32 where it simply disappears from the screen. And, I can assure you, while testing this code on a daily basis, I do some nasty things.

 

SeventyThree(s).

On 11/23/2022 2:42 AM Alex Del Chicca <ik5pwj@...> wrote:

 

 

Hi, already in the past the Logger32 program first versions 4.0... sometimes closed without understanding why.

Only the minimized window of the L32LogSync program application remained.

At that time I was using Windows 10 64Bit and now that I am using Windows 11 64Bit with 64gb of ram the problem occurs randomly and the

program closes while the L32LogSync application remains minimized.

 

Going to see in the control panel/maintenance,  and in problem details I see that almost every day the Logger32 randomly closes without giving indications

of the problem ... it closes and that's it.

Going into the specifics of the problem, in some crashes nothing is described, it only says: Logger32 It has stopped working and indicates the date and time.

 

In other cases, always looking in Problem details, the following is indicated: Logger32.exe Has stopped working date and time and in Action/view technical details,  is indicated:

 

Description:

Faulting Application Name: Logger32.exe, Version: 4.0.0.298, Timestamp: 0x63692f07

Faulting module name: OLEAUT32.dll, version: 10.0.22000.1, timestamp: 0x821a6441

Exception code: 0xc0000005

Error offset 0x00075c4c

Process ID that generated the error: 0x3380

Start time of the application that generated the error: 0x01d8fb219e69297b

Faulting application path: C:\Logger32\Logger32.exe

Path to the module that generated the error: C:\WINDOWS\System32\OLEAUT32.dll

Report ID: 04cb198f-777c-462f-9b8a-b2f214ea2a03

Full package name that generated the error:

Application ID of the package that generated the error:

 

Sorry for the length of the msg. but I would like to understand why now using version 4.0.... of Logger32 this program block often occurs,

while with Logger32 version 3.5.... these sudden blocks did not occur.

However, this does not happen to me but to several other Italian and European radio amateurs that I know and that we often discuss for info, program data, etc.

 

I would like to know how to solve this problem or minimize it as much as possible.

The program cannot close without a specific reason. Hoping for some help from someone, hoping there is a solution.

73 Alex ik5pwj


f2dx_patrick
 

Hi,

I am having exactly the same problem.

I'm using Windows 10 up-to-date (22H2). It's been a long time since I last used L32 which was v3.50.424.
When I took over a radio activity, I naturally wanted to install the latest version of my favorite program and I did a full install of v4 (not an update).

L32 regularly closes multiple times a day BUT only with a Telnet activity.
Indeed, w
hen I am not connected to a cluster, L32 does not close at all after several days.

Note of course that I had never encountered this problem before (with v3.50.424) on the same PC.

By following your advice, I started in "Windows 7 compatibility" and L32 has not closed by itself for more than 24 hours while I am well connected to the cluster. Thanks for this information.

73, F2DX Patrick


Bob
 

As an altrnative to running Win 7 compatibility (some users object to the concept) you could try turming off DEP for Logger32 instead. SeventyThree(s)

On 11/25/2022 4:05 PM f2dx_patrick via groups.io <f2dx@...> wrote:


Hi,

I am having exactly the same problem.

I'm using Windows 10 up-to-date (22H2). It's been a long time since I last used L32 which was v3.50.424.
When I took over a radio activity, I naturally wanted to install the latest version of my favorite program and I did a full install of v4 (not an update).

L32 regularly closes multiple times a day BUT only with a Telnet activity.
Indeed, w
hen I am not connected to a cluster, L32 does not close at all after several days.

Note of course that I had never encountered this problem before (with v3.50.424) on the same PC.

By following your advice, I started in "Windows 7 compatibility" and L32 has not closed by itself for more than 24 hours while I am well connected to the cluster. Thanks for this information.

73, F2DX Patrick


Alex Del Chicca
 

Hi Patrick,

the problem as you described is the same one I had since the first versions of the 4.0 release... and I had already found that if I opened the

connection via telnet this criticality increased and then suddenly the Logger32 program closed.

 

I read the new manual just these days and as suggested in an email from an OM, he suggests starting the Logger32 program in WIN7 mode.

 

if you are using WIN10 or WIN11 like in my case.

In the past every day if I turned on the Logger 32 systematically it closed one or more times.

Well……now  for 3 days Logger 32 hasn't closed anymore and it works without problems,  I repeat in WIN7 mode.

You will see that you will be able to eliminate the problem.

73 Alex ik5pwj.

 

Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di f2dx_patrick via groups.io
Inviato: venerdì 25 novembre 2022 22:05
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Logger32 vers. 4.0.... crash. It closes without indicating the problem ( no problem on vers. 3.5...)

 

Hi,

I am having exactly the same problem.

I'm using Windows 10 up-to-date (22H2). It's been a long time since I last used L32 which was v3.50.424.
When I took over a radio activity, I naturally wanted to install the latest version of my favorite program and I did a full install of v4 (not an update).

L32 regularly closes multiple times a day BUT only with a Telnet activity.
Indeed, when I am not connected to a cluster, L32 does not close at all after several days.

Note of course that I had never encountered this problem before (with v3.50.424) on the same PC.

By following your advice, I started in "Windows 7 compatibility" and L32 has not closed by itself for more than 24 hours while I am well connected to the cluster. Thanks for this information.

73, F2DX Patrick


F4FQH Olivier
 

Hi,
 
When i asked Bob why my Logger32 closed alone, and FT8 contacts from JTDX didn’t go in log, he said that in WIN 11 we have to use win7 mode.
The subject seem to be discused before , but i missed this. I don’t look every post on the forum due to the life time.
 
Since i use WIN7 mode, it seem to work for all my bugs. But i’m not often on the radio these days.
 
Today i moved to WIN8 mode with my win 11 22h2. I will see what’s happen.
 
I never used the comp mode in logger since i use it (2008). In WIN10, i had no issues with the V4. No more WIN10 here on PCs.
WIN10 users have to test with 22H2
 
So the problem is with win 11 only, and if the compatibility WIN7 mode works, so all is fine.
 
73s
Olivier
F4FQH
 
From: Alex Del Chicca
Sent: Saturday, November 26, 2022 7:48 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 vers. 4.0.... crash. It closes without indicating the problem ( no problem on vers. 3.5...)
 

Hi Patrick,

the problem as you described is the same one I had since the first versions of the 4.0 release... and I had already found that if I opened the

connection via telnet this criticality increased and then suddenly the Logger32 program closed.

 

I read the new manual just these days and as suggested in an email from an OM, he suggests starting the Logger32 program in WIN7 mode.

 

if you are using WIN10 or WIN11 like in my case.

In the past every day if I turned on the Logger 32 systematically it closed one or more times.

Well……now  for 3 days Logger 32 hasn't closed anymore and it works without problems,  I repeat in WIN7 mode.

You will see that you will be able to eliminate the problem.

73 Alex ik5pwj.

 

Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di f2dx_patrick via groups.io
Inviato: venerdì 25 novembre 2022 22:05
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Logger32 vers. 4.0.... crash. It closes without indicating the problem ( no problem on vers. 3.5...)

 

Hi,

I am having exactly the same problem.

I'm using Windows 10 up-to-date (22H2). It's been a long time since I last used L32 which was v3.50.424.
When I took over a radio activity, I naturally wanted to install the latest version of my favorite program and I did a full install of v4 (not an update).

L32 regularly closes multiple times a day BUT only with a Telnet activity.
Indeed, when I am not connected to a cluster, L32 does not close at all after several days.

Note of course that I had never encountered this problem before (with v3.50.424) on the same PC.

By following your advice, I started in "Windows 7 compatibility" and L32 has not closed by itself for more than 24 hours while I am well connected to the cluster. Thanks for this information.

73, F2DX Patrick


Michael Harris
 

OK, has anyone got anything positive to say about running L32 on a Win11 PC. I find it difficult to believe all this crashing is a universal affliction on Win11 PC's.

The reason I ask is that my new PC, due to arrive in mid December is Win11 based.

Why Win7? I've been running L32 v4 on Win10 since it was released without issue.

Regards,

Mike VP8NO

On 26/11/2022 15:48, Alex Del Chicca wrote:
Hi Patrick,
the problem as you described is the same one I had since the first versions of the 4.0 release... and I had already found that if I opened the
connection via telnet this criticality increased and then suddenly the Logger32 program closed.
I read the new manual just these days and as suggested in an email from an OM, he suggests starting the Logger32 program in WIN7 mode.
if you are using WIN10 or WIN11 like in my case.
In the past every day if I turned on the Logger 32 systematically it closed one or more times.
Well……now for 3 days Logger 32 hasn't closed anymore and it works without problems, I repeat in WIN7 mode.
You will see that you will be able to eliminate the problem.
73 Alex ik5pwj.
Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di f2dx_patrick via groups.io
Inviato: venerdì 25 novembre 2022 22:05
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Logger32 vers. 4.0.... crash. It closes without indicating the problem ( no problem on vers. 3.5...)
Hi,
I am having exactly the same problem.
I'm using Windows 10 up-to-date (22H2). It's been a long time since I last used L32 which was v3.50.424.
When I took over a radio activity, I naturally wanted to install the latest version of my favorite program and I did a full install of v4 (not an update).
L32 regularly closes multiple times a day BUT only with a Telnet activity.
Indeed, when I am not connected to a cluster, L32 does not close at all after several days.
Note of course that I had never encountered this problem before (with v3.50.424) on the same PC.
By following your advice, I started in "Windows 7 compatibility" and L32 has not closed by itself for more than 24 hours while I am well connected to the cluster. Thanks for this information.
73, F2DX Patrick


Bob
 

Let my try one more time to put/keep this in context ... Like you, I am running Win 10 with DEP (Data Execution Prevention) disabled. I have never seen a single crash. I do not run in any compatibility mode. I did not disable DEP, it was disabled by default when I got the PCs.

Why Win 7 compatibility mode appears to solve the problem, and not Win 8 or other compatibility mode? I don't know if anyone has actually done any careful analysis of which compatibility modes solve the problem and which don't. If there has been a careful study, I haven't seen the evidence/results.

Mike, I'll take a SWAG that if you check, you'll find that either DEP is disabled, or you are have forgotten you're running Logger32 in a compatibility mode.

Reports I have seen here offer no favoritism to either Win 10 or 11. Both appear to suffer equally if system settings are not appropriately set..

SeventyThree(s).

On 11/26/2022 5:08 PM Michael Harris via groups.io <mike.harris@...> wrote:


OK, has anyone got anything positive to say about running L32 on a Win11
PC. I find it difficult to believe all this crashing is a universal
affliction on Win11 PC's.

The reason I ask is that my new PC, due to arrive in mid December is
Win11 based.

Why Win7? I've been running L32 v4 on Win10 since it was released
without issue.

Regards,

Mike VP8NO

On 26/11/2022 15:48, Alex Del Chicca wrote:
Hi Patrick,

the problem as you described is the same one I had since the first versions of the 4.0 release... and I had already found that if I opened the

connection via telnet this criticality increased and then suddenly the Logger32 program closed.



I read the new manual just these days and as suggested in an email from an OM, he suggests starting the Logger32 program in WIN7 mode.



if you are using WIN10 or WIN11 like in my case.

In the past every day if I turned on the Logger 32 systematically it closed one or more times.

Well……now for 3 days Logger 32 hasn't closed anymore and it works without problems, I repeat in WIN7 mode.

You will see that you will be able to eliminate the problem.

73 Alex ik5pwj.



Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di f2dx_patrick via groups.io
Inviato: venerdì 25 novembre 2022 22:05
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Logger32 vers. 4.0.... crash. It closes without indicating the problem ( no problem on vers. 3.5...)



Hi,

I am having exactly the same problem.

I'm using Windows 10 up-to-date (22H2). It's been a long time since I last used L32 which was v3.50.424.
When I took over a radio activity, I naturally wanted to install the latest version of my favorite program and I did a full install of v4 (not an update).

L32 regularly closes multiple times a day BUT only with a Telnet activity.
Indeed, when I am not connected to a cluster, L32 does not close at all after several days.

Note of course that I had never encountered this problem before (with v3.50.424) on the same PC.

By following your advice, I started in "Windows 7 compatibility" and L32 has not closed by itself for more than 24 hours while I am well connected to the cluster. Thanks for this information.

73, F2DX Patrick


Jan <hamlogger@...>
 

How to disable DEP ??

73
Jan
PA4JJ

Op 26-11-2022 om 23:36 schreef Bob:
Let my try one more time to put/keep this in context ... Like you, I am running Win 10 with DEP (Data Execution Prevention) disabled. I have never seen a single crash. I do not run in any compatibility mode. I did not disable DEP, it was disabled by default when I got the PCs.

Why Win 7 compatibility mode appears to solve the problem, and not Win 8 or other compatibility mode? I don't know if anyone has actually done any careful analysis of which compatibility modes solve the problem and which don't. If there has been a careful study, I haven't seen the evidence/results.

Mike, I'll take a SWAG that if you check, you'll find that either DEP is disabled, or you are have forgotten you're running Logger32 in a compatibility mode.

Reports I have seen here offer no favoritism to either Win 10 or 11. Both appear to suffer equally if system settings are not appropriately set..

SeventyThree(s).

On 11/26/2022 5:08 PM Michael Harris via groups.io <mike.harris@...> wrote:


OK, has anyone got anything positive to say about running L32 on a Win11
PC. I find it difficult to believe all this crashing is a universal
affliction on Win11 PC's.

The reason I ask is that my new PC, due to arrive in mid December is
Win11 based.

Why Win7? I've been running L32 v4 on Win10 since it was released
without issue.

Regards,

Mike VP8NO

On 26/11/2022 15:48, Alex Del Chicca wrote:
Hi Patrick,

the problem as you described is the same one I had since the first versions of the 4.0 release... and I had already found that if I opened the

connection via telnet this criticality increased and then suddenly the Logger32 program closed.



I read the new manual just these days and as suggested in an email from an OM, he suggests starting the Logger32 program in WIN7 mode.



if you are using WIN10 or WIN11 like in my case.

In the past every day if I turned on the Logger 32 systematically it closed one or more times.

Well……now for 3 days Logger 32 hasn't closed anymore and it works without problems, I repeat in WIN7 mode.

You will see that you will be able to eliminate the problem.

73 Alex ik5pwj.



Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di f2dx_patrick via groups.io
Inviato: venerdì 25 novembre 2022 22:05
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Logger32 vers. 4.0.... crash. It closes without indicating the problem ( no problem on vers. 3.5...)



Hi,

I am having exactly the same problem.

I'm using Windows 10 up-to-date (22H2). It's been a long time since I last used L32 which was v3.50.424.
When I took over a radio activity, I naturally wanted to install the latest version of my favorite program and I did a full install of v4 (not an update).

L32 regularly closes multiple times a day BUT only with a Telnet activity.
Indeed, when I am not connected to a cluster, L32 does not close at all after several days.

Note of course that I had never encountered this problem before (with v3.50.424) on the same PC.

By following your advice, I started in "Windows 7 compatibility" and L32 has not closed by itself for more than 24 hours while I am well connected to the cluster. Thanks for this information.

73, F2DX Patrick







-- 
73
Jan
PA4JJ
______________________________________________________

My dxspider clusters running 24/7 on a raspberry pi 2
pa4jj-2 telnet 77.174.195.163 port 7300
pa4jj-3 telnet 77.174.195.163 port 7388


Bob
 

Several ways. Best option is to Google it. 73.

On 11/26/2022 5:56 PM Jan <hamlogger@...> wrote:


How to disable DEP ??

73
Jan
PA4JJ

Op 26-11-2022 om 23:36 schreef Bob:
Let my try one more time to put/keep this in context ... Like you, I am running Win 10 with DEP (Data Execution Prevention) disabled. I have never seen a single crash. I do not run in any compatibility mode. I did not disable DEP, it was disabled by default when I got the PCs.

Why Win 7 compatibility mode appears to solve the problem, and not Win 8 or other compatibility mode? I don't know if anyone has actually done any careful analysis of which compatibility modes solve the problem and which don't. If there has been a careful study, I haven't seen the evidence/results.

Mike, I'll take a SWAG that if you check, you'll find that either DEP is disabled, or you are have forgotten you're running Logger32 in a compatibility mode.

Reports I have seen here offer no favoritism to either Win 10 or 11. Both appear to suffer equally if system settings are not appropriately set..

SeventyThree(s).

On 11/26/2022 5:08 PM Michael Harris via groups.io <mike.harris@...> wrote:


OK, has anyone got anything positive to say about running L32 on a Win11
PC. I find it difficult to believe all this crashing is a universal
affliction on Win11 PC's.

The reason I ask is that my new PC, due to arrive in mid December is
Win11 based.

Why Win7? I've been running L32 v4 on Win10 since it was released
without issue.

Regards,

Mike VP8NO

On 26/11/2022 15:48, Alex Del Chicca wrote:
Hi Patrick,

the problem as you described is the same one I had since the first versions of the 4.0 release... and I had already found that if I opened the

connection via telnet this criticality increased and then suddenly the Logger32 program closed.



I read the new manual just these days and as suggested in an email from an OM, he suggests starting the Logger32 program in WIN7 mode.



if you are using WIN10 or WIN11 like in my case.

In the past every day if I turned on the Logger 32 systematically it closed one or more times.

Well……now for 3 days Logger 32 hasn't closed anymore and it works without problems, I repeat in WIN7 mode.

You will see that you will be able to eliminate the problem.

73 Alex ik5pwj.



Da: hamlogger@groups.io <hamlogger@groups.io> Per conto di f2dx_patrick via groups.io
Inviato: venerdì 25 novembre 2022 22:05
A: hamlogger@groups.io
Oggetto: Re: [hamlogger] Logger32 vers. 4.0.... crash. It closes without indicating the problem ( no problem on vers. 3.5...)



Hi,

I am having exactly the same problem.

I'm using Windows 10 up-to-date (22H2). It's been a long time since I last used L32 which was v3.50.424.
When I took over a radio activity, I naturally wanted to install the latest version of my favorite program and I did a full install of v4 (not an update).

L32 regularly closes multiple times a day BUT only with a Telnet activity.
Indeed, when I am not connected to a cluster, L32 does not close at all after several days.

Note of course that I had never encountered this problem before (with v3.50.424) on the same PC.

By following your advice, I started in "Windows 7 compatibility" and L32 has not closed by itself for more than 24 hours while I am well connected to the cluster. Thanks for this information.

73, F2DX Patrick


   

-- 
73
Jan
PA4JJ
______________________________________________________

My dxspider clusters running 24/7 on a raspberry pi 2
pa4jj-2 telnet 77.174.195.163 port 7300
pa4jj-3 telnet 77.174.195.163 port 7388