Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!ux1.cso.uiuc.edu!news.iastate.edu!sharkey!nstar!larry
From: larry@nstar.rn.com (Larry Snyder)
Newsgroups: comp.dcom.modems
Subject: Re: V.32bis frozen?
Message-ID: <1991Mar04.134553.17624@nstar.rn.com>
Date: 4 Mar 91 13:45:53 GMT
References: <1991Jan19.015521.22170@athena.mit.edu> <15@mich-ns.UUCP> <19377@cbmvax.commodore.com> <23@mich-ns.UUCP>
Organization: NSTAR Public Access Unix Site - 8 dial up lines - 4200 megabytes
Lines: 21

tech@mich-ns.UUCP (Mich. Network Sys. TECH SUPPORT) writes:

>standard has not yet stabilized. Anything that you get out there today
>that is "V.32bis" is likley to be an unstable implementation. 

Yes - but if the vendor is willing to continue to support the product
as v.32bis is ratified - nothing is lost -

In our case, we needed the additional throughput of v.32bis since
we are running a pair of USR V.32/v.32bis/v.42bis modems over a leased
line running SLIP.  The USR modems produce ftp transfers of around 2.4 kb/sec
while the pure V.32 only around 1.4.  Since USR is the only company currently
shipping v.32bis, their modems are in use.  USR promises upgrades to keep
the modems current with v.32bis as it is ratified - and USR has a 
history of excellent support with free ROM upgrades fixing bugs and
adding features.

-- 
   Larry Snyder, NSTAR Public Access Unix 219-289-0287 (HST/PEP/V.32/v.42bis)
                        regional UUCP mapping coordinator 
               {larry@nstar.rn.com, ..!uunet!nstar.rn.com!larry}