From owner-freebsd-questions Wed Sep 3 10:07:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA23662 for questions-outgoing; Wed, 3 Sep 1997 10:07:11 -0700 (PDT) Received: from rainey.blueneptune.com (root@rainey.blueneptune.com [207.104.147.238]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA23643; Wed, 3 Sep 1997 10:07:05 -0700 (PDT) From: michael@blueneptune.com Received: (from michael@localhost) by rainey.blueneptune.com (8.6.12/8.6.12) id KAA19575; Wed, 3 Sep 1997 10:18:55 -0700 Message-Id: <199709031718.KAA19575@rainey.blueneptune.com> Subject: Re: Problem connecting to K56Flex PM-3 To: stefan@exis.net (Stefan Molnar) Date: Wed, 3 Sep 1997 10:18:54 -0700 (PDT) Cc: kevin_eliuk@sunshine.net, FreeBSD-questions@FreeBSD.ORG, FreeBSD-ISP@FreeBSD.ORG In-Reply-To: from "Stefan Molnar" at Sep 3, 97 10:57:31 am Reply-To: michael@blueneptune.com X-Mailer: ELM [version 2.4 PL24 ME8b] Content-Type: text Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > The ISP that I subscribe to and I are having trouble > > understanding why I cannot connect to there upgraded > > Portmaster 3 K56Flex with my Taicom (cheap) MU32PV 14.4 > > internal UMC V.32bis/FAX/VOICE MODEM, S/W Ver 6.05/ V1.0-A. > > Hopefully Livingston did not cut out 14.4 from the PM3 code. > I over heard something about that a few months ago. You need > to ask the SysAdmin of your ISP, if the K56Flex code they > got will support it. Livingston puts out diffrent versions > all the time. No, they did not cut the 14.4 code. That would be an incredibly stupid thing to do, and nobody's going to do that. However, there have been problems with the PM3 recently, with some people saying it's a problem in the new ComOS 3.7 (affecting both the old and the new modem cards), and others saying it's a problem with the new K56Flex modem cards and their software in the PM3. It appeared to be mostly a problem with the "cheaper" modems (and hence usually lower quality), and several brands of USR. Last I knew, it was not resolved, although I am nearly a week behind in reading the portmaster-users mailing list. [If you have a PM3 and are seeing problems, I strongly recommend subscribing to the portmaster-users mailing list. Go for the digest version, though, unless you have a good way to automatically separate the incoming mail, as it is an -extremely- active list. Send mail to majordomo@livingston.com for more info on their lists.] One workaround that seemed to be helping some people was setting &K0 in the modem init strings. -- Michael Bryan michael@blueneptune.com