This is always my first suggestion: Backup and then delete your fldigi configuration directory. Now try running fldigi again. Let us know how it works. On Tue, Feb 14, 2012 at 07:13:39AM -0600, Bernard Dekok wrote: > I get the flDigi lockup on my little Acer Netbook client all the time > recently. (Not previously.) > Could be memory related, but I doubt it. > Could be RF in the system, maybe..., but testing with low power into a > dummy load, so doubt that too. > > flDigi on my server has been running fine from the gitgo. > > Will investigate the setup differences between the two flDigis and report > on your spreadsheet. > > KC9SGV > > > On Tue, Feb 14, 2012 at 3:35 AM, Rein Couperus <rein@xxxxxxxxxxxx> wrote: > > > Very nice initiative, this is my main pain in the butt.... > > Have to restart PI4TUE 2x a day... > > > > Rein EA/PA0R/M > > > > > > >Hi all, > > > > > >This is an old subject but it seems some are still experiencing lockups. > > >I tried to find the cause earlier and got as far as pointing the finger > > >at rigcat (that part handles ptt and is used even if not selected). I > > >then had a patch on fldigi to try to log more during the next crash but > > >it never came.. What I did find earlier was that it happened during ptt > > >on/off and could be related to frequency change during those events. As > > >some still have to restart fldigi now and then I figured we could > > >perhaps find something in common if we gather some more data about the > > >servers with issues. Its a longshot but could be interesting anyway. I > > >put a simple spreadsheet here: > > >http://bit.ly/AeKwmx > > > > > >You are all welcome to add details to that spreadsheet if you wish, > > >perhaps we can see something that helps thack this issue? > > > > > >73 de Per, sm0rwo > > > > > > > > > -- Larry Levesque www.surrycomputerservices.com