From owner-freebsd-current Wed Feb 25 09:00:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21703 for freebsd-current-outgoing; Wed, 25 Feb 1998 09:00:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA21467 for ; Wed, 25 Feb 1998 08:58:48 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #3) id 0y7k9n-0004lt-00; Wed, 25 Feb 1998 08:58:07 -0800 Date: Wed, 25 Feb 1998 08:58:06 -0800 (PST) From: Tom To: Simon Shapiro cc: Kingson Gunawan , freebsd-current@FreeBSD.ORG Subject: Re: Help needed with DPT card + Asus M/B In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Feb 1998, Simon Shapiro wrote: > On 25-Feb-98 Tom wrote: > > > > On Tue, 24 Feb 1998, Simon Shapiro wrote: > > > >> That is not it. Unless some other driver is stealing the PCI interrupt > >> (which I do not know how to do with PCI). > > > > Unless it is a silly ISA device... > > True only if the MB allows interrupts to be shared between ISA and PCI, > which it should not. Kingston reports that Win95 works on that MB, with > the DPT and all. Hmmm, but how does a motherboard know what interupts a ISA card might use? You certainly can't have ISA and PCI devices sharing the IRQ, but it is up to the operators to make sure it doesn't happen. Win95 often works great in that situation, up until you address the rogue ISA device. Or maybe it doesn't even have a driver installed for the rogue device. > ---------- > > > Sincerely Yours, > > Simon Shapiro > Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 > > Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message