> This is covered in the thread I referred you to. My work-arounds (as
> distinct from my fix) _don't_ require messing with the driver. Among
> other things, you can simply disable and re-enable the device in
> hardware manager to run IPCONFIG -- just do it before the auto-disable
> kicks back in.

Ok, sorry, maybe I didn't read enough of the thread. When I used
google to view the thread, it only showed me three postings, and they
seemded all to be about rolling back the driver. I will go and look
again.

> How about encouraging the folks in your company to fix their driver
> problem? Trying to get them to take notice of this issue has been
> futile and frustrating for me -- your company seems uninterested in bug
> reports to the point of making it very difficult to submit them
> (reminding me of former arrogance I thought it had put behind it).

Yes, this seems like the right solution long term. I will try to find
you the right people to get the bug report noticed. I don't know if I
will have any better luck getting them to notice, but I will try.

-Chris