A7N8X and on board 3COM disabling??

[Chris Wilson]

I have "removed" the on board 3COM LAN card from my hardware list, and
each time I reboot Windows 2000 it"finds" the new hardware. The 3COM
stuff is
built on the motherboard, an Asus A7N8X, along with NVidia networking,
which I am using. How do I stop this each time I need to reboot please? I

"removed" the 3COM hardware via the Control Panel - Add / Remove hardware

tool.

Thanks.

 

[James]

I have "removed" the on board 3COM LAN card from my hardware list, and
each time I reboot Windows 2000 it"finds" the new hardware. The 3COM
stuff is
built on the motherboard, an Asus A7N8X, along with NVidia networking,
which I am using. How do I stop this each time I need to reboot please? I

"removed" the 3COM hardware via the Control Panel - Add / Remove hardware

tool.

Thanks.
--

You can turn it off in the bios. Can't remember where, but if you
look, you will find it.

 

[D R Tester]

Why do you want to remove it, if it is causing probs you could always
disable it in the hardware profile.

Dom

 

[Chris Wilson]

You can turn it off in the bios. Can't remember where, but if you
look, you will find it.

Found it, and the pause as Windows loaded whilst I presume the 3COM stuff
was checking out possible connections and then reporting with a pop up
has gone. Thanks a lot!

 

[Chris Wilson]

Why do you want to remove it, if it is causing probs you could always
disable it in the hardware profile.

Dom

t was causing a pause after Windows loaded, possibly as it was seeking a
connection? Then the pop up with the 3COM logo appeared and the pause
cleared. Disabling in the BIOS has sorted it, thanks.

 

[MAC]

I have "removed" the on board 3COM LAN card from my hardware list, and
each time I reboot Windows 2000 it"finds" the new hardware.

First disable the card in the Bios.

 

[Kyle Brant]

Found it, and the pause as Windows loaded whilst I presume the 3COM stuff
was checking out possible connections and then reporting with a pop up
has gone. Thanks a lot!

--

The delay you were experiencing is the 3com NIC looking for a DHCP server to
receive assignment of an IP. Assigning a fixed IP to the 3com NIC would
eliminate the delay.

 

[Chris Wilson]

The delay you were experiencing is the 3com NIC looking for a DHCP server to
receive assignment of an IP. Assigning a fixed IP to the 3com NIC would
eliminate the delay.

Thanks Kyle, I am using Netbui at the moment, but will enter the
terrifying world of TCP/IP in the near future as this will make the file
transfers faster, right? Thanks very much for the reply, this "dirty" fix

by disabling will do for now, TCP/IP is not something I have had good
experiences with <VBG>

--



Best Regards,
Chris.

 

[Ben Pope]

Thanks Kyle, I am using Netbui at the moment, but will enter the
terrifying world of TCP/IP in the near future as this will make the file
transfers faster, right? Thanks very much for the reply, this "dirty" fix

by disabling will do for now, TCP/IP is not something I have had good
experiences with <VBG>

You're connected to the net aren't ya'?

The only thing you need to know really are the IP ranges assigned for LANs,
as well as localhost.

127.0.0.1 always refers to localhost (your machine)

192.168.x.y is your standard class B subnet, you are allowed to specify x
from 1 to 255 inclusive (usually 0 for the first LAN, 1 for the second etc.)
and y from 1 (usually the router/gateway to another network) to 254. y =
255 specifies a broadcast, y = 0 I don't recall, but might not go anywhere.
Another subnet is 10.x.y.z suitable for ~65K to 16M machines on your subnet.

What that basically means is that you set your machine thats hooked up to
the net to 192.168.0.1 on your internal subnet, and all other machines on
that subnet to 192.168.0.x where 2 <= x <= 254.

Your subnet mask specifies which adresses are on a particular subnet and
which are on another subnet. Usually you simply set it to 255.255.255.0 and
then you can directly access machines with an IP of 192.168.0.x for all x.
255.255.0.0 and you'll be able to directly access machines for all x and y,
both are valid and widely used.

The gateway is the machine that deals with requests to IP addresses that do
not meet the mask - usually considered to be machines on the internet.

Then there's DHCP which is there to set up all of these IP addresses
automatically (The IP address of the interface, the mask and the gateway) -
with dialup your ISP usually has a DHCP server and assigns your modem an IP
address. With broadband using a USB modem, the same happens. With a modem
connected via ethernet, what happens is that your modem is assigned the IP
address, then you have to either set your gateway to be the IP address of
the modem (often 192.168.x.1 where I usually see x=1 or 100, but any value
(0-255) is valid), or your modem will have a DHCP server and be able to sort
it for you. Usually your ethernet modem will be predefined to be on a
192.168.x.y stlye address so your machine will have to take on an IP adress
of the same form.

I've been a little inconsistent with my terminology, a machine can have
multiple IP addresses, one for each network device - often your network card
will have an IP address, your modem will have an ip address, and if
connected to your machine via not ethernet you can consider your machine to
have that IP address too and of course, 127.0.0.1 is also always the machine
your using.

Ben

 

[jeff s]

You're connected to the net aren't ya'?

The only thing you need to know really are the IP ranges assigned for LANs,
as well as localhost.

127.0.0.1 always refers to localhost (your machine)

192.168.x.y is your standard class B subnet, you are allowed to specify x

actually that's where class C addresses begin, Class B is from
128.0.0.0 to 191.255.255.255.255. Minor mistake.

from 1 to 255 inclusive (usually 0 for the first LAN, 1 for the second etc.)
and y from 1 (usually the router/gateway to another network) to 254. y =
255 specifies a broadcast, y = 0 I don't recall, but might not go anywhere.

the .0 would be the subnet address and is used for routing. Not an
issue in your discussion.

Another subnet is 10.x.y.z suitable for ~65K to 16M machines on your subnet.

What that basically means is that you set your machine thats hooked up to
the net to 192.168.0.1 on your internal subnet, and all other machines on
that subnet to 192.168.0.x where 2 <= x <= 254.

Your subnet mask specifies which adresses are on a particular subnet and
which are on another subnet. Usually you simply set it to 255.255.255.0 and
then you can directly access machines with an IP of 192.168.0.x for all x.
255.255.0.0 and you'll be able to directly access machines for all x and y,
both are valid and widely used.

The gateway is the machine that deals with requests to IP addresses that do
not meet the mask - usually considered to be machines on the internet.

Then there's DHCP which is there to set up all of these IP addresses
automatically (The IP address of the interface, the mask and the gateway) -
with dialup your ISP usually has a DHCP server and assigns your modem an IP
address. With broadband using a USB modem, the same happens. With a modem
connected via ethernet, what happens is that your modem is assigned the IP
address, then you have to either set your gateway to be the IP address of
the modem (often 192.168.x.1 where I usually see x=1 or 100, but any value
(0-255) is valid), or your modem will have a DHCP server and be able to sort
it for you. Usually your ethernet modem will be predefined to be on a
192.168.x.y stlye address so your machine will have to take on an IP adress
of the same form.

I've been a little inconsistent with my terminology, a machine can have
multiple IP addresses, one for each network device - often your network card
will have an IP address, your modem will have an ip address, and if
connected to your machine via not ethernet you can consider your machine to
have that IP address too and of course, 127.0.0.1 is also always the machine
your using.

Ben

jeff

 

[Ben Pope]

actually that's where class C addresses begin, Class B is from
128.0.0.0 to 191.255.255.255.255. Minor mistake.

Class B subnet means 16 bit mask, for the set of addresses 192.168.x.y you
use a 16 bit mask, making it a Class B subnet.

Class B addresses do indeed have the range you mentioned.

Class A addresses have the first bits of the address clear, Class B is the
first bit set, Class C the first 2 bits set etc., giving ranges 0 to 127,
128 to 191, 192 to 223 and so on to Class E which is 240 to 255 and has the
first 4 bits of the address set.

the .0 would be the subnet address and is used for routing. Not an
issue in your discussion.

It is an issue in my discussion since you're not allowed to assign it to a
machine.

Ben