Re: My motherboard has a bottle neck - BTW

Using a static TCP/IP address will not allow the particular PC direct access the internet with that connection.

Should you want this PC to access the internet, you will have to enable DHCP (which disables the static address), and connect the network cable to your modem-router. No reboot is required. If your motherboard has 2 RJ45 outlets, then you can configure one with DHCP for internet use, the other with a static TP/IP address for the internal network...unless of course your ISP provider gives you a permanent static TCP/IP address for your internet connection.

Best advice I can give is not to allow all production PCs in the network to access the internet. Use a laptop or another PC....and USB thumb drives to transfer update/files. There are other ways such as using a Guest Account to access the Net since Guest Acounts have no installation rights and will not accept .exe files, etc. But I have found that denial is the best. Tedious, but ultimately 99.99% safe. This way, you can also do away with anti-virus software on the production PCs...as long as you scan before introducing new files from the USB thumb drive. Another benefit is that without an internet cache building up, XP will consistently boot up within about 20-40secs all the time as if it were just freshly installed. This has been my modus operandi for years now...and life with XP SP1 has been sweet (don't even need SP2 or 3 with all their extra security!).

Thomas