Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 3 Sep 1997 10:18:54 -0700 (PDT)
From:      michael@blueneptune.com
To:        stefan@exis.net (Stefan Molnar)
Cc:        kevin_eliuk@sunshine.net, FreeBSD-questions@FreeBSD.ORG, FreeBSD-ISP@FreeBSD.ORG
Subject:   Re: Problem connecting to K56Flex PM-3
Message-ID:  <199709031718.KAA19575@rainey.blueneptune.com>
In-Reply-To: <Pine.LNX.3.95.970903105509.6742A-100000@sailfish.exis.net> from "Stefan Molnar" at Sep 3, 97 10:57:31 am

next in thread | previous in thread | raw e-mail | index | archive | help

> > 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709031718.KAA19575>