From owner-freebsd-stable Mon Sep 14 05:43:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28966 for freebsd-stable-outgoing; Mon, 14 Sep 1998 05:43:56 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from calis.BlackSun.org (slip-ppp-4-198.escape.com [205.160.46.198]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA28961 for ; Mon, 14 Sep 1998 05:43:54 -0700 (PDT) (envelope-from don@calis.BlackSun.org) Received: from localhost (don@localhost) by calis.BlackSun.org (8.8.8/8.8.7) with SMTP id IAA03163; Mon, 14 Sep 1998 08:43:21 -0400 (EDT) (envelope-from don@calis.BlackSun.org) Date: Mon, 14 Sep 1998 08:43:21 -0400 (EDT) From: Don To: Christer Hermansson cc: stable@FreeBSD.ORG Subject: Re: Most compatible modem In-Reply-To: <35FCCCE1.A53778E0@chdev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The modem I planning to purchase should be a internal, V90-compliant and > support both FreeBSD and NT. Why do you want to use an internal modem? Setting them up under any os is a pain in the rear especially if you dont have a lot of free IRQ's. Figuring out onto what com port, irq, and dma they have decided to dump them selves on is pain. Resetting them if they hang or die means rebooting the system. An external modem has none of these failings. It resides on whatever com port you attach it to. It is easily reset. There is nothing to figure out (such as irq's on a windows box). Not to mention that volume control and status lights on the modem can be such a blessing if things are not working right for some reason. As for a particular brand of modem. I have never had a problem with US Robotics (now 3com) or Motorola modems. -Don To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message