home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dcom.modems
- Path: sparky!uunet!think.com!spool.mu.edu!umn.edu!csus.edu!netcom.com!adler
- From: adler@netcom.com (Bruce Adler)
- Subject: Re: hayes response codes and uugetty/getty
- Message-ID: <1993Jan3.000336.6189@netcom.com>
- Organization: Netcom Online Communications Services (408-241-9760 login: guest)
- References: <1992Dec30.043842.3548@daimi.aau.dk> <6609.2b43778e@hayes.com>
- Date: Sun, 3 Jan 1993 00:03:36 GMT
- Lines: 28
-
- In article <6609.2b43778e@hayes.com> you write:
- >With many newer modems, you can. The "Q2" command causes the modem
- >to disable all result codes associated with answering of calls,
- >including RING, CARRIER, PROTOCOL, COMPRESSION, CONNECT, etc., but
- >leave them enabled when originating calls -- exactly what you're
- >looking for. You don't mention what modem you have, so it's hard to
- >say whether or not it supports Q2, but it wouldn't hurt to try
- >setting it and then calling to see if you get a RING.
-
- If I don't disable the answering result codes (i.e. Q0), does the
- modem generate the CONNECT messages before or after it raises DCD?
-
- Idle speculation follows:
-
- It seems to be that the if the modem raises DCD last then a correctly
- functioning Unix serial port driver would merely throw away any
- preceeding text (at least this is the way the drivers used to work).
- In fact on a port with "modem controls" enabled the receiver should
- be disabled and the receiver interrupt should be masked off when DCD
- is low to avoid extraneous interrupts. Perhaps the original poster
- has a driver which supports the FIFO mode on the '550, but doesn't
- disable the receiver and/or flush the FIFO when DCD is asserted. This
- could cause upto 16 garbage bytes to be received.
-
- I expect that there are a number of versions of Unix out there that
- don't function correctly, so the Q2 feature is a pretty neat solution.
-
- adler@netcom.com
-