From owner-freebsd-questions Mon Apr 14 01:17:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA25446 for questions-outgoing; Mon, 14 Apr 1997 01:17:41 -0700 (PDT) Received: from obiwan.aceonline.com.au (obiwan.aceonline.com.au [203.103.90.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA25439 for ; Mon, 14 Apr 1997 01:17:32 -0700 (PDT) Received: from localhost (adrian@localhost) by obiwan.aceonline.com.au (8.8.5/8.8.5) with SMTP id QAA01313; Mon, 14 Apr 1997 16:03:59 +0800 (WST) Date: Mon, 14 Apr 1997 16:03:59 +0800 (WST) From: Adrian Chadd To: Doug White cc: Hinrich Eilts , freebsd-questions@freebsd.org Subject: Re: Etherexpress 10/pro In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > If PnP of Etherexpress is disabled, it work, but the computer have to run > > W95 too, and this will fail with PnP disabled (the motherboard is a > > Gigabyte GA586ATM/P256, which has no support for non-PnP ISA cards leading > > to resource conflicts if the Etherexpress is in non-PnP mode). > > THen you have a bigger problem than FreeBSD can support :) Huh? That isn't true. :) You can specify Windows 95 to *use* a certain setting instead of letting Windows (/PnP) decide everything. I do this in my PC. I have non-PnP ISA Soundblaster Pro and 3com 3c509, and a PnP SB32. I just went into my BIOS, disabled the particular IRQs the non-PnP cards were set to, and *told* win95 to use certain settings for my PnP SB32 card. It complains saying it can no longer figure things out, but then, it doesn't do a crash hot job in the first place. (For a laugh, try autodetecting a non-PnP NE2000 clone and see how many times Win95 gets the IRQ right :) I think people trust PnP too much. Cya, Adrian