TIP: Click on subject to list as thread! ANSI
echo: locsysop
to: Bill Grimsley
from: Paul Edwards
date: 1996-02-03 15:50:34
subject: USR Courier

BG> Utter bullshit Paul!  The manual DOES say that, and quite explicitly.  Did 
BG> you read the extracts I posted yesterday, from the on-line text Courier 
BG> manual?

PE> Indeed I did. 

I even read that bit before you quoted it, in an attempt to find
the bit about the auto-baud rate detect that DD told me to read
(nevermind it wasn't even there).

BG> You could've fooled me then.  You may have glanced at them, but you sure 
BG> didn't grasp what they had to say.  The bottom line is that you should 

YOU are the one who can't grasp it.

BG> simply set Binkley to a serial port speed of 57600 bps, fire up the modem, 
BG> and enter the required init$ (say AT&F1&K3S54=64&W,
which disables MNP5 but 
BG> not V.42bis, and also disables the V.25 call-indicate tones).  The
&W will 
BG> also write the port speed to the Courier's NVRAM, and like all 
BG> error-correcting modems, you should NEVER need change it again, regardless 
BG> of the link rate of an incoming call.

And like all other modems, expect that if I do change the baud
rate, to test something out, I expect it to AUTO BAUD RATE
DETECT.  What a shame that USR's are stuffed in that regard.

BTW, you can't even grasp that you keep on quoting something
about the baud rate that happens AFTER a connect.  I am talking
about something that happens BEFORE a connect.

BG> Bloody hell Paul, is that such a difficult concept for you to grasp ?

Basically because you are wrong.  Be interesting to see if you
end up apologizing for all your ranting.

PE> Maybe I should have said that a little more graciously:

PE> You just misinterpreted the manual.

BG> Nope, there's nothing at all wrong with MY comprehension.

Apologize when ready.

PE> In fact, if you type ATZ at 38400, it WILL auto baud rate
PE> detect, and send the answer, "OK" back to the computer.

BG> Yep.  It just doesn't permanently write that value to NVRAM, that's all.  

Aha, the man suddenly understands what auto baud rate detect is
in this context.

PE> It decides to send "RING" to the computer at a rate other than
PE> 38400 though.  Fucked, either by design or by a bug.

BG> Operator error perhaps?  

Nope, any modem designed to send characters to the modem at two
different speeds is fucked by design or by a bug.

BG> Seriously though, if different, mine auto-bauds to 
BG> the terminal's port rate as expected, with either incoming or outgoing 

Yay, the man is starting to understand.

BG> calls, and regardless of what had previously been written to NVRAM.  I just 

Yay, the understanding continues.

BG> ran a few tests with 57600 saved to the modem, but varied my locked port 
BG> rate between 38400 and 115200 bps.  No problems at all, even on incoming 

Yay, still going.

BG> calls.  If your Courier isn't doing the same thing, it may indeed be 
BG> faulty, 

ROFL!  Well what do you know?  I was right all along.  I'll still
have to see the results of the proper test though.  Ok, the proper
test to do, is have the NVRAM set to 57600 as usual, fire up your
comms program at 38400, ATZ, should respond "OK".  Now get someone
else to call you, and see if the word "RING" appears on your
screen.  If it does, the bug is not affecting you.

BG> or (more likely) the last SDL didn't "take" properly.  That has 
BG> been known to happen before.

I've just done a reload, just rerun the test, same thing.

BG> It's specific behaviour is controlled by the &Bn command.

PE> Yeah, and I've got &B1, locked com port.  With "OK" coming in
PE> at a different speed to "RING".

BG> The &B1 setting is "correct", but I don't understand
what you mean when you 
BG> say that the incoming RING is at a different rate.  If both your modem and 
BG> your serial port are locked to say 57600 bps, that's the speed at which the 
BG> PC is communicating with the Courier, and is totally unrelated to the 
BG> caller's speed, which is completely irrelevant from your POV.

My modem has &B1, which means locked com port.  I can send AT
commands at 38400, and get the response at 38400, long before
a connect.  Now the USR detects someone is trying to ring me,
so it tells me "RING".  Only trouble is, it sends that at the
speed of the last NVRAM save.  Tell me the bit that you don't
understand.  Try to understand, Bill, I know what I'm talking
about.

BG> I say again...

BG> ======================================================================
BG>    &B1   Fixed rate.  Default.  The modem always communicates with the 
BG>          terminal or computer at the rate at which you have set the 
BG>          terminal or software, regardless of the connection rate.  
BG> ======================================================================

See, the rate of my terminal is 38400, not 57600, in the tests
that I was doing.

PE> What we CERTAINLY know is that the Spirit was far more robust
PE> with this REAL-WORLD modem.

BG> Oh crap.  If you had a genuine grievance with the Courier, I'd go out of my 
BG> way to help you solve any legitimate problems, but I'm almost 100% 
BG> convinced that your "fault-finding" is little more than a
childish exercise 
BG> in oneupmanship, and I for one am no longer interested in playing your 
BG> silly games.

They are all legitimate problems. 

BG> My last piece of advice to you is to give the Courier back to Paul, then 

It looks like Paul Markham has saved me $175.  Thanks Paul!

BG> look around in Aust_Trading for a second-hand Spirit, seeing as how you 
BG> like them so much.  As far as I'm concerned, you'll deserve each other.

And you know that's a blatant lie too.  I was screaming about
the Spirit whilst you were still in nappies (or a dress at any
rate).  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™.