Actually, it probably is a pretty bare-bones clone of lp.c. It was
written as a masters project and I haven't had much time to work on
it. The problem with these multiplexors is that they don't let you know
they are there to start with and other than that they are really
dumb. Really, the ideal solution would be to take most of the code from
lp and modify it so that it will switch the ports.
On Fri, 2 Feb 2001, Mike Murphy wrote:
> From looking at the parswitch driver, it seems the hard part is determining
> how to communicate with my multiplexor to get it to switch. parswitch
> appears to be a bare-bones clone of lp.c; is this an accurate assessment?
> Thanks for your help.
> ----- Original Message -----
> From: "Tim Waugh" <firstname.lastname@example.org>
> To: "Mike Murphy" <email@example.com>
> Cc: <firstname.lastname@example.org>
> Sent: Friday, February 02, 2001 9:03 AM
> Subject: Re: [PARPORT] Port Multiplexor Problem
> On Fri, Feb 02, 2001 at 08:21:04AM -0800, Mike Murphy wrote:
> > I recently purchased what I believed to be a port multiplexor (4
> > way), but the parport driver doesn't seem to recognize it and only
> > recognizes whichever printer is currently selected on the device. I
> > suspect the multiplexor doesn't speak the 1284.3 protocol, if this
> > is even a possibility (haven't read the spec or have much experience
> > with these devices). It comes with some windows software which will
> > (allegedly) operate the autoswitch.
> There certainly are non-IEEE1284.3 multiplexors out there. For
> -- To unsubscribe, send mail to: email@example.com --
> -- with the single word "unsubscribe" in the body of the message. --
-- 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 : Sun Feb 04 2001 - 01:36:10 EST