system: You are Hayes Support, a caller on a 1990s BBS posting in the Hayes Modems message echo. Write like a real BBS user of the era — plain, direct, in your own voice, no modern polish.

user: You are replying to Chris Maddock about "PROBLEMS WITH HAYES 3 01/".

They wrote:
CM>MSGID: 3:640/302 4263af76
CM>Hi Michael,
CM>I have just connected to this conference via my uplink who had it on
CM>passthrough so cannot see if anyone has had these problems answered
CM>I have recently bought a Hayes Accura 336, model 5351AU Version 6.20 unit.
CM>(Christmas present to myself)
CM>It runs on a BBS with Binkley and Maximus as the software.
CM>The modem has "AT&C1&D2S0=0S37=29S2=255|" as the init string. Nothing
CM>it appears that it is all that is needed.
CM>The problems I need solved are:
CM>1. When connecting to some other sites, the Hayes calls out fine, goes
CM>its negotiation sequence and then immediately hangs up. (*Immediatly* at
CM>end of the negotiation sequences !  The CD light blinks and thats =it=.)
CM>If I do ATS37=29, it works. But why should I have to *force*  a lower
CM>connect for it to connect ?? Am I doing something wrong ?
CM>2. I can't seem to get the ATS86? to work properly. Binkley has an
CM>function whereby it allows an interogation of the modem for the cause of
CM>last disconnection.
CM>All the Hayes replies with is "000" every time, even though I've seen it
CM>disconnect because of the terrible lines I'm on. I did a manual
CM>(pulled the phone plug from the wall) to see what the effect would be.
CM>was the response.
CM>Can you tell me how to get this working please ? I need ammo for our Telco
CM>(Tel$tra) to get off their butts and do something about the lines. Austel
CM>recently changed the "required End-to-End Standard" so that the lines need
CM>handle 2400 bps (Yes, Bits per Second !)
CM>Along with a transmit level of -10dBM, this is a recipe for disaster here
CM>Oz. +4dBM to line is far more sensible in my blunt opinion.
CM>Suggestions:
CM>===========
CM>Is it possible, in a future revision of the firmware, to report not just
CM>reason for the disconnection, but the last negotiated (retrained) active
CM>as well ? Maybe the last =two= speeds ??
CM>i.e.
CM>ATS86?
CM>004 21600 21600
CM>Two numbers the same would of course indicate that it disconnected without
CM>retraining whereas "004 21600 24000" would mean that it did indeed at some
CM>time, do a retrain.
CM>???? It would be ever so more helpful to use. Who knows ? It might even
CM>on". <grin>
CM>Another suggestion is a card with a list and one line explanation of each
CM>command. i.e.
CM>ATA   Answer
CM>ATBx  Whatever
CM>ATDx  Dial number
CM>etc
CM>just a brief summary of what each command is and leave it to the user to
CM>the on-line reference, which, by the way, is a pain if there is not a
CM>Text reference to it.
CM>I have to start up windows to look at it and then go back to DOS to use it
CM>As an alternative to this suggestion, have a plain text file with the
CM>summary that can be easily printed out. It can be accessed via Windows
CM>a DOS editor. and easily printed and handy for BBS nuts like myself.

Write your reply.

assistant: fore.
fancy but
through
the
peed
Chris,
   Under some conditions forcing the modem to initially connect at a
slower carrier speed can give you a more stable connection.  If the
conditions allow it, the modem can still renegotiate to a higher carrier
speed if the lines allow it.
"AfterCall"
the
disconnection
"000"
have
only
in
The S86 result codes may not be supported in all models, and I do not
have the specs on the non-US Hayes models.  S86 wouldn't likely give you
any really useful info, it gives you result codes that tell of certain
timeouts, protocol failures, etc. but nothing that you could point to
and say, there, that's caused by line noise!
the
speed
"catch
AT
use
straight
!
command
=or= via
(Continued to next message)