Hi Petr,

I am doing some testing on 1.0.0 Alpha. I noticed when I exported my log from 0.96, the state, lotw_qsls and lotw_qslr fields were not exported to the adif file! Please have a look.

Hi,

I've tried to compile 0.9.9 from source today and use it, but found problem. While rig control and MySQL works just fine, there are problems with fldigi.
While fldigi and cqrlog can work side by side (sharing CAT interface via rigctld), turning on "remote mode for fldigi" in cqrlog causes it to freeze after few seconds.
Logging QSO to cqrlog fails, cqrlog must be killed (won't exit or unfreeze after fldigi closed).

When running "Good, old" cqrlog 0.9.6 "forgotten" QSOs has been logged OK and interactions with fldigi works excelent.

System: Ubuntu 10.04 (lucid) on Intel x86_64

Hi!
I'm using cqrlog mainly on x86-64 architecture and one thing that was missing to me was the hamlib support (32 static binary cqrlog vs. 64bit system with hamlib).
So I want to compile cqrlog as 64bit application and don't have any free pascal/lazarus experience (but write some code in C/C++) ;)

Version 0.9.6 doesn't compile (uses unit libc - as I found not available for my architecture), 0.9.9 compiles pretty easy, but...

Non standard serial port locations do not seem to work.

Hi Petr, I'm building a rig bridge for
linux using python (like lp-bridge for windows). I have quite a bit of success and have run CQRLOG from a remote computer using a serial line to a second computer running the bridge program and talking to my K3.

I have used socat to build several virtual serial ports and have tested
them with my bridge using a terminal program and using hamlib through
rigctl

Some call signs do not return data even when data is available on QRZ

. Try H40FN in CQRLOG then enter it directly into QRZ. Data is present but no data is displayed.

Ubuntu Maverick