From owner-freebsd-hackers  Fri Mar 29 02:47:26 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA02491
          for hackers-outgoing; Fri, 29 Mar 1996 02:47:26 -0800 (PST)
Received: from MediaCity.com (root@easy1.mediacity.com [205.216.172.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA02486
          Fri, 29 Mar 1996 02:47:20 -0800 (PST)
Received: (from brian@localhost) by MediaCity.com (8.6.11/8.6.9) id CAA19411; Fri, 29 Mar 1996 02:53:43 -0800
From: Brian Litzinger <brian@MediaCity.com>
Message-Id: <199603291053.CAA19411@MediaCity.com>
Subject: Re: BitsurfrPro on FBSD 2.1 & MLPPP broken
To: dwalton@psiint.com (Dave Walton)
Date: Fri, 29 Mar 1996 02:53:43 -0800 (PST)
Cc: jkh@time.cdrom.com, lmcsato@lmc.ericsson.se, questions@FreeBSD.ORG,
        hackers@FreeBSD.ORG
In-Reply-To: <Pine.A32.3.91.960328141129.43928F-100000@vv.psiint.com> from Dave Walton at "Mar 28, 96 02:49:24 pm"
Reply-To: brian@MediaCity.com
X-Mailer: ELM [version 2.4ME+ PL11 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Dave Walton wrote:
> On Thu, 28 Mar 1996, Jordan K. Hubbard wrote:
> 
> > > After this result I'm starting to suspect freebsd as being the problem, 
> [* especially after I gave it a try with win 95 and the modem didn't resets 
> [* itself.
> 
> > I wouldn't, at least not yet - try another brand; who's to say that Moto
> > *fixed* the problem?
> 
> I don't mean to be a pain here, but I really don't understand the 
> insistence that this is purely a hardware problem.  The second half of 
> his sentence above (which you didn't quote) points out that the same 
> hardware works correctly under Win95.  I'm not suggesting that it's 
> entirely FreeBSD's problem, since other TA's work correctly.  I'm just 
> surprised at the attitude that it's all Motorola's fault.  Win95 
> demonstrates that it IS possible for the hardware to work correctly.

It's all motorola's fault.  I spend much of my life testing all
sorts of HICAP solutions on all sorts of platforms.

Brian Litzinger
brian@mediacity.com