Log4OM

No, it's on the cloud.... This worked OK untill now without issues, except it became slow in recent weeks

That should be fine I also run portable from the cloud (Google drive) and have done for years

OK it does seem that you have lost all of your data so here is my recommendation

1. Create a new Log4OM database - File/Open/New Database but locate it in the P:\Log4OM Portable folder, not in the config folder

2. Then import your last backup ADIF before the time of the LOTW download

3. When you have completed items 1 & 2 above you should be back to your full database so now open and close Log4OM a couple of times to ensure a couple of recent backups before you do an LOTW download again.

I have no idea what happened with your problem and I suspect that you will never find out why! It could be something to do with a windows update, anti virus or firewall interruption, who knows?

Going to play aerials now, let me know how you get on

Obviously, with 55,000+ QSOs, it took a while, but all OK now !
All up-to-date !

And as far as knowing what created the issue, I'll ask my friend Bill Gates !

Thanks Terry !

It did it again !
When I tried to log a QSO, the program blocked itself, the Windows timer showed up and would not disappear, even after 1 hour.
And after the previous repair, the program was still runing slow.
I do not want to have to go through that again and again.
You may remeber my issue with 2 different callsigns, so I may have to reconsider the whole setup. But do not know what is the best solution, with Log4OM + JTDX + JTAlert, mentioning that JTAlert is not an absolute must.
But I want to be able to switch from one call to the other quickly and easily, having FT8 QSOs logged into the proper log.
What would be your suggestion ?

F6EXV wrote: 08 Mar 2021, 21:16 It did it again !
When I tried to log a QSO, the program blocked itself, the Windows timer showed up and would not disappear, even after 1 hour.
And after the previous repair, the program was still runing slow.
I do not want to have to go through that again and again.
You may remeber my issue with 2 different callsigns, so I may have to reconsider the whole setup. But do not know what is the best solution, with Log4OM + JTDX + JTAlert, mentioning that JTAlert is not an absolute must.
But I want to be able to switch from one call to the other quickly and easily, having FT8 QSOs logged into the proper log.
What would be your suggestion ?

So are you saying that you lost your log again?

Or that the program froze and if so what happened when you started the program again?

Also I need a full description of your set up for WSJT operation

Yes, the log was lost entirely.
WXhat do you mean by full JTDX setup ? What info do you need ?

Please try to email me a log file before you restart log4om it will be in the portable folder containing these folders \config\log - below is the location and the file for my portable installation.



DO NOT POST THE FILE ON THE FORUM - Email it to me at g4pop (AT) arrl.net