Date: Fri, 6 Aug 93 04:30:05 PDT
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V93 #200
To: tcp-group-digest
TCP-Group Digest Fri, 6 Aug 93 Volume 93 : Issue 200
Today's Topics:
Compileing convers + readline
Ethernet problem
KISS, 9600, and DIGEST
KISS problem?
Kiss Works Fine!
Nos strange behaviour
Running ka9q TCP/IP on HP 95LX
Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
----------------------------------------------------------------------
Date: Thu, 05 Aug 93 13:34:23 CET
From: BARRY TITMARSH <BTITMARS%ESOC.BITNET@vm.gmd.de>
Subject: Compileing convers + readline
To: Fred Baumgarten <DC6IQ@INSU1.ETEC.UNI-KARLSRUHE.DE>,
Ok my problem solved i forgot to read the GCC.FAQ re the adding of
-lbsd in the LDFLAGS when compileing the libreadline support
so all working fine here..
Thanks for the new version of ping pong convers 2.38
Barry
------------------------------
Date: Thu, 05 Aug 93 16:27:25 GMT
From: kf5mg@kf5mg.ampr.org
Subject: Ethernet problem
To: tcp-Group@ucsd.edu
When NOS loads, I get a message that says that my Ethernet card is using
ffffffffff as it's broadcast address or something similar. I don't recall
seing this error message before and now my Card doesn't seem to let NOS talk
to my other two boxes. Anyone know what this message it trying to tell me
and what I need to do to fix it? Thanks.
73's de Jack - kf5mg ( running JNOS in a 735K - OS/2 2.1 Dos Box! )
Internet - kf5mg@kf5mg.ampr.org - 44.28.0.14
AX25net - kf5mg@kf5mg.#dfw.tx.usa.noam - home (817) 488-4386
Worknet - kf5mg@vnet.ibm.com - work (817) 962-4409
-------------------------------------------------------------------------
| "I am Homer of Borg.... Prepare to be assim.... oooo Donuts." |
-------------------------------------------------------------------------
------------------------------
Date: 05 Aug 1993 12:58:31 -0500 (EST)
From: Mike Murphree <mike.murphree@stpete.honeywell.com>
Subject: KISS, 9600, and DIGEST
To: tcp-group@ucsd.edu
Re: KISS
I've seen that behavior before, maybe adding a sequence number to
the frames would prevent duplicate frames from being queued for
transmit... (KISS firmware & NOS changes)
If you want to see a TNC go beserk send out a ping with an interval
of 30 seconds and forget to use the x1000 multiplier... Oh and
be sure to do it on a frequency you don't use often... <G>
Re: 9600
Thanks for all the replies and good information that I've received
on 9600 operation and Micors... Keep it coming...
Re: DIGEST
Geez! Can someone exterminate those addresses, this mailing is
getting close to a monthly digest.
******************************************************
* 73 de Mike, N4CNW@W4DPH.#TPA.FL.USA.NA *
* Amprnet: n4cnw@n4cnw.ampr.org [44.98.0.151] *
* Internet: mike.murphree@stpete.honeywell.com *
* -------------------------------------------------- *
* "I'd rather have a bottle in front of me, *
* than a frontal labotomy!" *
******************************************************
------------------------------
Date: Thu, 5 Aug 93 14:27:48 +0100
From: agodwin@acorn.co.uk (Adrian Godwin)
Subject: KISS problem?
To: tcp-group@ucsd.edu
I think that G8BPQ proposed (and possibly implemented) some changes
to KISS to allow this to be detected, though I don't know that anyone
except BPQ has made use of them.
Adding such features is also rather anti-KISS, but unfortunately
the KISS TNC has stayed around a lot longer than anyone, I think,
expected.
-adrian
------------------------------
Date: Thu, 5 Aug 93 13:02:07 MDT
From: "Karl Larsen" <klarsen@centaur.arl.army.mil>
Subject: Kiss Works Fine!
To: tcp-group@ucsd.edu
I am tired of all the flack about using the "Keep It Simple
Stupid" (KISS) software. If you own a tnc-1 or tnc-2 or a mfj tnc
then you either replace the existing e-prom with a kiss e-prom. Or
if you bought the mfj in the last 2 years or so just set the tnc
to the kiss mode. If you own a Kam just switch it to kiss. If you
own any other kind of tnc, read the book.
I use my Kam in the kiss mode daily since it's connected to
my G8BPQ switch that way. I have a Pac-Com Tiny tnc I use when
traveling and it has a kiss e-prom made from a file in the
collection sent with the BPQ switch. All my tcp/ip and hf packet
and all other things I have done with a kiss mode tnc work fine.
I'm at a loss to understand why anyone has any problems.
73, de karl
_________________________________________
| Internet klarsen@centaur.arl.army.mil |
| Fido 1:381/401 |
| k5di@k5di.nm.usa.na |
| Ham IP 44.30.2.5 |
| (505) 678-3145 weekdays 524-3303 home |
|________________________________________|
------------------------------
Date: 6 Aug 93 10:25:30 GMT
From: Jon Jagger <J.R.Jagger@sheffield-hallam.ac.uk>
Subject: Nos strange behaviour
To: tcp-group@ucsd.edu
Hi,
I've got a version of NOS that compiles fine. It's based on JNOS 1.08
I haven't actually changed anything, just stripped it down a lot.
(Basically its a kernel and ?,help,status,mem,exit. I've stripped
down Socklink to include only TYPE_LOCAL_STREAM)
What happens is that
a) sometimes keyboard typed char does not get ochoed to the screen
b) sometimes text from a function calling tprintf() does not
get echoed to the screen.
some times I get both a) and b), sometimes just one, sometimes
neither. In all cases NOS actually works, ie if I enter
exit CR y CR I can't see what i type but I can exit NOS, and
functions that use printf() rather than tprintf() eg mem freelist
display and work fine.
I was wondering If anyone had any ideas on the cause of this.
Even more strange is that if I insert a few printf() statements to
let me know whats happening, sometimes I can alter the behaviour
of a)b) above (from working to not and vice-versa). Worse than
that there is no pattern to this behaviour.
I also noticed in one of the .asm files there is a NOP loop which
has some comments based on timings for a 386. I'm running a 486 DX-33
Could this be a problem?
Any help appreciated
Thanks
JJ:: Jon Jagger, Comp. Serv., Sheffield Hallam University, S1 1WB, UK
:: Internet J.R.Jagger@shu.ac.uk AMPRnet 2e1bsd (TCP/IP mailbox soon)
:: Tel 0742 533802/432889 (work/home) Fax 0743 533840
:: Roses are red, violets are blue,
:: I'm schizophrenic, and so am I
------------------------------
Date: Thu, 5 Aug 93 11:42:46 EDT
From: Ali Taalebi <taalebi@gel.ulaval.ca>
Subject: Running ka9q TCP/IP on HP 95LX
To: tcp-group@ucsd.edu, taalebi@gel.ulaval.ca
I wonder if it is feasible to run ka9q TCP/IP on HP 95LX?
Are there any potential difficulties?
Your comments will be very much appreciated.
>> Ali Taalebi
------------------------------
End of TCP-Group Digest V93 #200
******************************
******************************