Also, some motherboards sporting integrated LAN don't like other NIC's being
installed.. more often than not, the integrated card has to be disabled in
BIOS..

--
Mike Hall
MVP - Windows Shell/User


"xfile" <cou-cou@remove.nospam.com> wrote in message
news:%23r6SoIYFGHA.3176@TK2MSFTNGP12.phx.gbl...
> Hi,
>
> Just to share with you for something I just learned and many may not aware
> of it:
>
> If you're installing a second NIC, you may find Windows (Server 2003 or
> XP) may not recognize it (not list in device manager) or has it listed
> with a yellow exclamation mark.
>
> If that happens and you're sure the NIC is good, you may wish to change it
> to a different PCI slot before doing something else, such as find a new
> driver, calling vendor, returning the card, and so on.
>
> It turned out that some (or all, for which I don't know) motherboards will
> have resource conflicts at certain PCI slots due to resources sharing.
> Well, I don't know specific reasons and how they do it, but that's how I
> have learned from Asus.
>
> So changing it to another PCI slot could solve the problem.
>
> That happened to us when we were trying a second NIC card. After we moved
> the card from slot 2, slot 3, to slot 5, it works out fine.
>
> We did turn off the onboard LAN chip just to ensure the second card would
> be detected when we changed it to a different PCI slot.
>
> Interesting enough, even the vendor of NIC (ZyXEL in this case) did not
> know this could be a problem and we shared with them also after we found
> out and solved the problem.
>
> Hope this helps those who will be installing a second NIC in the future.
>
>
>

Hi,

Just to share with you for something I just learned and many may not aware
of it:

If you're installing a second NIC, you may find Windows (Server 2003 or XP)
may not recognize it (not list in device manager) or has it listed with a
yellow exclamation mark.

If that happens and you're sure the NIC is good, you may wish to change it
to a different PCI slot before doing something else, such as find a new
driver, calling vendor, returning the card, and so on.

It turned out that some (or all, for which I don't know) motherboards will
have resource conflicts at certain PCI slots due to resources sharing.
Well, I don't know specific reasons and how they do it, but that's how I
have learned from Asus.

So changing it to another PCI slot could solve the problem.

That happened to us when we were trying a second NIC card. After we moved
the card from slot 2, slot 3, to slot 5, it works out fine.

We did turn off the onboard LAN chip just to ensure the second card would be
detected when we changed it to a different PCI slot.

Interesting enough, even the vendor of NIC (ZyXEL in this case) did not know
this could be a problem and we shared with them also after we found out and
solved the problem.

Hope this helps those who will be installing a second NIC in the future.

"xfile" <cou-cou@remove.nospam.com> wrote in message
news:%23r6SoIYFGHA.3176@TK2MSFTNGP12.phx.gbl...
> Hi,
>
> Just to share with you for something I just learned and many may not aware
> of it:
>
> If you're installing a second NIC, you may find Windows (Server 2003 or
> XP) may not recognize it (not list in device manager) or has it listed
> with a yellow exclamation mark.
>
> If that happens and you're sure the NIC is good, you may wish to change it
> to a different PCI slot before doing something else, such as find a new
> driver, calling vendor, returning the card, and so on.

<snip>

Although I've never had a problem installing a 2nd NIC in XP...
I have *never* been able to remove it in device manager (show hidden)
if I physically remove the card from the machine.

I have posted about that many times on Usenet and never gotten an answer
either !

"philo" <philo@privacy.net> wrote in message
news:e5syghYFGHA.984@tk2msftngp13.phx.gbl...
>
> "xfile" <cou-cou@remove.nospam.com> wrote in message
> news:%23r6SoIYFGHA.3176@TK2MSFTNGP12.phx.gbl...
> > Hi,
> >
> > Just to share with you for something I just learned and many may not
aware
> > of it:
> >
> > If you're installing a second NIC, you may find Windows (Server 2003 or
> > XP) may not recognize it (not list in device manager) or has it listed
> > with a yellow exclamation mark.
> >
> > If that happens and you're sure the NIC is good, you may wish to change
it
> > to a different PCI slot before doing something else, such as find a new
> > driver, calling vendor, returning the card, and so on.
>
> <snip>
>
> Although I've never had a problem installing a 2nd NIC in XP...
> I have *never* been able to remove it in device manager (show hidden)
> if I physically remove the card from the machine.
>
> I have posted about that many times on Usenet and never gotten an answer
> either !

Proper policy would be to
remove it from Device Manager BEFORE physically
removing it in any circumstance.

>
>

<snip>
>
> Proper policy would be to
> remove it from Device Manager BEFORE physically
> removing it in any circumstance.


I'll have to give that a try.

(of course having the listing there does not seem to hurt anything)

Put this into a little batch file:

set devmgr_show_nonpresent_devices=1
cd\ %SystemRoot% \System32
start devmgmt.msc


When the device manager opens select the show hidden devices, you will now be able to see the items
that are no longer physically present. The icons for these items will be dimmed out when you expand
their tree.
--
Dave Vair
CNE, CNA, MCP, A+, N+

"philo" <philo@privacy.net> wrote in message news:e5syghYFGHA.984@tk2msftngp13.phx.gbl...
>
> "xfile" <cou-cou@remove.nospam.com> wrote in message
> news:%23r6SoIYFGHA.3176@TK2MSFTNGP12.phx.gbl...
>> Hi,
>>
>> Just to share with you for something I just learned and many may not aware of it:
>>
>> If you're installing a second NIC, you may find Windows (Server 2003 or XP) may not recognize it
>> (not list in device manager) or has it listed with a yellow exclamation mark.
>>
>> If that happens and you're sure the NIC is good, you may wish to change it to a different PCI
>> slot before doing something else, such as find a new driver, calling vendor, returning the card,
>> and so on.
>
> <snip>
>
> Although I've never had a problem installing a 2nd NIC in XP...
> I have *never* been able to remove it in device manager (show hidden)
> if I physically remove the card from the machine.
>
> I have posted about that many times on Usenet and never gotten an answer either !
>

You might also get problems if you have 2 identical NICs, as a lot of the
DRIVERS don't understand that.


--
Tumppi
=================================
Most learned on these newsgroups
Helsinki, FINLAND
(translations from/to FI not always accurate
=================================




"xfile" <cou-cou@remove.nospam.com> kirjoitti
viestissä:%23r6SoIYFGHA.3176@TK2MSFTNGP12.phx.gbl. ..
> Hi,
>
> Just to share with you for something I just learned and many may not aware
> of it:
>
> If you're installing a second NIC, you may find Windows (Server 2003 or
> XP) may not recognize it (not list in device manager) or has it listed
> with a yellow exclamation mark.
>
> If that happens and you're sure the NIC is good, you may wish to change it
> to a different PCI slot before doing something else, such as find a new
> driver, calling vendor, returning the card, and so on.
>
> It turned out that some (or all, for which I don't know) motherboards will
> have resource conflicts at certain PCI slots due to resources sharing.
> Well, I don't know specific reasons and how they do it, but that's how I
> have learned from Asus.
>
> So changing it to another PCI slot could solve the problem.
>
> That happened to us when we were trying a second NIC card. After we moved
> the card from slot 2, slot 3, to slot 5, it works out fine.
>
> We did turn off the onboard LAN chip just to ensure the second card would
> be detected when we changed it to a different PCI slot.
>
> Interesting enough, even the vendor of NIC (ZyXEL in this case) did not
> know this could be a problem and we shared with them also after we found
> out and solved the problem.
>
> Hope this helps those who will be installing a second NIC in the future.
>
>
>

I just installed a third LAN adapter (in addition to the two that are part
of the M/B) because Windows Vista didn't recognize the on-board LAN
selections and manufacturer drivers (Nvidia) are not available yet - that
work! All three connections will work within Windows XP, depending upon
which one I have connected when I bootup the system.

Yes, I am dual booting. Actually I boot between many operating systems.

--


Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

"philo" <philo@privacy.net> wrote in message
news:e5syghYFGHA.984@tk2msftngp13.phx.gbl...
>
> "xfile" <cou-cou@remove.nospam.com> wrote in message
> news:%23r6SoIYFGHA.3176@TK2MSFTNGP12.phx.gbl...
>> Hi,
>>
>> Just to share with you for something I just learned and many may not
>> aware of it:
>>
>> If you're installing a second NIC, you may find Windows (Server 2003 or
>> XP) may not recognize it (not list in device manager) or has it listed
>> with a yellow exclamation mark.
>>
>> If that happens and you're sure the NIC is good, you may wish to change
>> it to a different PCI slot before doing something else, such as find a
>> new driver, calling vendor, returning the card, and so on.
>
> <snip>
>
> Although I've never had a problem installing a 2nd NIC in XP...
> I have *never* been able to remove it in device manager (show hidden)
> if I physically remove the card from the machine.
>
> I have posted about that many times on Usenet and never gotten an answer
> either !
>

It's also a recognised fact that IRQ conflicts DO happen on the PCI bus,
even though the theory says they shouldn't. This is often the cause of slow
or erratic network transfers, intermittent sound, etc.

"David Vair" <dvair@nycap.rr.com> wrote in message
news:TmFwf.92236$ME5.4062@twister.nyroc.rr.com...
> Put this into a little batch file:
>
> set devmgr_show_nonpresent_devices=1
> cd\ %SystemRoot% \System32
> start devmgmt.msc
>
>
> When the device manager opens select the show hidden devices, you will now
> be able to see the items that are no longer physically present. The icons
> for these items will be dimmed out when you expand their tree.


Yes
I can see the non-present devices
but cannot delete the non-present NIC card
but it's not hurting anything...
so I will leave it alone

Not sure , but you may have to remove the Packet Scheduler Miniport one first, then remove the card.
--
Dave Vair
CNE, CNA, MCP, A+, N+

"philo" <philo@privacy.net> wrote in message news:%23cUQdElFGHA.1032@TK2MSFTNGP15.phx.gbl...
>
> "David Vair" <dvair@nycap.rr.com> wrote in message
> news:TmFwf.92236$ME5.4062@twister.nyroc.rr.com...
>> Put this into a little batch file:
>>
>> set devmgr_show_nonpresent_devices=1
>> cd\ %SystemRoot% \System32
>> start devmgmt.msc
>>
>>
>> When the device manager opens select the show hidden devices, you will now be able to see the
>> items that are no longer physically present. The icons for these items will be dimmed out when
>> you expand their tree.
>
>
> Yes
> I can see the non-present devices
> but cannot delete the non-present NIC card
> but it's not hurting anything...
> so I will leave it alone
>

Nobody else asked, so I will. What board? I have two nic's in my hp zd8000
with no problems and two on my Asus p4s533. If you count my usb adapter, I
have 3.


"xfile" <cou-cou@remove.nospam.com> wrote in message
news:%23r6SoIYFGHA.3176@TK2MSFTNGP12.phx.gbl...
> Hi,
>
> Just to share with you for something I just learned and many may not aware
> of it:
>
> If you're installing a second NIC, you may find Windows (Server 2003 or
> XP) may not recognize it (not list in device manager) or has it listed
> with a yellow exclamation mark.
>
> If that happens and you're sure the NIC is good, you may wish to change it
> to a different PCI slot before doing something else, such as find a new
> driver, calling vendor, returning the card, and so on.
>
> It turned out that some (or all, for which I don't know) motherboards will
> have resource conflicts at certain PCI slots due to resources sharing.
> Well, I don't know specific reasons and how they do it, but that's how I
> have learned from Asus.
>
> So changing it to another PCI slot could solve the problem.
>
> That happened to us when we were trying a second NIC card. After we moved
> the card from slot 2, slot 3, to slot 5, it works out fine.
>
> We did turn off the onboard LAN chip just to ensure the second card would
> be detected when we changed it to a different PCI slot.
>
> Interesting enough, even the vendor of NIC (ZyXEL in this case) did not
> know this could be a problem and we shared with them also after we found
> out and solved the problem.
>
> Hope this helps those who will be installing a second NIC in the future.
>
>
>

Hi,

In this case, this is Asus P4P800 - this is for sure.

We also have P4P800 SE, and if I remembered correctly, it has similar
problems as well, but I did not "see" it with my own eyes.


"Joel" <joel@invalide.aol.com> wrote in message
news:%23bsJ6IoFGHA.2320@TK2MSFTNGP11.phx.gbl...
> Nobody else asked, so I will. What board? I have two nic's in my hp zd8000
> with no problems and two on my Asus p4s533. If you count my usb adapter, I
> have 3.
>
>
> "xfile" <cou-cou@remove.nospam.com> wrote in message
> news:%23r6SoIYFGHA.3176@TK2MSFTNGP12.phx.gbl...
>> Hi,
>>
>> Just to share with you for something I just learned and many may not
>> aware of it:
>>
>> If you're installing a second NIC, you may find Windows (Server 2003 or
>> XP) may not recognize it (not list in device manager) or has it listed
>> with a yellow exclamation mark.
>>
>> If that happens and you're sure the NIC is good, you may wish to change
>> it to a different PCI slot before doing something else, such as find a
>> new driver, calling vendor, returning the card, and so on.
>>
>> It turned out that some (or all, for which I don't know) motherboards
>> will have resource conflicts at certain PCI slots due to resources
>> sharing. Well, I don't know specific reasons and how they do it, but
>> that's how I have learned from Asus.
>>
>> So changing it to another PCI slot could solve the problem.
>>
>> That happened to us when we were trying a second NIC card. After we
>> moved the card from slot 2, slot 3, to slot 5, it works out fine.
>>
>> We did turn off the onboard LAN chip just to ensure the second card would
>> be detected when we changed it to a different PCI slot.
>>
>> Interesting enough, even the vendor of NIC (ZyXEL in this case) did not
>> know this could be a problem and we shared with them also after we found
>> out and solved the problem.
>>
>> Hope this helps those who will be installing a second NIC in the future.
>>
>>
>>
>
>