Page 1 of 1

"Resolution to high..." v5.3.10

Posted: Mon 9. Feb 2015, 02:26
by KM6NY
I've had good success with v5.3.10 and only once before did I get the "Resolution too high, decrease your resolution, ok" button endless-loop. My previous fix was to de-install and re-install making a new log for the logfile.rsd, then importing my backup contacts.

My problem is that I'm still getting the endless loop error "Resolution must be decreased OK" - after clicking on "OK" the same message instantly pops up again.
RUMLOGERR.tiff
RUMLOGERR.tiff (40.93 KiB) Viewed 3627 times
RUMLOGERR.tiff
RUMLOGERR.tiff (40.93 KiB) Viewed 3627 times
I have to kill the app. Is there a fix for this? Something I need to adjust? Unfortunately, until this is fixed, I can not use RumLog for any contacts :(

-Jose
KM6NY

Re: "Resolution to high..." v5.3.10

Posted: Mon 9. Feb 2015, 10:46
by DL2RUM
Unfortunately, this is an always returning problem. I run into the same trap for few weeks ago and I made some changes. Try this version: http://dl2rum.de/rumsoft/RUMlogApp.zip

Other helpful tips, which may be help or not:

Set your trx to the 30m band before you start RUMlog
Use the Terminal and enter the lines below, one by one, followed by an Enter:
defaults write RumLogOwn PpkIndexMasterOnBand_0 0
defaults write RumLogOwn PpkIndexMasterOnBand_1 0
defaults write RumLogOwn PpkIndexMasterOnBand_2 0
defaults write RumLogOwn PpkIndexMasterOnBand_3 0
defaults write RumLogOwn PpkIndexMasterOnBand_4 0
defaults write RumLogOwn PpkIndexMasterOnBand_5 0
defaults write RumLogOwn PpkIndexMasterOnBand_6 0
defaults write RumLogOwn PpkIndexMasterOnBand_7 0
defaults write RumLogOwn PpkIndexMasterOnBand_8 0
defaults write RumLogOwn PpkIndexMasterOnBand_9 0
defaults write RumLogOwn PpkIndexMasterOnBand_10 0
defaults write RumLogOwn PpkIndexMasterOnBand_11 0

When nothing helps, you have to delete the RUMlog preferences file in your Home folder: ~/library/preferences/RumLogOwn.plist.

Re: "Resolution to high..." v5.3.10

Posted: Mon 9. Feb 2015, 22:48
by KM6NY
Thank you. Yes, using the "RUMLogAPP" v5.3.11 appears to have fixed this problem.

If I use the other features (I only use this only for straight logging only with LoTW and ADIF exports), I'll try the rest.

Thanks again :)

Jose,
KM6NY
73