From: "Robert Comer" 

> You guys do realize the alternative is you have to find an open IRQ, edit
> config.sys and autoexec.bat to both load the driver and assign it to that
> open IRQ and then if you move it to another port you have to go back and
> redo all this.. Course you only have to copy the driver to C:\util one
> time
> so it does address your complaint... 

That's not the only alternative, a slightly smarter PnP that really worked
is all that's needed.

--
Bob Comer


"Geo"  wrote in message
news:450e06c1$1{at}w3.nls.net...
> You guys do realize the alternative is you have to find an open IRQ, edit
> config.sys and autoexec.bat to both load the driver and assign it to that
> open IRQ and then if you move it to another port you have to go back and
> redo all this.. Course you only have to copy the driver to C:\util one
> time
> so it does address your complaint... 
>
> Geo.
>
> "Robert Comer"  wrote in message
> news:450d809b$1{at}w3.nls.net...
>> > I had thought that bit of foolishness would have been fixed in versions
>> > of Windows subsequent to the aging Windows 2000 that I am using here, I
>> > guess I overestimated Microsoft's concern about usability.
>>
>> The same thing happens for other interfaces too, just move your NIC or
>> PCI
>> modem card to another slot on the motherboard, it'll require installing
>> drivers again.  I never could understand why, it should take inventory of
>> already installed drivers and use the right one if already there.  Vista
> is
>> no better at it...
>>
>> --
>> Bob Comer
>>
>>
>> "/m"  wrote in message
>> news:q8mqg2thmpdiqb9gr2d4lu2tgiqpkd3q95{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.
>> >
>> > I ran into that problem with Windows 2000 and the USB-based audio
>> > device
>> > I had been using*.  When I moved the device from one USB port to
>> > another, I had to reinstall the drivers for that second port, drivers
>> > that were already installed for the first port.  I also noticed a
>> > similar occurrence when I plugged my PC Card wireless NIC into a
>> > different slot than the one in which I had originally installed it.
>> >
>> > I had thought that bit of foolishness would have been fixed in versions
>> > of Windows subsequent to the aging Windows 2000 that I am using here, I
>> > guess I overestimated Microsoft's concern about usability.
>> >
>> > /m
>> >
>> >
>> > * - past tense is used because I now use a MacMini (and AirPort
>> > Express)
>> > for my audio stuff, and I have left that particular foolishness of
>> > Windows behind...
>>
>>
>
>

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