linux
APRSIS on Linux
APRSISce/32 is a Windows 32-bit application. From here on it will be referred to as APRSIS32 (since the Windows 32-bit version is what is being installed.

There are 2 methods of install APRSIS32 under Linux:

  • 1. Using WINE – Wine lets you run Windows software on other operating systems.
    With Wine, you can install and run these applications just like you would in Windows.
  • 2. Using a Virtual Environment – A Virtual Environment is an application that allows an entire virtual computer within an existing computer.
    In covering each of these options, the assumption will be that you already have the base (WINE or Virtual environment) setup and functional. For specifics on installing either (or both), do a search on the subject and you should find plenty of information. In either case, I recommend the latest stable version be installed from the start.
  • Using WINE:
    Since APRSIS32 is a single executable file, the steps of getting it running are pretty straight forward – run the application. The keys to getting it 'functional' under Linux are in getting LINUX to allow WINE to talk with hardware properly. In this case that would be serial ports.

WINE provides a direct connection to the installed network card install, so there is no special setup to gain access to the map tiles or APRS-IS servers.

I am using WINE 1.2.2 (1.2.3 is the latest stable version as of Nov 1, 2011).
For greater compatibility, you can try CrossOver by CodeWeavers.

The WINE install creates a directory which is basically the Windows C: drive. You can work within that directory from within WINE (Windows style tools) or from within Linux (Linux tools). Each has advantages and disadvantages. Keep in mind that Linux is case sensitive (where Windows is typically not) and therefore WINE somewhat also.
Direct: ~/.wine/drive_c this is equal to C: in Windows
WINE: c: this is actually a link to the above
NOTE: '~' means your home directory on Linux.
There is a DOT before the word wine → that's important!
Steps fro Install:Create Directory for APRSIS32 and its supporting files.
I tend to create an applications directory for my applications with subdirectories:

Direct: mkdir ~/.wine/drive_c/myapps
mkdir ~/.wine/drive_c/myapps/aprsis32

  • WINE: _

From your desktop you must pick the Wine menu
> Application > Browse C: Drive {This is like WinFile}
>right-click > create a directory {same old Windows drill}

Now I have the location where APRSIS32 will work from – the working directory,

Copy APRS32.exe to the directory you created and change it to executable (see Linux info on chmod command).
Running from here should provide non-RF access just as in Windows.
You should be able to follow the APRSIS32 wiki and connect to an APRS-IS server.

Create a shortcut in your Linux menu to application
The command line for APRSIS32 would be
wine ~/.wine/myapps/aprsis32/APRSIS32.exe
or I had to use xdg-open .wine/dosdevices/c:/myapps/aprsis32/aprsis32.exe
again – case sensitive!

  • HARDWARE:
    Now let's setup the connections to ports for RF access.

Windows refers to serial ports as COM#. Linux refers to them as ttyS# or ttyUSB# under the /dev directory. You access the device as a file in the /dev directory . Since WINE needs access from a specific directory, you create a link to the /dev/{device} you want to access. This requires a 'unique link' for each port number that you want to connect to. To create a functional link that WNIE can use:
ln -s /dev/ttyS0 ~/.wine/dosdevices/com1
ln -s /dev/ttyUSB0 ~/.wine/dosdevices/com2
The first link command is to the FIRST physical serial port (typically 9-pin D-sub) and the second link command is to the FIRST USB to com port. NOTE the device numbering starts at ZERO.

CATCH: USB devices are dynamic and can change. I have experienced a USB to Serial device that hangs and Linux does some sort of retry which may cause the number to change. Since each 'brand' of Linux has different ways of resolving this (UDEV for example), you should consult your brand for details.

Some versions of WINE require a Windows Registry entry to map the files to the comm ports

The Windows Registry is a simple text file. You can edit the file and search to see if you need to add the description. More info at Wine Registry.

The file to modify can be found using the WINE
> Application > Browse C: Drive {This is like WinFile}
open the windows directory
find regedit.exe
This may help your see if the info is there, but I recommend using a text editor to
add the required lines in the text file as described below:

> Application > Browse C: Drive {This is like WinFile}
Then go back 2 directories to .wine
or ~/.wine

the file name is system.reg. Copy and past the lines below (corrected for your ports)
[HARDWARE\\DEVICEMAP\\SERIALCOMM]
"COM1"="COM1"
"COM2"="COM2"

I added them to the top (and yes with quotes).

Your user name needs to be added to the dialout group in Linux to gain access to the hardware.

This can be done through the 'USER and GROUPS' which is usually found in the 'Administration' menu (recommended method). Just go to 'Manage Groups', choose the dialout group and make sure the check box next to your username is checked.

You can also edit the /etc/group file as root (or sudo) with a text editor and manually add your user name at the end of the line:
dialout:x:20:{your user name here}

Good Luck!
73 KB8RCO

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License