MN-510 not recognized until remove/insert on Win 2000

All my other USB devices are OK. USB host controller
drivers for Intel ICH3 are standard Microsoft. Also tried
plugging into a PCI-USB adapter with NEC EHCI/OHCI
controller. Same, MN-510 is never recognized until I
remove/insert. Cold and warm boot, same difference.

Anybody seeing this???


DaveR

This may sound strange but is your BIOS flashed with the latest version?

DaveR wrote:

> All my other USB devices are OK. USB host controller
> drivers for Intel ICH3 are standard Microsoft. Also tried
> plugging into a PCI-USB adapter with NEC EHCI/OHCI
> controller. Same, MN-510 is never recognized until I
> remove/insert. Cold and warm boot, same difference.
>
> Anybody seeing this???

No, it's not strange, joker, I'm a BIOS engineer and I
know the BIOS can do the most amazing things to perfectly
good hardware!

I should have listed more details, so here they are -

I have the latest BIOS for my Intel 815EA board. The
drivers are all Microsoft standard, even for the NEC
controller. I didn't need the drivers from the CD that
came with it.

I have all OS updates that might remotely bear on the
problem.

I have a dialog going with Microsoft tech support. The
first suggestion from them was that some power management
registers weren't being saved by the BIOS, obviously
confusing an S3 or S4 sleep state with power off. So I
haven't gotten anywhere with them.

The problem follows the adapter regardless of the physical
USB port. And now I've tried it on 2 Intel and 1 NEC
controller, behaves all the same.

When the adapter is plugged in for the first time into a
new controller, there is an error dialog after the "Found
new device.." dialog. I can't make it happen right now,
but I remember it said there was no instance of that
device. I should have screen-shot it, maybe I'll hack the
registry to make it happen again.

Appreciate your time.



>-----Original Message-----
>This may sound strange but is your BIOS flashed with the
latest version?
>
>DaveR wrote:
>
>> All my other USB devices are OK. USB host controller
>> drivers for Intel ICH3 are standard Microsoft. Also
tried
>> plugging into a PCI-USB adapter with NEC EHCI/OHCI
>> controller. Same, MN-510 is never recognized until I
>> remove/insert. Cold and warm boot, same difference.
>>
>> Anybody seeing this???
>
>.
>

Having the same problem on an intel D845WN board...
>-----Original Message-----
>No, it's not strange, joker, I'm a BIOS engineer and I
>know the BIOS can do the most amazing things to
perfectly
>good hardware!
>
>I should have listed more details, so here they are -
>
>I have the latest BIOS for my Intel 815EA board. The
>drivers are all Microsoft standard, even for the NEC
>controller. I didn't need the drivers from the CD that
>came with it.
>
>I have all OS updates that might remotely bear on the
>problem.
>
>I have a dialog going with Microsoft tech support. The
>first suggestion from them was that some power
management
>registers weren't being saved by the BIOS, obviously
>confusing an S3 or S4 sleep state with power off. So I
>haven't gotten anywhere with them.
>
>The problem follows the adapter regardless of the
physical
>USB port. And now I've tried it on 2 Intel and 1 NEC
>controller, behaves all the same.
>
>When the adapter is plugged in for the first time into a
>new controller, there is an error dialog after
the "Found
>new device.." dialog. I can't make it happen right now,
>but I remember it said there was no instance of that
>device. I should have screen-shot it, maybe I'll hack
the
>registry to make it happen again.
>
>Appreciate your time.
>
>
>
>>-----Original Message-----
>>This may sound strange but is your BIOS flashed with
the
>latest version?
>>
>>DaveR wrote:
>>
>>> All my other USB devices are OK. USB host controller
>>> drivers for Intel ICH3 are standard Microsoft. Also
>tried
>>> plugging into a PCI-USB adapter with NEC EHCI/OHCI
>>> controller. Same, MN-510 is never recognized until I
>>> remove/insert. Cold and warm boot, same difference.
>>>
>>> Anybody seeing this???
>>
>>.
>>
>.
>