Article View: comp.protocols.ppp
Article #126Re: dp-2.2-beta problems
From: Bob Sutterfield
Date: Mon, 12 Oct 1992 18:36
Date: Mon, 12 Oct 1992 18:36
56 lines
3045 bytes
3045 bytes
In article <87Rw02E025vQ01@JUTS.ccc.amdahl.com> lra00@pecan.spa.amdahl.com (Larry R. Ader) writes: I'm getting apprx. 2.4-2.6 KB/s for /vmunix, but only 2.0 KB/s for large (~500K) text files. Very strange. English text should be much more compressible, on the whole, than a SPARC binary, so it should flow across the line at a speed much closer to the limiting DTE rate. My test data was five concatenated copies of /usr/dict/words, being the most convenient and easily-replicated source of lots of text. Incidentally, when I'm uploading to work from home, I often see the CTS (and thusly SD) LEDs go off. Should data be being held back this frequently? Yes. And that's a good sign in some ways: it means that the compressor in your modem is filling up your carrier to its capacity. On the other hand, your interactive latency is now maximally bad, because your modems' buffers are as full as they can get. Bob, could I possilbly get a copy of your WorldBlazer configuration so that I can see what we're doing differently? Here are some excerpts from our example Dialers file: # # Set up a Telebit WorldBlazer by giving it the following command: # # at&f9 s0=1 s7=120 s48=1 s51=6 s58=2 s59=15 s61=0 s63=1 s92=1 tq2x12&c1&d3&s1&w # WORLDBLAZER ABORT NO\sCARRIER ABORT NO\sDIALTONE ABORT BUSY \ ABORT RRING\r\n\r\nRRING\r\n\r\nRRING ABORT ERROR \ TIMEOUT 5 "" AT OK-AT-OK ATS111=0DT\T TIMEOUT 60 CONNECT # # You should use the WorldBlazer in PEP mode only if the telephone # lines are unable of sustaining a V.32bis carrier connection. # WORLDBLAZER-PEP ABORT NO\sCARRIER ABORT NO\sDIALTONE ABORT BUSY \ ABORT RRING\r\n\r\nRRING\r\n\r\nRRING ABORT ERROR \ TIMEOUT 5 "" AT OK-AT-OK ATS111=0S50=255DT\T TIMEOUT 90 CONNECT and here's what it looks like when it's done: at&v WorldBlazer - SA - Version LA5.01 - Active Configuration B1 E1 L2 M1 Q2 T V1 X12 Y0 &C1 &D3 &G0 &J0 &L0 &Q0 &R3 &S1 &T4 &X0 S000:1 S001=0 S002=43 S003=13 S004=10 S005=8 S006=2 S007:120 S008=2 S009=6 S010=14 S011=70 S012=50 S018=0 S025=5 S026=1 S038=0 S041=0 S045=0 S046=0 S047=4 S048:1 S050=0 S051:6 S056=17 S057=19 S058:2 S059:15 S060=0 S061:0 S062=15 S063:1 S064=0 S068=255 S069=0 S090=0 S092:1 S093=8 S094=1 S100=0 S104=0 S105=1 S111=255 S112=1 S151=4 S155=0 S180=2 S181=1 S183=25 S190=1 S191=7 S253=10 S254=255 S255=255 OK Hope this helps...
Technical Details
Message-ID:
<BOB.92Oct12143642@volitans.MorningStar.Com>Path:
arc1-ca.pugleaf.net!sparky!uunet!ukma!darwin.sura.net!zaphod.mps.ohio-state.edu!mstar!mstar!bobReferences:
<87Rw02E025vQ01@JUTS.ccc.amdahl.com>Show Full Headers
Complete Article Headers
Newsgroups: comp.protocols.ppp Path: arc1-ca.pugleaf.net!sparky!uunet!ukma!darwin.sura.net!zaphod.mps.ohio-state.edu!mstar!mstar!bob From: bob@MorningStar.Com (Bob Sutterfield) Subject: Re: dp-2.2-beta problems In-Reply-To: lra00@pecan.spa.amdahl.com's message of 12 Oct 92 09: 14:46 GMT Message-ID: <BOB.92Oct12143642@volitans.MorningStar.Com> Sender: news@MorningStar.Com Nntp-Posting-Host: volitans.morningstar.com Organization: Morning Star Technologies References: <87Rw02E025vQ01@JUTS.ccc.amdahl.com> Date: Mon, 12 Oct 1992 18:36:48 GMT Lines: 56