arcOS Documentation
Introduction to arcOS:
arcOS is a customized Linux distribution, based on Linux Mint (currently version 21.3 "Virginia"). arcOS is a "live" operating system booted from the USB device, meaning no installation to the hard drive is required. When arcOS is booted for the first time, any free space on the USB device is made available as persistent storage. This space (an exFAT partition) is called "ARCOS-DATA". When the system is powered off (or rebooted) any data not saved to this persistent storage will be lost.
System Requirements:
- Intel or AMD 64-bit processor (arcOS will NOT run on ARM devices like the Raspberry Pi)
- 4GB+ RAM (8GB+ recommended)
USB Device Requirements:
- 8GB+ capacity (arcOS will occupy ~4GB, with the rest available as persistent storage
- USB 3.0 strongly recommended
- All USB storage devices will fail eventually. Use a reputable brand, and backup any important data regularly.
- Here are a few that have been tested with good results:
Computer-to-Radio Interface:
- arcOS is optimized for "out of the box" use with the simple and affordable Digirig device.
GPS Devices:
arcOS works with nearly any USB GPS device. Here are some affordable and tested options:
*As an Amazon Associate I earn from qualifying purchases made using the above links. However, I will not recommend products I have not personally tested.
Quick Start Guide:
ISO files are hosted at SourceForge.net
Once you've obtained a copy of arcOS, verify the MD5 checksum of the ISO to ensure the file is not corrupted.
From a Linux system, verify the checksum with the following command:
user@host:~$ md5sum /path/to/downloaded/iso/file.iso
*The above is an example only. Replace the path appropriately.
From a Windows system, verify the checksum with the following command:
Open the Windows command line. Press Windows + R, type "cmd" and press Enter.
certutil -hashfile C:\Path\To\Downloaded\ISO\File MD5(Tip: You can drag and drop a folder from Windows Explorer to insert the path.)
*The above is an example only. Replace the path appropriately.
Using an appropriate tool, write the ISO image to the USB drive.
Note: If using Rufus to write the ISO image, be sure to use the "DD" method, with no other changes to the recommended defaults.
For a convenient cross-platform solution, consider using the Raspberry Pi Imager, as it is capable of writing ISO images to disk (even non-RPi images).
Windows Users: Please disable Secure Boot, Fast Startup, and BitLocker (or at least make a note of the recovery key).
Note: Secure Boot setting are in the BIOS. Fast Startup settings must be changed from within Windows.
Enable USB boot devices in the BIOS of the computer. There are many different computer manufacturers, and the keystrokes required at boot time to enter the BIOS settings vary. A quick web search of the manufacturer and model should provide the information needed to gain access (usually, pressing an F1-F12 key).
Once configured to boot from USB devices, save the settings, and power off the computer. Insert the arcOS USB drive, and power on the computer to boot arcOS from the USB drive.
QRV Modules: Are you QRV?
QRV is Amateur Radio shorthand for "Are you ready?/I am ready."
arcOS provides some core QRV modules in the ISO, which are active by default. These core modules provide out-of-the-box configuration and persistence for the included fundamental software.
Community QRV modules in arcOS allow for individuals or groups of operators to configure their digital station for interoperability when needed, and to switch between configurations for differing scenarios with relative ease.
When arcOS starts, the "Station Setup" window appears and, if previously run, the fields will be auto-populated with the same information. When the user confirms the station setup information, arcOS looks at the ARCOS-DATA storage for a directory named "QRV", and will then run any active core and community modules under the directory for the supplied callsign.
QRV modules can be obtained from KG4VDK's Github, and can be kept up to date in arcOS by opening a terminal and running the update-modules command.