Download / Install

Ready to Copy - ARRL National Traffic System - Message Management
Copyright 2014 - D. Lane Kendall WK4WC


The current version of Ready To Copy is 1.7.6 Build 
1510011552 (October 1, 2015)

(The build number can be found on the "About" screen under the main help menu)

See Revision History

RTC is distributed in a Setup executable file. RTC_SETUP_XXX.EXE  (were XXX = Version Number)

Many Anti-Virus programs won't allow an executable file to download. You may need to temporarly disable your Anti-Virus to download RTC_SETUP_XXX.EXE

RTC is also available as a zip file RTC_SETUP_XXX.ZIP from which the EXE file can be extracted. 

Both files are available on the Download RTC Page 

If you decide to use RTC please send an email to so that you can notified of future releases and upgrades. I will not share your email address or try to sell you anything.


For your own peace of mind, as well as mine, I recommend scanning these and all executable files with your favorite virus scanner before running them.

There are no other packages to install and no reliance on external or existing dynamic link library (DLL) files. 

The RTC_SETUP_XXX.EXE works for new installations as well as upgrades from previous versions. 

If you are installing RTC for the first time, setup will install RTC with a set of empty data files. The default installation folder is "C:\Ready_To_Copy" (notice the underscores) but you may select any folder for installation but be sure to select the same folder for subsequent upgrades.

If you are installing an upgrade from a previous version of RTC...

Make sure you make a complete backup of your existing installation before you proceed. 

Also, make sure Ready To Copy is NOT running on your computer when you install.

After the backup is complete, shut down RTC, run Setup.exe and select the folder where the existing version is installed. RTC_SETUP_XXX.EXE will not overwrite your existing data files.

NOTICE: During testing we have noticed that many of the anti-virus programs take a keen interest in the fact that you are downloading an EXE file and many will scan both the RTC_SETUP_XXX.EXE and the RTC.EXE files the first time you run them. As I said earlier please feel free to scan these files with any virus software that makes you feel comfortable.

If you have a problem with download or installation I will do what I can to help. Please email

Revision History

Version 1.7.0 was released to a limited number of "pilot" users. Since that release in July 2014. There have been only minor issues. 

Version 1.7.1 included several minor enhancements and corrections including but not limited to an optional duplicate record detection feature. This new feature is described in the "Navigation" section of this help documentation. 

The major enhancement in RTC 1.7.1 was the installation process using a setup.exe file. The setup also creates an "Uninstall RTC" start menu selection.

Version 1.7.2 also includes several minor corrections and enhancements as well as a new "NTS Reference" tab on the main RTC Radiogram screen. This tab contains references to ARRL numbered radiograms, message precedence, and handling instructions. See the Reference / Web Access section of this help document for details. There are also enhancements to the "Find" screen. See the "Navigation" section of this help document. 

RTC 1.7.2a is a minor change and addresses an issue that was called to my attention by one of the test users. It was not a coding error but a misunderstanding on the part of the programmer. The change applies ONLY to the NTSD features.

RTC 1.7.6 is a major release. The most noticeable changes are to the look and feel of the main radiogram screen with the ability to re-size the main screen and select fonts. For NTSD AirMail 2000 users an automated export to AirMail has been added. For a complete list of changes and upgrades go to What's New in Version 1.7.6

RTC 1.7.6 Build 1508171800 (August 17. 2015) contains a correction to the AirMail 2000 message import routines. Make sure you have this build if you are using the NTSD features.

RTC 1.7.6 Build 1510011552 (October 1, 2015) contains further corrections and changes to the AirMail 2000 message import routines. The changes are required to accomodate minor changes messages on the BPQ32 MBO system. Make sure you have this build if you are using the NTSD features.

RTC 1.7.6 Interim Build 1512011433 (December 1, 2015)  
-Several users reported data loss due to a forced shutdown. RTC will always save data to the database because it writes directly to the database, however the operating system may not. A Force flush was added and should help during a forced shutdown but the best bet is to shut RTC down before you leave your computer. A forced shutdown could still cause data loss.
-Corrected a minor issue with NTSD "TO" when there is no callsign for the receipient.
Make sure you have this build if you are using the NTSD features.
- Add a tab to the RTC to AirMail AutoIT script, limited results but it may prevent an invalid header error in AirMail. 
-RTC can now extract city and state without a zip code
-Message numbers in message index instead of RTC id. (popular demand)
-Reverse the traffic list and station activity buttons on the main screen.
(popular demand)

Operating System Requirement

RTC is does not require a lot of computing power. It has been tested on WindowsXP and Windows7. Given the RTC budget of $0.00 annually I don't have the luxury of a room full of "clean" computers with different operating systems for testing. There is no reason to think it would not work on any Windows based operating system XP or later including Windows8. 

Update August 17 2015 RTC has now been tested on both Windows 8 and Windows 10 with no issues.

Hardware Requirement

Any computer that is with processor speed and enough memory required to run WindowsXP should have no problem running RTC.

Ready To Copy - License Agreement

RTC is free software. The author has made every effort to deliver a high quality product. However, he does not guarantee that the product is free from defects. The software is provided “as is," and you use it at your own risk.

There are no warranties made as to performance, fitness for a particular purpose, or any other warranties whether expressed or implied.

In no event will the author be held liable for any damages arising from the use of this software.