BD>MSGID: 1:387/31.0 3259806e
BD>___- Cross-Post from Fido_Communications ----------------------------
BD> Subj: Multiple Re-dials, Original to Craig Ford
BD>After ten years of good experience with Hayes modem products, I am
BD>very disappointed with the behavior of the current FaxModem 28.8..
BD>There is *BOUND* to be some workaround if my present symptoms are
BD>at all common, else I ought to have cause to exchange the critter.
BD>About four years ago, I bought a Hayes Accura FaxModem 14.4 that I
BD>never had a single complaint about. It replaced an off-breed type
BD>that hadn't been much of a bargain whatever I'd paid for it -- it
BD>was Japanese or Korean -- can't recall whose. Before whatever it
BD>was, there'd been a couple of old Hayes Smart-Modems, too expensive,
BD>but dependable, solid, & trouble-free.
BD>Using Mustang's Qmodem Pro (DOS) with the Accura 14.4 worked fine
BD>with a 386, and the 486 that replaced it (DX-100, 16 MB, 16550 for
BD>both UARTs). With that software, there are two BBS's with whom it
BD>may require anywhere from four to six re-dials to connect. When
BD>using Zmodem for downloads, CRC errors can run to **ASTRONOMICAL**
BD>counts. There were 50-something of them a few days ago on a 1.5 MB
BD>file! I am using QM's configuration for an Optima 28.8 V.FC, as
BD>Mustang hasn't updated their PDF file for the software in a year.
BD>I have two Accura FaxModem 28.8's. The internal isn't used for a
BD>regular telecomm connection, and I have less experience with it..
BD>The number of re-dials required has remained fairly consistent all
BD>along since replacing the Accura 14.4. There are quite a few BBS's
BD>with whom first-call connects continue to be the norm, of course.
BD>The CRC error problem in Zmodem is not constant; fairly often the
BD>downloads of mail run smoothly. And these repeats of the same
BD>block of data weren't required any more frequently when the 28.8
BD>first went into use than had been possible to blame on phone line
BD>problems with the prior modem. Since mid-September (I got these
BD>Accura modems in May of 1996), the CRC's have become endemic!
BD>I can think of nothing that has been done with or to the system to
BD>affect the operation of a transfer protocol!
BD>With one particular BBS (the local 1:387 NC), downloads would hang
BD>on a block and Zmodem would keep requesting repeats until I gave
BD>up on the download, almost always at about the 90% complete mark.
BD>A change to Xmodem-1K helped some, but even that protocol lost one
BD>download in mid-stream, had to be aborted & started over.
BD>At this point, neither I nor QMPro are using anything other than
BD>the default ("ATM"?) to wake up the modem.. BUT it does seem that
BD>part of the trouble is the software. I don't like ProCommWin much
BD>at all, yet on a couple of experimental calls, it *can* manage a
BD>connect at either "problem" BBS with one call, and *its* version of
BD>Zmodem seemed to be devoid of the CRC's.
BD>Any ideas??
BD>Bill Dawson
Bill,
I'm not sure if you got my last response to you, but here it is
again:
Bill,
What is the model number of the ACCURA 28.8 that you have? If you
could, please issue an ATi3 to the modem and let us know what it returns
so that we will be able to tell exactly what version of the modem you
have. Is the modem external or internal? If internal, what com port is
the modem configured for and what com ports do you have on the system?
Please let us know what you find.
As for our online support, we can be reached via any of the following
means:
---
Hayes Support via email: support@os.hayes.com
World Wide Web: http://www.hayes.com
FTP: ftp://ftp.hayes.com
Hayes Online BBS: 770-446-6336 or telnet://hayes.com
Voice Support: 770-441-1617 (Mon-Fri 8AM-6PM eastern)
AOL Keyword: Hayes
CompuServe: Go Hayforum
To add on to this, generally CRC errors are not indicative of a 'modem'
problem. When dealing with internals the problem may be traced to a
hardware conflict, with both internals and externals it could be caused
(Continued to next message)
--- FLAME v1.1
---------------
* Origin: Southern Star - V32b/V.FC/V.34/ISDN - 504-885-5928 - (1:396/1)
|