Setup Freezes in XP Pro 1

[Chrispr]

I just recently build a fairly simple computer. I bought the elite group package with an AMD 2000+ processor and all the connections such as LAN build into the motherboard. I bought a case for it, 256 Mb DDR 266 Ram, and A WD 40 Gb hard drive.
Pretty simple setup. I put everything together and I go to install windows XP Pro and it freezes during the setup at '32 minutes remaining' when it is installing the network. The copy of windows I have is in perfect working condition, so it can't be the CD. Is there something I have installed wrong on the MB that would cause setup to freeze during this stage?

 

[mattjurado]

Could be the motherboard itself. Odd that it is fine until it gets to that point though... Try disabling the onboard network card, and see if it installs ok. If it does, I suspect you should return that board.

If it doesn't you might try swapping out the RAM before you return that board.

Matt J.

Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.

 

[bcastner]

http://support.microsoft.com/default.aspx?scid=kb;en-us;815319

 

[Chrispr]

Thanks for your response guys. The copy of XP Pro I have is actually an older on I bought, so it doesn't have SP1 integrated into it. I will try to swap the memory and disable the network card to see if that does anything. For some reason I think it might have something to do with the network card just for the fact that it is freezing during that stage. Would that fix that microsoft suggests for SP1 still be applicable to me?
Thanks for the help guys.

 

[Chrispr]

Very interesting. I disabled the LAN connection in the BIOS and setup restarted itself and magically it completed. So when windows rebooted, I enabled the LAN device again and then proceded into windows to install the drivers for the MB. The first time it was going to install the drivers for the LAN connection, it froze half way through so I had to end the program and restart the computer. I eventually did get it so the CD with the drivers scanned and found that there had been no drivers for each onboard component that had not been installed. Went to device manager, everything was working except for the network adapter, it had the lovely yellow question mark beside it. I brought up the properties and it said this device cannot start (code 10). Am I right to assume the device is bad and therefore the MB is bad too? I bought the thing new, or at least I thought I did.

 

[bcastner]

. for any not needed network adapter, use Device Manager and disable;
. For any needed adapter, consider if possible a static IP assignment;
. Consider for a need adapter, using the XP Alternate Configuration feature:

http://support.microsoft.com/default.aspx?scid=kb;en-us;283676&Product=winxp

 

[peanutbutteryesjelly]

I have an older version without SP1 as well. I had the same problem during upgrade from Win98SR2, with the exception of the Code 10 on the NIC card in Device Manager. I have a 3COM 3c509. (By the way, I'm connecting my cable modem to a NetGear MR814 wireless router with 4-port switch. My WinXP tablet connects just fine wirelessly, and my Win2K server connects fine in the switch.) I tried an Intel PRO 100+ card and got the Code 10. I then tried a Macronix card and did NOT get Code 10. So I'm back to the 3COM card, and I've tried several things that bcastner has suggested in other posts, including the WinsockFix. That Network Diagnostics is good stuff. I've tried a static IP but still no go. I'm thinking of re-installing after reading this article:

http://www.experts-exchange.com/Operating_Systems/WinXP/Q_20788636.html

Not sure what else to try.

 

[bcastner]

Wow.
You might consider:

http://www.microsoft.com/technet/prodtechnol/winxppro/sp2preview.mspx

Service Pack 1 should have sorted this issue, but Service Pack 2 is all inclusive. It is all you need.

 

[lamar225]

Make sure the bios recognize the drive Wd supplies a bios cover up that if you dont do it correct the bios wont recognize the drive correctly and wala your problem occurs, it happen to me and it took me 4 hrs to figure out