Page 2 of 2
Re: FT-950 Support
Posted: Wed 24. Nov 2010, 16:02
by M0JEK
No, no special characters. I will see if I can have a further look this evening, and see if I can try and trace the strangeness. Just a thought. Do think nuking the database(s) and rebuilding afresh from scratch, i.e. a new RUMped install might help?
Re: FT-950 Support
Posted: Wed 24. Nov 2010, 16:39
by DL2RUM
No!
The problem must be within the plist file.
Re: FT-950 Support - plist troubles
Posted: Thu 25. Nov 2010, 07:38
by M0JEK
Last night I wasn't able to do much poking around with RUMped, however I am not sure if this proves anything, but I notice that Property List Editor can't open RumDX.plist. It shows the following error, but if I check the file I don't see any obvious problems with the file.
The document "RumDX.plist" could not be opened.
Re: FT-950 Support
Posted: Thu 25. Nov 2010, 11:45
by DL2RUM
Yes, I know. Even on 10.6 I can't open it in the Property List Editor. This
should not be the problem.

- Error.tiff (30.24 KiB) Viewed 7366 times

- Error.tiff (30.24 KiB) Viewed 7366 times
To make sure this is not the problem, open the plist file in a text editor and search for the complained "&" and delete it. I use this in the keyword "S&P" (It will be reappear again while quitting RUMped.)
Re: FT-950 Support
Posted: Fri 26. Nov 2010, 00:23
by M0JEK
Behaves as you expected , Tom. Removing the '&' from the file allows it to be opened by the plist editor.
Anyway, still can't get Beta 37 to work but Beta 30 is still fine. It is late here, I will have to look at this another day. Thanks for the help effort so far.
All I can think now, is to grab the build tree from you and see what it does if compiled on 10.4, but like you say ... there really is no reason why Beta 37 is not working.
Re: FT-950 Support
Posted: Wed 12. Jan 2011, 12:43
by M0JEK
Hi Tom,
I have an update w.r.t the strange problems with the preferences file, etc. Well, it is all working now, and I am using Beta 39. What I needed to do was to create a new fresh log and all seems to be working now. I have removed all the older problem logs from the database, just incase I accidently use one and the problem returns.