> I don't know if there's a way to stop this, but it's normal, whenever I use
> my Parallel port zip drive, I have similar problems.
There isn't, really. The parallel port is terribly inefficient.
> > But what surprises me is that copying that data to the parallel intfc burns
> > up an incredible amount of CPU. Until the document is printed, there's a
> > steady bg buzz of ~10% CPU use, with periods of 50% and even 100% CPU
> > utilization by the 'parallel'[1] process. The load is sufficient that it
> > locks out the mouse on X (interrupt blocking?).
> >
> > Anyone care to comment? Does this sound normal? Is there a way to reduce
> > the amount of CPU needed to drive the parallel port?
Get a USB printer, or a USB-parallel adapter cable. It won't necessarily
be much faster, but it will use a lot less CPU. The cables are pretty
cheap (< $30), and they're mostly based on a single design that's known
to work.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
