Paul, at 13:26 on Mar 31 1996, you wrote ...

DD>> Having a modem that doesn't take a week to configure, and 
DD>> causes no heartache at all is worth at least $200 too.

PE> Took me a lot longer to get it set than that.  Disabling 
PE> V32terbo, disabling whatever it was Russell told me to 
PE> disable, disabling the thing that Poe said to disable.

DD>> Set and forget . . . .

PE> Uh oh, zealotry strikes again.  Not to mention if you want 
PE> to change baud rates.

When I got the Courier I was running Bink and BNU at 38,400 - I connected
the Courier and types AT&F1&W - It worked well.

After a while I decided to re-program the little data/voice switch on the
front panel - I type ATS32=8&W - it worked well.

When I moved to OS/2 I decided to set the portspeed to 57,600 - I adjusted
SIO, Binkley and the Mode statement, did an ATI4 and ATI5 to check the
settings, then AT&W - The modem has never looked back. 

I have never felt the need to disable V.32ter as I have a number of callers
who actually connect at that speed.  I also have callers and a downfeed who
connect at V.FC, so I feel no urge to disable that.

Rod's modem appears to be the only one to have connection problems at
V32bis - I sometimes login from work using a Yum-Cha internal V.32bis
modem.  If there is a retrain argument at connect then it is resolved very
quickly as the Bink logo shows on the screen without any apparent delay.

I have flashed a few new ROMs into it.  I usually do this on the laptop so
that I don't have to boot the BBS from DOS (long story).  The laptop
doesn't have a 16550 so I usually flash it at 38,400 - When I put the modem
back onto the BBS (at 57,600) I simply type ATI7 or similar then AT&W.

I find the inconvenience of having to set the speed somewhat minor compared
with the benefits of a modem that is always working without having to fuck
around with endless S registers (and it doesn't hang with the phone line
open like the M34F did to me once).

David
@EOT:

--- Msgedsq/2 3.10