Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!decwrl!netcomsv!netcom.com!alm From: alm@netcom.com (Andrew Moore) Subject: Re: Problem with com ports and slip Message-ID: <almCDsD2I.5Dp@netcom.com> Organization: Netcom Online Communications Services (408-241-9760 login: guest) References: <CDrDup.GC5@usenet.ucs.indiana.edu> Date: Thu, 23 Sep 1993 02:47:06 GMT Lines: 19 In article <CDrDup.GC5@usenet.ucs.indiana.edu> pitts@bigbang.astro.indiana.edu (Jim Pitts) writes: >Need I say this had no effect? The new board has ONLY 2 serial ports on >it, one with a 16550A and the other without (it drives the mouse). The NetBSD serial driver is not so good. If you are dependent on high-speed serial communication, your best bet at the moment seems to be FreeBSD. >tip seems to work fine. Zmodem seems to produce a mesage like >'BAD CRC 0' followed by 'See man pages BUG chapter' (there is no such >thing ... at least that I can find.) Which Zmodem are you using? Are you invoking it from tip's undocumented ~C (CONNECT) command? This is the correct way to do it. Recent versions of zmodem are incompatible with tip. However, it is still possible to hack zmodem back into shape. You can find such a version on netcom.com as ~ftp/pub/alm/rzsz-3.24.tar.Z. -AM