From owner-freebsd-questions@FreeBSD.ORG Mon Mar 21 08:07:09 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 979F416A4CE for ; Mon, 21 Mar 2005 08:07:09 +0000 (GMT) Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [65.75.192.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4051543D1D for ; Mon, 21 Mar 2005 08:07:09 +0000 (GMT) (envelope-from tedm@toybox.placo.com) Received: from tedwin2k (nat-rtr.freebsd-corp-net-guide.com [65.75.197.130]) j2L87Jb25643 for ; Mon, 21 Mar 2005 00:07:19 -0800 (PST) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: Date: Mon, 21 Mar 2005 00:07:08 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <5810323424.20050321052023@wanadoo.fr> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 Importance: Normal Subject: RE: MS Exchange server on FreeBSD? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 08:07:09 -0000 owner-freebsd-questions@freebsd.org wrote: > Ted Mittelstaedt writes: > >> You were given things to try and do to solve the problem. > > No, I was not. I encountered a few people throwing darts and trying > to pretend that they had a clue and/or working to divert any > suspicion from > FreeBSD towards unspecified, unverified hardware problems, but I got > no real answers. I don't think anybody has any idea, which doesn't > surprise me. The problem is you just don't want it to be a hardware problem because you don't accept the possibility that the NT driver wrote around a hardware problem and the FreeBSD driver doesen't. Despite the fact that making up for hardware problems with writearounds in the software drivers is a common thing in the industry. So you won't do the testing to prove that it is or isn't a hardware bug, and thus you can continue pretending to yourself that it must be software, and thus not your responsibility. Ted