Re: Parallel port zip drives - inventory of working and non-working systems

[J McKitrick]

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 -- [EMAIL PROTECTED]   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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Parallel port zip drives - inventory of working and non-working systems

[Walter Brameld]

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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message