Actually, that's not really the right way to go about it.
Depending on if you are using an Ethernet connection to either a router or a modem, these settings should be set accordingly for either DHCP or static IP. In the case of an ISP serving up DHCP (and not a DHCP serving Router) to your workstation, you should leave the settings on the default DHCP where XP will obtain the settings automatically.
If your ISP requires setting a static address for DNS, you should go ahead and input those settings; however, in most cases, DNS is served by DHCP, thus having it discover the settings automatically (as is the default setting in XP) is appropriate. Even users with Home Networks (IE using a switched/router like a NetGear RT314, etc...) should use the XP default settings.
The correct configuration for most users that have a slow boot due to a failed DHCP discovery is to simply click the "Repair" Icon under Network Settings. This will force a DHCP discovery. Rebooting immediately after will set the registers to use these settings as the default thus fixing the slowness issues for WAN problems.
All of this is assuming that you have attempted to configure the system for networking via the, "Network Setup Wizard" and are still having lags or delays after bootup. In 99% of our deployments, this has been the best way to go about getting a good configuration. Remember however that you will need to either change all of your other systems to use the "MSHOME" workgroup, or better yet, simply change your new XP system to indicate the actual Workgroup your other systems are already using.
I should note that most of the time, slow network startup issues are not from WAN connection failures but rather the system looking for other LAN systems in the defined workgroup. The default, "MSHOME" workgroup tends to be the real culprit here since almost nobody has a network with computers in that default workgroup.
The IP address 192.168.0.1 with the subnet mask of 255.255.255.0 is actually the default address for about 99% of the switched or bridged routers out there, thus most of the time using this address will actually create a conflict (versus resolving one) so I wouldn't recommend using it.
Finally, don't forget that XP is a Server OS. If you want two-way access (remote assistance, remote desktop, IIS Website Serving) you will need to insert your XP Pro CD and install the Remote Networking components and Anonymous priveleges to enable all of these functions. In some cases, users have checked the enable boxes in the network setup, but have failed to install the components. This too will create lags as the system has to inspect for the components on bootup. If they aren't there, you won't see an error, but you will get the lag. If you really really really want to find the error, you will see it under Administrative Tools in the System log.
Keep playing!
Steve Benoit
Stable Technologies
'The way IT should be!'