Last chance


Colin Hendry
 

I ave spent 4 days getting Logger32 up and running again just as I had it and yesterday this happened.

logger hung

not
        responding

I left the computer running overnight just incase it was being extremely slow but no Logger32 is dead.

Has any one got and smart ideas as to how I can get this working with out reinstalling.


Colin G0ODR



Andy M0NKR
 

Hi Colin,

Does it still happen if you were to shut down pc and start it up again? 

Try disabling any virus protection you have running and try again, or try opening as an administrator.

73
Andy
M0NKR


On 17 Jun 2021, at 09:32, Colin Hendry via groups.io <colin.hendry23@...> wrote:



I ave spent 4 days getting Logger32 up and running again just as I had it and yesterday this happened.

<Screenshot 2021-06-17 092430.jpg>

<Screenshot 2021-06-17 092534.jpg>

I left the computer running overnight just incase it was being extremely slow but no Logger32 is dead.

Has any one got and smart ideas as to how I can get this working with out reinstalling.


Colin G0ODR



Colin Hendry
 

Hi Andy,

Tried reboots, is already running as administrator and have checked as such. As been OK and wont disable antivirus as that real defeats the object.

Thanks for the suggestions Andy, you OK

73 Colin G0ODR


On 17/06/2021 09:45, Andy M0NKR via groups.io wrote:
Hi Colin,

Does it still happen if you were to shut down pc and start it up again? 

Try disabling any virus protection you have running and try again, or try opening as an administrator.

73
Andy
M0NKR


On 17 Jun 2021, at 09:32, Colin Hendry via groups.io <colin.hendry23@...> wrote:



I ave spent 4 days getting Logger32 up and running again just as I had it and yesterday this happened.

<Screenshot 2021-06-17 092430.jpg>
<Screenshot 2021-06-17 092534.jpg>

I left the computer running overnight just incase it was being extremely slow but no Logger32 is dead.

Has any one got and smart ideas as to how I can get this working with out reinstalling.


Colin G0ODR



John Munton - G7SSE
 

Colin

As a guess, it looks like Logger32 is trying, on starting, to perform a task it cannot complete.

As a test, go to your Logger32 directory, find the Logger32.ini file and temporally move it to another location on your system for safe keeping.
Then try running Logger32, it will recreate a default ini file.

Does it run ok?

If so it's something in your config/settings that is the problem.

One idea, could it be Logger32 is trying to auto start another program from its utilities menu that is no longer on your system?

Another is did you change any of the default fonts in Logger32? 

Regarding virus protection; rather than disable it you could add Logger32 as an exception.

Just out of curiosity, why have you had to "get Logger32 up and running again" ?
--
73, John - G7SSE


Andy M0NKR
 

If it’s an update and first load of it then anti virus may need to be disable to allow it to load,

Failing that revert to the previous known working version 

73
Andy
Nkr


On 17 Jun 2021, at 10:50, John Munton - G7SSE <johng7sse@...> wrote:

Colin

As a guess, it looks like Logger32 is trying, on starting, to perform a task it cannot complete.

As a test, go to your Logger32 directory, find the Logger32.ini file and temporally move it to another location on your system for safe keeping.
Then try running Logger32, it will recreate a default ini file.

Does it run ok?

If so it's something in your config/settings that is the problem.

One idea, could it be Logger32 is trying to auto start another program from its utilities menu that is no longer on your system?

Another is did you change any of the default fonts in Logger32? 

Regarding virus protection; rather than disable it you could add Logger32 as an exception.

Just out of curiosity, why have you had to "get Logger32 up and running again" ?
--
73, John - G7SSE


alan
 

Hi Colin,

for what its worth I cannot run logger 32 updates in the normal mode,

so when it comes up with the update(yes/no) I say "no" then close logger 32.

Then I go to the C Drive and right click on the L32 Icon tell it to run as administrator, wait for the update message

and this time say"yes" click full backup and hit install, it  then installs the upgrade version. once that is

done I close L32 again as LogSync etc wont run under administrator and boot l32 from the task bar and it

boots cleanly into the updated version. Have done this for about 2 years now and and works fine everytime.

I am running windows 10.

73  Alan  ZL3KR


On 17/06/2021 8:45 pm, Andy M0NKR via groups.io wrote:
Hi Colin,

Does it still happen if you were to shut down pc and start it up again? 

Try disabling any virus protection you have running and try again, or try opening as an administrator.

73
Andy
M0NKR


On 17 Jun 2021, at 09:32, Colin Hendry via groups.io <colin.hendry23@...> wrote:



I ave spent 4 days getting Logger32 up and running again just as I had it and yesterday this happened.

<Screenshot 2021-06-17 092430.jpg>
<Screenshot 2021-06-17 092534.jpg>

I left the computer running overnight just incase it was being extremely slow but no Logger32 is dead.

Has any one got and smart ideas as to how I can get this working with out reinstalling.


Colin G0ODR



Jan
 

Hi Alan (and Andy)

Why don't you let Logger32 runs as administrator all the time?
Logsync will run as administrator as well (I assume you use the N2AMG utility Logsync)
It's running perfect here on my PC

73
Jan
PA4JJ

Op 17-6-2021 om 12:05 schreef alan:

Hi Colin,

for what its worth I cannot run logger 32 updates in the normal mode,

so when it comes up with the update(yes/no) I say "no" then close logger 32.

Then I go to the C Drive and right click on the L32 Icon tell it to run as administrator, wait for the update message

and this time say"yes" click full backup and hit install, it  then installs the upgrade version. once that is

done I close L32 again as LogSync etc wont run under administrator and boot l32 from the task bar and it

boots cleanly into the updated version. Have done this for about 2 years now and and works fine everytime.

I am running windows 10.

73  Alan  ZL3KR


On 17/06/2021 8:45 pm, Andy M0NKR via groups.io wrote:
Hi Colin,

Does it still happen if you were to shut down pc and start it up again? 

Try disabling any virus protection you have running and try again, or try opening as an administrator.

73
Andy
M0NKR


On 17 Jun 2021, at 09:32, Colin Hendry via groups.io <colin.hendry23@...> wrote:



I ave spent 4 days getting Logger32 up and running again just as I had it and yesterday this happened.

<Screenshot 2021-06-17 092430.jpg>
<Screenshot 2021-06-17 092534.jpg>

I left the computer running overnight just incase it was being extremely slow but no Logger32 is dead.

Has any one got and smart ideas as to how I can get this working with out reinstalling.


Colin G0ODR



-- 
____________________________________________________
my dxspider clusters running on a raspberry pi zero:  
pa4jj-2 83.162.186.242 port 7300
pa4jj-3 83.162.186.242 port 7388


Andy M0NKR
 

Your correct, I run my version as administrator all the time. I’ve had no issue with any update so far.

73
Andy
M0NKR


On 17 Jun 2021, at 11:16, Jan <hamlogger@...> wrote:

 Hi Alan (and Andy)

Why don't you let Logger32 runs as administrator all the time?
Logsync will run as administrator as well (I assume you use the N2AMG utility Logsync)
It's running perfect here on my PC

73
Jan
PA4JJ

Op 17-6-2021 om 12:05 schreef alan:

Hi Colin,

for what its worth I cannot run logger 32 updates in the normal mode,

so when it comes up with the update(yes/no) I say "no" then close logger 32.

Then I go to the C Drive and right click on the L32 Icon tell it to run as administrator, wait for the update message

and this time say"yes" click full backup and hit install, it  then installs the upgrade version. once that is

done I close L32 again as LogSync etc wont run under administrator and boot l32 from the task bar and it

boots cleanly into the updated version. Have done this for about 2 years now and and works fine everytime.

I am running windows 10.

73  Alan  ZL3KR


On 17/06/2021 8:45 pm, Andy M0NKR via groups.io wrote:
Hi Colin,

Does it still happen if you were to shut down pc and start it up again? 

Try disabling any virus protection you have running and try again, or try opening as an administrator.

73
Andy
M0NKR


On 17 Jun 2021, at 09:32, Colin Hendry via groups.io <colin.hendry23@...> wrote:



I ave spent 4 days getting Logger32 up and running again just as I had it and yesterday this happened.

<Screenshot 2021-06-17 092430.jpg>
<Screenshot 2021-06-17 092534.jpg>

I left the computer running overnight just incase it was being extremely slow but no Logger32 is dead.

Has any one got and smart ideas as to how I can get this working with out reinstalling.


Colin G0ODR



-- 
____________________________________________________
my dxspider clusters running on a raspberry pi zero:
pa4jj-2 83.162.186.242 port 7300
pa4jj-3 83.162.186.242 port 7388


Colin Hendry
 

Thanks John,

Yes it will run after the .ini file is moved, looks like starting afresh. This will mean setting the windows as I like them to be again. Why details like date, time, callsign, RST's etc aren't at the beginning of the log entry window escapes me. That is what takes time moving columns about. They aren't even alphabetical.

I don't know if the system is trying to auto start another program, I can not remember asking it to. I had set it to use LogSync and Loglookup but wasn't aware they could be auto started. Yes I did change some default fonts, if you can't why have the option, but it has booted many times over the last couple of days without issue. I don't know if it did an auto update but it may have.


The reason for getting up and running again was because when I upgraded to V4 the antenna selection system would not work automatically. I set it up as it was in the older version using the data window and as instructed by the help file distributed with the software, link to G4 site. Has I found out this was not the latest version of the help file and that method is no longer used, I suggested that a link to a permanent current help file be installed and I see the programmers listened. Even using the Antenna selector serial port set up it still wouldn't work in auto or manual, and yes I had set the band and modes. the Data terminal still worked in manual. I missed the instruction that rollback was not an option and tried it thus screwing everything up. The assistance wasn't exactly helpful so my only option was to clear all the old stuff out and start with a fresh full download of V4. Guess what it all worked know with the antennas selector serial port. So I can only conclude that the update to V4 from previous version, which was always kept up to date, was the issue.

If you can't roll back from the new version why wasn't the option removed or disabled until it could be safely used again. When I was working if we didn't want something to happen by mistake we disabled or removed that option, simple.

So what can't I do with fonts and personalising it to how I want it?


73

Colin G0ODR


On 17/06/2021 10:50, John Munton - G7SSE wrote:
Colin

As a guess, it looks like Logger32 is trying, on starting, to perform a task it cannot complete.

As a test, go to your Logger32 directory, find the Logger32.ini file and temporally move it to another location on your system for safe keeping.
Then try running Logger32, it will recreate a default ini file.

Does it run ok?

If so it's something in your config/settings that is the problem.

One idea, could it be Logger32 is trying to auto start another program from its utilities menu that is no longer on your system?

Another is did you change any of the default fonts in Logger32? 

Regarding virus protection; rather than disable it you could add Logger32 as an exception.

Just out of curiosity, why have you had to "get Logger32 up and running again" ?
--
73, John - G7SSE


Colin Hendry
 

I am running Win 10 and have had now issue with leaving the auto update selected. Tells me when there is one and gives me the option to install or not. I always take the advice to do a full backup and upto now have had no issues.

73 Colin G0ODR


On 17/06/2021 11:05, alan wrote:

Hi Colin,

for what its worth I cannot run logger 32 updates in the normal mode,

so when it comes up with the update(yes/no) I say "no" then close logger 32.

Then I go to the C Drive and right click on the L32 Icon tell it to run as administrator, wait for the update message

and this time say"yes" click full backup and hit install, it  then installs the upgrade version. once that is

done I close L32 again as LogSync etc wont run under administrator and boot l32 from the task bar and it

boots cleanly into the updated version. Have done this for about 2 years now and and works fine everytime.

I am running windows 10.

73  Alan  ZL3KR


On 17/06/2021 8:45 pm, Andy M0NKR via groups.io wrote:
Hi Colin,

Does it still happen if you were to shut down pc and start it up again? 

Try disabling any virus protection you have running and try again, or try opening as an administrator.

73
Andy
M0NKR


On 17 Jun 2021, at 09:32, Colin Hendry via groups.io <colin.hendry23@...> wrote:



I ave spent 4 days getting Logger32 up and running again just as I had it and yesterday this happened.

<Screenshot 2021-06-17 092430.jpg>
<Screenshot 2021-06-17 092534.jpg>

I left the computer running overnight just incase it was being extremely slow but no Logger32 is dead.

Has any one got and smart ideas as to how I can get this working with out reinstalling.


Colin G0ODR



John Munton - G7SSE
 

Hi Colin

Regarding fonts; yes you can change them. It can cause issues, more usually when folk transfer their settings file to a new PC which doesn't have the selected font installed.
Unlikely in your case, just me thinking out loud.

It would seem it is definitely an issue with a setting in your ini file though.

One thing you can try is to open the file with a text editor (such as Notepad) and copy & paste one section at a time to the file in the Logger32 directory.
Run Logger after each time and see when it hangs.
This will give you some idea of where the problem may be.

Regarding rolling back; this is for going back to earlier revisions of the current version, eg:4.0.266 back to 4.0.265 and therefore is safe to use.
It just cannot be used to go back from version 4 to version 3.
I'm fairly sure when v4 was announced that there was a warning issued that after upgrading rolling back to v3 was not possible.

Colin, will you send me a copy of your problem ini file (by direct email)
Can't promise anything but would like to take a look at it.
--
73, John - G7SSE


Bob
 

I suspect Andy meant to temporarily disable your AV software ... Depending on your paranoia level you might even want to disconnect your internet while conducting the test. SeventyThree(s). 
 
 

On 06/17/2021 5:22 AM Colin Hendry via groups.io <colin.hendry23@...> wrote:
 
 

Hi Andy,

Tried reboots, is already running as administrator and have checked as such. As been OK and wont disable antivirus as that real defeats the object.

Thanks for the suggestions Andy, you OK

73 Colin G0ODR

 

On 17/06/2021 09:45, Andy M0NKR via groups.io wrote:
Hi Colin,
 
Does it still happen if you were to shut down pc and start it up again? 
 
Try disabling any virus protection you have running and try again, or try opening as an administrator.
 
73
Andy
M0NKR


On 17 Jun 2021, at 09:32, Colin Hendry via groups.io <colin.hendry23@...> wrote:

I ave spent 4 days getting Logger32 up and running again just as I had it and yesterday this happened.

<Screenshot 2021-06-17 092430.jpg>
<Screenshot 2021-06-17 092534.jpg>

I left the computer running overnight just incase it was being extremely slow but no Logger32 is dead.

Has any one got and smart ideas as to how I can get this working with out reinstalling.

 

Colin G0ODR


Colin Hendry
 

Thanks for the information. I will attach the ini file. If the screenshots came out in the first email you can see it stopped while loading band maps. What I didn't show was that one bandmap was on the screen as well. I have had a look and I can several auto start instructions but not for external programs, but then again I don't really know what I am talking about. I am the horse that cant be taken to water as Bob said.

I will let you have a look at the ini file before I do anything else, spent far to much time on this already this week.

73

Colin G0ODR

On 17/06/2021 12:30, John Munton - G7SSE wrote:
Hi Colin

Regarding fonts; yes you can change them. It can cause issues, more usually when folk transfer their settings file to a new PC which doesn't have the selected font installed.
Unlikely in your case, just me thinking out loud.

It would seem it is definitely an issue with a setting in your ini file though.

One thing you can try is to open the file with a text editor (such as Notepad) and copy & paste one section at a time to the file in the Logger32 directory.
Run Logger after each time and see when it hangs.
This will give you some idea of where the problem may be.

Regarding rolling back; this is for going back to earlier revisions of the current version, eg:4.0.266 back to 4.0.265 and therefore is safe to use.
It just cannot be used to go back from version 4 to version 3.
I'm fairly sure when v4 was announced that there was a warning issued that after upgrading rolling back to v3 was not possible.

Colin, will you send me a copy of your problem ini file (by direct email)
Can't promise anything but would like to take a look at it.
--
73, John - G7SSE


Colin Hendry
 

John, the plot thickens.

I have just done what you said and added blocks of lines to the new .INI and nothing stop the loading. I then deleted the new .INI file and replaced it with the old one, program now boots up. Not as it was though. Logbook page is populated with contacts but the order has reverted to the standard non sensible column layout i.e. Address first column instead of date. Also all the child windows look the same size as when the program first starts and not how I had adjusted them although the dx spots are working from the cluster I had setup. Also I had edited the log entry window and the modifications are still. I have also had to go into the antenna selector and with in the Set up serial port it lost the data of 2 antennas but once the 2 was put back in all the hex commands are still there and it works. Band and modes still has new data in it as well.

I had 10 bandmaps setup 2 to 80, missed 30, and a monitor one. These are not loading now and if I select from the "View" drop down or "#15 Band Map" button one bandmap appears but it is this that then sends the program into a non responsive condition. Has I said early this band map was on the screen orginally.
Hope this information may help to find a cause or lead to an explianation as to whats going on.
73
Colin G0ODR

-------- Forwarded Message --------
Subject: Re: [hamlogger] Last chance
Date: Thu, 17 Jun 2021 13:21:09 +0100
From: Colin Hendry <colin.hendry23@...>
To: hamlogger@groups.io


Thanks for the information. I will attach the ini file. If the screenshots came out in the first email you can see it stopped while loading band maps. What I didn't show was that one bandmap was on the screen as well. I have had a look and I can several auto start instructions but not for external programs, but then again I don't really know what I am talking about. I am the horse that cant be taken to water as Bob said.

I will let you have a look at the ini file before I do anything else, spent far to much time on this already this week.

73

Colin G0ODR

On 17/06/2021 12:30, John Munton - G7SSE wrote:
Hi Colin

Regarding fonts; yes you can change them. It can cause issues, more usually when folk transfer their settings file to a new PC which doesn't have the selected font installed.
Unlikely in your case, just me thinking out loud.

It would seem it is definitely an issue with a setting in your ini file though.

One thing you can try is to open the file with a text editor (such as Notepad) and copy & paste one section at a time to the file in the Logger32 directory.
Run Logger after each time and see when it hangs.
This will give you some idea of where the problem may be.

Regarding rolling back; this is for going back to earlier revisions of the current version, eg:4.0.266 back to 4.0.265 and therefore is safe to use.
It just cannot be used to go back from version 4 to version 3.
I'm fairly sure when v4 was announced that there was a warning issued that after upgrading rolling back to v3 was not possible.

Colin, will you send me a copy of your problem ini file (by direct email)
Can't promise anything but would like to take a look at it.
--
73, John - G7SSE


John Munton - G7SSE
 

We might be getting somewhere here Colin.

try this:

Open your ini file and find this line: 

Child Forms Open=+frmBandMap+wndTracking+wndLogbookEntry+wndWorkedConfirmed+wndLogbookPage+wndDxSpot+wndClusterWindow+wndPreviousQSO+

and remove +frmBandMap from it.

Next find each section that starts:

 [frmMonitorBandMap# Settings]

and delete them (the # will be the bandmap number)

Use the text file I've attached as a guide.

You could even cut & paste from it, overwriting the relevant sections and then if running ok change the positions and displayed bands as required.

I'm wondering Colin, have you changed your computer monitor set up at all? Maybe gone from dual monitors to one large one, or vice versa?
When I ran your ini on my system Logger32 showed several EOF error messages and then reset the position of all the Bandmaps to the default (top left)


Lastly, should you get everything running ok take a look at the built in backup options.
You can backup both your logbook and your settings / config files on shutting down Logger32 (see attached images)
   

After your first backup of good working user files, find the backup zip and keep it tucked away somewhere safe.
Then should thing go wrong in the future you'll have known to be good settings to fall back on.
--
73, John - G7SSE


Colin Hendry
 

Hello John  and thanks for the help. I will have a look at the files tomorrow. I have always used two monitors and the same PC for well over a year now. I have the logger32 main window, and power SDR, which is quite often minimised, with the panadaptor for the wsjtx if that is being used. The other has the rotator window, bandmaps as detailed and the wsjtx software if running.
Thanks again let’s hope for a good result.
73Colin G0ODR

On 17 Jun 2021, at 22:10, John Munton - G7SSE <johng7sse@...> wrote:

We might be getting somewhere here Colin.

try this:

Open your ini file and find this line: 

Child Forms Open=+frmBandMap+wndTracking+wndLogbookEntry+wndWorkedConfirmed+wndLogbookPage+wndDxSpot+wndClusterWindow+wndPreviousQSO+

and remove +frmBandMap from it.

Next find each section that starts:

 [frmMonitorBandMap# Settings]

and delete them (the # will be the bandmap number)

Use the text file I've attached as a guide.

You could even cut & paste from it, overwriting the relevant sections and then if running ok change the positions and displayed bands as required.

I'm wondering Colin, have you changed your computer monitor set up at all? Maybe gone from dual monitors to one large one, or vice versa?
When I ran your ini on my system Logger32 showed several EOF error messages and then reset the position of all the Bandmaps to the default (top left)


Lastly, should you get everything running ok take a look at the built in backup options.
You can backup both your logbook and your settings / config files on shutting down Logger32 (see attached images)
<Toolbar.png> <Backup User Files.png>  <Backup Logbook.png>

After your first backup of good working user files, find the backup zip and keep it tucked away somewhere safe.
Then should thing go wrong in the future you'll have known to be good settings to fall back on.
--
73, John - G7SSE
<BandMaps Position.txt>


Colin Hendry
 

Morning John,

Don't know how but this is the line from the .ini file

Child Forms Open=+wndTracking+wndLogbookEntry+wndWorkedConfirmed+wndLogbookPage+wndDxSpot+wndClusterWindow+wndPreviousQSO+

As you can see the +frmBandMap  was not there but must have been in the copy I sent you. All I did was moved the old .ini to a different folder on the hard drive. Started Logger as you said, played about with the new .ini and then deleted the new and just put the old one back into the Logger folder which was the same file I sent you.

I cut and pasted the details in as you suggested ( I did check the details and could see the changes you made but to save any typos) and the program starts as it did before with no bandmaps and the logbook columns in the default but not sensible order. As soon as I clicked to view a bandmap it appeared in the lower right hand corner of screen 1 . which I guess where you expected it to. But if I then click on the top banner to change the config or copy to produce more bandmaps that is when the system stops responding. Only option then is to kill it in task manager or via the popup asking if I want to wait for program to respond or kill it.

As I said don't know what happened to +frmBandMap as the file I sent you is the only file there is apart from the new one I binned and its seems its the action of trying to generator more bandmaps which is the issue as at the start of all this it would load to the point with one bandmap displayed and then lock up.

any thoughts?

73 Colin G0ODR.

p.s. EOF ?

On 17/06/2021 22:10, John Munton - G7SSE wrote:
We might be getting somewhere here Colin.

try this:

Open your ini file and find this line: 

Child Forms Open=+frmBandMap+wndTracking+wndLogbookEntry+wndWorkedConfirmed+wndLogbookPage+wndDxSpot+wndClusterWindow+wndPreviousQSO+

and remove +frmBandMap from it.

Next find each section that starts:

 [frmMonitorBandMap# Settings]

and delete them (the # will be the bandmap number)

Use the text file I've attached as a guide.

You could even cut & paste from it, overwriting the relevant sections and then if running ok change the positions and displayed bands as required.

I'm wondering Colin, have you changed your computer monitor set up at all? Maybe gone from dual monitors to one large one, or vice versa?
When I ran your ini on my system Logger32 showed several EOF error messages and then reset the position of all the Bandmaps to the default (top left)


Lastly, should you get everything running ok take a look at the built in backup options.
You can backup both your logbook and your settings / config files on shutting down Logger32 (see attached images)
   

After your first backup of good working user files, find the backup zip and keep it tucked away somewhere safe.
Then should thing go wrong in the future you'll have known to be good settings to fall back on.
--
73, John - G7SSE


Colin Hendry
 

It has all gone quite again but the issue is still there. If I open a bandmap and try to duplicate or configure it the program hangs. The only option left as far as I can see is to uninstall logger32 again and start with a fresh download and see what happens.

73 Colin G0ODR



On 18/06/2021 09:43, Colin Hendry via groups.io wrote:

Morning John,

Don't know how but this is the line from the .ini file

Child Forms Open=+wndTracking+wndLogbookEntry+wndWorkedConfirmed+wndLogbookPage+wndDxSpot+wndClusterWindow+wndPreviousQSO+

As you can see the +frmBandMap  was not there but must have been in the copy I sent you. All I did was moved the old .ini to a different folder on the hard drive. Started Logger as you said, played about with the new .ini and then deleted the new and just put the old one back into the Logger folder which was the same file I sent you.

I cut and pasted the details in as you suggested ( I did check the details and could see the changes you made but to save any typos) and the program starts as it did before with no bandmaps and the logbook columns in the default but not sensible order. As soon as I clicked to view a bandmap it appeared in the lower right hand corner of screen 1 . which I guess where you expected it to. But if I then click on the top banner to change the config or copy to produce more bandmaps that is when the system stops responding. Only option then is to kill it in task manager or via the popup asking if I want to wait for program to respond or kill it.

As I said don't know what happened to +frmBandMap as the file I sent you is the only file there is apart from the new one I binned and its seems its the action of trying to generator more bandmaps which is the issue as at the start of all this it would load to the point with one bandmap displayed and then lock up.

any thoughts?

73 Colin G0ODR.

p.s. EOF ?

On 17/06/2021 22:10, John Munton - G7SSE wrote:
We might be getting somewhere here Colin.

try this:

Open your ini file and find this line: 

Child Forms Open=+frmBandMap+wndTracking+wndLogbookEntry+wndWorkedConfirmed+wndLogbookPage+wndDxSpot+wndClusterWindow+wndPreviousQSO+

and remove +frmBandMap from it.

Next find each section that starts:

 [frmMonitorBandMap# Settings]

and delete them (the # will be the bandmap number)

Use the text file I've attached as a guide.

You could even cut & paste from it, overwriting the relevant sections and then if running ok change the positions and displayed bands as required.

I'm wondering Colin, have you changed your computer monitor set up at all? Maybe gone from dual monitors to one large one, or vice versa?
When I ran your ini on my system Logger32 showed several EOF error messages and then reset the position of all the Bandmaps to the default (top left)


Lastly, should you get everything running ok take a look at the built in backup options.
You can backup both your logbook and your settings / config files on shutting down Logger32 (see attached images)
   

After your first backup of good working user files, find the backup zip and keep it tucked away somewhere safe.
Then should thing go wrong in the future you'll have known to be good settings to fall back on.
--
73, John - G7SSE


John Munton - G7SSE
 

Busy with work last couple of days Colin.
John 
G7SSE 





-------- Original message --------
From: "Colin Hendry via groups.io" <colin.hendry23@...>
Date: 19/06/2021 11:29 (GMT+00:00)
To: hamlogger@groups.io
Subject: Re: [hamlogger] Last chance

It has all gone quite again but the issue is still there. If I open a bandmap and try to duplicate or configure it the program hangs. The only option left as far as I can see is to uninstall logger32 again and start with a fresh download and see what happens.

73 Colin G0ODR



On 18/06/2021 09:43, Colin Hendry via groups.io wrote:

Morning John,

Don't know how but this is the line from the .ini file

Child Forms Open=+wndTracking+wndLogbookEntry+wndWorkedConfirmed+wndLogbookPage+wndDxSpot+wndClusterWindow+wndPreviousQSO+

As you can see the +frmBandMap  was not there but must have been in the copy I sent you. All I did was moved the old .ini to a different folder on the hard drive. Started Logger as you said, played about with the new .ini and then deleted the new and just put the old one back into the Logger folder which was the same file I sent you.

I cut and pasted the details in as you suggested ( I did check the details and could see the changes you made but to save any typos) and the program starts as it did before with no bandmaps and the logbook columns in the default but not sensible order. As soon as I clicked to view a bandmap it appeared in the lower right hand corner of screen 1 . which I guess where you expected it to. But if I then click on the top banner to change the config or copy to produce more bandmaps that is when the system stops responding. Only option then is to kill it in task manager or via the popup asking if I want to wait for program to respond or kill it.

As I said don't know what happened to +frmBandMap as the file I sent you is the only file there is apart from the new one I binned and its seems its the action of trying to generator more bandmaps which is the issue as at the start of all this it would load to the point with one bandmap displayed and then lock up.

any thoughts?

73 Colin G0ODR.

p.s. EOF ?

On 17/06/2021 22:10, John Munton - G7SSE wrote:
We might be getting somewhere here Colin.

try this:

Open your ini file and find this line: 

Child Forms Open=+frmBandMap+wndTracking+wndLogbookEntry+wndWorkedConfirmed+wndLogbookPage+wndDxSpot+wndClusterWindow+wndPreviousQSO+

and remove +frmBandMap from it.

Next find each section that starts:

 [frmMonitorBandMap# Settings]

and delete them (the # will be the bandmap number)

Use the text file I've attached as a guide.

You could even cut & paste from it, overwriting the relevant sections and then if running ok change the positions and displayed bands as required.

I'm wondering Colin, have you changed your computer monitor set up at all? Maybe gone from dual monitors to one large one, or vice versa?
When I ran your ini on my system Logger32 showed several EOF error messages and then reset the position of all the Bandmaps to the default (top left)


Lastly, should you get everything running ok take a look at the built in backup options.
You can backup both your logbook and your settings / config files on shutting down Logger32 (see attached images)
   

After your first backup of good working user files, find the backup zip and keep it tucked away somewhere safe.
Then should thing go wrong in the future you'll have known to be good settings to fall back on.
--
73, John - G7SSE

--
73, John - G7SSE


Colin Hendry
 

     That’s OK John, you time is more important and I really appreciated your help.
Today I have uninstalled logger32 again. Cleaned up the files etc with Ccleaner etc..
Downloaded latest version of logger32 and installed. All appears OK. I have multiple bandmaps, looks like the antenna switching will work (I decided to re-box the relay unit and awaiting parts) the dx-cluster is up and even WSJt-x will run. Lookup is working. Happy days. What the hell has been going on I have no idea but things are a lot better today.
      One question I have to ask of the developers is, is there any way of running 2 instances of WSJT-X from logger32. I guess you would have to use two UDP map ports. I have seen other software that can listen to multiple ports but no idea if it is possible.

John, thanks again for all your assistance,

73 Colin G0ODR

On 19 Jun 2021, at 16:35, John Munton - G7SSE <johng7sse@...> wrote:

Busy with work last couple of days Colin.
John 
G7SSE 





-------- Original message --------
From: "Colin Hendry via groups.io" <colin.hendry23@...>
Date: 19/06/2021 11:29 (GMT+00:00)
Subject: Re: [hamlogger] Last chance

It has all gone quite again but the issue is still there. If I open a bandmap and try to duplicate or configure it the program hangs. The only option left as far as I can see is to uninstall logger32 again and start with a fresh download and see what happens.

73 Colin G0ODR



On 18/06/2021 09:43, Colin Hendry via groups.io wrote:

Morning John,

Don't know how but this is the line from the .ini file

Child Forms Open=+wndTracking+wndLogbookEntry+wndWorkedConfirmed+wndLogbookPage+wndDxSpot+wndClusterWindow+wndPreviousQSO+

As you can see the +frmBandMap  was not there but must have been in the copy I sent you. All I did was moved the old .ini to a different folder on the hard drive. Started Logger as you said, played about with the new .ini and then deleted the new and just put the old one back into the Logger folder which was the same file I sent you.

I cut and pasted the details in as you suggested ( I did check the details and could see the changes you made but to save any typos) and the program starts as it did before with no bandmaps and the logbook columns in the default but not sensible order. As soon as I clicked to view a bandmap it appeared in the lower right hand corner of screen 1 . which I guess where you expected it to. But if I then click on the top banner to change the config or copy to produce more bandmaps that is when the system stops responding. Only option then is to kill it in task manager or via the popup asking if I want to wait for program to respond or kill it.

As I said don't know what happened to +frmBandMap as the file I sent you is the only file there is apart from the new one I binned and its seems its the action of trying to generator more bandmaps which is the issue as at the start of all this it would load to the point with one bandmap displayed and then lock up.

any thoughts?

73 Colin G0ODR.

p.s. EOF ?

On 17/06/2021 22:10, John Munton - G7SSE wrote:
We might be getting somewhere here Colin.

try this:

Open your ini file and find this line: 

Child Forms Open=+frmBandMap+wndTracking+wndLogbookEntry+wndWorkedConfirmed+wndLogbookPage+wndDxSpot+wndClusterWindow+wndPreviousQSO+

and remove +frmBandMap from it.

Next find each section that starts:

 [frmMonitorBandMap# Settings]

and delete them (the # will be the bandmap number)

Use the text file I've attached as a guide.

You could even cut & paste from it, overwriting the relevant sections and then if running ok change the positions and displayed bands as required.

I'm wondering Colin, have you changed your computer monitor set up at all? Maybe gone from dual monitors to one large one, or vice versa?
When I ran your ini on my system Logger32 showed several EOF error messages and then reset the position of all the Bandmaps to the default (top left)


Lastly, should you get everything running ok take a look at the built in backup options.
You can backup both your logbook and your settings / config files on shutting down Logger32 (see attached images)
<Toolbar.png> <Backup User Files.png>  <Backup Logbook.png>

After your first backup of good working user files, find the backup zip and keep it tucked away somewhere safe.
Then should thing go wrong in the future you'll have known to be good settings to fall back on.
--
73, John - G7SSE

--
73, John - G7SSE