Paul, at 09:19 on Feb 02 1996, you wrote to Bill Grimsley...

DD> If you want your port & modem to lock at 38,400 you must send an
AT command 
DD> at 38,400 followed by an &W to write that speed to NVRAM.

PE> You just made that up.  The manual does not say what happens.

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. 

You could've fooled me then.  You may have glanced at them, but you sure
didn't grasp what they had to say.  The bottom line is that you should
simply set Binkley to a serial port speed of 57600 bps, fire up the modem,
and enter the required init$ (say AT&F1&K3S54=64&W, which
disables MNP5 but not V.42bis, and also disables the V.25 call-indicate
tones).  The &W will also write the port speed to the Courier's NVRAM,
and like all error-correcting modems, you should NEVER need change it
again, regardless of the link rate of an incoming call.

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

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

PE> You just misinterpreted the manual.

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

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.

Yep.  It just doesn't permanently write that value to NVRAM, that's all. 
You'd need to issue an &W if you wanted to do that (for some obscure
reason).

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.

Operator error perhaps?  Seriously though, if different, mine auto-bauds to
the terminal's port rate as expected, with either incoming or outgoing
calls, and regardless of what had previously been written to NVRAM.  I just
ran a few tests with 57600 saved to the modem, but varied my locked port
rate between 38400 and 115200 bps.  No problems at all, even on incoming
calls.  If your Courier isn't doing the same thing, it may indeed be
faulty, or (more likely) the last SDL didn't "take" properly. 
That has been known to happen before.

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".

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

I say again...

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

DD> USR Couriers work perfectly well at my place, especially when I dial my 
DD> host who uses someother brand modem.

Marwick runs a Maestro 288FM V.34, in case you're interested.

PE> No they don't.  Not when Rod called you. 

BG> Of course, we all know that Rod's 5 year old, NON-APPROVED Supra is not 
BG> faulty, don't we?  :)

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

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

My last piece of advice to you is to give the Courier back to Paul, then
look around in Aust_Trading for a second-hand Spirit, seeing as how you
like them so much.  As far as I'm concerned, you'll deserve each other.

Regards, Bill

--- Msgedsq/2 3.20