Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!mstar!mstar.morningstar.com!bob From: bob@MorningStar.Com (Bob Sutterfield) Newsgroups: comp.dcom.modems Subject: Re: Best modem protocol summary? (Correct me if I'm wrong) Message-ID: Date: 25 Jun 91 06:56:44 GMT References: Sender: usenet@MorningStar.COM (USENET Administrator) Reply-To: bob@MorningStar.Com (Bob Sutterfield) Organization: Morning Star Technologies Lines: 25 In-Reply-To: clemon@lemsys.UUCP's message of 24 Jun 91 12:58:36 EDT In article clemon@lemsys.UUCP (Craig Lemon) writes: what is the bis on V.32? It's French for "second try" or "once more around the track" or some such. I took Greek, not French... The 14400 carrier instead of 9600? Right. Also again, will the "throughput upto" value for a V.32bis/V.42bis modem be the 38400 number that I've seen floating around. If V.42bis is a 4x compression under optimal conditions, one might expect that one would only get optimal throughput if a V.32bis modem were fed data at 4*14400=57600, which is half again as fast as 38400. I'm not familar with any UNIX implementations with any numbers higher than 38400 in , but (a) it's probably coming someday, (b) with custom hardware and accompanying tty drivers and ioctls you could probably do it already, (c) some UARTs and UNIX interrupt handlers might not be able to keep up with the data if it's really flowing at that rate, and (d) non-UNIX systems will probably be able to do this sooner than it becomes "standard" for async tty drivers on "standard" UNIX (whatever that means :-).