[aprssig] Before You Install Windows 10 (Or even if you don't want to) Read This

Lynn W. Deffenbaugh (Mr) ldeffenb at homeside.to
Fri Sep 18 09:19:51 CDT 2015


>From http://aprsisce.wikidot.com/doc:linux (contributed by KB8RCO):

>   * *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 <http://wiki.jswindle.com/index.php/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}
>


Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 9/18/2015 8:57 AM, Randy Allen via aprssig wrote:
> I tried this a few years ago using Mint, but was never able to 
> establish a link between Wine and a com port to connect to my MFJ 1270 
> TNC.  The internet connection worked fine, but I want an RF tool, not 
> another internet only appliance in the shack.  To me APRS-IS 
> functionality is a secondary and not a critical feature.
>
> It's been a few years and I realize I don't have details here, but is 
> there someplace with a simple step by step in connecting to com ports 
> through Wine?
>
> On 9/18/2015 00:29, Greg D via aprssig wrote:
>> +1
>>
>> Been using it this way for several years on my OpenSuSE Linux machines.
>>
>> Greg  KO6TH
>>
>>
>> Lynn W. Deffenbaugh (Mr) via aprssig wrote:
>>>
>>> Oh, and APRSISCE/32 runs just fine under Wine.  See:
>>>
>>> http://aprsisce.wikidot.com/doc:linux
>>
>> _______________________________________________
>> aprssig mailing list
>> aprssig at tapr.org
>> http://www.tapr.org/mailman/listinfo/aprssig
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20150918/cd227931/attachment.html>


More information about the aprssig mailing list