I have just built a pc using an Intel mobo and cpu, and am running XP
Pro. XP and all devices are using the most recent patches / fixes.
The pc is running fantastically in all other respects, with no other
issues nor performance problems.

My old PC used an ISP-supplied network card, but my mobo has built-in
LAN, which I am using.

If I leave the Local Area Connection enabled when I shut down, booting
show the XP splash / starting screen, but I never get the user login /
select which user to login screen. Shortly after the splash screen
fades, the drive access light goes out, and the monitor goes into power
save mode.

Booting to safe mode *always* works, with and without network
connection. Network connection works in safe mode.

Boot to last-known good settings does not work.

---------------------------------------------------------
If I *disable* the LAN connection before shutdown, the boot always
works. Connecting the cable modem using USB also works.
---------------------------------------------------------
I have *not* set my ISP's IP address in the IP Properties
configuration, instead allowing "Obtain an IP address automatically.
(This is a suggested work-around.)

I have found very few search results for this problem, and wanted to
document it for others having the same problem.

Setting a static IP does not cure the stall problem, however it does
establish a 1GB/s link to the cable modem.

I *can* use the static IP, if I enable it after XP fully boots.

Powering off the mobo, and the cable modem also help to achieve a clean
boot.

Setting a static IP does not cure the stall problem, however it does
establish a 1GB/s link to the cable modem.

I *can* use the static IP, if I enable it after XP fully boots.

Powering off the mobo, and the cable modem also help to achieve a clean
boot.

Having the cable modem turned off during boot is the trick.

Having the cable modem turned off during boot is the trick.

skid00skid00******.com wrote:
> Having the cable modem turned off during boot is the trick.

Actually, it wasn't.

The problem lies in the motherboard, which has 'advanced' :-/
power saving features. These must be turned off. They are intended
for use in media pc's, where the pc stays powered up, in a power-saving
mode.