Trouble as usual installing XP Pro

[BoboKatt]

This is really getting to me...
here's the issue -- I have installed WIndows XP at least 80 times now between all my systems (home and work) and parents and family's systems, friend and so on. I have this one lovely thing that happens ever so often; essentially as the installation process if at the stage where it starts to copy the files needed from the CD to the hardrive, I get RAMDOM errors (usually a blue screen OR a cannot read or access such and such a file).

Here's the kicker... I have used at least 50 different STORE BOUGHT copies of XP... I have installed on anythinng from department store computers to AMD or Intel Chips.. from SATA to EIDE, from different motherboards the list goes on an on including using NTFS or FAT32 though I have to admit it's a long time since I did use FAT32. I have never been able to explain this... eventually I fix it by messing around with settings in the BIOS or using a differnt copy of XP (mine usually).. or what I have noticed is that at times I actually have to underclock the memory and CPU, then after all is installed I return it to Auto or whatever the settings work and it all works fine.

WHY WHY WHY... this does not happen on all my installations but for sure at least 50%. Is there somethign I am doing wrong? Doing the math here I am the only common factor in these installs. However one thing I would like to mention is that I always use the Windows XP CD that I boot from and then with that I partition and format. I have read that it migth have to do with that or how the MBR is done up.. but still not sure.

thanks in advance,
Robert

 

[scottws]

I know what you mean. I always turn my RAM timings down, increase the voltage to the CPU and RAM a few ticks, and turn up all my fans to full blast whenever I install Windows, because this has happened to me a few times.

It seems that the Windows installation, for one reason or another, really stresses the hardware. I've heard some suggestions that you should disconnect unnecessary devices. Like leave only one optical drive connected, and disconnect your sound card and other extraneous, and temporarily unneeded devices. Then reconnect them after Windows is set up.

 

[spyordie007]

Whenever installing any OS you shouldnt have your hardware overclocked, just too many variables.

But anyways as for the OP you should not have issues this frequently. I have seen plenty of read errors while copying off the media, most of the time this is due to an older CD-ROM drive and/or issues with it. Here are some general suggestions to keep problems like this to a minimum:
1. Ensure you have the latest BIOS for your motherboard (you'd be surprised how many issues this can solve)
2. Ensure the CD drive is connected directly to the motherboard's IDE connection. CD/DVD drives SHOULD NOT be connected to an IDE controller (either expansion or built-on to the motherboard) as this can cause all sorts of problems.
3. When it doubt swap-out the CD drive, there are a lot of old/POS CD drives out there that tend to give unreliable reads; this will (of course) cause issues installing an OS.

The biggest question I have is hardware; what about the hardware on these "80 times" is similar? Are these installs on totally differant hardware (make and manufacturer) or are they on a consistant platform?

Good Luck,
Erik

 

[scottws]

Originally posted by: spyordie007
Whenever installing any OS you shouldnt have your hardware overclocked, just too many variables.

Not sure if you're responding to me or not (thought you were since you seemed to shift response to the OP in the next sentence)... but I don't overclock my hardware. The only thing I do is run some pretty aggressive RAM timings (yet my FSB is 266Mhz and I have DDR 333).

 

[firewall]

I have never had any major problems installing WinXP except once when it gave a BSOD and on looking it up, the reason was the usage of a 40pin, 40 wire cable instead of the 40 pin, 80wire ATA cable...... or some rot like that.

 

[spyordie007]

Originally posted by: scottws

Originally posted by: spyordie007
Whenever installing any OS you shouldnt have your hardware overclocked, just too many variables.

Not sure if you're responding to me or not (thought you were since you seemed to shift response to the OP in the next sentence)... but I don't overclock my hardware. The only thing I do is run some pretty aggressive RAM timings (yet my FSB is 266Mhz and I have DDR 333).

When performing OS installs it is (generally) a good idea to run standard timings on your RAM also. During an OS install it's best to have the system setup to be as stable as possible.

-Erik

 

[scottws]

Originally posted by: spyordie007

Originally posted by: scottws

Originally posted by: spyordie007
Whenever installing any OS you shouldnt have your hardware overclocked, just too many variables.

Not sure if you're responding to me or not (thought you were since you seemed to shift response to the OP in the next sentence)... but I don't overclock my hardware. The only thing I do is run some pretty aggressive RAM timings (yet my FSB is 266Mhz and I have DDR 333).

When performing OS installs it is (generally) a good idea to run standard timings on your RAM also. During an OS install it's best to have the system setup to be as stable as possible.

-Erik

Right, as I stated, I always turn the timings down before I try to install. I turn them down to the minimum.

 

[spyordie007]

OK

 

[BoboKatt]

Wow good to know.. yeah i always fiddle with my BIOS setting prior to installing XP.. and usually will set the RAM and CPU to max.. and by that I mean max of that the items are intened to reach. For instance last night I was building a new system for my gf.. it was using some pieces I had lying around such as my XP2500 and using my Asus socket & board. I could not install windows with it running at its stock 166 bus and 166 RAM (1:1) timings even though my freaking RAM is actually a CAS 2, PC3200 512 stick of quality RAM> I tried swapping out different RAM types.. and same errors just at different times. It was NOT till I set everything to 133 that it worked. For fun I set everything to AUTO and that also worked and showed after that it was running 166 and 166. So bahhh :

 

[MrChad]

Windows setup instability is due to hardware failure 99 percent of the time. If you're running at stock settings and can't install Windows, you need to invest in some better hardware.

 

[mechBgon]

Originally posted by: BoboKatt
Wow good to know.. yeah i always fiddle with my BIOS setting prior to installing XP.. and usually will set the RAM and CPU to max.. and by that I mean max of that the items are intened to reach. For instance last night I was building a new system for my gf.. it was using some pieces I had lying around such as my XP2500 and using my Asus socket & board. I could not install windows with it running at its stock 166 bus and 166 RAM (1:1) timings even though my freaking RAM is actually a CAS 2, PC3200 512 stick of quality RAM> I tried swapping out different RAM types.. and same errors just at different times. It was NOT till I set everything to 133 that it worked. For fun I set everything to AUTO and that also worked and showed after that it was running 166 and 166. So bahhh :

What precise RAM is it, and what voltage did you select (key word: SELECT) for it to run at? Also, is your power supply fairly decent in quality?

 

[RebateMonger]

Wow BoboKatt. Remind me never to fly with you.

I've never had a problem with ANY XP install. I stick the CD in and hit "Enter" as appropriate. I typically let XP do a Quick NTFS format, unless I'm concerned about the hard drive condition. I've never had to adjust a BIOS to do an install. I never overclock anything nowadays. I use Factory default settings. Most of the motherboards I work with nowadays are Gateway, Dell, HP/Compaq, Sony, Toshiba, Abit, or Intel.