JC>-=> Quoting Hayes Support to Murray Weismer <=-
JC> MW>He is the second USR v.everything user to
JC> MW>tell me that they have connect problems. 
JC> MW>Does anyone have a handle on this?
 
JC> HS> Murray,
JC> HS> What is the model number and version of the internal OPTIMA 288? 
JC> HS> If you would, please issue an ATi3 to the modem and let us know what 
it
JC> HS> returns so we can see exactly what you've got.  When the USR calls in
JC> HS> and gets the 'garbage' characters, what carrier speed is it getting
JC> HS> initially?
JC> HS> Michael -- Hayes Online Services
JC>I sometimes have a similar problem here when I call my ISP using an
JC>x2 upgraded Courier.  The ISP has a few different types of modems
JC>and I see the problem only occasionally.  My Hayes Optima 288
JC>connects without the garbage.  I know that none of my ISP's modems
JC>are Hayes.
JC>I solved the problem with my ISP by placing S54=128 in my Courier's
JC>initialization string, which causes a Courier to connect in v.fc mode.
JC>Not an ideal solution.  Using the Hayes to call the ISP is much
JC>better. 
JC>I suppose I am trying to say that x2 did introduce an interoperability
JC>problem for a few users of Courier modems.  For what it's worth, I
JC>call other systems and have not noticed this Courier problem with any
JC>of the others.
Jim,
  That's very interesting.  The only similar issue I have seen had to do
with the 3429 symbol rate.  I was going to suggest to try the command
S54=32 to disable the 3429 symbol rate on the USR side, that has been
shown to help in similar cases when the modems would connect at 28,800
but get garbage and/or disconnect almost immediately after.
Michael -- Hayes Online Services
--- FLAME v1.1
---------------