On 6/25/10 6:01 AM, "Dave Freese W1HKJ" <[email protected]> wrote:
>> >> I only have one fldigi_def.xml in my .fldigi folder and I assume both >> versions use the same file. I do not try to run them at the same time. >> > I strongly suggest that you do not use the same fldigi_def.xml file for > both the alpha and production executables. Every attempt is made to > insure compatibility between the two but no guarantees can be made. This is the first time I have ever seen a real incompatibility. I am not sure how to maintain two versions of the fldigi_def.xml file. Having to start over with a new fldigi_def.xml fie for each revision is a pain to reset the fonts, logs etc. The Wizard for new users only does very basic stuff. I have to remember and reset my fonts and preferred waterfall settings. >> When I suspected a bad fldigi_def.xml, I used a known good backup. It >> works fine with the alpha but for some reason 3.20.17 has a mind of its >> own and may not read the file or write to it. >> >> Something strange is going on and that may have caused the rig control >> to go south >> >> When you start 3.20.17, does it come up in THOR 5 or your last saved mode? >> > If you saved a configuration in 3.21.0AF and then started 3.20.17 you > can expect that the last saved mode will not be correct. That is > because new modes (WEFAX) have been added to 3.21.0AF. That causes a > translation in the mode tables. Then there is something wrong with the tables. I probably need to trash 3.21.0AF and wait for the next alpha release. Like Windows, I don't do WEFAX and that seems to be the only item excluded from the 3.20.17 release. I am starting over with 3.20.17 as a new user and it came up with THOR as the default; however, this time I was able to set to RTTY and it was saved to the fldigi_def.xml file. I am not sure WEFAX is worth all these problems. Dick _______________________________________________ fldigi-alpha mailing list [email protected] https://lists.berlios.de/mailman/listinfo/fldigi-alpha
