Help please!! Yet another WinXP/2000 install problem

Twister00

Senior member
Feb 20, 2001
256
0
0
I have an Abit TH7II MB (non raid)with the most recent BIOS. A PIV 1.8a and 512MB of Samsung
PC800 memory, a 60GB Maxtor HD and Radeon 32MBDDR video card. I have tried many times to install WindowsXP Pro onto this computer and it continues to hang up at about the same point each time. At about 26% of files copied. Always on 1 of 3 files. I have had all cards in and then all out except video card. I tried loading the XP disc on 2 other computers and the install went fine. I pulled the 60GB drive out of the PIV and installed XP on it in another PC without a hitch. I have tried a different HD in the PIV and hangs at the same point. I have tried different cables and drive configurations all with the same result. I also tried putting Win2000 on with similar results. However, Win98 SE loads just fine.


Any help will be greatly appreciated.
 

Doh!

Platinum Member
Jan 21, 2000
2,325
0
76
I would try different RAM but it sounds like you have only 1 stick of 512mb. If you have more than 1 stick of RAM, try one at a time & in different slots.
 

Twister00

Senior member
Feb 20, 2001
256
0
0
"I would try different RAM but it sounds like you have only 1 stick of 512mb. If you have more than 1 stick of RAM, try one at a time & in different slots."

This MB uses Rambus RAM and needs to be installed in pairs, and I only have 1 pair of 256's


"are you saying when you are Installing XP if so try a different CD Rom!"

I have used 3 different drives all with the same results and I know that the CD's are good since I was able to do the installs on 2 other PC's. Also CD drive in the new PC read and installed 98SE just fine.

Thanks for the input!
 

Dreadogg

Golden Member
Mar 1, 2001
1,780
0
76
are you getting a blue screen during installation or is it just frezzing? Because I had this happen to me twice once with bad media ( so I swiched drive went through fine) second with bad ram but I caught a blue screen that time, and I new it was a memory error by the screen code!