Date   
Re: Update crash

gboutin@...
 

Jim,

It would seem some other criteria is also involved. I have L32 on the bottom of two monitors. No problem with the update to 319 for me.

I am using Windows 10 Pro (15063.332) and I do my L32 updates manually rather than using auto-updates.

> Gerald, VE1DT


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

We are making progress. We think we have a fix.

"Analysis indicates that the reported post auto-update the crash ONLY occurs if the user has the main Logger32 Window configured and running on a monitor other than the top/left one. 

 

Anyone running Logger32 on a second monitor and unable to auto-update let me know If you would be willing to help us verify the fix..

Please send direct to my e-mail listed below.

 

73, Jim – w5ifp@...

Re: Update crash

Kenneth Hansen
 

Either monitor in my shack is fine

KB2SSE

Ken

On Thu, Jun 8, 2017 at 9:00 AM, Mike Harris mike.harris@... [hamlogger] <hamlogger@...> wrote:
 

From Jim's post the location of the main logger window within a two
monitor set-up is the potential issue, not the simple fact it is running
on two monitors or whatever.

"Analysis indicates that the reported post auto-update the crash ONLY
occurs if the user has the main Logger32 Window configured and running
on a monitor other than the top/left one."

Where does yours fit in this scenario? Vital information for the developers.

Regards,

Mike VP8NO

On 08/06/2017 09:51, Dave n8dc-8@... [hamlogger] wrote:
> I did mine last week and I also run 2 monitors and no problems here ?
> Dave N8DC
>
>
> ----- Original Message -----
>
> From: "Kenneth Hansen khansen@... [hamlogger]" <hamlogger@...>
> To: "hamlogger" <hamlogger@...>
> Sent: Thursday, June 8, 2017 8:46:20 AM
> Subject: Re: [hamlogger] Update crash
>
>
>
>
> Jim,
>
> For what it's worth, I upgrade yesterday without any issues, and I am using a 2 monitor setup.
>
> de KB2SSE
>
> Ken




--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

Re: Update crash

Michael Harris
 

From Jim's post the location of the main logger window within a two monitor set-up is the potential issue, not the simple fact it is running on two monitors or whatever.

"Analysis indicates that the reported post auto-update the crash ONLY occurs if the user has the main Logger32 Window configured and running on a monitor other than the top/left one."

Where does yours fit in this scenario? Vital information for the developers.

Regards,

Mike VP8NO

On 08/06/2017 09:51, Dave n8dc-8@... [hamlogger] wrote:
I did mine last week and I also run 2 monitors and no problems here ?
Dave N8DC
----- Original Message -----
From: "Kenneth Hansen khansen@... [hamlogger]" <hamlogger@...>
To: "hamlogger" <hamlogger@...>
Sent: Thursday, June 8, 2017 8:46:20 AM
Subject: Re: [hamlogger] Update crash
Jim,
For what it's worth, I upgrade yesterday without any issues, and I am using a 2 monitor setup.
de KB2SSE
Ken

Re: Update crash

NICK K. PLUMIDAKIS
 

 

Version 3.50319

In my 3 monitor setup it is working fabulous.

With  ICOM IC 756PROII and IC-7300.

DE

Nick

SV1VS

 

From: hamlogger@... [mailto:hamlogger@...]
Sent: Thursday, June 08, 2017 15:46
To: hamlogger@...
Subject: Re: [hamlogger] Update crash

 

 

Jim,

For what it's worth, I upgrade yesterday without any issues, and I am using a 2 monitor setup.

de KB2SSE

Ken

 

On Thu, Jun 8, 2017 at 12:39 AM, 'Jim Hargrave' w5ifp@... [hamlogger] <hamlogger@...> wrote:

 

We are making progress. We think we have a fix.

"Analysis indicates that the reported post auto-update the crash ONLY occurs if the user has the main Logger32 Window configured and running on a monitor other than the top/left one. 

 

Anyone running Logger32 on a second monitor and unable to auto-update let me know If you would be willing to help us verify the fix.

Please send direct to my e-mail listed below.

 

73, Jim – w5ifp@...




--

Kenneth Hansen

Owner

ScanAm Technical Services, LLC

Re: Update crash

Dave Colliau
 

I did mine last week and I also run 2 monitors and no problems here ?
Dave N8DC



From: "Kenneth Hansen khansen@... [hamlogger]" <hamlogger@...>
To: "hamlogger"
Sent: Thursday, June 8, 2017 8:46:20 AM
Subject: Re: [hamlogger] Update crash

 


Jim,

For what it's worth, I upgrade yesterday without any issues, and I am using a 2 monitor setup.

de KB2SSE

Ken

On Thu, Jun 8, 2017 at 12:39 AM, 'Jim Hargrave' w5ifp@... [hamlogger] <hamlogger@...> wrote:
 


We are making progress. We think we have a fix.

"Analysis indicates that the reported post auto-update the crash ONLY occurs if the user has the main Logger32 Window configured and running on a monitor other than the top/left one. 

 

Anyone running Logger32 on a second monitor and unable to auto-update let me know If you would be willing to help us verify the fix..

Please send direct to my e-mail listed below.

 

73, Jim – w5ifp@...






--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC



Re: Update crash

Kenneth Hansen
 

Jim,

For what it's worth, I upgrade yesterday without any issues, and I am using a 2 monitor setup.

de KB2SSE

Ken

On Thu, Jun 8, 2017 at 12:39 AM, 'Jim Hargrave' w5ifp@... [hamlogger] <hamlogger@...> wrote:
 

We are making progress. We think we have a fix.

"Analysis indicates that the reported post auto-update the crash ONLY occurs if the user has the main Logger32 Window configured and running on a monitor other than the top/left one. 

 

Anyone running Logger32 on a second monitor and unable to auto-update let me know If you would be willing to help us verify the fix..

Please send direct to my e-mail listed below.

 

73, Jim – w5ifp@...




--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

Re: Update crash

villemin denis
 

Hi Jim

After putting the display of the window of logger32 on screen 1, the update 3.50.319 was carried out without problem after the update I handed logger32 on the screen2 everything is ok
sorry for my English

Tnx for the job With logger32

F5RJM-Denis

 

De : hamlogger@... [mailto:hamlogger@...]
Envoyé : jeudi 8 juin 2017 06:40
À : hamlogger@...
Objet : [hamlogger] Update crash

 

 

We are making progress. We think we have a fix.

"Analysis indicates that the reported post auto-update the crash ONLY occurs if the user has the main Logger32 Window configured and running on a monitor other than the top/left one. 

 

Anyone running Logger32 on a second monitor and unable to auto-update let me know If you would be willing to help us verify the fix..

Please send direct to my e-mail listed below.

 

73, Jim – w5ifp@...

Re: confirm lotw qso

Jim Hargrave
 

Suggest following the process outlined in the Logger32 Help file: Tips, Tricks and Troubleshooting, paragraph 1.13



73, Jim – w5ifp@...



From: hamlogger@... [mailto:hamlogger@...]
Sent: Wednesday, June 7, 2017 4:01 PM
To: hamlogger@...
Subject: RE: [hamlogger] Re: confirm lotw qso








Hi John.



If you are certain you have signed and uploaded ALL your QSOs to LoTW, you could export your log as an ADIF (saving a just-in-case offline copy), then edit it using a text editor such as Notepad, Wordpad or TED to add <LOTW_QSL_SENT:1>Y to every record, before the <EOR> marker, then open a new log in Logger32 and import the edited ADIF.



If you are uncertain that you have in fact uploaded all your QSOs, it doesn’t hurt to export the QSOs as an ADIF then sign and upload them all to LoTW. tQSL will hopefully tell you that some are duplicates: it’s up to you whether to sign and upload them anyway, just to be certain, or only sign and upload the uniques. After that, edit the ADIF file and set up a new log as I said before.



73

Gary ZL2iFB



PS Yahoo! or the email software may mangle the XML definitions in this message. The crucial bit you need to add to each ADIF record is: less-than LOTW underscore QSL underscore SENT colon 1 greater-than Y space



I hope that comes through OK!



From: hamlogger@... [mailto:hamlogger@...]
Sent: Thursday, 8 June 2017 6:45 a.m.
To: hamlogger@...
Subject: [hamlogger] Re: confirm lotw qso





Hello I have tried both ways but it does not change something has happened here and some time suddenly and i do not know why, the contacts are all uploaded to the lotw but do not appear in the logger some that they are uploaded

Update crash

Jim Hargrave
 

We are making progress. We think we have a fix.

"Analysis indicates that the reported post auto-update the crash ONLY occurs if the user has the main Logger32 Window configured and running on a monitor other than the top/left one. 

 

Anyone running Logger32 on a second monitor and unable to auto-update let me know If you would be willing to help us verify the fix..

Please send direct to my e-mail listed below.

 

73, Jim – w5ifp@...

Re: confirm lotw qso

Gary Hinson
 

Hi John.

 

If you are certain you have signed and uploaded ALL your QSOs to LoTW, you could export your log as an ADIF (saving a just-in-case offline copy), then edit it using a text editor such as Notepad, Wordpad or TED to add Y to every record, before the marker, then open a new log in Logger32 and import the edited ADIF.

 

If you are uncertain that you have in fact uploaded all your QSOs, it doesn’t hurt to export the QSOs as an ADIF then sign and upload them all to LoTW.  tQSL will hopefully tell you that some are duplicates: it’s up to you whether to sign and upload them anyway, just to be certain, or only sign and upload the uniques.  After that, edit the ADIF file and set up a new log as I said before.

 

73

Gary  ZL2iFB

 

PS  Yahoo! or the email software may mangle the XML definitions in this message.  The crucial bit you need to add to each ADIF record is:   less-than LOTW underscore QSL underscore SENT colon 1 greater-than Y space

 

I hope that comes through OK!

 

From: hamlogger@... [mailto:hamlogger@...]
Sent: Thursday, 8 June 2017 6:45 a.m.
To: hamlogger@...
Subject: [hamlogger] Re: confirm lotw qso

 

 

Hello I have tried both ways but it does not change something has happened here and some time suddenly and i do not know why, the contacts are all uploaded to the lotw but do not appear in the logger some that they are uploaded

Re: confirm lotw qso

john Kalou
 

Hello I have tried both ways but it does not change something has happened here and some time suddenly and i do not know why, the contacts are all uploaded to the lotw but do not appear in the logger some that they are uploaded

Re: Crashed after update

Jim Hargrave
 

Attached



73, Jim – w5ifp@...



From: hamlogger@... [mailto:hamlogger@...]
Sent: Wednesday, June 7, 2017 8:45 AM
To: hamlogger@...
Subject: RE: [hamlogger] Crashed after update








Jim, while the problem will fixed, where i can
get the file logger32exe-318.zip ?

Thanks

​Andre​








André Cavalcante Sampaio PP6ZZ <http://www.qrz.com/db/pp6zz>

Also PYØFF <http://www.qrz.com/db/py0ff> PY7CW <http://www.qrz.com/db/py7cw>

http://www.qrz.com/db/pp6zz


http://www.acsampaiodesign.wix.com/pp6zz


DXPeditions :
PYØCW (1981, 1982) Fernando de Noronha Island

PY7CW/Ø (1987) Fernando de Noronha Island

ZYØRF (1989) Rocas Atoll (IOTA SA-038)

PWØS (2001) St. Peter & St. Paul Rocks

PWØT (2002) Trindade Island

PW6C (2009) Coroa Vermelha Island (IOTA SA-062)










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

Re: Crashed after update

Andre Sampaio
 

Jim, while the problem will fixed, where i can
get the file logger32exe-318.zip ?
Thanks
​Andre​

 

                     André Cavalcante Sampaio  PP6ZZ                 
                                       Also PYØFF  PY7CW
                               http://www.qrz.com/db/pp6zz
                    
                   http://www.acsampaiodesign.wix.com/pp6zz

DXPeditions :
PYØCW (1981, 1982) Fernando de Noronha Island
PY7CW/Ø (1987) Fernando de Noronha Island
ZYØRF (1989) Rocas Atoll (IOTA SA-038)
PWØS (2001) St. Peter & St. Paul Rocks
PWØT (2002) Trindade Island
PW6C (2009) Coroa Vermelha Island (IOTA SA-062)

Re: .319 crash FIX

Andre Sampaio
 

Hi Mike
Unhappyly for me not work.
My Logger32 is located in my second monitor ........
Any influence ?
73,
Andre

                     André Cavalcante Sampaio  PP6ZZ                 
                                       Also PYØFF  PY7CW
                               http://www.qrz.com/db/pp6zz
                    
                   http://www.acsampaiodesign.wix.com/pp6zz

DXPeditions :
PYØCW (1981, 1982) Fernando de Noronha Island
PY7CW/Ø (1987) Fernando de Noronha Island
ZYØRF (1989) Rocas Atoll (IOTA SA-038)
PWØS (2001) St. Peter & St. Paul Rocks
PWØT (2002) Trindade Island
PW6C (2009) Coroa Vermelha Island (IOTA SA-062)

Re: Crashed after update

Jim Hargrave
 

Thanks to all who sent screen captures of the error message. We still cannot positively identify the conflict.

 

We have not been able to duplicate the condition. We need a little help.

IF you get the Runtime error when opening version 3.50.319, please send me a copy of your file: “Logger32.ini”

Send direct to the e-mail listed below.

Thanks!

 

73, Jim – w5ifp@...

Re: confirm lotw qso

john Kalou
 

Hello unfortunately and this I did but does not say to indicate that the contacts are uploaded to lotw

Re: Crashed after update

John Munton <JOHNG7SSE@...>
 

Look in the files section for Logger32exe-318 zip

73
John
G7SSE

------ Original Message ------
From: "bsumner@... [hamlogger]" <hamlogger@...>
Sent: 07/06/2017 01:08:50
Subject: RE: [hamlogger] Crashed after update

 

could someone please post Logger32.exe (3.50.0318) in the files section?

Re: Sound card input drop out

Richard M. Gillingham
 

Great, Chris!!

The different antiviruses each miss something.  Having another arrow in the quiver never hurts.  

73 and gud DX...

Gil, W1RG



From: "'Chris Saunders' c_saunders@... [hamlogger]"
To: hamlogger@...
Sent: Tuesday, June 6, 2017 6:40 PM
Subject: RE: [hamlogger] Sound card input drop out

 
Got it!
Or rather got rid of it!
It’s been stable for over 30 minutes now.
Thanks Gil, the use of Malwarebytes seems to have purged whatever was causing the problem.
AVG didn’t see it.
Good luck to anyone else who gets infected.
 
Thanks to all for the tips.
 
Chris, G4ZCS
 
From: hamlogger@... [mailto:hamlogger@...]
Sent: 06 June 2017 21:40
To: hamlogger@...
Subject: RE: [hamlogger] Sound card input drop out
 
 
I used another antivirus as well, but Malwarebytes uses some other system to find tbe beasties.  The download is a free version good for a couple weeks.  I have since purchased a copy.   Free is good.  And if it doesn't help, nothing lost.  It's a frustrating problem.  
 
73 Gil. W1RG
 
 
 
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
 
-------- Original message --------
From: "'Chris Saunders' c_saunders@... [hamlogger]" <hamlogger@...>
Date: 6/6/17 3:27 PM (GMT-05:00)
Subject: RE: [hamlogger] Sound card input drop out
 
 
Thanks Gil.
 
Tried that, I use AVG.
I also reloaded the driver for the I/F no change.
This problem is evident on other programs as well as L32.
Anyone else seen this or got any clues please?
 
Chris, G4ZCS
 
From: hamlogger@... [mailto:hamlogger@...]
Sent: 04 June 2017 22:53
To: hamlogger@...
Subject: Re: [hamlogger] Sound card input drop out
 
 
I had this problem recently. Try downloading Malwarebytes and scan your pc. It turned out to be a virus.  Problem somved in about 10 minutes...
 
Hope your troube is as simple to resolve.
 
73
Gil, W1RG
 
 
 
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
 
-------- Original message --------
From: "'Chris Saunders' c_saunders@... [hamlogger]" <hamlogger@...>
Date: 6/4/17 4:39 PM (GMT-05:00)
Subject: [hamlogger] Sound card input drop out
 
 
Hi All.
My PC has recently decided to throw a wobbly!
The sound card input continually resets itself to “mute” approx. 10 seconds after being reset to “on”.
I am using Windows 10, Logger ver’ 3.50.318, and a USB audio interface.
All hardware and cables tested OK, so a system problem.
Anyone able to offer any suggestions please?
 
Chris, G4ZCS
 
Virus-free. www.avg.com
 


Re: Crashed after update

Bradford Sumner
 

could someone please post Logger32.exe (3.50.0318) in the files section?

Re: Sound card input drop out

Chris Saunders
 

Got it!

Or rather got rid of it!

It’s been stable for over 30 minutes now.

Thanks Gil, the use of Malwarebytes seems to have purged whatever was causing the problem.

AVG didn’t see it.

Good luck to anyone else who gets infected.

 

Thanks to all for the tips.

 

Chris, G4ZCS

 

From: hamlogger@... [mailto:hamlogger@...]
Sent: 06 June 2017 21:40
To: hamlogger@...
Subject: RE: [hamlogger] Sound card input drop out

 

 

I used another antivirus as well, but Malwarebytes uses some other system to find tbe beasties.  The download is a free version good for a couple weeks.  I have since purchased a copy.   Free is good.  And if it doesn't help, nothing lost.  It's a frustrating problem.  

 

73 Gil. W1RG

 

 

 

Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone

 

-------- Original message --------

From: "'Chris Saunders' c_saunders@... [hamlogger]" <hamlogger@...>

Date: 6/6/17 3:27 PM (GMT-05:00)

Subject: RE: [hamlogger] Sound card input drop out

 

 

Thanks Gil.

 

Tried that, I use AVG.

I also reloaded the driver for the I/F no change.

This problem is evident on other programs as well as L32.

Anyone else seen this or got any clues please?

 

Chris, G4ZCS

 

From: hamlogger@... [mailto:hamlogger@...]
Sent: 04 June 2017 22:53
To: hamlogger@...
Subject: Re: [hamlogger] Sound card input drop out

 

 

I had this problem recently. Try downloading Malwarebytes and scan your pc. It turned out to be a virus.  Problem somved in about 10 minutes...

 

Hope your troube is as simple to resolve.

 

73

Gil, W1RG

 

 

 

Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone

 

-------- Original message --------

From: "'Chris Saunders' c_saunders@... [hamlogger]" <hamlogger@...>

Date: 6/4/17 4:39 PM (GMT-05:00)

Subject: [hamlogger] Sound card input drop out

 

 

Hi All.

My PC has recently decided to throw a wobbly!

The sound card input continually resets itself to “mute” approx. 10 seconds after being reset to “on”.

I am using Windows 10, Logger ver’ 3.50.318, and a USB audio interface.

All hardware and cables tested OK, so a system problem.

Anyone able to offer any suggestions please?

 

Chris, G4ZCS

 

Virus-free. www.avg.com