A suggestion to make the manual more readable.
Look at the difference.
- merge_from_ofoct.jpg (243.66 KiB) Viewed 2508 times
Search found 5 matches
- 20 Mar 2021, 07:42
- Forum: Feature suggestions
- Topic: Layout suggestion
- Replies: 0
- Views: 2512
Layout suggestion
Hi,
A suggestion to make the manual more readable.
Look at the difference.
A suggestion to make the manual more readable.
Look at the difference.
- 28 Jan 2018, 08:11
- Forum: User Support
- Topic: Log4om 1.31.0.0 database issue
- Replies: 37
- Views: 22425
Re: Log4om 1.31.0.0 database issue
same problem here.
- 04 Dec 2016, 14:39
- Forum: User Support
- Topic: starting log4om with default "recent QSO (F8)" screen
- Replies: 1
- Views: 1673
starting log4om with default "recent QSO (F8)" screen
HI,
Is it possible to start log4om with default "recent QSO (F8)" screen?
Now "QSO information (F7)" is default.
Geert
pa3cps
Is it possible to start log4om with default "recent QSO (F8)" screen?
Now "QSO information (F7)" is default.
Geert
pa3cps
- 09 Nov 2016, 16:44
- Forum: Software Integration
- Topic: JTAlert logging
- Replies: 3
- Views: 5158
Re: JTAlert logging
Problem solved:
Solution:
I did a fresh Windows 10 install.
Solution:
I did a fresh Windows 10 install.
- 04 Nov 2016, 14:43
- Forum: Software Integration
- Topic: JTAlert logging
- Replies: 3
- Views: 5158
JTAlert logging
Is use: Windows 10, WSJT-X 1.7 RC2, JTAlert 2.8.4, LOG4OM v1.26.0.0 I have sometimes problems with the logging from JTAlert to LOG4om. With several qso's everything works perfect, but sometime's i get a failure and i have to log the qso manual. Failure: QSO not logged! ERROR Message: LOG4OM file: un...
