Path: utzoo!utgpu!water!watmath!clyde!att!rutgers!gatech!ncar!ames!xanth!amon-re!tadguy From: tadguy@amon-re.cs.odu.edu (Tad Guy) Newsgroups: comp.dcom.modems Subject: Re: Everex problem (redundant) Message-ID: <6019@xanth.cs.odu.edu> Date: 2 Aug 88 18:05:06 GMT References: <11100001@uxh.cso.uiuc.edu> <5955@xanth.cs.odu.edu> <1818@rtmvax.UUCP> Sender: news@xanth.cs.odu.edu Reply-To: tadguy@cs.odu.edu (Tad Guy) Organization: Old Dominion University, Norfolk, Va. Lines: 22 In article <1818@rtmvax.UUCP> rob@rtmvax.UUCP (Robert Talley) writes: >In article <5955@xanth.cs.odu.edu> tadguy@cs.odu.edu (Tad Guy) writes: >>We have been using Everex Evercom 2400s here for 7 months and haven't >>had any problems with them. None at all. > >Well Tad, you don't state whether you are using the newer (MNP) Everex or >the old one. We ran two of these (the sans MNP versions) and had to sell >both of them for scrap. They just would not reset back to answer at 2400 >once anyone called in at something lower. I did notice that they didn't revert to 2400 bps after a 1200 or 300 connection, but I figured it was normal: our Prometheus 2400Gs do the same thing. I had long since added in a hack to getty to reset the modem before waiting for carrier, so I didn't think much of it. I guess I'll have to replace the "None at all" with "At least none that our other 2400 bps modems didn't have." ...tad -- Tad Guy Old Dominion University, Norfolk, VA