Date: Wed, 5 Apr 2000 15:39:14 +0100 From: J McKitrick <jcm@freebsd-uk.eu.org> To: Nick Hibma <n_hibma@calcaphon.com> Cc: FreeBSD STABLE Mailing List <stable@freebsd.org>, FreeBSD CURRENT Mailing List <current@freebsd.org> Subject: Re: Parallel port zip drives - inventory of working and non-working systems Message-ID: <20000405153914.A13658@dogma.freebsd-uk.eu.org> In-Reply-To: <Pine.BSF.4.20.0004051427180.2058-100000@localhost>; from n_hibma@calcaphon.com on Wed, Apr 05, 2000 at 02:31:55PM %2B0100 References: <Pine.BSF.4.20.0004051427180.2058-100000@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000405153914.A13658>