T
tony.yanez
We are deploying WinXP on IBM X205-8480 eServer. On this hardware
there are different revisions of the same ethernet adapter.
Under Windows NT, this was never a problem, the existing drivers worked
for all flavors of the network adapter. XP is more selective and if we
install our existing image (built with flavor A of the NIC) on a system
with flavor B of the NIC, XP creates a new instance of Local Area
Connection ("Local Area Connection 1") in the network configuration.
Unfortunately XP is using some defaults that we would like different.
For example, DHCP is enabled. We would like to use a static IP
Address.
So here are the questions:
1) Is there any way to convince XPe to use the existing Local Area
Connection (with the correct configuration already set) instead of
creating a new one?
If not, then
2) How does XP determine which defaults to use? We would like to use a
static IP Address.
there are different revisions of the same ethernet adapter.
Under Windows NT, this was never a problem, the existing drivers worked
for all flavors of the network adapter. XP is more selective and if we
install our existing image (built with flavor A of the NIC) on a system
with flavor B of the NIC, XP creates a new instance of Local Area
Connection ("Local Area Connection 1") in the network configuration.
Unfortunately XP is using some defaults that we would like different.
For example, DHCP is enabled. We would like to use a static IP
Address.
So here are the questions:
1) Is there any way to convince XPe to use the existing Local Area
Connection (with the correct configuration already set) instead of
creating a new one?
If not, then
2) How does XP determine which defaults to use? We would like to use a
static IP Address.