Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uwm.edu!linac!att!att!cbnewsl!urban From: urban@cbnewsl.att.com (john.urban) Newsgroups: comp.unix.sysv386 Subject: Re: SVR4 (i386) serial port setup Keywords: SVR4, bidirectional, serial port, modem Message-ID: <1991May14.145737.24410@cbnewsl.att.com> Date: 14 May 91 14:57:37 GMT References: <1991May8.194639.28749@ux1.cso.uiuc.edu> <1991May13.125733.8838@cbnewsl.att.com> Organization: AT&T Bell Laboratories Lines: 27 In article gemini@geminix.in-berlin.de (Uwe Doering) writes: >urban@cbnewsl.att.com (john.urban) writes: > >>I forgot to ask this question before. The modem that you're using, does it >>have DTR strapped high or is it unstrapped? If its strapped high, then I >>don't know what the problem is. However, if it's unstrapped, you might >>not have the ,M in the Devices file for your "cu" port. >> >>ie: ACU tty01,M - 1200 hayes1200 >> >>The ,M "tells" cu, ct or uucico not to worry about DTR during the \M to \m >>Dialers string in the Dialers file. I think the BNU Guide talks about this. >>I don't have the guides in front of me. > >This isn't quite right. I assume you meant DCD instead of DTR. DTR is >an output while DCD is the carrier detect input that blocks the open() >call if it is low. > That's true I did mean DCD and not DTR. I was working from home yesterday and did not have all my crib sheets in front of me. However, the ,M is probably the fix that is needed. We add the ,M to the Device entries when we use a Hayes Modem. Sincerely, John Ben Urban