NetNews Usenet Archive 1993 #1/NN_1993_1.iso/spool/comp/dcom/modems/19042

Internet Message Format | 1993-01-06 | 1.9 KB

Path: sparky!uunet!olivea!spool.mu.edu!uwm.edu!ogicse!das-news.harvard.edu!cantaloupe.srv.cs.cmu.edu!crabapple.srv.cs.cmu.edu!andrew.cmu.edu!<UNAUTHENTICATED>+
From: [e-mail] (Bradley D. Keister)
Newsgroups: comp.dcom.modems
Subject: Digicom Scout+ problems
Message-ID: <[e-mail]>
Date: 6 Jan 93 16:10:45 GMT
Organization: Carnegie Mellon, Pittsburgh, PA
Lines: 26

I'm having two intermittent problems with a Digicom Scout+ on a
Gateway 16 MHz 386sx.

1.  Occasionally, when I've used the modem for some application, it
will answer the phone (which is used for voice!) with its tone, even
though I've set every initialization string I can find to turn off
auto answer (ATS0=0).  Perhaps I've missed something, but it's getting
to the point where, after running any communication session, I will
start kermit or procomm and type AT*O just to make sure that S0 really
is zero.  It does appear that the AT&F reset command sets S0=2, so
perhaps there's an additional software reset being made that I haven't
seen.  Is there a clean way around this?

2.  There are also times (which keep recurring, though I can't
forcibly reproduce them) where the modem becomes completely silent,
that is, it gives no response whatsoever to any AT commands, including
AT*O, and various AT&F commands (even repeated); by "silent" I mean
not just no echo, but no OK, either.  The only way I can remedy this
is to reboot, and, in a few instances, use the reset button.  Is this
something I should expect, and/or is there a way around it?

-------------------------------------------------------------------------------
Brad Keister                   OFFICE:   [phone]
Department of Physics          FAX:      [phone]
Carnegie Mellon University     INTERNET: [e-mail]
Pittsburgh, PA 15213           BITNET:   keister%poincare.phys.cmu.edu@CARNEGIE