by n1ho » Fri 17. Feb 2012, 20:02
I'm a newbie to Mac OS X and RUMlog/RUMped - I just migrated from Linux, so I am slightly familiar with *NIX stuff, but not with OS X. I have a mid-2011 iMac and Mac OS X 10.7.3 (Lion, with last week's update).
I "installed" RUMlog-4.9 a couple of weeks ago, and things seem to be running smoothly.
However, I just installed RUMped yesterday, and when I did, realized that I hadn't install RUMlog properly. I used Finder
to move both apps to "Applications". Both applications now show up on my Launchpad screen (along with the other applications that I've already installed, such as fldigi), and each will start up, EXCEPT:
RUMlog claims, via a pop-up window "Can't connect to database 'DXCC.rsd'!" and
RUMped claims the same thing AND that "'CallMaster.rsd' not found!" and "Can't open DXCC Data File!"
At one point, while trying to troubleshoot this, using EditDXCC (which I used a few days ago to add KG4KL to KG4), I managed to destroy the DXCC and CQ Zone columns of my primary database. While I only have about 90 QSOs logged under RUMlog, I'm a little bit discouraged.
The files seem to be there - I initially installed everything in /Users/n1ho/ham-radio/rumsoft, with each application in its
own directory (RUMlog-4.9 and "RUMped 3.1.8") under rumsoft and have my log files (e.g., LHPRUMlog2012.rsd) in the 'rumsoft' directory.
I haven't created a log file under RUMped yet. I'm rather confused as to exactly where all of the application files "live" and
what might have been moved when I "installed" them. The DXCC.rsd file permissions seem to be ok (644@), the RUMlog-4.9 directory entry in .../rumsoft is drwxrwxrwx@ but RUMped's is drwxr-xr-x@ although it's unclear to me if group and work write permissions would be needed - I didn't change them - so that may not be relevant. Is there another directory where I should look for these application files? If I need to re-install these two apps, how can I be sure that I've properly destroyed the old bits before I install the new ones? (In Linux, most distributions have "package managers" of one type or another which seem to handle this sort of situation gracefully, and I'm not sure what the paradigm under Mac OS X is yet, which is why I'm quite confused!)
Thank you and 73,
Brandy, N1HO