>My guess is that the parport sharing code is causing some sort of
>bottleneck which is only showing up on the slow 486. When the laptop is
>using the 2.0.3 PLIP code (no parport sharing), it communicates fine with
>the PIII which is using the more modern PLIP (sharing) code.
I doubt this is the problem. The parport sharing code isn't *that*
Does PLIP think it's using interrupts? (Check with dmesg.) It might be
falling back to polled operation, which always brings a large performance hit.
-- To unsubscribe, send mail to: firstname.lastname@example.org --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2b29 : Thu Aug 23 2001 - 17:36:34 EDT