Date: Wed, 5 Apr 2000 19:36:17 -0400 From: Walter Brameld <brameld@twave.net> To: J McKitrick <jcm@freebsd-uk.eu.org>, 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: <00040519372802.01864@Bozo_3.BozoLand.domain> In-Reply-To: <20000405153914.A13658@dogma.freebsd-uk.eu.org> References: <Pine.BSF.4.20.0004051427180.2058-100000@localhost> <20000405153914.A13658@dogma.freebsd-uk.eu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 05 Apr 2000, in a never-ending search for enlightenment, J McKitrick wrote: > 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? My problem was it stopped working when I went to 4.0. When I changed my BIOS setting the parallel port to EPP, it started working again. -- Walter Brameld Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? Walter: And what does THIS button do?? 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?00040519372802.01864>