Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.vbc.net!samba.rahul.net!rahul.net!a2i!news.PBI.net!news.mathworks.com!newsfeed.internetmci.com!in1.uu.net!shore!news From: "Greg Arsenault" <greg@beacondesign.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: term prob trying FTP download/install Date: 11 Sep 96 15:32:56 -0500 Organization: Shore.Net/Eco Software, Inc; (info@shore.net) Lines: 64 Message-ID: <AE5C8C2F-1651CA@204.167.102.207> NNTP-Posting-Host: slip-9-7.slip.shore.net Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="Cyberdog-AltBoundary-0016500F" Content-Transfer-Encoding: 7bit X-Mailer: Cyberdog/1.1 X-News-Servers: news.shore.net X-Newsgroups-TO: nntp://news.shore.net/comp.unix.bsd.freebsd.misc --Cyberdog-AltBoundary-0016500F Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable During the final phases of the the install process, I am having absolutely no luck getting the 'term' program to interact with my PC's internal modem. I have configured the correct com port (COM2) at which my modem resides, yet term doesn't even echo chars I type at my keyboard, and it eventually locks up (I suppose because some sort of keyboard input buffer fills up...). I need to get term working in order to get to the next step of dialing up my ISP and trying to download the disksets for FreeBSD. Is there something I may be missing in regard to the device setup for COM2? Thanks, -- Greg mailto:greg@beacondesign.com --Cyberdog-AltBoundary-0016500F Content-Type: multipart/mixed; boundary="Cyberdog-MixedBoundary-0016500F" Content-Transfer-Encoding: 7bit --Cyberdog-MixedBoundary-0016500F Content-Type: text/enriched; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <X-FONTSIZE><PARAM>12</PARAM><FONTFAMILY><PARAM>Geneva</PARAM>During the final phases of the the install process, I am having absolutely no luck getting the 'term' program to interact with my PC's internal modem. I have configured the correct com port (COM2) at which my modem resides, yet term doesn't even echo chars I type at my keyboard, and it eventually locks up (I suppose because some sort of keyboard input buffer fills up...). I need to get term working in order to get to the next step of dialing up my ISP and trying to download the disksets for FreeBSD. Is there something I may be missing in regard to the device setup for COM2? Thanks, -- Greg </FONTFAMILY></X-FONTSIZE> --Cyberdog-MixedBoundary-0016500F Content-Type: application/X-url Content-Transfer-Encoding: base64 Content-Description: Greg at BeaconDesign bWFpbHRvOmdyZWdAYmVhY29uZGVzaWduLmNvbQ== --Cyberdog-MixedBoundary-0016500F-- --Cyberdog-AltBoundary-0016500F--