Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!qns3.qns.net!imci4!pull-feed.internetmci.com!newsfeed.internetmci.com!news.sgi.com!news-out.microserve.net!news-in.microserve.net!mr.net!visi.com!news From: Pat Sonnek <psonnek@soncom.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: modem concerns Date: Sat, 31 Aug 1996 20:01:48 -0500 Organization: (missing) Lines: 42 Message-ID: <3228E07C.640F@soncom.com> References: <Pine.BSF.3.91.960829072735.5950A-100000@nancy.soncom.com> <3228A014.41C67EA6@www.play-hookey.com> NNTP-Posting-Host: win95.soncom.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.0 (Win95; I) Ken Bigelow wrote: > > Patrick Sonnek wrote: > > > > I am having a problem, that I belive is line noise. But I thought I > > would run the problem past you folks, and see if I am missing somthing. > > > > I have installed a USR 14.4K modem set up for hardware flow control, as > > well as &c1&d2 below is my stty for the device. > > > [SNIP...] > > > > When calling into this line. Many times I will receive a NO CARRIER > > message, without ever receiving a CONNECT message. and if I do connect, > > the first connection will display the login prompt, but I am unable to > > key anything in, and the it disconnects. the second connection, I am > > able to logon, and I have no problems until I logoff, and log back on later. > > > > As I said, I think it's a line noise problem, but I'm not 100% sure that > > it is a line noise problem. I am running 2.1.0 release. > > > > Line noise wouldn't be that consistent. > > The NO CARRIER message indicates that the modem has timed out, or else > you hit a key while it was trying to connect. > > If you *always* are unable to send any characters the first time you > manage to make the connection, and then can *always* complete the login > process on the second connection, I would look first at your chat > scripts, or whatever other software you're using to connect to your ISP. Actually, I'm the ISP. It's my incoming lines that are behaving this way. I too felt the the problem occured too frequently and with too much predictability to be just line noise. (in other words, what is set wrong on either the modem or stty.) -- Patrick Sonnek - VTAM/NCP Systems Programmer Best Buy Co. http://www.soncom.com/psonnek