[nos-bbs] Cross posting: [Fwd: [wl2kemcomm] Heads up...]

[Demetre Valaris]

Hi Maiko,

> -----Original Message-----
> From: nos-bbs-bounces at lists.tapr.org 
> [mailto:nos-bbs-bounces at lists.tapr.org] On Behalf Of maiko at pcs.mb.ca
> Sent: Tuesday, July 05, 2005 6:56 PM
> To: TAPR xNOS Mailing List
> Subject: Re: [nos-bbs] Cross posting: [Fwd: [wl2kemcomm] Heads up...]
> 
> 
> 
> > Interesting timing ?
> 
> I won't look into it too heavily ... The WinLink guys are 
> simply making improvements to their system, just like 
> everyone else does ...
> 
> > From the interoperability perspective, this seems like a new bogey ?
> 
> Why ? I have no idea what the port is for, I'm not part of 
> the WinLink development team. I'm sure they have a reason for 
> it, to make their system more redundant. I wouldn't 
> necessarily call this a bogey.
> 
> Guys, let's be clear. I have no problem with WinLink as far 
> as the software is concerned. Targetting the windows 
> environment is smart of them, let's give them that much 
> credit. Look how it's grown.

Neither has anyone here I believe. It is the attitude of some of the
developers
that bother me. First of all they think they know it all and second they
want
to impose their ideas only. For a start they started banning PACTOR I
from 
PMBOs and they tend towards using PACTOR III only in some. This is not
very good thinking. Also they try to promote the one and only client
"Airmail",
they do not allow anyone using the keyboard to send e-mail on HF and
they 
do not like anyone using the keyboard to send e-mail via a TELPAC node
either. 
They say that "keyboarding" is bad and it is only accepted for test
purposes
on the TELPAC and it is not allowed on HF.

> 
> I want very much to target the windows environment as well, 
> but the nature of the applications will be like that of the 
> KLMproxy project, allowing windows applications to use a 
> packet radio connection as a tunnel to other services (via a 
> NOS server).

We all use Windows and we do not have any problems with windows. I 
personally have problems when there is no otjher way to do something and

I am tied to a Windows only system, that is why I like JNOS, because 
you are not tied to one and only system.

> 
> If people want to use NOS, they need to have a love for 
> Linux, or the DOS platform (which is still supported in a 
> limited way). Apparently the DOS userbase is higher than I 
> thought too, but I have no numbers :-(
> 
> IF people want to set up the equivalent of a 'Telpac' type of 
> node using JNOS, then they will have to do it on a linux or 
> DOS machine, the latter requiring a network card packet 
> driver (TSR). I ran a system like that for years, ending 
> 2000. Don't laugh ! It worked very well, with uptimes well 
> over a month most of the time.
> 

Well I have done the same exactly Maiko and had one DOS computer
running JNOS as a router and the other running JNOS as an SMTP/POP/
FTP etc SERVER. No problems with this setup. I still use JNOS in
my HP200LX palmtop (it can work 20 hours in 2 X AA Alkiline cells not
just 2 hours like most LAPTOPS).

> If people do not want to use linux or dos, and windows is 
> what they feel most comfortable with, then so be it. They can 
> use the WinLink Telpac node software as an introduction to the hobby.
> 

Finally about TELPAC. It can run in JNOS by just altering the
AUTOECE.NOS
and setting up an alias with the following commands:

mbox alias TELPAC "t PMBOIpAddress 12001"
mbox showalias on

Each time a user connects to JNOS he can type TELPAC, hit ENTER and he 
is connected to a Winlink PMBO. We can have many aliases or someone can
think of a way to try many PMBOs in a rotational basis should the first
one in the
list fail to reply.

Another way is the use DL5DI's TELPAC node in LINUX if you are using
AX25 in the
LINUX kernel. It is dead easy to install but it does nothing else. It
just connects you to
a WINLINK 2000 PMBO.

> Maiko Langelaar / VE4KLM

===
73 de Demetre Valaris - SV1UY
e-mail  sv1uy at ham.depa.gr
webpage http://www.athnet.ampr.org/~sv1uy
        http://sv1uy.ampr.org/~sv1uy
SSTV_RX http://sv1uy.ampr.org/~sv1uy/sstv_rx.html