LogHX: English version

[Alde]

Thanks for your attention and support, 73 from py5ej.[/QUOTE]

Alexei, thanks for your attention and suggestion.

Unfortunately, the problem persists. In the old versions, it was possible to sort the QSLR(S)_Date columns without any problems.



However, in recent versions including the recommended 770, when I try to sort it is no longer possible.
I'm in a loop, removing the date 30-12-1899 leaves the field empty, with the field empty it is NOT possible to sort the column, if I repair the logHX as suggested the date 30-12-1899 reappears.
How can I remove the unwanted date from the logHX, and then sort the columns mentioned?
Thanks for your attention and support, 73 from py5ej.

[Jim Smith]

Hi Alexei,

Just a heads up that Windows Defender flagged a threat after I installed build 771 this evening, clearly it's a false positive - details in the screengrab image below in case it's of any help:



I am also getting the error below when I click on a DX spot - everything happens normally as it should but I also get this pop up box:



I clear the box down and all is fine.

[RX4HX]

image below

Yes, CreateBauckup.exe create zip-archive, and it's look like virus.

I clear the box down and all is fin

Fixed -
http://rx4hx.qrz.ru/files/loghx/test..._build_772.exe

[IK2XDE]

Hello Alexey,
with new buid 774 - 08/01/2025
whean I use OFFLINE MANAGERS DATABASE
function LOAD from *.TXT file
I receive this error:





LogHX run as administrator.

Hope you will find this bug.

Thanks.

73 de IK2XDE Andrea.

[RX4HX]

function LOAD from *.TXT file

Hello Andrea!

Please, write here 2-5 lines from this TXT-file.

[IK2XDE]

here some example.

--------
3A/IZ8EGM,IZ8EGM,01-01-2015,31-12-2015
3A/MM0NDX,EB7DX,01-01-2021,31-12-2024,WEB OQRS - https://www.eb7dx.com - ONLY DIRECT - NO BUREAU
3A/MM0SAJ,EB7DX,16-01-2024,31-12-2024
3A/N0FW/P,W8QID,01-01-2005,31-12-2005
3A/N9NS/P,W8QID,01-01-2005,31-12-2005
3A/OJ0Y,EB7DX,01-01-2019,31-12-2019,WEB OQRS - https://www.eb7dx.com - ONLY DIRECT - NO BUREAU
3A/OK1CZ,OK1CZ,01-01-2000,31-12-2000
3A/ON4LUC/P,ON6DP,01-01-2007,31-12-2007
3A/ON5NT/P,ON5NT,01-01-2007,31-12-2007
3A/ON5UR,M0URX,01-01-2012,31-12-2014,WEB OQRS - https://www.m0urx.com
3A/ON8AK,M0URX,01-01-2012,31-12-2012,WEB OQRS - https://www.m0urx.com
3A/PB8DX,OQRS,01-01-2022,31-12-2022,CLUBLOG OQRS - LOTW
3A/RA9USU,UA3DX,01-01-2021,31-12-2021
3A/SP2FAX/P,SP2PI,01-01-2005,31-12-2005
3A/SP2JMB/P,SP2PI,01-01-2005,31-12-2005
---------


This file never change
File CREATE with "SAVE TO TXT FILE"

73 de IK2XDE Andrea

[RX4HX]

here some example.

Fixed -
http://rx4hx.qrz.ru/files/loghx/LogH..._build_774.exe

[IK2XDE]

Hello Alexey,
now all work fine.

Thanks.

[Josef]

Last version:

Wrong CONNECT_SERVER!

on any server. What is new, where is a problem?

73 Josef OK2WO

[Josef]

Solved - all my data, including the callsign, disappeared from the setup, I don't know why, after upgrade...

73 Josef OK2WO

[RX4HX]

all my data, including the callsign, disappeared from the setup, I don't know why, after upgrade

All setup data saved in <LogHX>\INI folder. You can restore all data from backup.

[Jim Smith]

.

- - - Добавлено - - -

Ignore my previous, I solved it.

[Jim Smith]

It looks like recent Windows Defender updates is generating false positives for trojan viruses in LogHX files.

This morning, Spottercollector.exe was eaten by Defender.

I updated LogHX to 776 and this time Defender ate LogHX.exe as well as SpotterCollector.

I have put an exception on the LogHX folder, reinstalled and all is ok now.

[RX4HX]

It looks like recent Windows Defender updates is generating false positives for trojan viruses in LogHX files.

Yes, last update of Windows Defender find trojan in SpotMachineServer.exe (not Spottercollector.exe!).
This is a problem of Windows Defender. Log is not trojan)))

[Jim Smith]

Yes, last update of Windows Defender find trojan in SpotMachineServer.exe (not Spottercollector.exe!).
This is a problem of Windows Defender. Log is not trojan)))

Haha, yes thats hat I meant. Not enough coffee consumed at that point.

On another note - I was using 775, but I had to roll back to an earlier build becasue Telnet kept disconnecting and was not re-connecting automatically. I find it strange that it should disconnect at all, as it's a localhost / 127.0.0.1 connection to VE7CC cluster client running on the same machine.....

The disconnection happens due to "Timeout get gata from server [127.0.0.1]" ( assume gata = data ). Another program I use doesn't get these disconnections, so I wonder how long a timeout has to be before LogHX assumes a timeout and disconnects.

Anyway, I rolled back to 771 (the last I'd downloaded) and all is well again, the disconnects still happen but HX connects again straight away.