Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) v.90? When?
On Fri, 13 Mar 1998 13:54:45 -0500 (EST), William T Wilson
<fluffy@dunadan.com> wrote:
>On Thu, 12 Mar 1998, Chris A. Epler wrote:
>> Amen! My users are just going to have to wait. I refuse to go thru all the
>> beta testing we were put thru with the K56 crap. Ascend, take notice, do
>> not release that code until you are damn sure it is rock solid.
>I'm not 100% in agreement with this. I'd like to be able to support USR
>modems ASAP, especially since increasing numbers of my USR customers have
>the V90 upgrade and want it to go faster. (I serve some small mountain
>areas where there are no X2 ISP's, so USR customers make up a relatively
>large portion of my clientele). As long as it doesn't get WORSE than
>V.34, I have no where to go but up. I'd be happy telling my customers "We
>have V90 now. If you have KFlex you can upgrade if you like. X2
>customers should upgrade if they want to be on the bleeding edge and trade
>reliability for speed". As long as the KFlex modems continue to work
>reasonably wwell, I'd be happy with this.
If your situation is really as you describe, it sounds like you have a
captive audience. Either they get Internet access from you or they don't
get any at all. If that truly is your situation (lucky you) and I'd be
all the more inclined to wait for a more mature turn of firmware than the
first or second pass. But if you are a rural provider, there's also a
fair chance that not many of your customers will be able to achieve the
new protocol speeds.
How quickly we forget what modeming was like when V.32 was new and again
when V.32bis was new and all over again when V.34 was new. Each and every
time there was "a learning curve" coupled with a period of 8-10 months
during which time competing brands did not interoperate especially well.
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
Follow-Ups:
References: