www.dl2rum.de

Thanks Tom - I rebooted/powered down & back up my system. Started only RumLog and cleared Console messages. Opened Preferences, added my Call, Name, Grid and then Close prefs and then opened it again gives following Console messages. Prefs changes again not saved. 1/29/16 5:07:17.026 PM RUMlogNG[441 ...

Updated to 2.5.1 from Ap Store recently. Today I noticed that all my preferences entries are missing with only the defaults shown. If I add an entry (Name, callsign, etc,) and "Close" preferences and then reopen Preferences my changes are not saved. No error or warning messages. Seems like it is not ...

As of today I've had no more RumLogNG hangs/crashes since installing the latest version of the Prolific chipset drivers mentioned above.

Tnx to Tom for pointing me in the right direction!

73 Phil NA4M

Thanks Tom. I found a new v1.6 certificate signed OS X driver dated 10-22-2015 on Prolific's web site. ------------ Revision Change: ==================== v1.6.0: Add code sign certificate to driver for Mac OS X security requirement. Only supports Mac OSX 10.9, 10.10, 10.11 ...

Yes - I run CAT with my K3 and P3. I assume you are asking about USB-RS232 CAT cable chipset? I am not sure of chipset but I think it may be Prolific PL-2303 When I added P3 (before OS X 10.11) to my station my Elecraft KUSB cable would not work with my K3/P3 CAT combination. My KUSB would function ...

After upgrading to OS X 10.11 RUMlogNG began to hang/crash on my system. I've happily run RUMLog and RUMLogNG on previous OS X versions with no noticeable problems. But under 10.11 recent RUMlogNG versions (v 2+) hang/crash frequently. Typically RUMlogNG will run ok for some time then hang/crash ...

DL2RUM wrote:Please test the version below. This should work for the older and for the newest version of Fldigi.

http://dl2rum.de/rumsoft/RUMlogBeta.zip

The test version appears to have fixed the problem I was seeing using Fldigi 3.21.71. I did not test any older versions.

Tnx Tom!

73 Phil NA4M

Dave - I'm not especially interested in the QRZ/HamQTH info per se so I don't use those lookups in Fldigi. I'm interested in finding out if I've got the station in my RUMLog's log along with it's band/DXCC/etc. data. RUMLog popping up that data from QRZ/HamQTH, etc. is secondary for me. 73 Phil NA4M

I installed the latest version of Fldigi 3.21.71 and now RUMLog's Digi > Fldigi - Call Check seems to be broken. It worked fine on earlier Fldigi versions. Now nothing happens when "Fldigi - Call Check" is clicked. I noticed that the maintenance notes for Fldigi 3.21.71 has this that may be related ...

Perhaps I've overlooked this somewhere. Is there a way to change the behavior of the Band Map to lock the red current VFO freq indicator in the center of the window and have the VFO frequency scroll up/down? Always having the VFO indicator in the center of the scale allows easier viewing of stations ...