From: "Gary Britt" 

Thanks.

The user still has to select the correct printer driver when printing or
change the default to the correct driver.  You only have to do this once
though for each time the USB cable gets moved and it prevents the new
hardware detected install driver routine from coming up on the next boot
after the USB cable gets moved.  To know which one is the correct one to
pick, if you hold the mouse over the printer drivers one by one when asked
to select a printer, the  tooltip will show "Not Ready" or
"Offline" for the ones not connected and "Ready" for
the one that is connected.

Gary

"Mike N."  wrote in message
news:sbkqg29bl0g3p5abbtfs5vng8h5skmge9u{at}4ax.com...
> On Sat, 16 Sep 2006 18:04:06 -0400, "Gary Britt"
 wrote:
>
>>Are you running into a problem with the fact that a printer driver
>>installed
>>for a particular USB receptacle/port won't communicate with the very same
>>printer if its USB cable gets moved to a different USB receptacle/port.
>
>  That could explain 2 of the cases where the communication just quit.  I
> used to visualize the USB connection as a simple transport.  If the driver
> found its device on the other end, it could just talk via whatever
> transport is available.   But Now I have seen several cases where a unique
> signature is created that includes the port number.   The most extreme
> case
> I have seen is an IEEE 488 USB adapter that WIndows would detect as a new
> device based on what was plugged into the far end.   If one of the remote
> devices were powered off, it would force a 'detected new hardware' cycle,
> and driver reinstall.
>
>   That's a good tip about creating multiple installs with different USB
> ports so there'll always be something present when printing.

--- BBBS/NT v4.01 Flag-5