The next step in upgrading my access to Winlink 2000 was to try to get the new client software (RMS Express) to run in the computer that follows me in every trip: the MacBook Pro (Retina, 15-inch, Late 2013).
I decided to follow the steps outlined October 2014 by Andrew N4AWL (http://n4awl.com/how-to-setup-rms-express-on-os-x-apple/) and use “CrossOver” from “CodeWeavers” (and thus avoid having to install Windows in the Apple). However, in the last year, the version of Crossover had evolved from v. 13.0 to v. 14.0; Microsoft .NET Framework, from 3.5 to 4; and RMS Express for Windows, from v. 18.104.22.168 to v. 22.214.171.124. Only VOACAP latest version was still v. 12.0722. Also my MacBook Pro is running OS X v. 10.10.5 (Yosemite) instead of OS X v. 10.9.4 (Mavericks) used a year ago by Andrew.
I decided to download the latest versions whenever possible and had little difficult in installing CrossOver. Following the indication in the RMS Express page (http://www.winlink.org/RMSExpress) that “Windows XP is not supported”, I created the initial CrossOver Bottle as Windows 7, and installed the latest Microsoft .NET Framework 4. Then, after installing the newest version of RMS Express I followed all the steps as outlined by Andrew. RMS did run at first try and I was able to configure it as required. However, although it did connect via Telnet to a CMS server, no exchanges took place after the initial handshake. I suspected the Firewall in the Apple until I found out that newer versions of Windows had shipped with the Telnet Client disabled. I knew how to enable it in Windows using the Control Panel, but was unable to find a way to achieve that within CrossOver.
Hence I decided to retry the entire installation sticking as close as possible to Andrew’s steps: I created a Windows XP Bottle, installed inside it the Microsoft .NET Framework 3.5 Service Pack 1, RMS Express and the ITSHFBC propagation software. I was immediately rewarded by being able to send test messages from RMS Express via Telnet (via the CMS in Perth, Australia – see below) to both my Gmail and Yahoo e-mail addresses and, similarly, to receive the replies from these addresses (this time via the CMS in Halifax, NS):
*** Connecting to a CMS…
*** Connected to Perth
Perth CMS >
; WL2K DE VA3PCJ (FN25EJ)
FC EM MZYMPDZKW5D0 204 185 0
*** Sending MZYMPDZKW5D0.
*** Completed send of message MZYMPDZKW5D0
*** Sent 1 message. Bytes: 207, Time: 00:00, bytes/minute: 20725
*** — End of session —
*** Total bytes sent: 207, Time: 00:06, bytes/minute: 1912
*** Total bytes received: 0, Total session time: 00:06, bytes/minute: 0
Next step will be to bring the Elecraft KX3 into the equation and to get RMS Express to interface with it via an external sound card.
Note added 2015/09/15 18:41z
On the problem of how to enable Telnet in a CrossOver “Bottle” configured as Windows 7, this is what the Codeweavers “Guru” had to say:
“It sounds like the application works in a WinXP bottle correct? If so I would suggest just using a WinXP bottle as that is the default setting and has the best compatibility for most applications in Crossover.”
In other words: “if it ain’t broke…”