From owner-freebsd-stable Wed Apr 5 7:39:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id 30EE337B57A; Wed, 5 Apr 2000 07:39:25 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3) id 12cqxe-0007sr-00; Wed, 5 Apr 2000 15:39:14 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id PAA13696; Wed, 5 Apr 2000 15:39:14 +0100 (BST) (envelope-from jcm) Date: Wed, 5 Apr 2000 15:39:14 +0100 From: J McKitrick To: Nick Hibma Cc: FreeBSD STABLE Mailing List , FreeBSD CURRENT Mailing List Subject: Re: Parallel port zip drives - inventory of working and non-working systems Message-ID: <20000405153914.A13658@dogma.freebsd-uk.eu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from n_hibma@calcaphon.com on Wed, Apr 05, 2000 at 02:31:55PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone recall seeing or making a remark about a group of interrupts or hardware port locations that could be causing this problem? I was searching my email and i can't find it. Someone said 4.0 allocates a group of hardware locations (0x380-0x3f0?) differently from 3.4, and that this may affect the parallel port allocation on laptops. Has anyone had this zip timeout error on a desktop machine and not been able to fix it? jm -- ------------------------------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org To Microsoft: "Your tyranny I was part of, is now cracking on every side. Now your own life is in danger. Your Empire is on fire." Front 242 ------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message