BD>
MSGID: 1:387/770.0 3269a16e
BD>
PID: BWTAG 3.11 [Reg]
BD>
TID: FastEcho 1.45a 7160
BD> -=> Repeating a message of = = = = - >      12 Oct 96  17:39:00 <=-
BD>    To: Hayes Support
BD>  Subj: RE-DIALS & CRC'S
BD>ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
BD>(No response seen, but Fido is more tricksy lately than it used to be)
BD>Mike, is it?
BD> BD>04-00971-720 34AC
BD> HS> That's the latest firmware version of that modem, and it's proven to
BD> HS> be very solid with connectivity and stable connections.
BD> HS> Yes, the CRC errors generally indicate a problem on the system, after
BD> HS> the data is already passed the modem, but could also be due to 
noise'
BD> HS> on the line which can send the modem into long retrains.  If you are
BD> HS> having problems making the initial connection, this is usually
BD> HS> related to conditions on the phone line, especially if you are seeing
BD> HS> problems more often when connecting to particular systems more so 
han
BD> HS> with others.
BD>There never is any fading, noise, scratchiness, or interference heard
BD>when connected by voice on that same line..
There rarely is, it usually has more to do with available 'bandwidth'
than actual 'noise' on the line.
BD> HS> This really doesn't appear to be a modem problem, but it is not
BD> HS> inconceivable that the modem could be defective.  I still wouldn't
BD> HS> consider returning it for repair unless the problems could be
BD> HS> duplicated on other systems and at other locations, using other
BD> HS> software.
BD>It is always possible that the local phone company has degraded the
BD>service recently.  Transfer speeds *are* down somewhat from August
BD>when connected to several local BBS's at which there has been no re-
BD>dial or CRC problem.  I checked to see if connecting in the house via
BD>another (internal) extension might help.  What I haven't tried is un-
BD>plugging the several instruments that are scattered around the house
BD>on that same line to see if one has gone bad unbeknownst & is causing
BD>these faults..
That's something to try, but unless the device is connected directly
between your modem and the wall jack, it shouldn't be able to cause any
problems.
BD> HS> If you want something very basic to initialize the modem, you BD>
HS> might want to use AT&F&C1&D2 to wake it up.
BD>I will certainly give that a try.  Meanwhile, due to having to call
BD>long distance and finding Fido is as fast or faster, I left a note
BD>last night on the Hayes Support BBS that I prefer to use this route
BD>over calling there, especially if it's essentially the same folks in
BD>each case who will answer..
BD>(Well, maybe that was a mistake, after all.  I never saw any reply
BD>get to this area.)
We have several folks handling the mail on the bbs, so it really depends
on what section you leave it in as to who will get it.  However, if you
leave a message on the Hayes BBS, it is answered on the Hayes BBS.
BD>Although I still wonder where the very first query that I uploaded
BD>to your support BBS disappeared to..
You should have gotten a response on the BBS within 1-2 business days.
What section did you leave it in?
BD>Maybe a second line would be worthwhile.. Craig Ford suggested adding
BD>a "Q6%C0" for calling those BBS's I have trouble with.  I have the
BD>slightly more detailed manual from the Accura 14.4, didn't find that
BD>one in there, but there was an S Register setting for bad lines in
BD>there somewhere.
"Q6%C0" would not be valid commands for your modem.
BD>(In that particular regard, I cannot determine from Qmodem's manual
BD>how/where that code of Craig's is tucked into the terminal software,
(Continued to next message)
--- FLAME v1.1
---------------