home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dcom.modems
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!sdd.hp.com!wupost!spool.mu.edu!umn.edu!student.tc.umn.edu!alla0008
- From: alla0008@student.tc.umn.edu (Graham Allan)
- Subject: Re: Digicom Scout+ problems
- Message-ID: <1993Jan7.034725.867@news2.cis.umn.edu>
- Sender: news@news2.cis.umn.edu (Usenet News Administration)
- Nntp-Posting-Host: student.tc.umn.edu
- Organization: University of Minnesota
- References: <9301070210.AA05696@poincare.phys.cmu.edu>
- Date: Thu, 7 Jan 1993 03:47:25 GMT
- Lines: 21
-
- In article <9301070210.AA05696@poincare.phys.cmu.edu> keister@poincare.phys.cmu.edu (Bradley D. Keister) writes:
- >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?
-
- You could set S0=0 and then store it permanently as the default using the
- &W command. I think that worked for me. Sorry, I don't know about your other
- problem.
-
- Graham.
-
-
-