![]() Hopefully, taking a look at the guide may help resolve your situation. While the guide is based on using MacLogger as the controller, there is a quite parallel configuration with how RUMlogNG should be configured (if memory serves me right!). localhost, or 127.0.0.1) or a broadcast address like 192.168.1.255 to provide information in the whole LAN. RUMlog is a shortwave logging and QSL handling/printing tool. ![]() The entered address or hostname has to ensure, RUMlog can be reached in the LAN. GEDitCOM II is a genealogy application for MacOS X that sets the standard for ease-of-use. That was done with the hope that getting it all documented may help someone else at a later date - I had a hard time with some of the integration in getting certain aspects to work, but finally was able to resolve problems and get it all working right. For use with RUMLog, just the settings on the left hand side are required. jamfHelper/Library/Application Support/JAMF/bin/jamfHelper.app/Contents/MacOS/jamfHelper. The document was created documenting how MacLogger, WSJT-X, and fldigi were successfully integrated. rumloglogPath/AdobeRUMUpdatesLog.log mmmmmm, rum log. I have a previous post on this and you can find it here, Ham Radio iMac (iCOM Macintosh) In The Shack. The "Mac-Based Amateur Radio Digital Applications - Installation and Integration" guide is there to view and/or download. Unlike the software developed for Windows system, most of the applications installed in Mac OS X generally can be removed with relative ease. RUMLogNG is a free logging program for the MacOS. Please take a look at my website, and in particular the "Mac Amateur Radio Digital Applications" page at. That is done without using JT-Bridge or any other application too. In my Mac-based situation, MacLogger controls the session when either WSJT-X or fldigi are "up" and running. John- I did have WSJT-X and fldigi successfully integrated with RUMlogNG for about 4-6 months, but returned back to using MacLogger several years ago.
0 Comments
Leave a Reply. |