Hi Jürgen,
Sorry, but at that time I was running version 2.8.0.0
anyway, It did not work for me in Version 2, At the time of my question at July 2020 I was under the assumption that I made a mistake.
73, Dick
Search found 64 matches
- 08 Apr 2022, 12:29
- Forum: User support
- Topic: country_user file is no longer taken into account
- Replies: 10
- Views: 2010
- 08 Apr 2022, 12:00
- Forum: Error reports
- Topic: V 2.21.0.0 worked same band not signalled
- Replies: 11
- Views: 3037
Re: V 2.21.0.0 worked same band not signalled
some screen shots:
- 07 Apr 2022, 14:09
- Forum: Error reports
- Topic: V 2.21.0.0 worked same band not signalled
- Replies: 11
- Views: 3037
Re: V 2.21.0.0 worked same band not signalled
Thanks Daniele,
I just installed Discord via the link and will see how i have to use it, because Discord is new for me.
I also installed the Beta 2.21.1.1 it did not fix the problem for me. it is still showing the wrong color
I just installed Discord via the link and will see how i have to use it, because Discord is new for me.
I also installed the Beta 2.21.1.1 it did not fix the problem for me. it is still showing the wrong color
- 07 Apr 2022, 12:42
- Forum: User support
- Topic: country_user file is no longer taken into account
- Replies: 10
- Views: 2010
Re: country_user file is no longer taken into account
This is confusing for me, because I asked this same question in July 2020 and received the following response:
- 07 Apr 2022, 09:08
- Forum: Error reports
- Topic: V 2.21.0.0 worked same band not signalled
- Replies: 11
- Views: 3037
Re: V 2.21.0.0 worked same band not signalled
Thanks! i have some additional information for you. during my test yesterday I saw that a new QSO which I saved then did get the correct cluster status. The QSO's already present in my database get the wrong status in the cluster view if the station in question has a cluster entry. I use LOG4OM dail...
- 06 Apr 2022, 15:53
- Forum: Error reports
- Topic: V 2.21.0.0 worked same band not signalled
- Replies: 11
- Views: 3037
Re: V 2.21.0.0 worked same band not signalled
Hi,
I have found exactly the same problem after installing version 2.21
I have found exactly the same problem after installing version 2.21
- 22 Feb 2022, 10:44
- Forum: User support
- Topic: RX Field in ver 2.20
- Replies: 5
- Views: 1412
Re: RX Field in ver 2.20
Hi,
I also prefer to have it back as it was in version 2.18
I have not seen an announcement or a mention in update log of this change.
It was changed in version 2.19 and I have been hoping it would be back version 2.20.
73, Dick
I also prefer to have it back as it was in version 2.18
I have not seen an announcement or a mention in update log of this change.
It was changed in version 2.19 and I have been hoping it would be back version 2.20.
73, Dick
- 14 Aug 2020, 17:26
- Forum: Error reports
- Topic: Not reading Country_user.xml
- Replies: 12
- Views: 5824
Re: Not reading Country_user.xml
it's indeed very odd that this problem only occurs to me. I have installed Log4OM v2 on 3 different computers and all 3 act the same. I put logging in debug mode and viewed the log and then turned on Real-time log and watched it. How can I check or where can I see that Country_user.xml is being used...
- 09 Aug 2020, 13:56
- Forum: Error reports
- Topic: Not reading Country_user.xml
- Replies: 12
- Views: 5824
Re: Not reading Country_user.xml
Thanks Jim, I really appreciate your help. I wasn't aware of that change and made the change, then downloaded the clublog file again and now there was data in it as well. Previously this file was empty except for the headers. Unfortunately this didn't solve the problem either. I have now simply chan...
- 06 Aug 2020, 15:02
- Forum: Error reports
- Topic: Not reading Country_user.xml
- Replies: 12
- Views: 5824
Re: Not reading Country_user.xml
Jim,
My settings were indeed different.
I then adjusted the settings as you described it. Saved settings and then restarted Log4OM.
However, the result is still the same see here:
73 Dick
My settings were indeed different.
I then adjusted the settings as you described it. Saved settings and then restarted Log4OM.
However, the result is still the same see here:
73 Dick