N2OHH > BPQ 10.01.99 13:55l 24 Lines 1193 Bytes #-10148 (0) @ WW
BID : 12598_K2PUT
Read: DH6BB DB1RAS GUEST
Subj: Re: bpq vs flexnet
Path: DB0AAB<DB0MWS<DB0RBS<DB0PSC<DB0GE<DB0HOM<DB0ZDF<DB0SRS<DB0ABH<DB0RGB<
OK0PPL<OK0POK<9A0YRB<PP5BLU<WB0TAX<N4GAA<WA2PNU<KB2VLX<WA2SNA<N2ERH<
KA2MSL<K2PUT
Sent: 990110/0146Z @:K2PUT.FN31DK.#ENY.NY.USA.NA #:12598 [Carmel] $:12598_K2PUT
From: N2OHH@K2PUT.FN31DK.#ENY.NY.USA.NA
To : BPQ@WW
in responce to SM7MMQ comments:
FlexNet doesn't work well when operating as a lone DIGI (node) since it isn't
able to properly check link status independant of what the other nodes have
set for PACLEN PERSIST etc.
Here in the New York City (USA) metro area there has been an (almost)
overwelming acceptance of PC-FlexNet. It started out slowly but as more
NodeOps so how link through puts increase apr. %10-%20 without changing link
speeds they also opted to switch to FlexNet. Some say the FACT that Flexnet
wasn't designed for KISS TNCs is a major draw-back. Well for many in the area
that wasn't a big issue since many use Tiny IIs or other TNC2 clones. Thus
it was simply (in theory) a matter of changing EPROMs and adding a PC. I know
at the site I run adding the PC wasn't a major issue. Actually I would say that
FlexNet could help in a major way of bringing users back to packet since for
some they won't need to buy a TNC at all since PC-Flexnet has the Win9x software
to use the sound card (SB compatible) instead.
I would like to thank John WB2CIK & Bob K2BJG for helping with the
change-over.
7 3
Vin N2OHH
Read previous mail | Read next mail
| 
