开云体育

Built and runs OK, but ...

a)??? Not sure where the new font choices appear, I can't see anything new listed in the config font menu choices relating specifically to RTTY.

That, and more worryingly...

b)??? The new .27 alpha, has wiped out my pre-existing macro configurations and log's!....

I had backups, so copied them back into the default .Fldigi folder structure (as I had to do for .26) and ran it again.? Same result, logs etc are empty (it appears to write new blank/default files without checking first it seems.)

Past alpha (pre .26) updates didn't have this issue, but .26 and .27 do it seems.? .27 with a vengeance it seems!

OS:??? LMDE 6 64bit, on 4 core intel with 8G RAM.? All up-to-date.

73.

Dave G0WBX

开云体育

Hi again.

OK, I've tried every which way and then some.

I can get the new .07 alpha to restore my station and operator details, the view window layout (including the "show all 48 macros" setting) etc.

But it still flatly refuses to use any pre existing macro definition file, or accumulated Log data file?

And yes, I know Linux is case sensitive.? Ive been copying the needed files "as is" between backup folders and the same location(s) in the new .fldigi folder tree.? (That the new .07 does create.? And I think that is the problem, it creates new, overwriting what was there.)

What do you need from me to debug this?

Or...? What specific instructions do you have to install an alpha, but retain the pre-existing settings and logs etc.

73.

Dave G0WBX.

开云体育

Hi Dave.

Not seeing the accumulated logs (and a lot of other problems) maybe a result of that change some years ago to use $HOME/.fldigi/.fldigi when it was previously just $HOME/.fldigi

eg my older installation in $HOME/.fldigi/fldigi.prefs defines the macro files as;

last_macro_file:/home/xxxx/.fldigi/macros/macros.mdf

Whereas some experimental configs add an extra "'.fldigi". eg

last_macro_file:/home/xxxx/.fldigi.experimental/.fldigi/macros/macros.mdf

(The .nbems directory also gets put in the later .fldigi structure)

Also check fldigi_def.xml for every reference to a file/directory location, that is valid for your installation. Mine for example are;
<THOR_AVATAR_IMAGE_FILE>/home/xxxx/.fldigi/avatars/vk2yqa.png</THOR_AVATAR_IMAGE_FILE>
<CTYDAT_PATHNAME>/home/xxxx/.fldigi/</CTYDAT_PATHNAME>
<XMLRIGFILENAME>/home/xxxx/.fldigi/rigs/IC-9100-D.xml</XMLRIGFILENAME>
<LOGBOOKFILENAME>/home/xxxx/.fldigi/logs/logbook.adif</LOGBOOKFILENAME>
<WEFAXSAVEDIR>/home/xxxx/.fldigi/wefax/</WEFAXSAVEDIR>
<KML_SAVE_DIR>/home/xxxx/.fldigi/kml/</KML_SAVE_DIR>
<AUTO_PROG3_PATHNAME>/home/xxxx/bin/logsn3</AUTO_PROG3_PATHNAME>

Oh and make sure you haven't merged an old and new tree together. There would normally be nothing except .fldigi and .nbems directories within the newer $HOME/.fldigi one. Any mixing might explain the lack of logfile visibility too.

As an in initial check in a shell box, cd to the directory you want to check and;

find . -print

Then post the output here along with fldigi.prefs and fldigi_def.xml. Check that there is only one file of that name in your tree. (Pls verify nothing personal/private gets posted)

Hope this makes sense!

Cheers Bob VK2YQA