[FADCA] KISS - at first!

[Chuck Hast]

On Tue, 14 Sep 2004 07:08:08 -0400, bud thompson <budt at cfl.rr.com> wrote:
> >From Chuck:
> 
> > With this I shall crawl back into my hole and watch. Y'all enjoy!
> >
> 
> >From bud:
> 
> NO! Not until we have those working CD ROMs for FPAC and EMCOMMs!

That is where I am crawling back too... By way I have a FPAC DOS running
on a CF card. Boy you should see how fast is loads!! I have been pulling the
tools together I need to set up the FPAC Linux stuff. What we want is a CD
that will load it on anything just like the little floppy that apperas to run on
anything that you stick it in.


> 
> By the way the free AGW PE does work - it may take a little fiddling and
> farting to get it up and running, but that is all Charlie N3PPC and I have
> been testing as it is what the masses would use because of the cost of the
> Pro version.  Once I have this stable with Paclink (and it has been quite so
> for several months), I'll start working with the  Pro version as it has
> better support for sound cards.

Bud, I did a lot of testing of it at UP, I was trying to get something
up and running
so we could get our product to run over the amateur radio network, I
had it running
on Win2k and XP, but when I stressed it it would go tits up, when I say stressed
it, I mean when I would basicly start sending it a lot of traffic. I
would download the
latest and greatest and see if that would fix it, but no joy. As long
as I was just
sending something here and there life was good. But when I really laid into like
you would if you had a system set up at a disaster point and were handling say
triage traffic, and entering data as fast as it was entered you were
in deep trouble.

Then when I e-mailed him and asked him about doing connected mode IP and got
that hauty response that really kind of burnt me, and to top it off I
downloaded the
new expensive stuff and tried it, found it to be worse, when I tried
to back out of
it, it would not remove it's self so that silly 30 minute timer kept
on killing my
link even though I had gone back to the original code for the which I had paid
$25. I had to go into the registery and kill every reference to AGW and then
re-install my old code. No needless to say I would NEVER trust it, yes it will
run just fine if not stressed but my experience is that under stress
it is a piece
of crap, and I have the tools to STRESS it good. I have to tools to stress a 
commercial network to the point of taking a dump, one of my hats is that of
"can you hear me now?" and indeed probably going to be doing such a study
right here in Hillsborough, Co. on AT&T, Sprint and Verizon, besides trying to
see if the advertised coverage is real, I also try to see how deep the pond is
and if I can break it simulating a yard full of vehicles trying to log
into the mobile
workforce server all at the same time, so I am pretty good at
stressing things to
the max.

I again would recommend that someone who can write code get the TNOS
source for DOS, look at the AX25 stack and try to use it in Win2k and ExPEE
it was already running on 95 and 98, and I think that there are people who have
it running on Win2K.Not sure about XP. First thing I would do is just bring up
TNOS, it has all the appropriate hooks to use it with other programs as just the
communications stack, but the source is out there and it WILL do heavy duty
weight lifting, Brian Tom and I DID pound on it mercylessly it handled our AXIP
links to other ROSE/FPAC networks and also I used it to do SMTP to the network
up in TX.

Here is a site where you can download all of the TNOS DOS stuff.
ftp://ftp.ucsd.edu/hamradio/packet/tcpip/tnos/current/dos/
Take some time and take a look at it. tnos230s.zip is the source code and in
there is all that you should need to get a AX25 system running under Windows,
If someone will take the time to look at it I think they can figure
out what they
need to pull out and use to build the Ax.25 piece.  




-- 
Chuck Hast 
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going
out and having to identify your bits and pieces in the midst of torn
and twisted metal."