THANKS Larry -

For windows, I am using XP Home Pro.

As you said, there are many versions of of Linux out there.  I am using =
Linux Mint - Maya Version 13.  I picked this because it has long term =
support to 2017.  Many of the other versions out there are too =
experimental and do not offer long terms support.  It is set up with a =
dual boot mode, you can pick Windows or Linux.  Once I get all my =
programs running, I will dump windows and do a clean install of Linux.  =
The support for XP terminates on April 8, 2014.

You can order the RS-232 to USB with the FTDI Chip set either as a plug =
or with line from Valley Enterprises - I ordered the plug, see link:

	=
http://www.amazon.com/s/ref=3Dnb_sb_noss?url=3Dme%3DA1UZH0Q8MMO1YX&field-k=
eywords=3Drs-232

Currently, when I check the ports, I get the following:

	bob@linuxmint ~ $ dmesg | grep tty
	[ 0.000000] console [tty0] enabled
	[ 0.303680] serial8250: ttyS0 at I/O 0x3f8 (irq =3D 4) is a =
16550A
	[ 0.496548] 00:0c: ttyS0 at I/O 0x3f8 (irq =3D 4) is a 16550A
	[ 0.532321] 0000:05:01.0: ttyS4 at I/O 0xec00 (irq =3D 17) is a =
16550A
	[ 0.568231] 0000:05:01.0: ttyS5 at I/O 0xe880 (irq =3D 17) is a =
16550A
	[ 17.131609] usb 8-2: cp210x converter now attached to ttyUSB0
	bob@linuxmint ~ $ =20

I have Linux/WinSDR set on tty/S0 Com1, and when I open WinSDR, it says =
it cannot open Comm Port 1. =20

I will update after I get the plug.

Bob Hancock

On Jul 15, 2013, at 11:39 PM, Larry Cochrane  =
wrote:

> Hi Bob,
>=20
> Lets keep this on the PSN list so others can learn how to run WinSDR =
and WinQuake on Linux/Wine. What version of Linux are you using? One of =
my main problems with Linux is there are too many Linux distribution out =
there...
>=20
> Your problem may be that Nmserial1 may not be the hardware com port on =
your system or you have a permission problem. You may need to try other =
device numbers or names. One thing you can try is a USB to RS-232 Serial =
adapter. If you look in your /dev/ directory before and after you plug =
in the device you should see the new USB/Serial device. The new device =
name should then be used in the ln (link) command to let Wine know what =
physical device to use for com1.
>=20
> If you do try a USB to RS-232 adapter you should get one based on the =
FTDI chip set. Adapters, and the Windows/Linux drivers that FTDI have =
available, seem to work pretty well under Windows and Linux.
>=20
> Regards,
> Larry Cochrane
> Redwood City, PSN
>=20
>=20
> On 7/14/2013 3:35 PM, Bob Hancock wrote:
>> Hi Larry -
>>=20
>> THANKS for everything - I am experiencing a few problems, mainly I am =
unable to get the com port open..  I have an old Version 1 data logger =
and its connected to the computer through a serial port (DB9).  I took a =
look at WinSdr and following is what is says for com port:
>>=20
>> 	Com - 4\Device\Nmserial1
>>=20
>> I need to understand UNIX more and right now that is my Achilles =
heal.
>>=20
>> Don't worry, I am not giving up - I just need to educate myself in =
this are.
>>=20
>> Thanks Again for everything
>>=20
>> Bob
>>=20
>>=20
> __________________________________________________________
>=20
> Public Seismic Network Mailing List (PSNLIST)
>=20
> To leave this list email PSNLIST-REQUEST@.............. with the body =
of the message (first line only): unsubscribe
> See http://www.seismicnet.com/maillist.html for more information.
>=20

	http://www.amazon.com/s/ref=3Dnb_sb_noss?url=
=3Dme%3DA1UZH0Q8MMO1YX&field-keywords=3Drs-232

Currently, when I check the ports, I get the =
following:

	bob@linuxmint ~ $ dmesg | grep =
tty
=09
=09
	
	[    0.000000] console [tty0] =
enabled=20
	[    0.303680] serial8250: ttyS0 =
at I/O
0x3f8 (irq =3D 4) is a 16550A=20
	[    0.496548] 00:0c: ttyS0 at =
I/O
0x3f8 (irq =3D 4) is a 16550A=20
	[    0.532321] 0000:05:01.0: =
ttyS4 at
I/O 0xec00 (irq =3D 17) is a 16550A=20
	[    0.568231] 0000:05:01.0: =
ttyS5 at
I/O 0xe880 (irq =3D 17) is a 16550A=20
	[   17.131609] usb 8-2: cp210x
converter now attached to ttyUSB0
	=
bob@linuxmint ~ $  

I have =
Linux/WinSDR set on tty/S0 Com1, and when I open WinSDR, it says it =
cannot open Comm Port 1.  

I will update =
after I get the plug.

Bob =
Hancock

On Jul 15, 2013, at 11:39 PM, Larry Cochrane =
<lcochrane@..............> =
wrote:

Hi Bob,

Lets keep this on the PSN list so others =
can learn how to run WinSDR and WinQuake on Linux/Wine. What version of =
Linux are you using? One of my main problems with Linux is there are too =
many Linux distribution out there...

Your problem may be that =
Nmserial1 may not be the hardware com port on your system or you have a =
permission problem. You may need to try other device numbers or names. =
One thing you can try is a USB to RS-232 Serial adapter. If you look in =
your /dev/ directory before and after you plug in the device you should =
see the new USB/Serial device. The new device name should then be used =
in the ln (link) command to let Wine know what physical device to use =
for com1.

If you do try a USB to RS-232 adapter you should get =
one based on the FTDI chip set. Adapters, and the Windows/Linux drivers =
that FTDI have available, seem to work pretty well under Windows and =
Linux.

Regards,
Larry Cochrane
Redwood City, =
PSN


On 7/14/2013 3:35 PM, Bob Hancock wrote:
Hi Larry -

THANKS for everything - I am =
experiencing a few problems, mainly I am unable to get the com port =
open..  I have an old Version 1 data logger and its connected to =
the computer through a serial port (DB9).  I took a look at WinSdr =
and following is what is says for com port:

	Com - =
4\Device\Nmserial1

I need to understand UNIX more and right now =
that is my Achilles heal.

Don't worry, I am not giving up - I =
just need to educate myself in this are.

Thanks Again for =
everything

Bob


____________________________=
______________________________

Public Seismic Network Mailing =
List (PSNLIST)

To leave this list email PSNLIST-REQUEST@............
COM with the body of the message (first line only): =
unsubscribe
See http://www.seismicnet.com=
/maillist.html for more =
information.


=