TIP: Click on subject to list as thread! ANSI
echo: locsysop
to: Bill Grimsley
from: Paul Edwards
date: 1996-01-28 13:34:34
subject: USR Courier sux

PE> I am now getting statistics, but I have to actually put those
PE> ATI commands on separate lines.  :-(  Also, would you care to
PE> explain the "2400" in the stats?  Oh, and a reason for the
PE> retrain failure would be nice too.  Considering two USRs and
PE> all that.  BFN.  Paul.

BG> Something is VERY wrong at your end, Paul.

Yeah, I'm running a courier.

PE> # 26 Jan 22:19:29.40   CONNECT 28800/ARQ/V34/LAPM/V42BIS

BG> OK so far.

Except I wanted 33600 anyway.

PE> 26 Jan 22:23:05.75   CPS: 3346 (676027 bytes)  Efficiency: 116%

BG> An excellent result, although Dave also runs a V.34+ Courier, so why not a 
BG> 33k6 connect 

Good bloody question.

PE> 26 Jan 22:24:57.69   for some reason, ZCRCW is error
PE> 26 Jan 22:27:52.22   lost zmodem carrier
PE> 26 Jan 22:27:52.22   Zmodem Recv Problem  ???

BG> I don't know what this means, nor which end would have dropped carrier.

He dropped carrier on me.

PE> 26 Jan 22:27:52.40   string is ~~ATI11|~~ATI6|

BG> Do you need the first CR character?  ~~ATI11~~I6| should work fine.

That was still at experimental stage.  Now I've just got ATI6|
ie no delays.

PE> # 26 Jan 22:27:56.69   Modulation               V.34+

BG> Seems you did get Dave's Courier after all.

Hmmm, didn't know that you could tell from that.

PE> # 26 Jan 22:27:56.72   Carrier Freq (Hz)        44672/44672
PE> # 26 Jan 22:27:56.72   Symbol Rate              48905/48905

BG> Those figures are complete bullshit.  ISDN lines perhaps?  :)

Don't ask me.

PE> # 26 Jan 22:27:56.84   Recv/Xmit Level (-dB)    28/17

BG> A tad low on Xmit, but still well within tolerance.

PE> # 26 Jan 22:27:56.87   Roundtrip Delay (msec)   0

BG> That's bullshit too.  0mS delay is impossible.

I've been told by a reliable source that nothing is impossible
if you put enough money into it.  In this case, $600 to beat
the speed of light would seem reasonable.

PE> # 26 Jan 22:27:57.28   Speed                  21600/2400

BG> The first figure is your receive rate, the other is sending speed.  Given 
BG> the rest of your stats, I wouldn't believe any of it, especially with the 
BG> cps rates you achieved, which were quite normal for a 28k8 connect.

The modem is a heap of shit.

PE> # 26 Jan 22:27:57.31   Disconnect Reason is Unable to Retrain

BG> Don't believe that either.

The modem is a heap of shit.

BG> It seems to me that there is something not quite right with your setup (I'm 
BG> very loath to immediately blame the modem, although I'd like to see you try 

Yeah, right.

BG> another one, to be absolutely certain).  Are you using SIO, and if so, what 

Oh, here we go again.  I get modems when it is CONVENIENT.  I
got a Spirit Viper some time ago, and had very few problems with
it, remember?  I had a Spirit Thunder not very long ago, and had
far less problems with IT, too.  Now I've got a USR Courier
loaner.  It is not looking good.

BG> version?  Some are said to be quite buggy, although I've had NO problems 

I use COM.SYS.

BG> with 1.40 or 1.45 here.  Also, are you using EXACTLY the same MODE command 
BG> as I mentioned earlier?  If not, try changing it.

To solve which problem do you want me to change my mode command?
I am getting 33600 connects with David Drummond, that basically
proves my setup, ie my mode command etc.  Anything else is a modem
problem.

BG> Something else I'd be checking is your serial I/O card, just in case the 
BG> storm damaged it somehow when it took out your Spirit.  The bottom line is 

Again, the connects I have, even with you, prove that my serial
card is working.  My serial card doesn't care what is happening
between your modem and my modem, or Dave's modem and my modem,
or Frank's modem and my modem.  Only the modem cares.

BG> that you are experiencing strange problems which nobody else has ever 
BG> reported, and whilst it's not inconceivable that the modem is faulty, the 
BG> fact that the 100s I tested (and used) at CHH lead me to believe that this 
BG> is probably not the case at all.

People should give me modems to test, I'm the only one who tests
them properly.  Actually, I suppose the guy at work did too, and
told me the USRs kept dropping out.  Not as thorough as my tests,
but I had longer to do mine.  He strongly recommended Netcomm.  I
am getting the feeling that whatever modem I buy, I will get 0
support for it, and I have to stick with it until the next
lightning strike.  Therefore, I have the choice between a Yum Cha
for ~$300, a Netcomm for ~$400 sysop, a USR for ~$600 sysop.  I
am leaning towards the Netcomm at this stage, I know someone who
is using them on their internet service (they are a provider).

BG> A serious suggestion:  Do you want to swap modems for a few days?  If my 

It's Paul Markham's modem, not mine.  I think borrowing a 
state-of-the-art V34+ modem for an entire month is more than
what is reasonable, and sending it up to Brisbane is just
completely mad.

BG> Sportster exhibits similar problems at your end, that will virtually 
BG> eliminate the modem as being the cause, as I know for a fact that this 

ROFL!  The Spirit Thunder has already done the elimination of 
anything my end.

BG> modem is rock-solid here (as have been the Couriers I've used here as 
BG> well).

Bill, you don't have anything like the variety of schmucks 
dialling you as I do.

BG> Sorry, but I simply don't know what else to suggest.

Netcomm or Yum Cha, I have to make a gamble either way, which
one?  BFN.  Paul.
@EOT:

---
* Origin: X (3:711/934.9)

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.