Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!decwrl!decwrl!netcomsv!netcom.com!hasty From: hasty@netcom.com (Amancio Hasty Jr) Subject: Re: More causes garbage on dialin Message-ID: <hastyCKB3rL.MBq@netcom.com> Organization: Netcom Online Communications Services (408-241-9760 login: guest) References: <2hnoc9$b4f@crl2.crl.com> <2i4gd4$hvc@cleese.apana.org.au> Date: Thu, 27 Jan 1994 21:02:08 GMT Lines: 39 In article <2i4gd4$hvc@cleese.apana.org.au> newton@cleese.apana.org.au (Mark Newton) writes: >In article <2hnoc9$b4f@crl2.crl.com> rmc@crl.com (Jeff Phillips) writes: >>When we dial into our NETBSD host and use more, the output gets all >>messed up. Looks like a port over run. the port is locked at 19200 using >>a usr sportster 14400. Any suggestions on where to begin looking? > >You haven't said whether you're using 386bsd, FreeBSD or NetBSD. > >Early patchlevels of 386bsd had a problem whereby certain programs >would spontaneously change the terminal settings to 8-bit mode, and >others would spontaneously change them back to 7 bit mode. If you >have an early 386bsd patchlevel release, I'd suggest upgrading. > >Another thing to look for is flow control: Type "stty crtscts" and >re-start "more" to see if it happens again. It might be that >you're blasting chars at your modem too quickly, and overrunning its >buffer. Note that for this solution to work at all, you need to be >using a modem cable which has all the flow control signal lines >connected -- a 3-wire cable will be utterly useless. > >Good luck. > > - mark Hmm... do you have the correct termcap entry also make sure that that parity setting matches the one on your system. Cheers, Amancio -- FREE unix, gcc, tcp/ip, X, open-look, interviews, tcl/tk, MIME, midi, sound at freebsd.cdrom.com:/pub/FreeBSD Amancio Hasty, Consultant | Home: (415) 495-3046 | e-mail hasty@netcom.com | ftp-site depository of all my work: ahasty@cisco.com | sunvis.rtpnc.epa.gov:/pub/386bsd/X