On 18 Sep 99 at 15:04, Jan Wasserbauer wrote:
> Jose Angel Amador Fundora <[EMAIL PROTECTED]> wrote:
> > I once made it work with ax25-utils, but that disk crashed and I have
> > not been able to do it again. It makes changes in the kernel sources
> > when you want to include kernel ax25 support.
> Changes to kernel ? I have never noticed such thing. The original ax25 code in
> TNT had never heard about 2.2.12 kernel which I use :)
I am still using 2.0.36 on a 486DX2. I got afraid of instabilities
and decided to stick to what is known to work well until all the ham
stuff works OK again. Then, I will jump in when the important stuff
stops giving headaches. I am watching...
> Have you tried "./configure --enable-ax25k" again ?
Yes. It exits on error when I make TNT again. I do not have a copy
of the error messages right now.
> BTW: What TNT version ?
Version 1.8. Once ran OK.
> Version 1.8 did compile without problems with axutils (on 2.0.x system).
>
> > One problem I found with TNT is that I could not change radio ports,
> > it forced me to one port, and I have two TNC's plus a software link
> > port where JNOS talks to FBB and viceversa in the same machine. It
> > should work via different selectable ports.
> That is simple - just use :c port_name:call (":c test:N0DE")
Hmmmm, I see. I am not used to insert : , I just used c port_name call
Old BPQ and JNOS usual way to do it....
> > I have not reloaded kernel sources. I have made slight changes to
> > ax25 kernel code and I would have to redo it all. It doesn't seem a
> > proper behavior from TNT.
> TNT is user software and IMHO it should compile and run without
> any need for root permissions. Modifying kernel doesn't seem a
> proper behaviour to me too. But as I said - I have never seen TNT
> to do that.
I have been quite busy. On August 17 thunder damaged CO9BQQ, and I
am the sysop. Yesterday, thunder damaged my FT757's CAT (I run
pactor on HF) and who knows what else....I will recompile TNT and
post the results. But I am afraid that staying behind with an old
kernel will not be interesting to many people, including the
developers...even when 2.0.36 works well.
> > I like the way it looks and what it offers, but I have had little
> > time to enjoy it. I wanted to try its YappC capabilities, but I have
> > not been able to.
> I like TOP (The Other Packet) DOS terminal and TNT is a bit different but I'm
> getting used to it. What I found most annoying is that TNT can't save
> backscroll-buffers on exit and sometimes I loose important information
> someone wrote me.
My preferences for a third program come from long, since I ran MSDOS.
FBB is a good server, but not a good sysop client. JNOS does not have
Yapp and never will. I used an argentinian program, Thunder, (under
MSDOS) that had only one stream, but had a lovely YappC download
capability, resume included. FBB as sysop client, does not resume
(maybe it does and I still have not found out) and "call" (Linux
terminal provided with ax25-utils) works well but does not resume
either. And if I would like to move something in from a users's PMS
(Winpacks and Tsthosts), it would be nice to count on a friendly
YappC terminal that does resume, and I was looking for that on TNT.
And I still don't know if it does what I am looking after.
73 de Jose, CO2JA
---
Ing. Jose A. Amador | Telf: (537) 20-7814
Depto de Telecomunicaciones | E-Mail: [EMAIL PROTECTED]
ISPJAE |
